How often does Supabase have outages?

Supabase has had 50 reported incidents recently. Visit apistatuscheck.com/incidents/supabase for the complete outage history with timelines and resolution details.

What was the last Supabase outage?

The most recent Supabase incident was "DNS record creation failures impacting project creation, restore, pause" on June 18, 2026. It was classified as major impact and is currently resolved.

Supabase Outage History

50 incidents reported. Data sourced from the official Supabase status page.

Total Incidents

Major/Critical

Minor

Resolved

June 2026

DNS record creation failures impacting project creation, restore, pause

major

Jun 18, 06:39 AM→Jun 18, 10:17 AMresolved

Jun 18, 10:17 AM

resolved — This issue has been resolved and all previous held project updates resumed.

Jun 18, 08:05 AM

monitoring — We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.

Jun 18, 07:37 AM

identified — We have identified a fix and working on recovering the impacted system. Project creation, pause and unpause functions will be restored on confirmed service recovery.

+2 more updates

Hardware failure in us-east

minor

Jun 17, 03:12 PM→Jun 17, 05:02 PMresolved

Jun 17, 05:02 PM

resolved — We have now recovered all Projects affected by the outage in us-east-2.

Jun 17, 04:13 PM

monitoring — All the identified affected projects in us-east-2 are now healthy. If your project is in us-east and not responsive, please open a ticket to let us know.

Jun 17, 03:44 PM

identified — We have identified projects specifically impacted by this issue and are recovering affected projects.

+1 more updates

Degraded Management API performance affecting payments and Supabase Studio

major

Jun 17, 12:31 PM→Jun 17, 02:10 PMresolved

Jun 17, 02:10 PM

resolved — All regions continue to report healthy Management API performance and platform stability.

Jun 17, 01:15 PM

monitoring — We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. All payment features have been re-enabled. Customers should no ...

Jun 17, 12:51 PM

investigating — We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2. Customers may experience failed payments, faile...

+1 more updates

Project usage analytics API endpoints breakage

minor

Jun 16, 03:47 PM→Jun 16, 05:01 PMresolved

Jun 16, 05:01 PM

resolved — All analytics responses have returned to normal.

Jun 16, 04:27 PM

monitoring — The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.

Jun 16, 04:22 PM

identified — The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.

+2 more updates

Degraded Log Explorer in the dashboard

minor

Jun 16, 11:26 AM→Jun 16, 03:08 PMresolved

Jun 16, 03:08 PM

resolved — We have rolled out additional performance improvements to reporting API endpoints.

Jun 16, 01:30 PM

monitoring — We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.

Jun 16, 01:01 PM

identified — The mitigations rolled out have resulted in a great reduction in errors and most users should now see fully-functional logging and usage charts; however, some users may still see erroneously empty usa...

+1 more updates

DNS Resolution Failures for TLD .co users

none

Jun 8, 03:39 AM→Jun 16, 08:16 AMresolved

Jun 16, 08:16 AM

resolved — The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.

Jun 15, 04:52 PM

monitoring — The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

Jun 12, 11:09 AM

monitoring — Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution ...

+5 more updates

Storage users in US-West-2 experiencing increased latency on storage requests

minor

Jun 12, 04:00 PM→Jun 13, 12:40 AMresolved

Jun 13, 12:40 AM

resolved — All residual jobs have drained. Storage performance and job activity is normal.

Jun 12, 11:57 PM

monitoring — Job queues continue to drain. We will actively monitor until they are complete.

Jun 12, 08:26 PM

monitoring — Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.

+5 more updates

Higher connection failure rate for ap-northeast-1 and ap-northeast-2

none

Jun 10, 12:00 AM→Jun 10, 12:00 AMresolved

Jun 10, 01:43 AM

resolved — From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 clusters caused a higher connection failure rate. Users would have experienced failing conne...

Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)

critical

Jun 2, 01:36 PM→Jun 2, 02:41 PMresolved

Jun 2, 02:41 PM

