← Back to Supabase History
major✓ Resolved
Increased response times for requests
Status
resolved
Duration
3d 22h
Updates
10
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedMon, Aug 31, 2026, 04:02 PM
This incident has been resolved.
monitoringSat, Aug 29, 2026, 01:25 AM
Response times have recovered in all regions. We will continue to monitor throughout the weekend.
monitoringFri, Aug 28, 2026, 09:06 PM
The rollout has been completed in all regions. We will continue to monitor.
identifiedFri, Aug 28, 2026, 06:15 PM
The roll out has also been completed for us-east-1.
identifiedFri, Aug 28, 2026, 05:21 PM
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.
identifiedFri, Aug 28, 2026, 01:10 PM
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.
identifiedFri, Aug 28, 2026, 01:38 AM
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.
investigatingThu, Aug 27, 2026, 08:37 PM
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigatingThu, Aug 27, 2026, 06:55 PM
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigatingThu, Aug 27, 2026, 05:57 PM
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.
investigatingThu, Aug 27, 2026, 05:20 PM
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.
📊 TECHNICAL DETAILS
Internal ID
7d7634e9-7f80-4f5e-9152-0a70a4d22101
External ID
bv4ntm4x0btf
🕐 Started
Thu, Aug 27, 2026, 05:20 PM
🔄 Last Updated
Mon, Aug 31, 2026, 04:02 PM
✓ Resolved
Mon, Aug 31, 2026, 04:02 PM
MAJOR
Impact Level
3d 22h
Total Duration
10
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed