Perplexity Outage History

Perplexity is up right now

Perplexity had 17 outages in the last 2 years totaling 4h 36m of downtime — averaging 0.7 incidents per month.

There were 17 Perplexity outages since September 16, 2024 totaling 4h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.perplexity.com

Major July 23, 2026

Computer sandbox issues

Detected by Pingoru
Jul 23, 2026, 05:48 PM UTC
Resolved
Jul 23, 2026, 06:14 PM UTC
Duration
25m
Affected: Computer
Timeline · 3 updates
  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 2, 2026

Computer Sandbox Issue

Detected by Pingoru
Jul 02, 2026, 06:30 PM UTC
Resolved
Jul 02, 2026, 06:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 02, 2026, 06:30 PM UTC

    Type: Incident Duration: 1 hour and 41 minutes Affected Components: Computer Jul 2, 18:30:00 GMT+0 - Investigating - We are currently investigating this incident. Jul 2, 20:01:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 2, 20:10:50 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major June 30, 2026

Computer outage

Detected by Pingoru
Jun 30, 2026, 10:49 PM UTC
Resolved
Jun 30, 2026, 11:00 PM UTC
Duration
11m
Affected: WebsiteComputer
Timeline · 1 update
  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 4, 2026

Connector connectivity issues

Detected by Pingoru
Jun 04, 2026, 09:10 PM UTC
Resolved
Jun 04, 2026, 09:10 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 04, 2026, 09:10 PM UTC

    Type: Incident Duration: 4 hours and 31 minutes Affected Components: Website 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. Jun 5, 01:40:38 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Perplexity Website and API incident

Detected by Pingoru
May 08, 2026, 12:20 AM UTC
Resolved
May 08, 2026, 04:19 AM UTC
Duration
3h 59m
Affected: WebsiteAPI
Timeline · 5 updates
  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

Detected by Pingoru
Feb 16, 2026, 09:35 PM UTC
Resolved
Feb 16, 2026, 09:35 PM UTC
Duration
Timeline · 1 update
  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 →

Minor February 5, 2026

An issue affecting the stability of the website has been detected

Detected by Pingoru
Feb 05, 2026, 10:18 PM UTC
Resolved
Feb 05, 2026, 10:18 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 05, 2026, 10:18 PM UTC

    Type: Incident Duration: 18 minutes Affected Components: Website Feb 5, 22:18:11 GMT+0 - Investigating - We are investigating elevated error rates on the Perplexity website. Feb 5, 22:36:11 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major December 5, 2025

Service outage

Detected by Pingoru
Dec 05, 2025, 09:06 AM UTC
Resolved
Dec 05, 2025, 09:06 AM UTC
Duration
Timeline · 1 update
  1. resolved Dec 05, 2025, 09:06 AM UTC

    Type: Incident Duration: 34 minutes Affected Components: Website, API Dec 5, 09:06:41 GMT+0 - Investigating - We are currently investigating this incident. 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:41:11 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor November 18, 2025

Investigating connectivity issues

Detected by Pingoru
Nov 18, 2025, 01:00 PM UTC
Resolved
Nov 18, 2025, 01:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 18, 2025, 01:00 PM UTC

    Type: Incident Duration: 2 hours Affected Components: Website, API Nov 18, 13:00:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 13:46:17 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 14:59:39 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major September 5, 2025

API outage

Detected by Pingoru
Sep 05, 2025, 04:30 PM UTC
Resolved
Sep 05, 2025, 04:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 05, 2025, 04:30 PM UTC

    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.

Read the full incident report →

Minor June 10, 2025

We are investigating slowness and elevated error rates on the Perplexity website

Detected by Pingoru
Jun 10, 2025, 11:50 AM UTC
Resolved
Jun 10, 2025, 11:50 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 10, 2025, 11:50 AM UTC

    Type: Incident Duration: 3 hours and 41 minutes Affected Components: Website Jun 10, 11:50:05 GMT+0 - Investigating - We are investigating slowness and elevated error rates on the Perplexity website. Jun 10, 12:37:48 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 10, 14:36:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 10, 15:31:29 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor May 7, 2025

Investigating increased API latency

Detected by Pingoru
May 07, 2025, 03:43 AM UTC
Resolved
May 07, 2025, 03:43 AM UTC
Duration
Timeline · 1 update
  1. resolved May 07, 2025, 03:43 AM UTC

    Type: Incident Duration: 1 hour and 49 minutes Affected Components: API May 7, 03:43:00 GMT+0 - Investigating - We are currently investigating this incident. 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.

Read the full incident report →

Minor April 28, 2025

P99 First Token Latency of Sonar Pro is elevated

Detected by Pingoru
Apr 28, 2025, 07:08 AM UTC
Resolved
Apr 28, 2025, 07:08 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 28, 2025, 07:08 AM UTC

    Type: Incident Duration: 20 hours and 20 minutes Affected Components: API Apr 28, 07:08:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 29, 03:28:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major March 28, 2025

Website outage

Detected by Pingoru
Mar 28, 2025, 04:03 PM UTC
Resolved
Mar 28, 2025, 04:03 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 28, 2025, 04:03 PM UTC

    Type: Incident Duration: 4 hours and 38 minutes Affected Components: Website 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. 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, 20:41:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor February 12, 2025

API Downtime

Detected by Pingoru
Feb 12, 2025, 09:32 PM UTC
Resolved
Feb 12, 2025, 09:32 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 12, 2025, 09:32 PM UTC

    Type: Incident Duration: 20 minutes Affected Components: API Feb 12, 21:52:00 GMT+0 - Resolved - This incident has been resolved. Feb 12, 21:32:00 GMT+0 - Investigating - An API downtime issue has been identified

Read the full incident report →

Major November 13, 2024

Website is down

Detected by Pingoru
Nov 13, 2024, 02:22 AM UTC
Resolved
Nov 13, 2024, 02:22 AM UTC
Duration
Timeline · 1 update
  1. resolved Nov 13, 2024, 02:22 AM UTC

    Type: Incident Duration: 8 minutes Affected Components: Website Nov 13, 02:22:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 13, 02:30:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor September 16, 2024

Elevated usage

Detected by Pingoru
Sep 16, 2024, 04:00 PM UTC
Resolved
Sep 16, 2024, 04:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 16, 2024, 04:00 PM UTC

    Type: Incident Duration: 11 minutes Affected Components: Website, API Sep 16, 16:04:36 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 16, 16:12:03 GMT+0 - Resolved - This incident has been resolved. Sep 16, 16:00:48 GMT+0 - Investigating - We are currently investigating this incident.

Read the full incident report →