Is Supabase Down?
Real-time status check for supabase.com
Checking status...
About Supabase Status
BlueMonitor checks Supabase (supabase.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Logs currently inaccessible via the Dashboard and Log Drains
Apr 8 , 20:05 UTC Resolved - This incident has been resolved. Apr 8 , 19:41 UTC 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 , 19:24 UTC Update - 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 , 19:11 UTC 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.
Increased error rates for plan upgrades
Apr 2 , 09:24 UTC Resolved - The issue causing increased error rates during plan upgrades has been resolved. All systems are operating normally. Apr 2 , 09:05 UTC Monitoring - A fix has been applied, and we are monitoring to ensure stability. Apr 2 , 08:40 UTC 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 , 08:28 UTC 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.
Degraded logs ingestion
Apr 1 , 01:11 UTC Resolved - Log ingestion has recovered and the incident is considered resolved. Some log data was lost during the incident between around 11pm to 11:45pm ETC on March 31. Apr 1 , 00:47 UTC Monitoring - We have identified the issue and a fix is in place. We will continue to monitor to ensure stability. Apr 1 , 00:13 UTC Investigating - We are seeing degradation of logs and are currently investigating the cause of this issue.
Supabase dashboard experiencing intermittent errors in Europe region
Mar 27 , 18:43 UTC Resolved - We have confirmed that project creation has returned to normal. Mar 27 , 18:18 UTC Monitoring - Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency. Mar 27 , 17:58 UTC Identified - We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.
Degraded Log Ingestion
Mar 27 , 17:03 UTC Resolved - Log ingestion has returned to normal Mar 27 , 16:17 UTC Monitoring - Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal. Mar 27 , 16:12 UTC Update - 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 , 15:52 UTC Update - 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 , 15:33 UTC 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 , 15:13 UTC Investigating - We are investigating a problem with log ingestion. Users may experience delay in current log data.
Realtime services unavailable
Mar 27 , 02:58 UTC Resolved - The issue has been resolved and Realtime services have returned to normal. Mar 27 , 02:48 UTC Monitoring - The fix has been implemented and we’re monitoring to ensure stability. Mar 27 , 01:44 UTC Update - We appreciate your patience as we continue to work on a fix. We will provide updates as they become available. Mar 27 , 01:13 UTC Update - We are working on a fix and we’ll continue to provide updates as progress is made. Mar 27 , 00:46 UTC Identified - We've identified the issue and are currently working on a fix, we will provide an update on our progress soon. Mar 27 , 00:20 UTC Update - We're still investigating network connectivity issues with Realtime. Mar 26 , 23:41 UTC Investigating - We are investigating network connectivity issues with Realtime.”
Branching access issues
Mar 24 , 15:56 UTC Resolved - Branching access has returned to normal, this issue is resolved. Mar 24 , 15:27 UTC Monitoring - The fix has been implemented and branching access has returned to normal. Mar 24 , 15:13 UTC 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.
Degraded Logging Ingestion impacting all regions
Mar 23 , 18:56 UTC Resolved - This issue is now resolved. All logging ingestion has resumed in all regions. Mar 23 , 17:05 UTC Monitoring - A fix has been implemented. The system is now operating normally, and we will continue to monitor. Mar 23 , 16:38 UTC Identified - The cause of the issue has been identified. Our engineering team is working on a fix. Mar 23 , 16:28 UTC 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 available.
Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Mar 23 , 15:42 UTC Resolved - Error rates have returned to normal. This incident has been resolved. Mar 23 , 14:32 UTC 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 , 14:16 UTC Investigating - We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Project creation failures across multiple regions
Mar 19 , 22:00 UTC Resolved - Project creation in all regions are now successful. Mar 19 , 21:21 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 19 , 21:08 UTC Identified - We have identified the issue and a fix is underway. Mar 19 , 20:55 UTC Investigating - We are currently investigating project creation failures across multiple regions.
Frequently Asked Questions
Is Supabase down right now?
This page shows the real-time status of Supabase. The status is checked automatically by pinging Supabase's servers. If the status shows "Down", it means Supabase is currently experiencing issues.
Why is Supabase not working?
Supabase may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Supabase is down for everyone?
BlueMonitor checks Supabase's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Supabase is down?
If Supabase is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.