Supabase incident

Increased response times for requests

Major Ongoing View vendor source →

Supabase is currently experiencing a major incident, which began 2d ago. The vendor's full update timeline is below.

Started
Aug 27, 2026, 05:20 PM UTC
Resolved
Ongoing
Duration
● 2d
Detected by Pingoru
Aug 27, 2026, 05:20 PM UTC

Update timeline

  1. investigating Aug 27, 2026, 05:20 PM 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.

  2. investigating Aug 27, 2026, 05:57 PM 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.

  3. investigating Aug 27, 2026, 06:55 PM UTC

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

  4. investigating Aug 27, 2026, 08:37 PM UTC

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

  5. identified Aug 28, 2026, 01:38 AM 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.

  6. identified Aug 28, 2026, 01:10 PM 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. identified Aug 28, 2026, 05:21 PM 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.

  8. identified Aug 28, 2026, 06:15 PM UTC

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

  9. monitoring Aug 28, 2026, 09:06 PM UTC

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

  10. monitoring Aug 29, 2026, 01:25 AM UTC

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