<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Perplexity Status - Incident history</title>
    <link>https://perplexity.instatus.com</link>
    <description>Perplexity</description>
    <pubDate>Thu, 10 Sep 2026 21:00:00 +0000</pubDate>
    
<item>
  <title>Status page migration to incident.io</title>
  <description>
    Type: Maintenance
    

    Affected Components: Computer, Website, API
    Jan 1, 00:00:00 GMT+0 - Identified - On Thursday, September 10 around 21:00 UTC (2:00 PM Pacific), we will migrate our status page from Instatus to incident.io as part of consolidating our incident response tooling. The switch is a DNS change, so it may take some time to complete for everyone.

## What is and isn&#039;t changing

* The status page URL stays the same: &lt;https://status.perplexity.com&gt;.
* Historical incidents have been migrated, so past incident history remains available on the new page.
* Email subscribers will be migrated automatically. No action needed.
* Slack subscriptions cannot be transferred, but you can pre-subscribe today at &lt;https://statuspage.incident.io/perplexity&gt;. Subscriptions made there carry over when &lt;https://status.perplexity.com&gt; switches on Thursday.
* Google Chat, Microsoft Teams, webhook, and SMS subscriptions will no longer be available. Please switch to email, Slack, or RSS.

## What you need to do

* Email: nothing.
* Everyone else: pre-subscribe via email, Slack, or RSS at &lt;https://statuspage.incident.io/perplexity&gt; today, or at &lt;https://status.perplexity.com&gt; after the migration on Thursday (the page footer will show &quot;Powered by incident.io&quot; once the switch is complete).

Questions? Contact support@perplexity.ai. Sep 10, 23:00:00 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  On Thursday, September 10 around 21:00 UTC (2:00 PM Pacific), we will migrate our status page from Instatus to incident.io as part of consolidating our incident response tooling. The switch is a DNS change, so it may take some time to complete for everyone.

## What is and isn&#039;t changing

* The status page URL stays the same: &lt;https://status.perplexity.com&gt;.
* Historical incidents have been migrated, so past incident history remains available on the new page.
* Email subscribers will be migrated automatically. No action needed.
* Slack subscriptions cannot be transferred, but you can pre-subscribe today at &lt;https://statuspage.incident.io/perplexity&gt;. Subscriptions made there carry over when &lt;https://status.perplexity.com&gt; switches on Thursday.
* Google Chat, Microsoft Teams, webhook, and SMS subscriptions will no longer be available. Please switch to email, Slack, or RSS.

## What you need to do

* Email: nothing.
* Everyone else: pre-subscribe via email, Slack, or RSS at &lt;https://statuspage.incident.io/perplexity&gt; today, or at &lt;https://status.perplexity.com&gt; after the migration on Thursday (the page footer will show &quot;Powered by incident.io&quot; once the switch is complete).

Questions? Contact support@perplexity.ai..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 10 Sep 2026 21:00:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/maintenance/cmtrutbr301gv1mpq81xpt464</link>
  <guid>https://perplexity.instatus.com/maintenance/cmtrutbr301gv1mpq81xpt464</guid>
</item>

<item>
  <title>We have identified few connectors that are impacting users.</title>
  <description>
    Type: Incident
    Duration: 2 hours and 19 minutes

    Affected Components: Computer
    Sep 5, 07:09:00 GMT+0 - Resolved - This incident has been resolved. Sep 5, 06:52:24 GMT+0 - Monitoring - We have mitigated the issue and are monitoring impacted connectors for recovery.  Sep 5, 04:50:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>07:09:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>06:52:24</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have mitigated the issue and are monitoring impacted connectors for recovery. .</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>04:50:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 5 Sep 2026 04:50:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmtnypntq056g13qw1u9uixby</link>
  <guid>https://perplexity.instatus.com/incident/cmtnypntq056g13qw1u9uixby</guid>
</item>

<item>
  <title>Issue with usage based billing</title>
  <description>
    Type: Incident
    Duration: 40 minutes

    Affected Components: Computer
    Sep 3, 21:10:35 GMT+0 - Resolved - This incident has been resolved. Sep 3, 20:44:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 3, 20:30:59 GMT+0 - Investigating - Computer is degraded. It is reporting insufficient credits wrongfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>21:10:35</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>20:44:45</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>20:30:59</var> GMT+0</small><br><strong>Investigating</strong> -
  Computer is degraded. It is reporting insufficient credits wrongfully.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 3 Sep 2026 20:30:59 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmtlzck6l02ny0wo50uicmt68</link>
  <guid>https://perplexity.instatus.com/incident/cmtlzck6l02ny0wo50uicmt68</guid>
