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

Errors have subsided and connections are back to normal.

Connection Logging feature is working fine for all customers now.

Storage uploads have remained stable, and this issue is now resolved.

This issue is now resolved.

We 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

This issue has been resolved and log delivery is operational again.

This issue has been resolved and our response times are back to operational.

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.