Supabase
Degraded InfrastructurePostgres + pgvector + auth — the default AI-app backend stack.
Partially Degraded Service · 30m ago
Response time · 24h
Measured by Prismix probes — not the vendor's status feed.
316ms
p50
- min
- 65ms
- p50
- 316ms
- p95
- 799ms
- p99
- 954ms
Embed this live badge
Updates ~30s · append ?theme=dark for dark READMEs
Light
Dark
Copy snippet ↓
Markdown · light
[](https://prismix.dev/service/supabase) Markdown · dark
[](https://prismix.dev/service/supabase) HTML
<a href="https://prismix.dev/service/supabase"><img src="https://prismix.dev/api/badge/supabase.svg" alt="Supabase status"></a> Active incidents
Intermittent latency in Eastern US
Started 1d ago · current status: Identified
- Identified 1d ago
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.
- Identified 1d ago
We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
- Identified 1d ago
A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
- Identified 1d ago
We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available.
- Identified 16h ago
We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.
- Identified 10h ago
We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available.
Components (28)
- Compute capacity Operational
- Analytics Operational
- ap-northeast-1 Operational
- API Gateway Degraded
- ap-northeast-2 Operational
- Auth Operational
- ap-south-1 Operational
- Connection Pooler Operational
- ap-southeast-1 Operational
- Dashboard Operational
- ap-southeast-2 Operational
- Database Operational
- ca-central-1 Operational
- Edge Functions Operational
- eu-central-1 Operational
- Management API Operational
- eu-central-2 Operational
- Realtime Operational
- eu-north-1 Operational
- Storage Operational
- eu-west-1 Operational
- eu-west-2 Operational
- eu-west-3 Operational
- sa-east-1 Operational
- us-east-1 Operational
- us-east-2 Operational
- us-west-1 Operational
- us-west-2 Operational
Resolved (last 30 days)
Full incident history →- Minor Details ↗
401 errors due to JWT rejections
Resolved 1d ago · lasted 1120h 23m
- Minor Details ↗
Log Ingestion Degradation
Resolved 2d ago · lasted 48m
- Major Details ↗
Project Lifecycle Issues in eu-west-1
Resolved 6d ago · lasted 2h 1m
- Critical Details ↗
Permission errors in the Supabase Dashboard
Resolved 6d ago · lasted 1h 12m
- Minor Details ↗
Storage search failing for restored projects
Resolved 6d ago · lasted 24h 29m
- Minor Details ↗
Supabase CLI CI workflow failures
Resolved 7d ago · lasted 1h 42m
- Major Details ↗
Increased error rate in project creation and project restore
Resolved 7d ago · lasted 1h 28m
- Minor Details ↗
Supavisor connection disruptions in EU West 1 (Ireland)
Resolved 8d ago · lasted 1h 30m
- Minor Details ↗
Project creations are degraded in multiple regions
Resolved 8d ago · lasted 31m
- Major Details ↗
Project Lifecycle Activity Degradation
Resolved 11d ago · lasted 2h
- Minor Details ↗
Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
Resolved 14d ago · lasted 2h 42m
- Minor Details ↗
Edge Function Latency
Resolved 14d ago · lasted 3h 2m
- Minor Details ↗
Auth Service Outage
Resolved 14d ago · lasted 2h 16m
- Informational Details ↗
Network access issues affecting a limited number of users in Myanmar
Resolved 15d ago · lasted 644h 55m
- Major Details ↗
Unresponsive Projects
Resolved 19d ago · lasted 27h 40m
- Informational Details ↗
Latency issues resulting in 504 errors
Resolved 19d ago
- Minor Details ↗
Brief connection disruptions in us-east-1 (N. Virginia)
Resolved 21d ago · lasted 0m
- Critical Details ↗
Project Lifecycle Actions Showing increased error rates across all regions
Resolved 26d ago · lasted 8h 2m
- Critical Details ↗
User unable to log in to Supabase Dashboard
Resolved 29d ago · lasted 1h 49m
Common questions about Supabase
Is Supabase down right now?
Supabase has 1 active incident as of 2026-10-01. The "Active incidents" section above lists details.
Where does this status data come from?
Directly from Supabase's official Statuspage.io feed at https://status.supabase.com. We refresh every 5 minutes and persist 24 hours of probe history.
Can I get email or webhook alerts when Supabase breaks?
Yes — sign in, star Supabase on the status dashboard, then add an email or Discord/Slack webhook on /alerts. Free tier gets 1 destination per channel; Pro gets 5.
What does "Degraded" mean?
Some users may notice slowness or intermittent errors. Core functionality intact.
Guides for Supabase
Related infrastructures
Get notified when Supabase changes state
One-click email alerts for Supabase only. No account. No Pro tier. Unsubscribe in every email.
Want to subscribe to multiple services + control severity threshold + add quiet hours? Create a free account instead.
Last refreshed 0s ago · live · data from https://status.supabase.com