Is Supabase Down?

Feb 13 , 01:53 UTC Resolved - Service has been fully restored. All impacted jobs have been requeued and are currently processing normally. We will be publishing a public post-mortem with additional details about this incident. Feb 13 , 01:26 UTC Monitoring - The revert of the change helped and most of the metrics are back to the pre incident levels. We are requeuing failed jobs and monitoring to make sure the issue doesn’t come back. Feb 13 , 01:04 UTC Identified - We identified a potential internal networking configuration that may have caused the incident. We have since reverted that change and it appears services are recovering. Feb 12 , 23:58 UTC Update - We are still investigating the root cause for this incident. us-east-2 region isn’t receiving any network traffic at this point. We are also seeing some API request errors in other US regions, but not as high as us-east-2. Feb 12 , 22:57 UTC Update - We continue to see increased levels of 500 errors across US-West and US-East regions. Our engineering team is investigating the issue. Feb 12 , 22:37 UTC Update - The issue identified it as a problem in US-West with some impact in US-East and the impact seems to be primarily on reads rather than writes. Feb 12 , 21:32 UTC Investigating - We have identified increasing 500 errors in some US regions and are actively investigating the cause.

Feb 10 , 21:28 UTC Resolved - This issue is now resolved. Feb 10 , 15:24 UTC Update - We continue to work with network vendors to mitigate this issue. In the interim, using a VPN will give you access to your Supabase project. Feb 4 , 18:08 UTC Update - We are actively working with network vendors to mitigate this issue. Feb 3 , 21:38 UTC Identified - We have noticed increase connection failures to supabase.co domains from connections originating in Yemen. Projects are up and running, this only impacts connections from this region. We are working to resolve this issue with appropriate parties and will provide an update soon. We have specifically had reports of connection issues from connections via these ISPs: Yemen Mobile Sabafon Y-Telecom Spacetel

Feb 9 , 19:34 UTC Resolved - This incident has been resolved. Feb 9 , 18:37 UTC Update - The team noticed that some connection pools had workers stuck as a consequence of the previous issue. This could cause query failures. Stuck workers were now restarted. Feb 9 , 17:56 UTC Monitoring - We've removed the problematic cluster node and latency returned to the normal level. We are now monitoring. Feb 9 , 17:39 UTC Investigating - We’re investigating high latency in us-west-1 affecting some connections to databases via our shared connection pooler.

Feb 5 , 15:49 UTC Resolved - This incident has been resolved. Feb 5 , 14:40 UTC Update - We've observing a recovery for latency and error rates after the capacity increase. We will be monitoring to make sure the problem was fully resolved. Feb 5 , 14:13 UTC Investigating - We're seeing elevated errors and latency in Realtime service. We are already working on increasing cluster capacity to stabilize it.

Feb 5 , 06:49 UTC Resolved - This incident has been resolved. Feb 5 , 03:48 UTC Monitoring - Our upstream provider has pushed a fix, and requests seem to be back to normal now. According to data from our partner, users in the US South were largely affected, with users in and around Texas being the most common, but some users in and around Georgia may have also seen issues, but these should all be resolved at this point. Users connecting to project URLs should no longer be seeing "DNS address could not be found" errors. We are continuing to monitor the situation. Feb 5 , 03:22 UTC Update - Our upstream provider has identified the specifc issues with DNS resolution and has begun working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found" Feb 5 , 03:03 UTC Update - We are continuing to work on this with our upstream network provider. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found" Feb 5 , 02:21 UTC Identified - Our upstream network provider has identified an issue and is working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found" Feb 5 , 01:52 UTC Investigating - We are seeing reports of DNS Lookup failures for users based in the United States. The issue does not seem to affect all DNS providers, and we are still working to narrow down affected areas. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

Feb 4 , 19:17 UTC Resolved - This issue is now resolved. Feb 4 , 18:48 UTC Monitoring - New project creation and unpauses are now available. We are working on remediation of projects impacted during the incident and will continue to monitor. Feb 4 , 18:14 UTC Identified - We have identified the issue and are working towards a resolution. Feb 4 , 17:55 UTC Investigating - We are investigating issues affecting instance operations globally. This may impact new project creation and project unpauses. Existing projects remain unaffected.

Feb 3 , 21:54 UTC Resolved - This issue is now resolved. Affected customers should delete any failed cloned projects and try again with a new clone. Feb 3 , 20:53 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 3 , 19:56 UTC Identified - The issue has been identified and a fix is being implemented. Feb 3 , 18:42 UTC Investigating - We are currently investigating an issue with our beta project cloning feature (Restore to a New Project). This has been disabled while we conduct our investigations and we will provide an update soon.