Supabase Outage History
Uptime record, past incidents, and downtime history for Supabase.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 70% | 10 | 3 |
| March 2026 | 54.8% | 31 | 14 |
| February 2026 | 78.3% | 23 | 5 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 64 Days)
Feb 6
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
Logs currently inaccessible via the Dashboard and Log Drains
Started: Apr 8, 7:10 PM
monitoring
All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.
Apr 8, 7:41 PM
identified
The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.
Apr 8, 7:24 PM
identified
Users may see errors when attempting to retrieve logs via the Supabase dashboard or may not see new logs arriving via log drains. The team has identified the issue and is working on a fix. Underlying projects are unaffected, this is only affecting the logging service.
Apr 8, 7:11 PM
Increased error rates for plan upgrades
Started: Apr 2, 8:28 AM
monitoring
A fix has been applied, and we are monitoring to ensure stability.
Apr 2, 9:05 AM
identified
We have identified the cause of increased error rates affecting plan upgrades and are working on a fix.
We will provide further updates as progress is made.
Apr 2, 8:40 AM
investigating
We are currently investigating increased error rates affecting plan upgrades. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.
Apr 2, 8:28 AM
Degraded logs ingestion
Started: Apr 1, 12:13 AM
monitoring
We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.
Apr 1, 12:47 AM
investigating
We are seeing degradation of logs and are currently investigating the cause of this issue.
Apr 1, 12:13 AM
March 2026
Project Creation Degradation
Started: Mar 27, 5:58 PM
monitoring
Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency.
Mar 27, 6:18 PM
identified
We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.
Mar 27, 5:58 PM
Degraded Log Ingestion
Started: Mar 27, 3:13 PM
monitoring
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
Mar 27, 4:17 PM
identified
We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.
Mar 27, 4:12 PM
identified
We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.
Mar 27, 3:52 PM
identified
We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.
Mar 27, 3:33 PM
investigating
We are investigating a problem with log ingestion. Users may experience delay in current log data.
Mar 27, 3:13 PM
Realtime services unavailable
Started: Mar 26, 11:41 PM
monitoring
The fix has been implemented and we’re monitoring to ensure stability.
Mar 27, 2:48 AM
identified
We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.
Mar 27, 1:44 AM
identified
We are working on a fix and we’ll continue to provide updates as progress is made.
Mar 27, 1:13 AM
identified
We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.
Mar 27, 12:46 AM
investigating
We're still investigating network connectivity issues with Realtime.
Mar 27, 12:20 AM
investigating
We are investigating network connectivity issues with Realtime.”
Mar 26, 11:41 PM
Branching access issues
Started: Mar 24, 3:13 PM
monitoring
The fix has been implemented and branching access has returned to normal.
Mar 24, 3:27 PM
identified
We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is being deployed. We will provide an update once resolved.
Mar 24, 3:13 PM
Degraded Logging Ingestion impacting all regions
Started: Mar 23, 4:28 PM
monitoring
A fix has been implemented.
The system is now operating normally, and we will continue to monitor.
Mar 23, 5:05 PM
identified
The cause of the issue has been identified. Our engineering team is working on a fix.
Mar 23, 4:38 PM
investigating
We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services.
Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all.
Projects remain fully functional. This issue is limited to logging only.
Our team is actively working to identify the root cause and restore normal performance as quickly as possible.
We will provide further updates as more information becomes ava...
Mar 23, 4:28 PM
Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Started: Mar 23, 2:16 PM
monitoring
We carried out a controlled redeployment of the affected services to restore stability.
The system is now operating normally, and we will continue to monitor.
Mar 23, 2:32 PM
investigating
We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Mar 23, 2:16 PM
Project creation failures across multiple regions
Started: Mar 19, 8:55 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 19, 9:21 PM
identified
We have identified the issue and a fix is underway.
Mar 19, 9:08 PM
investigating
We are currently investigating project creation failures across multiple regions.
Mar 19, 8:55 PM
Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region
Started: Mar 18, 4:27 PM
identified
The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.
Mar 18, 5:53 PM
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry.
Our team is actively working to determine the root cause and will provide further updates as more information becomes available.
Mar 18, 5:30 PM
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time.
Our team is actively working to determine the root cause and assess the full impact.
We will provide further updates as more information becomes available.
Mar 18, 4:58 PM
investigating
We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time.
We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.
Mar 18, 4:27 PM
Issues propagating Postgres configuration updates
Started: Mar 17, 4:50 AM
monitoring
A fix has been implemented and we are monitoring.
Mar 17, 7:07 AM
identified
We have identified the root cause and are currently working on a fix.
Mar 17, 5:11 AM
investigating
Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.
Mar 17, 4:50 AM
Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)
Started: Mar 13, 8:54 AM
monitoring
A fix has been implemented and error rates have reduced.
Our team is actively monitoring the system to ensure stability.
Mar 13, 9:40 AM
investigating
We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea)
We will provide further updates as information becomes available.
Mar 13, 9:25 AM
investigating
We are currently investigating increased error rates relating to the connection pooler in ap-northeast-2 (South Korea)
We will provide further updates as information becomes available.
Mar 13, 8:54 AM
Degraded Logging Ingestion impacting all regions
Started: Mar 12, 12:51 PM
monitoring
A fix has been implemented and log ingestion is now stabilising.
We are seeing recovery across the affected services.
Our team is actively monitoring the system to ensure ingestion fully returns to normal.
Mar 12, 12:54 PM
investigating
We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services.
Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs.
The logs for these services may only be partially ingested.
The services remain fully functional, this is only impacting logs.
Postgres Logs are not impacted.
Our team is actively working to identify the root cause and restore normal performance as quickly as...
Mar 12, 12:51 PM