Track Supabase with a free Huntertech account. Get outage alerts, watchlists, and cross-vendor monitoring in one place.

Try for free
2 incidents ongoing/145 total historical

Supabase incidents

Live feed from the vendor status page - prioritize ongoing work, jump to monitoring, scan the last seven days, or browse full history. Filters narrow by cloud, status, and timeframe.

Updated 1 minute ago
Showing 5 of 19 incidents on Public
Resolved
Aug 21, 2026, 08:15 AM EDT
Delays in project provisioning
Status: investigating We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.
Duration: 1h 48mVendor update 3 minutes ago
Incident community checkThis incident
Ongoing
Aug 20, 2026, 08:18 AM EDT
Network access issues affecting a limited number of users in Myanmar
Status: investigating We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.
Duration: 1d 20h 25m +Vendor update 1 day ago
Incident community checkThis incident
Resolved
Aug 19, 2026, 11:56 AM EDT
Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
Status: monitoring We've identified an issue causing sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts. We've identified the root cause and fix has been rolled out. Impacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC
Duration: 3h 9mVendor update 2 days ago
Incident community checkThis incident
Resolved
Aug 16, 2026, 09:56 PM EDT
Project creation failing in selected regions
Status: investigating We are investigating an issue with project creation failing. We will be confirming more information shortly.
Duration: 8mVendor update 4 days ago
Incident community checkThis incident
Ongoing
Aug 20, 2026, 12:37 PM EDT
401 errors due to JWT rejections
Status: identified We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.
Duration: 7d 9h 55m +Extended ongoingVendor update about 20 hours agoAPI Gateway
Incident community checkThis incident

19 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.

Signal
Incident
Reports0