</item>

<item>
  <title>Computer Tasks Degraded</title>
  <description>
    Type: Incident
    Duration: 33 minutes

    Affected Components: Computer
    Sep 1, 00:06:10 GMT+0 - Resolved - This incident has been resolved. Aug 31, 23:53:00 GMT+0 - Monitoring - Rollback completed and we are monitoring the health of Computer tasks. Aug 31, 23:42:00 GMT+0 - Identified - We have identified the root cause and are rolling back. Aug 31, 23:33:00 GMT+0 - Investigating - We are investigating reports of degraded Computer tasks. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>00:06:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>23:53:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Rollback completed and we are monitoring the health of Computer tasks..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>23:42:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the root cause and are rolling back..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>23:33:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of degraded Computer tasks..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 31 Aug 2026 23:33:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmthwd4oh0duj1as27ubnu8cj</link>
  <guid>https://perplexity.instatus.com/incident/cmthwd4oh0duj1as27ubnu8cj</guid>
</item>

<item>
  <title>Computer Sandbox Errors</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    Affected Components: Computer
    Aug 14, 11:43:00 GMT+0 - Resolved - This incident has been resolved. Aug 14, 10:46:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>11:43:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>10:46:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 14 Aug 2026 10:46:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmssvxu6f07yv0rqx45soqdhl</link>
  <guid>https://perplexity.instatus.com/incident/cmssvxu6f07yv0rqx45soqdhl</guid>
</item>

<item>
  <title>Investigating API issue</title>
  <description>
    Type: Incident
    Duration: 1 hour and 4 minutes

    Affected Components: API
    Aug 13, 01:49:15 GMT+0 - Resolved - This incident has been resolved. Aug 13, 01:43:04 GMT+0 - Monitoring - We identified the problematic deploy and rolled back the service.  Aug 13, 00:45:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>01:49:15</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>01:43:04</var> GMT+0</small><br><strong>Monitoring</strong> -
  We identified the problematic deploy and rolled back the service. .</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>00:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 00:45:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmsqu34nd04pn0rnwssz2zojt</link>
  <guid>https://perplexity.instatus.com/incident/cmsqu34nd04pn0rnwssz2zojt</guid>
</item>

<item>
  <title>Computer Sandbox Issue</title>
  <description>
    Type: Incident
    Duration: 3 hours and 33 minutes

    Affected Components: Computer
    Aug 6, 18:03:00 GMT+0 - Resolved - This incident has been resolved. Aug 6, 16:40:00 GMT+0 - Monitoring - We have mitigated the issue and are repairing impacted instances. Aug 6, 15:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 6, 14:30:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>18:03:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>16:40:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have mitigated the issue and are repairing impacted instances..</p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 6 Aug 2026 14:30:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmshq5jpp01ns1bpbx7j5ur1g</link>
  <guid>https://perplexity.instatus.com/incident/cmshq5jpp01ns1bpbx7j5ur1g</guid>
</item>

<item>
  <title>Computer sandbox issues</title>
  <description>
    Type: Incident
    Duration: 26 minutes

    Affected Components: Computer
    Jul 23, 18:14:10 GMT+0 - Resolved - This incident has been resolved. Jul 23, 17:50:11 GMT+0 - Monitoring - We have identified the problem and have rolled back the impacted services.  Jul 23, 17:48:28 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>18:14:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>17:50:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have identified the problem and have rolled back the impacted services. .</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>17:48:28</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 23 Jul 2026 17:48:28 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmrxt1rlu000f0zlcv4dzmdlr</link>
  <guid>https://perplexity.instatus.com/incident/cmrxt1rlu000f0zlcv4dzmdlr</guid>
</item>

<item>
  <title>Computer Sandbox Issue</title>
  <description>
    Type: Incident
    Duration: 1 hour and 41 minutes

    Affected Components: Computer
    Jul 2, 20:10:50 GMT+0 - Resolved - This incident has been resolved. Jul 2, 20:01:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 2, 18:30:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>20:10:50</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>20:01:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 2 Jul 2026 18:30:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmr3uqd3801w80kqfk6xdj08m</link>
  <guid>https://perplexity.instatus.com/incident/cmr3uqd3801w80kqfk6xdj08m</guid>
</item>

