← Back to Supabase History
major✓ Resolved

403 errors for PostgREST requests

Supabase•Tue, Apr 28, 2026, 09:26 PM
Status
resolved
Duration
2h 8m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedTue, Apr 28, 2026, 11:35 PM
This incident has been resolved.
monitoringTue, Apr 28, 2026, 11:03 PM
The exceptions fix has been rolled out, and we are monitoring for continued stability.
identifiedTue, Apr 28, 2026, 10:24 PM
We are continuing to work on a fix. We’ll share further updates as progress is made.
identifiedTue, Apr 28, 2026, 09:40 PM
We are continuing to work on a fix for this issue.
identifiedTue, Apr 28, 2026, 09:36 PM
The issue has been identified and we are working on a fix.
investigatingTue, Apr 28, 2026, 09:26 PM
We are investigating 403 errors for PostgREST requests across multiple regions.

📊 TECHNICAL DETAILS

Internal ID
78c40440-7198-4961-bd6c-f8bd3a7d6ca3
External ID
rzwtq93tzd4f
🕐 Started
Tue, Apr 28, 2026, 09:26 PM
🔄 Last Updated
Tue, Apr 28, 2026, 11:35 PM
✓ Resolved
Tue, Apr 28, 2026, 11:35 PM
MAJOR
Impact Level
2h 8m
Total Duration
5
Status Updates
Affected Components
API Gateway
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