Perplexity Outage History

Perplexity is up right now

Pingoru has recorded 30 incidents for Perplexity: 28 in the last 12 months and 13 in the last 90 days.

Source: status.perplexity.com

30incidents recorded
28last 12 months
13last 90 days
87 minutestypical duration
Incidents per month
048AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Perplexity in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202614 of 744 (1%)
June 202657 of 720 (1%)
July 202642 of 744 (0%)
August 202686 of 744 (1%)
September 202653 of 720 (0%)
October 202611 of 744 (0%)
November 202600 of 112 (0%)

Incidents, newest first

Minor October 9, 2026 Elevated API errors and timeouts 36m Website, App, Computer, API

Started Oct 09, 2026, 10:38 PM UTC· resolved Oct 09, 2026, 11:15 PM UTC

  1. investigating Oct 09, 2026, 10:38 PM UTC

    Users may experience errors or timeouts when making API requests. We are investigating elevated API errors and timeouts.

  2. monitoring Oct 09, 2026, 11:01 PM UTC

    The issue causing elevated API errors and timeouts has been mitigated.

  3. monitoring Oct 09, 2026, 11:10 PM UTC

    Correction to our previous updates: we do not believe the API was affected by this incident and it remains operational.

  4. resolved Oct 09, 2026, 11:15 PM UTC

    The issue affecting the Website, App, and Computer has been resolved. All services are operational. The API remained operational throughout this incident.

Read the full incident report →

Major September 5, 2026 We have identified few connectors that are impacting users. 2h 19m Computer

Started Sep 05, 2026, 04:50 AM UTC· resolved Sep 05, 2026, 07:09 AM UTC

  1. identified Sep 05, 2026, 04:50 AM UTC

    We are continuing to work on a fix for this incident.

  2. monitoring Sep 05, 2026, 06:52 AM UTC

    We have mitigated the issue and are monitoring impacted connectors for recovery.

  3. resolved Sep 05, 2026, 07:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 5, 2026 We have identified few connectors that are impacting users. 2h 19m Computer

Started Sep 05, 2026, 04:50 AM UTC· resolved Sep 05, 2026, 07:09 AM UTC

  1. investigating Sep 05, 2026, 05:48 AM UTC

    We are currently investigating this incident.

  2. monitoring Sep 05, 2026, 06:52 AM UTC

    We have mitigated the issue and are monitoring impacted connectors for recovery.

  3. resolved Sep 05, 2026, 07:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 3, 2026 Issue with usage based billing –

Started Sep 03, 2026, 09:10 PM UTC· resolved Sep 03, 2026, 09:10 PM UTC

  1. resolved Sep 03, 2026, 09:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 3, 2026 Issue with usage based billing 39m Computer

Started Sep 03, 2026, 08:30 PM UTC· resolved Sep 03, 2026, 09:10 PM UTC

  1. investigating Sep 03, 2026, 08:30 PM UTC

    Computer is degraded. It is reporting insufficient credits wrongfully

  2. monitoring Sep 03, 2026, 08:44 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Sep 03, 2026, 09:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 3, 2026 Issue with usage based billing 39m Computer

Started Sep 03, 2026, 08:30 PM UTC· resolved Sep 03, 2026, 09:10 PM UTC

  1. investigating Sep 03, 2026, 08:30 PM UTC

    Computer is degraded. It is reporting insufficient credits wrongfully

  2. monitoring Sep 03, 2026, 08:44 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Sep 03, 2026, 09:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 31, 2026 Computer Tasks Degraded 33m Computer

Started Aug 31, 2026, 11:33 PM UTC· resolved Sep 01, 2026, 12:06 AM UTC

  1. investigating Aug 31, 2026, 11:33 PM UTC

    We have identified some degradation in Computer tasks and investigating the root cause.

  2. identified Aug 31, 2026, 11:42 PM UTC

    We have identified the root cause and rolled back.

  3. monitoring Aug 31, 2026, 11:53 PM UTC

    Rollback completed and we are monitoring the health of Computer tasks.

  4. resolved Sep 01, 2026, 12:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026 Computer Sandbox Errors 57m Computer

Started Aug 14, 2026, 10:46 AM UTC· resolved Aug 14, 2026, 11:43 AM UTC

  1. investigating Aug 14, 2026, 10:46 AM UTC

    We are currently investigating this incident.

  2. resolved Aug 14, 2026, 11:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 Investigating API issue –

Started Aug 13, 2026, 01:49 AM UTC· resolved Aug 13, 2026, 01:49 AM UTC

  1. resolved Aug 13, 2026, 01:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 13, 2026 Investigating API issue 1h 4m App

Started Aug 13, 2026, 12:45 AM UTC· resolved Aug 13, 2026, 01:49 AM UTC

  1. investigating Aug 13, 2026, 12:45 AM UTC

    We are currently investigating this incident.

  2. monitoring Aug 13, 2026, 01:43 AM UTC

    We identified the problematic deploy and rolled back the service.

  3. resolved Aug 13, 2026, 01:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 Investigating API issue –

Started Aug 13, 2026, 12:45 AM UTC· resolved Aug 13, 2026, 12:45 AM UTC

  1. resolved Aug 13, 2026, 12:45 AM UTC

    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, 00:45:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 13, 01:43:04 GMT+0 - Monitoring - We identified the problematic deploy and rolled back the service.

Read the full incident report →

Major August 13, 2026 Investigating API issue 1h 4m API

Started Aug 13, 2026, 12:45 AM UTC· resolved Aug 13, 2026, 01:49 AM UTC

  1. investigating Aug 13, 2026, 01:22 AM UTC

    We are currently investigating this incident.

  2. monitoring Aug 13, 2026, 01:43 AM UTC

    We identified the problematic deploy and rolled back the service.

  3. resolved Aug 13, 2026, 01:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2026 test incident 5m

Started Aug 11, 2026, 10:35 PM UTC· resolved Aug 11, 2026, 10:40 PM UTC

  1. investigating Aug 11, 2026, 10:35 PM UTC

    hello

  2. resolved Aug 11, 2026, 10:40 PM UTC

    all our tests are back to normal

Read the full incident report →

Minor August 6, 2026 Computer Sandbox Issue 3h 33m Computer

Started Aug 06, 2026, 02:30 PM UTC· resolved Aug 06, 2026, 06:03 PM UTC

  1. investigating Aug 06, 2026, 02:30 PM UTC

    We are currently investigating this incident.

  2. identified Aug 06, 2026, 03:15 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Aug 06, 2026, 04:40 PM UTC

    We have mitigated the issue and are repairing impacted instances.

  4. resolved Aug 06, 2026, 06:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 23, 2026 Computer sandbox issues 25m

Started Jul 23, 2026, 05:48 PM UTC· resolved Jul 23, 2026, 06:14 PM UTC

  1. investigating Jul 23, 2026, 05:48 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 23, 2026, 05:50 PM UTC

    We have identified the problem and have rolled back the impacted services.

  3. resolved Jul 23, 2026, 06:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026 Computer sandbox issues 25m Computer

Started Jul 23, 2026, 05:48 PM UTC· resolved Jul 23, 2026, 06:14 PM UTC

  1. investigating Jul 23, 2026, 05:48 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 23, 2026, 05:50 PM UTC

    We have identified the problem and have rolled back the impacted services.

  3. resolved Jul 23, 2026, 06:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2026 Computer sandbox issues 25m

Started Jul 23, 2026, 05:48 PM UTC· resolved Jul 23, 2026, 06:14 PM UTC

  1. resolved Jul 23, 2026, 05:48 PM UTC

    Type: Incident Duration: 26 minutes Affected Components: Computer Jul 23, 17:48:28 GMT+0 - Investigating - We are currently investigating this incident. Jul 23, 17:50:11 GMT+0 - Monitoring - We have identified the problem and have rolled back the impacted services. Jul 23, 18:14:10 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor July 2, 2026 Computer Sandbox Issue 1h 40m Computer

Started Jul 02, 2026, 06:30 PM UTC· resolved Jul 02, 2026, 08:10 PM UTC

  1. investigating Jul 02, 2026, 06:30 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 02, 2026, 08:01 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 02, 2026, 08:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026 Computer Sandbox Issue –

Started Jun 30, 2026, 11:46 PM UTC· resolved Jun 30, 2026, 11:46 PM UTC

  1. resolved Jun 30, 2026, 11:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 30, 2026 Computer outage 11m Website, Computer

Started Jun 30, 2026, 10:49 PM UTC· resolved Jun 30, 2026, 11:00 PM UTC

  1. investigating Jun 30, 2026, 10:49 PM UTC

    We’re experiencing an internal infrastructure outage that’s degrading the Computer experience. Our team is actively investigating and working on a resolution.

Read the full incident report →

Minor June 30, 2026 Computer Sandbox Issue –

Started Jun 30, 2026, 09:39 PM UTC· resolved Jun 30, 2026, 09:39 PM UTC

  1. resolved Jun 30, 2026, 09:39 PM UTC

    Type: Incident Duration: 2 hours and 7 minutes Affected Components: Computer Jun 30, 21:39:00 GMT+0 - Investigating - The team has implemented a fix and are continuing to monitor recovery. Jun 30, 22:52:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 30, 23:46:04 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major June 30, 2026 Computer Sandbox Issue 2h 7m Computer

Started Jun 30, 2026, 09:39 PM UTC· resolved Jun 30, 2026, 11:46 PM UTC

  1. investigating Jun 30, 2026, 09:39 PM UTC

    The team has implemented a fix and are continuing to monitor recovery.

  2. monitoring Jun 30, 2026, 10:52 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 30, 2026, 11:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026 Connector connectivity issues 4h 30m Website

Started Jun 04, 2026, 09:10 PM UTC· resolved Jun 05, 2026, 01:40 AM UTC

  1. investigating Jun 04, 2026, 09:10 PM UTC

    We have identified connector issues that are currently impacting users.

  2. monitoring Jun 05, 2026, 01:00 AM UTC

    Connectors are recovering and getting back to normal.

  3. resolved Jun 05, 2026, 01:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026 Perplexity Website and API incident 3h 59m Website, API

Started May 08, 2026, 12:20 AM UTC· resolved May 08, 2026, 04:19 AM UTC

  1. investigating May 08, 2026, 12:20 AM UTC

    A small percentage of our users may experience instability while using Perplexity Website and products. We're investigating the incident.

  2. identified May 08, 2026, 12:30 AM UTC

    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.

  3. resolved May 08, 2026, 01:59 AM UTC

    This incident has been resolved.

  4. identified May 08, 2026, 02:10 AM UTC

    We are continuing to work on a fix for this incident.

  5. resolved May 08, 2026, 04:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 16, 2026 Sonar API incident –

Started Feb 16, 2026, 09:35 PM UTC· resolved Feb 16, 2026, 09:35 PM UTC

  1. resolved Feb 16, 2026, 09:35 PM UTC

    Type: Incident Duration: 52 minutes Affected Components: API Feb 16, 21:35:20 GMT+0 - Investigating - We are currently investigating this incident affecting Sonar API. Feb 16, 21:48:00 GMT+0 - Identified - We have identified the root cause and working on the mitigation. Feb 16, 22:14:44 GMT+0 - Monitoring - Sonar API is recovering. We'll continue monitoring the service and its health. Feb 16, 22:27:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →