Supabase status
Is Supabase down? This is Supabase’s current status, its components and its recent incidents, read from Supabase’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by Supabase’s status page, read Oct 24, 2026, 18:04 UTC.
Ongoing incidents
- Elevated Mgmt API Error Rates in Multiple Regions · Oct 22, 2026, 17:01 UTC · monitoring, minor impact
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
Scheduled maintenance
- Scheduled Platform Maintenance 07/02 · Jun 29, 2026, 17:07 UTC · scheduled, maintenance impact
Components
| Component | Status |
|---|---|
| ap-east-1 | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent Supabase incidents
- Elevated Mgmt API Error Rates in Multiple Regions · Oct 22, 2026, 17:01 UTC · monitoring, minor impact
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
- Log Drain Issues · Oct 22, 2026, 18:03 UTC · resolved, minor impact, lasted 47 min
This issue is now resolved.
- Project lifecycle operation errors in the EU region · Oct 22, 2026, 03:53 UTC · resolved, major impact, lasted 12 h 3 min
Error rates have remained at normal levels following the mitigation. This incident is now resolved.
- Elevated Mgmt API Error Rates in Multiple Regions · Oct 22, 2026, 11:29 UTC · resolved, major impact, lasted 2 h 13 min
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
- Project lifecycle operations such as project creation, pausing, and restoration, in all regions · Oct 21, 2026, 15:36 UTC · resolved, major impact, lasted 1 h 16 min
The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.
- Projects stuck in restarting state · Oct 20, 2026, 21:59 UTC · resolved, lasted 7 h 41 min
All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
- Support Form Errors · Oct 19, 2026, 17:13 UTC · resolved, minor impact, lasted 1 h 0 min
Ticket creation has remained normal. We re resolving this incident.
- Project creation errors ap-ne1 · Oct 17, 2026, 06:27 UTC · resolved, minor impact, lasted 1 h 22 min
Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.
- Realtime latency · Oct 12, 2026, 22:59 UTC · resolved, minor impact, lasted 45 h 26 min
Realtime has fully recovered.
- Edge Function Degradation · Oct 12, 2026, 19:49 UTC · resolved, minor impact, lasted 22 h 36 min
Edge function deployments have remained stable. We are closing the incident.
- Log ingestion impaired · Oct 12, 2026, 19:39 UTC · resolved, minor impact, lasted 5 h 51 min
We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.
- Intermittent connection errors via the connection pooler in us-east-1 · Oct 21, 2026, 16:27 UTC · resolved
Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected…
- Upgrade Issues · Oct 6, 2026, 15:23 UTC · resolved, lasted 2 h 56 min
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
- Intermittent latency in Eastern US · Sep 29, 2026, 16:26 UTC · resolved, minor impact, lasted 163 h 49 min
A fix for this issue has been implemented and our data shows previous impacted users have recovered.
- Increased errors on management api leading to project operation failures · Oct 6, 2026, 07:53 UTC · resolved, minor impact, lasted 1 h 10 min
This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all…
Source: Supabase, Supabase’s public status page, read Oct 24, 2026, 18:04 UTC. Uptimely is not affiliated with Supabase; incident text is Supabase’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of supabase.com to see whether it answers right now.
Get alerted when Supabase has an incident
Uptimely’s External Status Page monitor watches Supabase’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- GitHub status
- Bitbucket status
- npm status
- Docker status
- Twilio status
- Datadog status
- Sentry status
- PlanetScale status
- MongoDB Atlas status
- Elastic Cloud status
- Snowflake status
- Grafana Cloud status
- CircleCI status
- Mailgun status
- Resend status
- Clerk status
- Segment status
- Cloudinary status
Is Supabase down right now?
The status at the top of this page is Supabase's own, read from its public status page every couple of minutes. It shows what Supabase's team has confirmed. For an independent check of whether supabase.com answers right now, use the live check on the is-it-down page.
Where is Supabase's official status page?
Supabase publishes its status at https://status.supabase.com. This page shows the same data with the recent incident history in one place, and links each incident to Supabase's own write-up.
Why does Supabase not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when Supabase has an incident?
Add an External Status Page monitor in Uptimely pointed at https://status.supabase.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Supabase reports a problem, beside the monitors for your own services.