Major impactResolvedDatabases

Supabase outage: Increased response times for requests

Supabase reported this major-impact incident on its official status page on Aug 27, 2026, 17:20 UTC. It was resolved after 3d 22h.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Aug 27, 2026, 17:20 UTC
started
Aug 31, 2026, 15:57 UTC
resolved
3d 22h
duration
Major
impact
  1. resolvedAug 31, 2026, 15:57 UTC

    Response times have recovered in all regions. This issue is now resolved.

  2. monitoringAug 29, 2026, 01:25 UTC

    Response times have recovered in all regions. We will continue to monitor throughout the weekend.

  3. monitoringAug 28, 2026, 21:06 UTC

    The rollout has been completed in all regions. We will continue to monitor.

  4. identifiedAug 28, 2026, 18:15 UTC

    The roll out has also been completed for us-east-1.

  5. identifiedAug 28, 2026, 17:21 UTC

    PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions.

  6. identifiedAug 28, 2026, 13:10 UTC

    We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available.

  7. identifiedAug 28, 2026, 01:38 UTC

    The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.

  8. investigatingAug 27, 2026, 20:37 UTC

    We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

  9. investigatingAug 27, 2026, 18:55 UTC

    We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

  10. investigatingAug 27, 2026, 17:57 UTC

    We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.

  11. investigatingAug 27, 2026, 17:20 UTC

    We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history

Supabase outage on Aug 27, 2026: Increased response times for requests · APIStatus.watch