<item>
  <title>Computer Sandbox Issue</title>
  <description>
    Type: Incident
    Duration: 2 hours and 7 minutes

    Affected Components: Computer
    Jun 30, 23:46:04 GMT+0 - Resolved - This incident has been resolved. Jun 30, 22:52:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 30, 21:39:00 GMT+0 - Investigating - The team has implemented a fix and are continuing to monitor recovery. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>23:46:04</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>22:52:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>21:39:00</var> GMT+0</small><br><strong>Investigating</strong> -
  The team has implemented a fix and are continuing to monitor recovery..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jun 2026 21:39:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmr18mqib01bn0zqm49b8h3pv</link>
  <guid>https://perplexity.instatus.com/incident/cmr18mqib01bn0zqm49b8h3pv</guid>
</item>

<item>
  <title>Connector connectivity issues</title>
  <description>
    Type: Incident
    Duration: 4 hours and 31 minutes

    Affected Components: Website
    Jun 5, 01:40:38 GMT+0 - Resolved - This incident has been resolved. Jun 5, 01:00:00 GMT+0 - Monitoring - Connectors are recovering and getting back to normal for all users. Jun 4, 21:10:00 GMT+0 - Investigating - We have identified connector issues that are currently impacting users. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>01:40:38</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Connectors are recovering and getting back to normal for all users..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>21:10:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have identified connector issues that are currently impacting users..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 4 Jun 2026 21:10:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmq08wkuw02waqmn6yt1kdgej</link>
  <guid>https://perplexity.instatus.com/incident/cmq08wkuw02waqmn6yt1kdgej</guid>
</item>

<item>
  <title>Perplexity Website and API incident</title>
  <description>
    Type: Incident
    Duration: 3 hours and 59 minutes

    Affected Components: Website, API
    May 8, 04:19:16 GMT+0 - Resolved - This incident has been resolved. May 8, 02:10:32 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 8, 01:59:10 GMT+0 - Resolved - This incident has been resolved. May 8, 00:30:28 GMT+0 - Identified - We’ve identified the root cause in the underlying AWS infrastructure. We’re actively working with the AWS team to mitigate the issue and fully restore the service. May 8, 00:20:12 GMT+0 - Investigating - A small percentage of our users may experience instability while using Perplexity Website and products. We&#039;re investigating the incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>04:19:16</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>02:10:32</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>01:59:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>00:30:28</var> GMT+0</small><br><strong>Identified</strong> -
  We’ve identified the root cause in the underlying AWS infrastructure. We’re actively working with the AWS team to mitigate the issue and fully restore the service..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>00:20:12</var> GMT+0</small><br><strong>Investigating</strong> -
  A small percentage of our users may experience instability while using Perplexity Website and products. We&#039;re investigating the incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 8 May 2026 00:20:12 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmow64ygu00nssas2uxewm3ur</link>
  <guid>https://perplexity.instatus.com/incident/cmow64ygu00nssas2uxewm3ur</guid>
</item>

<item>
  <title>Sonar API incident</title>
  <description>
    Type: Incident
    Duration: 52 minutes

    Affected Components: API
    Feb 16, 22:27:00 GMT+0 - Resolved - This incident has been resolved. Feb 16, 22:14:44 GMT+0 - Monitoring - Sonar API is recovering. We&#039;ll continue monitoring the service and its health. Feb 16, 21:48:00 GMT+0 - Identified - We have identified the root cause and working on the mitigation. Feb 16, 21:35:20 GMT+0 - Investigating - We are currently investigating this incident affecting Sonar API. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>22:27:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>22:14:44</var> GMT+0</small><br><strong>Monitoring</strong> -
  Sonar API is recovering. We&#039;ll continue monitoring the service and its health..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>21:48:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the root cause and working on the mitigation..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>21:35:20</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident affecting Sonar API..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 16 Feb 2026 21:35:20 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmlpp0s6w0xw8kiq075jrclzi</link>
  <guid>https://perplexity.instatus.com/incident/cmlpp0s6w0xw8kiq075jrclzi</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 18 minutes

    Affected Components: Website
    Feb 5, 22:36:11 GMT+0 - Resolved - This incident has been resolved. Feb 5, 22:18:11 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>22:36:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>22:18:11</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 5 Feb 2026 22:18:11 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmla0pich002lmbagmgd3dea9</link>
  <guid>https://perplexity.instatus.com/incident/cmla0pich002lmbagmgd3dea9</guid>
</item>

