We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.

This issue is now resolved.

Error rates have remained at normal levels following the mitigation. This incident is now resolved.

Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.

The 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.

All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.

Ticket creation has remained normal. We re resolving this incident.

Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.

Realtime has fully recovered.

Edge function deployments have remained stable. We are closing the incident.

We 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.

Between 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 connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.

The 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.

We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

A fix for this issue has been implemented and our data shows previous impacted users have recovered.

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.

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/upgrading

Thank you again for your patience while we worked on resolving this issue.

Log ingestion is normal.

This incident has been resolved.

This incident has been resolved. Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.

Storage is now operating normally. We apologise for the disruption.

Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally.

The latency has recovered and the incident is now resolved.

Project lifecycle operations are behaving normally.

This has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

The scheduled maintenance has been completed.

We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved.

We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks

This incident has been resolved.

We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.

Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally. Projects and non-Dashboard traffic were unaffected throughout the incident.