resolved — All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.

Jun 2, 02:12 PM

monitoring — The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.

Jun 2, 02:05 PM

identified — We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.

+1 more updates

May 2026

Access Issues From Some Providers in Brazil

none

May 14, 03:34 PM→Jun 16, 08:15 AMresolved

Jun 16, 08:15 AM

resolved — The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.

Jun 15, 04:52 PM

monitoring — The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

Jun 12, 02:42 PM

monitoring — We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.

+7 more updates

Branch creation degradation

minor

May 21, 04:46 PM→May 21, 07:26 PMresolved

May 21, 07:26 PM

resolved — Branch creation continues to be stable.

May 21, 06:54 PM

monitoring — Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to id...

May 21, 05:45 PM

investigating — We continue investigating different possible underlying causes and will provide updates as progress is made.

+1 more updates

Login issues for SSO and Email accounts on Supabase Dashboard

minor

May 21, 08:30 AM→May 21, 10:51 AMresolved

May 21, 10:51 AM

resolved — The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.

May 21, 09:43 AM

monitoring — We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.

May 21, 09:26 AM

identified — A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.

+3 more updates

Network restrictions preventing read replica communication

minor

May 20, 09:04 PM→May 21, 04:44 AMresolved

May 21, 04:44 AM

resolved — Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.

May 21, 04:23 AM

monitoring — We have merged the fix and are monitoring for stability.

May 21, 03:49 AM

identified — We have developed a fix and it is currently being validated. We will provide more updates soon.

+5 more updates

Paused Projects Showing Incorrect Resume Deadline

minor

May 20, 03:40 PM→May 20, 07:41 PMresolved

May 20, 07:41 PM

resolved — The UI message incident has been resolved.

May 20, 07:11 PM

monitoring — This change has been reverted. We are monitoring to ensure things remain stable.

May 20, 05:41 PM

identified — The revert of the change is in process.

+2 more updates

Log ingestion issues

minor

May 18, 11:26 PM→May 19, 12:10 AMresolved

May 19, 12:10 AM

resolved — This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatic...

May 18, 11:58 PM

monitoring — Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot ...

May 18, 11:26 PM

investigating — Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

Auth Service Update

none

May 15, 06:11 PM→May 15, 07:18 PMresolved

May 15, 07:18 PM

resolved — All changes hav been applied.

May 15, 06:47 PM

monitoring — The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.

May 15, 06:11 PM

identified — We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.

Edge Traffic Issues

minor

May 13, 04:15 PM→May 13, 08:35 PMresolved

May 13, 08:35 PM

resolved — We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involvi...

May 13, 07:50 PM

identified — Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact...

May 13, 05:31 PM

investigating — We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the sco...

+2 more updates

Error spikes in one of the eu-central-1 Supavisor clusters

minor

May 9, 03:00 PM→May 9, 03:00 PMresolved

May 19, 10:31 AM

resolved — Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors rep...

Network connectivity in us-east-1-az4

major

May 8, 12:50 AM→May 9, 04:49 AMresolved

May 9, 04:49 AM

resolved — Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.

May 9, 04:34 AM

monitoring — Our infrastructure provider has resolved the underlying incident, and impacted services have recovered. We have completed recovery efforts for affected projects, re-enabled project creation, pausing,...

May 9, 04:10 AM

identified — Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered. Our team is currently working through the remaining projects that did not au...

+14 more updates

Customer Projects Experiencing Upgrade Issues

minor

May 8, 01:25 PM→May 8, 04:13 PMresolved

May 8, 04:13 PM

resolved — Upgrade operations have returned to normal.

May 8, 02:39 PM

monitoring — We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY witho...

May 8, 01:46 PM

identified — We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL v...

+2 more updates

Supavisor connectivity in eu-central-1

minor

May 3, 10:30 PM→May 3, 10:30 PMresolved

May 4, 04:58 PM

resolved — From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query faile...

April 2026

403 errors for PostgREST requests

