Supabase Outage History

We’ve identified that this affects only a subset of projects in us-east-2. We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general

We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general

We believe we have identified the underlying cause of the 504 errors affecting Edge Functions across multiple regions. The team are currently implementing corrective measures to address the issue and restore service stability.

We've identified a spike in queued jobs in the region, which are resulting in pause and read replica actions delayed. The team is looking into this spike and remediation options.

The queued jobs are being processed, and pause events and read replica configuration changes will complete as expected once the jobs are processed. The team is, in parallel, looking into making some adjustments to help these processes complete faster.

The job queue is continuing to decrease. The team is making further changes to help it complete faster. Note: The impact of this remains project pause and read replica configuration change delays. All projects remain up and accessible.

We have identified the components resulting in the delayed metrics collection, and the team is working on a fix. This does not impact project availability or functionality, which remain healthy.

The team is continuing to work on a fix for metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics. We'll continue to update here as we have more information. This does not impact project availability or functionality, which remain healthy.

The team has deployed a fix and is actively monitoring recovery of partially degraded metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics. This does not impact project availability or functionality, which remain healthy.

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.

We are removing v2.95.0 release, so the @2 tag will resolve to v2.94.1. This should resolve majority of issues. If you have previously switched to using v2.95.0 directly, please switch to v2.94.1

We’ve attempted several fixes on the npm registry side, but the esm.sh issue persists. We are continuing to investigate. In the meantime, use npm: or jsr: specifiers, or jsdelivr as an alternative CDN: import { createClient } from "npm:@supabase/[email protected]" or import { createClient } from "https://cdn.jsdelivr.net/npm/@supabase/[email protected]/+esm"

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"

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"

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"

We have identified the issue and are working towards a resolution.

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

We are actively working with network vendors to mitigate this issue.

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.

The issue has been identified and a fix is being implemented.

We have identified the issue causing errors for these changes, and the team is working on a fix.

We continue to monitor for resolution of the upstream provider incident.

We are continuing to monitor for resolution of the upstream provider incident.

We have received word from our upstream partner that their issue has been resolved. The team is currently testing all functionality on our side and cleaning up previously errored requests. Once we're confident things are back to normal, we'll resume project actions in the region.

The issue has been identified and a fix is being implemented.

For users experiencing this issue: esm.sh is having issues. Users can replace esm.sh with npm: or jsr imports to get function deploys to work.