down
Is Supabase down?
Check Supabase availability, incident history, downtime reports, and website performance.
https://supabase.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for Supabase
Last 24 hoursThere is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.
Last collection attempt: 2026-10-20 11:31:37 UTC · Insufficient activity.
No user-submitted outage reports in the last 24 hours.
Supabase outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Supabase website uptime and response time
Current website availability is unknown. No website checks available yet.
Unknown
Successful website checks (24h)
0 successful / 0 measurable checks
Unknown
Median response time
Unknown
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Supabase official status · fetched 2026-10-22 00:11:10 UTC
1 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| ap-east-1 | operational |
Official incident timeline
Project lifecycle operations such as project creation, pausing, and restoration, in all regions · resolved · 2026-10-21T16:51:51Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
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.
- · monitoring
A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.
- · investigating
We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.
Projects stuck in restarting state · resolved · 2026-10-21T05:39:55Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
- · monitoring
The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
- · identified
We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.
- · identified
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
- · identified
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
- · identified
We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.
- · identified
We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.
- · investigating
Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.
Support Form Errors · resolved · 2026-10-19T18:13:51Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Ticket creation has remained normal. We re resolving this incident.
- · monitoring
The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.
- · identified
We have identified an issue with support ticket creation for some customers, we have a fix in development.
Project creation errors ap-ne1 · resolved · 2026-10-17T07:49:32Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.
- · monitoring
Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.
- · identified
Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.
Realtime latency · resolved · 2026-10-14T20:25:15Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Realtime has fully recovered.
- · monitoring
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
- · identified
We’re seeing recovery for a large percentage of affected customers, though some issues remain in certain regions. We’re continuing to work on resolving the remaining issues and will share further updates as more information becomes available.
- · identified
We’ve added extra capacity to the system and are currently testing it. We expect to begin stabilizing the affected clusters shortly. We’ll continue to share further updates as more information becomes available.
- · identified
We are continuing to investigate increased Realtime latency and instability affecting the presence feature, which may impact join rates. Our team is actively working on mitigation and we will share another update as soon as more information becomes available.
- · identified
We’re seeing increased Realtime latency and instability affecting the presence feature, which may impact join rates. This recurrence comes as we continue work on the remaining preventative measures. We are actively investigating and taking steps to mitigate the impact. We’ll share another update as soon as we have more information.
- · monitoring
We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
- · monitoring
We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
- · investigating
We are experiencing increased latency with Realtime and are actively investigating.
Edge Function Degradation · resolved · 2026-10-13T18:24:49Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Edge function deployments have remained stable. We are closing the incident.
- · monitoring
Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
- · identified
Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
- · identified
We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
- · identified
We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
Log ingestion impaired · resolved · 2026-10-13T01:30:33Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
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.
- · monitoring
The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.
- · identified
We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.
- · identified
We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.
- · identified
We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.
- · identified
We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.
- · investigating
Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.
Intermittent connection errors via the connection pooler in us-east-1 · resolved · 2026-10-21T16:27:59Z
Product match: unmapped.
Read the provider’s incident report
- · 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 network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that
Recovery tracker
Provider marked the incident resolved; independent website recovery is still being checked.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: unknown. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Supabase.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
About Supabase status on Iszdown
Check Supabase availability, incident history, downtime reports, and website performance.
This page combines the available Supabase report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
1 product-matched official components are listed above. No public website measurement is available in the current window.
Visit the official Supabase website · Official provider status · How it works
What to check when Supabase is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Supabase will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Supabase is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Supabase outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Project lifecycle operations such as project creation, pausing, and restoration, in all regions | 76 min | resolved | |
| Support Form Errors | 60 min | resolved | |
| Project creation errors ap-ne1 | 82 min | resolved | |
| Realtime latency | 2726 min | resolved | |
| Edge Function Degradation | 1356 min | resolved | |
| Log ingestion impaired | 351 min | resolved | |
| Increased errors on management api leading to project operation failures | 70 min | resolved | |
| Intermittent latency in Eastern US | 9829 min | resolved |
Frequently asked questions about Supabase
Is Supabase down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:13:15.000Z.
How many Supabase outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Supabase show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Supabase feature.
When was Supabase status last updated?
The latest status observation was 2026-10-22T00:11:10.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Supabase had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Supabase or report a problem?
Use “Watch this service” to save Supabase in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Supabase
Check a related product separately; its status can differ from Supabase.