major

Apr 28, 09:26 PM→Apr 28, 11:31 PMresolved

Apr 28, 11:31 PM

resolved — This is now resolved. Thank you for your patience while we worked to resolve this issue.

Apr 28, 11:03 PM

monitoring — The exceptions fix has been rolled out, and we are monitoring for continued stability.

Apr 28, 10:24 PM

identified — We are continuing to work on a fix. We’ll share further updates as progress is made.

+3 more updates

Some Projects Unreachable following Project Restart

major

Apr 27, 10:54 AM→Apr 27, 08:05 PMresolved

Apr 27, 08:05 PM

resolved — All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.

Apr 27, 05:31 PM

monitoring — The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.

Apr 27, 04:05 PM

identified — The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.

+5 more updates

Some projects unavailable across multiple regions

major

Apr 27, 12:39 PM→Apr 27, 07:04 PMresolved

Apr 27, 07:04 PM

resolved — This incident has been resolved.

Apr 27, 06:34 PM

monitoring — We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new is...

Apr 27, 04:22 PM

identified — The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all ...

+4 more updates

Inadvertently disabled pg_graphql for some projects

none

Apr 26, 05:52 PM→Apr 26, 05:52 PMresolved

Apr 29, 05:52 PM

resolved — A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to...

Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1

major

Apr 25, 04:16 AM→Apr 25, 05:47 AMresolved

Apr 25, 05:47 AM

resolved — This issue has now been resolved and projects have returned to normal.

Apr 25, 05:14 AM

monitoring — Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.

Apr 25, 04:38 AM

identified — Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event...

+2 more updates

Newly created projects may be unreachable

major

Apr 24, 11:21 AM→Apr 24, 02:36 PMresolved

Apr 24, 02:36 PM

resolved — The issue has been resolved and DNS resolution is now operating normally.

Apr 24, 12:43 PM

monitoring — A fix has been implemented, and we are seeing improvements in DNS resolution. We’re closely monitoring to ensure the issue is fully resolved and services remain stable.

Apr 24, 11:56 AM

identified — We are currently experiencing an issue propagating new DNS records for our zone. We are working closely with our upstream network providers technical team to implement a fix and will share updates as ...

+1 more updates

Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

none

Apr 24, 10:00 AM→Apr 24, 10:00 AMresolved

Apr 28, 08:34 PM

resolved — Incident Summary A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially s...

Increased Errors on HTTP Endpoints

major

Apr 17, 01:02 PM→Apr 18, 02:01 AMresolved

Apr 18, 02:01 AM

resolved — All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident.

Apr 18, 12:37 AM

monitoring — We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a ...

Apr 17, 11:08 PM

identified — We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the...

+15 more updates

Transactional Email Delivery Delays

none

Apr 16, 07:05 PM→Apr 17, 05:00 PMresolved

Apr 17, 05:00 PM

resolved — Email queues have returned to normal.

Apr 16, 08:51 PM

monitoring — Customers will continue to see these delayed transactional emails while we clear the backlog. We will provide another update once these queued emails are sent.

Apr 16, 07:37 PM

monitoring — We have made progress investigating the specific causes of the email spike and are determining appropriate next steps to improve clearance of the backlog.

+1 more updates

Project creation failures in some APAC regions

major

Apr 12, 03:51 PM→Apr 12, 05:03 PMresolved

Apr 12, 05:03 PM

resolved — Capacity has been fully restored in the impacted APAC regions, and project creation is operating normally.

Apr 12, 04:19 PM

monitoring — We are recovering capacity in the impacted APAC regions and are seeing improvements in project creation success rates. We will continue to monitor to ensure stability.

Apr 12, 03:51 PM

investigating — We are currently investigating an issue affecting project creation in some APAC regions. Users may experience failures when attempting to create new projects in impacted regions. Existing projects ar...

Logs currently inaccessible via the Dashboard and Log Drains

critical

Apr 8, 07:10 PM→Apr 8, 08:05 PMresolved