<item>
  <title>Service outage</title>
  <description>
    Type: Incident
    Duration: 34 minutes

    Affected Components: Website, API
    Dec 5, 09:41:11 GMT+0 - Resolved - This incident has been resolved. Dec 5, 09:23:16 GMT+0 - Monitoring - The service is recovering and we are monitoring; the outage was caused by an underlying service provider issue. Dec 5, 09:06:41 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:41:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:23:16</var> GMT+0</small><br><strong>Monitoring</strong> -
  The service is recovering and we are monitoring; the outage was caused by an underlying service provider issue..</p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:06:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 5 Dec 2025 09:06:41 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmisn4u30004czxetcottiflf</link>
  <guid>https://perplexity.instatus.com/incident/cmisn4u30004czxetcottiflf</guid>
</item>

<item>
  <title>Investigating connectivity issues </title>
  <description>
    Type: Incident
    Duration: 2 hours

    Affected Components: Website, API
    Nov 18, 14:59:39 GMT+0 - Resolved - This incident has been resolved. Nov 18, 13:46:17 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 13:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:59:39</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:46:17</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 13:00:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmi4nr7dx004s10lslamg5662</link>
  <guid>https://perplexity.instatus.com/incident/cmi4nr7dx004s10lslamg5662</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 5 hours and 17 minutes

    Affected Components: Website
    Oct 20, 21:10:23 GMT+0 - Resolved - This incident has been resolved. Oct 20, 17:34:02 GMT+0 - Monitoring - Error rates have returned to normal. We will continue to monitor Oct 20, 16:53:02 GMT+0 - Identified - This has been determined to be related to the earlier AWS service degradation. &lt;https://health.aws.amazon.com/health/status&gt; 

We are continuing to work on a fix for this incident.  Oct 20, 16:29:14 GMT+0 - Investigating - We are still investigating this incident Oct 20, 15:53:36 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>21:10:23</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:34:02</var> GMT+0</small><br><strong>Monitoring</strong> -
  Error rates have returned to normal. We will continue to monitor.</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:53:02</var> GMT+0</small><br><strong>Identified</strong> -
  This has been determined to be related to the earlier AWS service degradation. &lt;https://health.aws.amazon.com/health/status&gt; 

We are continuing to work on a fix for this incident. .</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:29:14</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still investigating this incident.</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>15:53:36</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 15:53:36 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmgzbeye903dvap0ldskxl2pg</link>
  <guid>https://perplexity.instatus.com/incident/cmgzbeye903dvap0ldskxl2pg</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 3 hours and 2 minutes

    Affected Components: Website, API
    Oct 20, 09:55:49 GMT+0 - Resolved - This incident has now been resolved. Oct 20, 09:40:00 GMT+0 - Monitoring - Most services are operational now, we are continuing to monitor Oct 20, 09:24:00 GMT+0 - Identified - We can confirm this is related to an AWS service disruption. &lt;https://health.aws.amazon.com/health/status&gt;   
