Status: MonitoringWe will be conducting maintenance to address storage service improvements between 0800 and 0900 UTC on 5 November 2026. There may be an interruption of storage services in us-east-1 at some point during that window. The impact will be of a short duration and limited to us-east-1.Affected components us-east-1 (Operational) eu-central-1 (Operational)
Status: ResolvedErrors have subsided and connections are back to normal.Affected components us-east-2 (Operational)
Status: ResolvedConnection Logging feature is working fine for all customers now.
Status: ResolvedStorage uploads have remained stable, and this issue is now resolved.Affected components us-east-1 (Operational)
Status: ResolvedThis issue is now resolved.
Status: ResolvedWe have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
Status: ResolvedThis issue has been resolved and log delivery is operational again.Affected components Logging & Observability (Operational)
Status: ResolvedThis issue has been resolved and our response times are back to operational.Affected components ap-east-1 (Operational) ap-southeast-1 (Operational) eu-west-3 (Operational) ap-southeast-2 (Operational) eu-north-1 (Operational) ap-northeast-2 (Operational) eu-west-1 (Operational) us-west-2 (Operational) sa-east-1 (Operational) ap-south-1 (Operational) ap-northeast-1 (Operational) us…
Status: ResolvedThis issue is now resolved.Affected components Logging & Observability (Operational)
Status: ResolvedError rates have remained at normal levels following the mitigation. This incident is now resolved.Affected components eu-west-1 (Operational)
Status: ResolvedError rates and latency have remained at normal levels following the mitigation. This incident is now resolved.Affected components Dashboard (Operational) us-east-1 (Operational) eu-west-1 (Operational) us-west-1 (Operational) ap-southeast-1 (Operational)
Status: ResolvedThe 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.Affected components eu-central-2 (Operational) eu-central-2 (Operational) ap-east-1 (Operational) eu-central-1 (Operational) e…
Status: ResolvedAll affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
Status: ResolvedTicket creation has remained normal. We re resolving this incident.Affected components Dashboard (Operational)
Status: ResolvedService is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.Affected components ap-northeast-1 (Operational) ap-northeast-1 (Operational)
Status: ResolvedRealtime has fully recovered.Affected components Realtime (Operational)
Status: ResolvedEdge function deployments have remained stable. We are closing the incident.Affected components eu-west-2 (Operational) us-east-2 (Operational) ap-east-1 (Operational) eu-west-3 (Operational) sa-east-1 (Operational) ap-northeast-1 (Operational) eu-north-1 (Operational) us-west-2 (Operational) ca-central-1 (Operational) eu-west-1 (Operational) ap-south-1 (Operational) us-east-1 (Ope…
Status: ResolvedWe 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.Affected components Logging & Observability (Operational)
Status: ResolvedBetween 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 connection…
Status: CompleteThe statuspage migration is now complete. If you were previously subscribed via email, no action is needed, you were automatically resubscribed. If you were previously subscribed via any other method (SMS, Slack, webhook, RSS, etc.), you can now resubscribe.
Oct 7, 15:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 30, 22:08 UTC Scheduled - Starting October 7th, we are migrating our status page to a new platform to give you better visibility into Supabase's service status.What's changing:The status page URL will stay the same: https://status.supabase.comIf you are subscribed via email, you…
Status: ResolvedWe've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
Oct 6, 18:18 UTC Resolved - We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience. Oct 6, 17:27 UTC Monitoring - The fix has been implemented. Upgrade operation has been restored. We will monitor for stability. Oct 6, 16:37 UTC Update - A fix has been developed and we are going through the review and implementation process. Oct 6, 16:03…
Status: ResolvedA fix for this issue has been implemented and our data shows previous impacted users have recovered.Affected components API Gateway (Operational)
Oct 6, 12:15 UTC Resolved - A fix for this issue has been implemented and our data shows previous impacted users have recovered. Oct 5, 18:45 UTC Monitoring - A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident…
Status: ResolvedThis issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.Affected components Management API (Operational)
Oct 6, 09:03 UTC Resolved - This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored. Oct 6, 08:13 UTC Monitoring - We have identified a rollout causing error inc…
Status: ResolvedThe latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information: https://supabase.com/docs/guides/platform/upgrading Thank you again for your patien…
Sep 29, 18:46 UTC Resolved - The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information:https://supabase.com/docs/guides/platform/upgradingThank you again for…
Status: ResolvedLog ingestion is normal.