Apr 8, 08:05 PM

resolved — This incident has been resolved.

Apr 8, 07:41 PM

monitoring — All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.

Apr 8, 07:24 PM

identified — The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.

+1 more updates

Increased error rates for plan upgrades

major

Apr 2, 08:28 AM→Apr 2, 09:24 AMresolved

Apr 2, 09:24 AM

resolved — The issue causing increased error rates during plan upgrades has been resolved. All systems are operating normally.

Apr 2, 09:05 AM

monitoring — A fix has been applied, and we are monitoring to ensure stability.

Apr 2, 08:40 AM

identified — We have identified the cause of increased error rates affecting plan upgrades and are working on a fix. We will provide further updates as progress is made.

+1 more updates

Degraded logs ingestion

major

Apr 1, 12:13 AM→Apr 1, 01:11 AMresolved

Apr 1, 01:11 AM

resolved — Log ingestion has recovered and the incident is considered resolved. Some log data was lost during the incident between around 11pm to 11:45pm ETC on March 31.

Apr 1, 12:47 AM

monitoring — We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.

Apr 1, 12:13 AM

investigating — We are seeing degradation of logs and are currently investigating the cause of this issue.

March 2026

Supabase dashboard experiencing intermittent errors in Europe region

minor

Mar 27, 05:58 PM→Mar 27, 06:43 PMresolved

Mar 27, 06:43 PM

resolved — We have confirmed that project creation has returned to normal.

Mar 27, 06:18 PM

monitoring — Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency.

Mar 27, 05:58 PM

identified — We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.

Degraded Log Ingestion

minor

Mar 27, 03:13 PM→Mar 27, 05:03 PMresolved

Mar 27, 05:03 PM

resolved — Log ingestion has returned to normal

Mar 27, 04:17 PM

monitoring — Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.

Mar 27, 04:12 PM

identified — We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.

+3 more updates

Realtime services unavailable

major

Mar 26, 11:41 PM→Mar 27, 02:58 AMresolved

Mar 27, 02:58 AM

resolved — The issue has been resolved and Realtime services have returned to normal.

Mar 27, 02:48 AM

monitoring — The fix has been implemented and we’re monitoring to ensure stability.

Mar 27, 01:44 AM

identified — We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.

+4 more updates

Branching access issues

minor

Mar 24, 03:13 PM→Mar 24, 03:56 PMresolved

Mar 24, 03:56 PM

resolved — Branching access has returned to normal, this issue is resolved.

Mar 24, 03:27 PM

monitoring — The fix has been implemented and branching access has returned to normal.

Mar 24, 03:13 PM

identified — We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is b...

Degraded Logging Ingestion impacting all regions

minor

Mar 23, 04:28 PM→Mar 23, 06:56 PMresolved

Mar 23, 06:56 PM

resolved — This issue is now resolved. All logging ingestion has resumed in all regions.

Mar 23, 05:05 PM

monitoring — A fix has been implemented. The system is now operating normally, and we will continue to monitor.

Mar 23, 04:38 PM

identified — The cause of the issue has been identified. Our engineering team is working on a fix.

+1 more updates

Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

minor

Mar 23, 02:16 PM→Mar 23, 03:42 PMresolved

Mar 23, 03:42 PM

resolved — Error rates have returned to normal. This incident has been resolved.

Mar 23, 02:32 PM

monitoring — We carried out a controlled redeployment of the affected services to restore stability. The system is now operating normally, and we will continue to monitor.

Mar 23, 02:16 PM

investigating — We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Project creation failures across multiple regions

major

Mar 19, 08:55 PM→Mar 19, 10:00 PMresolved

Mar 19, 10:00 PM

resolved — Project creation in all regions are now successful.

Mar 19, 09:21 PM

monitoring — A fix has been implemented and we are monitoring the results.

Mar 19, 09:08 PM

identified — We have identified the issue and a fix is underway.

+1 more updates

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region