We are actively working with AWS on a resolution. We will continue to update this page. Oct 20, 07:32:36 GMT+0 - Identified - We are experiencing an outage related to an AWS operational issue. [https://health.aws.amazon.com/health/status.](https://health.aws.amazon.com/health/status)   
We are continuing to work on a fix for this incident. Oct 20, 06:54:10 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:55:49</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has now been resolved..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:40:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  Most services are operational now, we are continuing to monitor.</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:24:00</var> GMT+0</small><br><strong>Identified</strong> -
  We can confirm this is related to an AWS service disruption. &lt;https://health.aws.amazon.com/health/status&gt;   
We are actively working with AWS on a resolution. We will continue to update this page..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>07:32:36</var> GMT+0</small><br><strong>Identified</strong> -
  We are experiencing an outage related to an AWS operational issue. [https://health.aws.amazon.com/health/status.](https://health.aws.amazon.com/health/status)   
We are continuing to work on a fix for this incident..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>06:54:10</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 06:54:10 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmgys58bg00phtnwejry53dud</link>
  <guid>https://perplexity.instatus.com/incident/cmgys58bg00phtnwejry53dud</guid>
</item>

<item>
  <title>API outage</title>
  <description>
    Type: Incident
    

    Affected Components: API
    Sep 5, 17:25:07 GMT+0 - Resolved - This incident has been resolved. Sep 5, 16:30:00 GMT+0 - Resolved - We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>17:25:07</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We experienced an outage for the API that lasted roughly 20 minutes. This incident has been resolved..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 5 Sep 2025 16:30:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmf74zs6j001y3rwly4wymq3c</link>
  <guid>https://perplexity.instatus.com/incident/cmf74zs6j001y3rwly4wymq3c</guid>
</item>

<item>
  <title>We are investigating slowness and elevated error rates on the Perplexity website</title>
  <description>
    Type: Incident
    Duration: 3 hours and 41 minutes

    Affected Components: Website
    Jun 10, 15:31:29 GMT+0 - Resolved - This incident has been resolved. Jun 10, 14:36:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 10, 12:37:48 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 10, 11:50:05 GMT+0 - Investigating - We are investigating slowness and elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>15:31:29</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>14:36:10</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>12:37:48</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>11:50:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating slowness and elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 10 Jun 2025 11:50:05 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmbqglc8x00019b4dw876rm5a</link>
  <guid>https://perplexity.instatus.com/incident/cmbqglc8x00019b4dw876rm5a</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 25 minutes

    Affected Components: Website
    May 16, 07:39:10 GMT+0 - Resolved - This incident has been resolved. May 16, 07:14:10 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>07:39:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>07:14:10</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 16 May 2025 07:14:10 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmaqgq72u006dd3o1u64veogg</link>
  <guid>https://perplexity.instatus.com/incident/cmaqgq72u006dd3o1u64veogg</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    Affected Components: Website
    May 15, 14:58:11 GMT+0 - Resolved - This incident has been resolved. May 15, 14:44:12 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>14:58:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>14:44:12</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 15 May 2025 14:44:12 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmaphd3q9008snbmxvb9pzxim</link>
  <guid>https://perplexity.instatus.com/incident/cmaphd3q9008snbmxvb9pzxim</guid>
</item>

<item>
  <title>Investigating increased API latency</title>
  <description>
    Type: Incident
    Duration: 1 hour and 49 minutes

    Affected Components: API
    May 7, 05:31:43 GMT+0 - Resolved - This incident has been resolved. May 7, 04:31:43 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 7, 03:43:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>05:31:43</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>04:31:43</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>03:43:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 7 May 2025 03:43:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cmadfqyji001u66p9c6u8pgma</link>
  <guid>https://perplexity.instatus.com/incident/cmadfqyji001u66p9c6u8pgma</guid>
</item>

<item>
  <title>P99 First Token Latency of Sonar Pro is elevated</title>
  <description>
    Type: Incident
    Duration: 20 hours and 20 minutes

    Affected Components: API
    Apr 29, 03:28:00 GMT+0 - Resolved - This incident has been resolved. Apr 28, 07:08:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>03:28:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>07:08:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 28 Apr 2025 07:08:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cma4irllo003ufvm5no73v97y</link>
  <guid>https://perplexity.instatus.com/incident/cma4irllo003ufvm5no73v97y</guid>
</item>

<item>
  <title>An issue affecting the stability of the website has been detected</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: Website
    Apr 2, 00:03:10 GMT+0 - Resolved - This incident has been resolved. Apr 2, 00:01:11 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>00:03:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>00:01:11</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates on the Perplexity website..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 2 Apr 2025 00:01:11 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cm8z5vwak001lr1lyzv0df09e</link>
  <guid>https://perplexity.instatus.com/incident/cm8z5vwak001lr1lyzv0df09e</guid>
</item>

<item>
  <title>Website outage</title>
  <description>
    Type: Incident
    Duration: 4 hours and 38 minutes

    Affected Components: Website
    Mar 28, 20:41:00 GMT+0 - Resolved - This incident has been resolved. Mar 28, 19:31:18 GMT+0 - Monitoring - We are continuing to work on a fix for this incident and implementing fixes for various geos and user groups. Various services will be degraded or inaccessible.  Mar 28, 16:03:00 GMT+0 - Identified - Website cannot be accessed at the moment for various geographies. We are investigating and will notify once fully operational.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>20:41:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>19:31:18</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to work on a fix for this incident and implementing fixes for various geos and user groups. Various services will be degraded or inaccessible. .</p>
<p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>16:03:00</var> GMT+0</small><br><strong>Identified</strong> -
  Website cannot be accessed at the moment for various geographies. We are investigating and will notify once fully operational. .</p>
]]>
  </content:encoded>
  <pubDate>Fri, 28 Mar 2025 16:03:00 +0000</pubDate>
  <link>https://perplexity.instatus.com/incident/cm8t22p39002dg69u0yxplqiq</link>
  <guid>https://perplexity.instatus.com/incident/cm8t22p39002dg69u0yxplqiq</guid>
</item>

  </channel>
  </rss>