Is Supabase down?

We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

We have identified why projects are becoming unresponsive and are implementing a mitigation.

A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.

Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.

We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.

We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.

We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.

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

We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information

We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information.

The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information.

The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. We will provide additional updates as we have more information.

We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users. We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal. We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve. Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.

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

We are currently investigating an issue where users are unable to login to the Supabase dashboard

We’re investigating an issue preventing users from logging in to the Supabase Dashboard. Users who were logged into the dashboard were logged out. Dashboard actions are currently not available. Projects remain online and available. Non-Dashboard traffic is not impacted. We’ll share another update as soon as we have more information.

A recent change affected users ability to log in to the Supabase Dashboard. We’ve reverted the change, and testing indicates that the issue is resolved. Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry. Projects and non-Dashboard traffic remained unaffected.

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.

Project creation is failing for new projects on the platform. We are investigating.

We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.

We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.

While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.

We are seeing the mitigation steps having the desired effect. Project creation is recovering.

Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.

Project creation has returned to baseline consistently.