minor

Mar 18, 04:27 PM→Mar 18, 06:21 PMresolved

Mar 18, 06:21 PM

resolved — The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.

Mar 18, 05:53 PM

identified — The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.

Mar 18, 05:30 PM

investigating — We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findin...

+2 more updates

Issues propagating Postgres configuration updates

minor

Mar 17, 04:50 AM→Mar 17, 07:41 AMresolved

Mar 17, 07:41 AM

resolved — This incident has been resolved.

Mar 17, 07:07 AM

monitoring — A fix has been implemented and we are monitoring.

Mar 17, 05:11 AM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)

minor

Mar 13, 08:54 AM→Mar 13, 10:19 AMresolved

Mar 13, 10:19 AM

resolved — Error rates have returned to normal, and connectivity has stabilised.

Mar 13, 09:40 AM

monitoring — A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability.

Mar 13, 09:25 AM

investigating — We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.

+1 more updates

Degraded Logging Ingestion impacting all regions

minor

Mar 12, 12:51 PM→Mar 12, 01:53 PMresolved

Mar 12, 01:53 PM

resolved — The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.

Mar 12, 12:54 PM

monitoring — A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to n...

Mar 12, 12:51 PM

investigating — We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime,...

Projects failing to be created

major

Mar 11, 06:08 PM→Mar 11, 07:09 PMresolved

Mar 11, 07:09 PM

resolved — Project creation recovery has been confirmed across all regions. Regional dashboards show error rates returned to normal, and previously failing project creation operations are succeeding again.

Mar 11, 06:47 PM

monitoring — A fix has been implemented and we are seeing project creation recovery across regions. We're moving the incident to monitoring while we confirm full stability.

Mar 11, 06:25 PM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Storage errors in EU-Central-2

minor

Mar 7, 08:12 PM→Mar 7, 09:56 PMresolved

Mar 7, 09:56 PM

resolved — All storage operations have returned to normal.

Mar 7, 09:16 PM

monitoring — The upstream incident has been resolved and we have not observed any additional errors. We will continue to monitor our storage infrastructure for continued stable operations.

Mar 7, 08:44 PM

identified — We are observing storage error rates returning to normal.

+2 more updates

Elevated Management API error rates across all regions

major

Mar 7, 02:48 PM→Mar 7, 04:46 PMresolved

Mar 7, 04:46 PM

resolved — Error rates have returned to baseline and all regions are operating as expected.

Mar 7, 04:16 PM

monitoring — We've seen error rates return to normal levels, and all regions are now holding steady. We will continue to monitor to make sure things remain stable.

Mar 7, 03:51 PM

identified — We are continuing to see some periodic spikes in error rates; however, total rate of errors are decreasing across most regions. We're continuing efforts to get all systems back to green. When error r...

+4 more updates

Subscription Plan changes currently unavailable

minor

Mar 7, 12:10 PM→Mar 7, 01:58 PMresolved

Mar 7, 01:58 PM

resolved — This incident has been resolved.

Mar 7, 01:23 PM

monitoring — A fix has been applied by our upstream provider and we have re-enabled subscription plan upgrades and paid organization creation. We are monitoring to confirm full recovery.

Mar 7, 12:45 PM

investigating — We have temporarily disabled subscription plan upgrades and paid organization creation while we work with our upstream billing provider to resolve the issue. We’ll provide an update as soon as we have...

+1 more updates

Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2

major

Mar 6, 02:26 PM→Mar 6, 07:36 PMresolved

Mar 6, 07:36 PM

resolved — Both regions are now working as usual.

Mar 6, 03:56 PM

monitoring — Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised. We will continue to monitor the systems closely to ensure stability.

Mar 6, 03:46 PM

identified — Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts. We are currently rolling out the fix to the ap-northeast-2 (Seoul) region. Further updates will be pro...

+3 more updates

Related Incident Histories

Get Supabase Outage Alerts

Be the first to know when Supabase go down.