Supabase Outage History
50 incidents reported. Data sourced from the official Supabase status page.
50
Total Incidents
16
Major/Critical
25
Minor
50
Resolved
June 2026
Project status change failures in multiple regions
majorJun 30, 02:38 AM→Jul 13, 04:00 PMresolved
Jul 13, 04:00 PM
resolved — Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident.
Out of an a...
Jul 10, 06:41 PM
monitoring — We continue to monitor capacity across all regions.
The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to impr...
Jul 8, 04:41 PM
monitoring — We continue to monitor capacity recovery across all regions.
We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these u...
+24 more updates
Connection issues in Supavisor us-east-1 cluster
noneJun 30, 04:56 PM→Jun 30, 06:01 PMresolved
Jun 30, 06:01 PM
resolved — We have not observed any increased rates of connection problems on the us-east-1 Supavisor cluster during our monitoring period. We are confident that the incident is resolved.
Jun 30, 05:06 PM
monitoring — We believe the issue has resolved. We are monitoring for any recurrence.
Jun 30, 04:56 PM
investigating — We have detected increased rates of connection issues in a us-east-1 Supavisor cluster starting at 14:10 UTC. Our team is currently investigating.
Upgrade Failures
minorJun 25, 02:20 PM→Jun 25, 06:51 PMresolved
Jun 25, 06:51 PM
resolved — Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
Jun 25, 06:08 PM
monitoring — We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degrad...
Jun 25, 05:46 PM
identified — We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we obse...
+7 more updates
Elevated errors on Postgres change subscriptions
minorJun 24, 11:52 PM→Jun 25, 02:16 AMresolved
Jun 25, 02:16 AM
resolved — We have confirmed that the fix has been successfully applied and the issue affecting Postgres Change subscriptions has been resolved. We will continue to monitor the service, but all systems are opera...
Jun 25, 12:49 AM
monitoring — We have applied a fix and are monitoring the results to ensure the issue is fully resolved.
Jun 24, 11:58 PM
identified — We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information ...
+1 more updates
Degraded performance of the Shared Pooler cluster in ap-southeast-1
minorJun 24, 03:59 PM→Jun 24, 04:14 PMresolved
Jun 24, 04:14 PM
resolved — One of the processes in the ap-southeast-1 Supavisor cluster became overloaded, causing difficulties in starting new pools.
We restarted a node to stabilize the cluster and scaled the cluster up. The...
Jun 24, 03:59 PM
investigating — We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries.
The window of th...
Project create and unpause errors in eu-west-1
minorJun 23, 03:16 PM→Jun 23, 04:32 PMresolved
Jun 23, 04:32 PM
resolved — Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.
Jun 23, 04:01 PM
monitoring — Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 ...
Jun 23, 03:46 PM
identified — During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
+3 more updates
Increased latency for Management API requests
minorJun 23, 01:21 PM→Jun 23, 02:19 PMresolved
Jun 23, 02:19 PM
resolved — This incident has been resolved.
Jun 23, 01:39 PM
monitoring — Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
Jun 23, 01:21 PM
identified — We are seeing increased latency on management API requests, which results in slower-than-usual Dashboard performance, project creation and configuration changes may also be delayed. This is primarily ...
Failed to apply network restrictions
minorJun 19, 09:55 PM→Jun 20, 12:58 AMresolved
Jun 20, 12:58 AM
resolved — We are not detecting any remaining network restriction list issues.
Jun 20, 12:48 AM
monitoring — We have now deployed a fix for this issue across all regions, and we believe this issue to be resolved. We are continuing to monitor for any remaining issues. Please contact Support if you are experie...
Jun 19, 11:39 PM
monitoring — We have started deploying a fix for the issue and are validating the results as the rollout progresses. We will continue to provide updates as we move toward full resolution.
+2 more updates
DNS record creation failures impacting project creation, restore, pause
majorJun 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
minorJun 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
majorJun 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
minorJun 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
minorJun 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
noneJun 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
minorJun 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
noneJun 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)
criticalJun 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
July 2026
Degraded log ingestion
minorJul 9, 11:34 PM→Jul 10, 03:48 AMresolved
Jul 10, 03:48 AM
resolved — This issue has been resolved. Log ingestion and log visibility have returned to normal operation.
If you experience missing or delayed logs from the affected time period, please contact Support and w...
Jul 10, 03:03 AM
monitoring — We have implemented a fix for the issue affecting log visibility that began at approximately 22:15 UTC. Log ingestion has returned to normal. We are monitoring the system to ensure the issue is fully ...
Jul 10, 02:53 AM
identified — We've identified the issue and are implementing a fix.
If you need access to logs from the affected period (starting at approximately 22:15 UTC), please contact Support and we will work with you to ...
+4 more updates
Elevated JWT authorization errors
minorJul 8, 06:37 PM→Jul 8, 07:57 PMresolved
Jul 8, 07:57 PM
resolved — Edge function operations are normal.
Jul 8, 07:28 PM
monitoring — A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance.
Jul 8, 07:16 PM
identified — We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects.
+1 more updates
Project creation delays in AP regions
minorJul 8, 04:52 PM→Jul 8, 07:30 PMresolved
Jul 8, 07:30 PM
resolved — Project creation has returned to normal. The issue is now resolved.
Jul 8, 06:59 PM
monitoring — Recovery has continued and project creation in the relevant region has returned to normal. We will continue to monitor this for another 30 minutes.
Jul 8, 06:42 PM
identified — Project creation is recovering. We are actively tracking recovery.
+4 more updates
Endpoints in Americas regions returning 500 Internal server error
majorJul 6, 02:45 PM→Jul 6, 04:10 PMresolved
Jul 6, 04:10 PM
resolved — Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.
Jul 6, 03:42 PM
monitoring — The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.
Jul 6, 03:15 PM
identified — We have identified the cause of the 500 errors and are implementing a fix.
+3 more updates
Degraded project creation success rates in the ca-central-1 region
minorJul 2, 10:59 PM→Jul 3, 04:51 AMresolved
Jul 3, 04:51 AM
resolved — The project creation in ca-central-1 has been restored.
Jul 3, 02:56 AM
monitoring — We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.
Jul 3, 02:13 AM
identified — We are redirecting project creation to more healthy regions and working to continue to increase the success rate in ca-central-1.
A longer startup time is expected while project creation is recoveri...
+3 more updates
Errors when attempting to view advisor results in the Supabase dashboard
minorJul 2, 02:26 PM→Jul 2, 05:14 PMresolved
Jul 2, 05:14 PM
resolved — This issue is resolved and advisor results are now available in the Dashboard.
Jul 2, 04:53 PM
monitoring — We've deployed the fix and are now monitoring the issue.
Jul 2, 03:42 PM
identified — We continue to work on a fix for advisor results in the Dashboard. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboar...
+1 more updates
Issues with Restore to New Project
noneJul 1, 03:16 PM→Jul 1, 07:04 PMresolved
Jul 1, 07:04 PM
resolved — We've rolled out a fix for the R2NP issue, and users should be able to execute the flow again.
Jul 1, 03:16 PM
identified — We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue....
Delays in newly created project setup
minorJul 1, 05:39 PM→Jul 1, 06:56 PMresolved
Jul 1, 06:56 PM
resolved — This issue is now resolved. Provisioning times and project lifecycle operations have returned to normal.
Jul 1, 06:40 PM
monitoring — Provisioning times and project lifecycle operations have returned normal. We will continue to monitor.
Jul 1, 05:39 PM
identified — We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects.
Customers may experience longer than expected provisioning times after c...
Functions management API is returning 500s for multiple function operations
majorJul 1, 02:40 PM→Jul 1, 04:12 PMresolved
Jul 1, 04:12 PM
resolved — Edge Function API requests have returned to normal. This issue is now resolved.
Jul 1, 03:30 PM
monitoring — We have implemented a fix, and error rates have returned to expected levels.
We are continuing to monitor the platform closely to ensure the issue is fully resolved.
Jul 1, 02:59 PM
identified — The team has identified the root cause of the issue and is currently rolling out a fix across the platform.
We will continue to monitor the rollout and provide another update once it has been complete...
+1 more updates
May 2026
Access Issues From Some Providers in Brazil
noneMay 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
minorMay 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
minorMay 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
minorMay 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
minorMay 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
minorMay 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
noneMay 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
minorMay 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
minorMay 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
majorMay 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
minorMay 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
minorMay 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
majorApr 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
majorApr 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
majorApr 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
noneApr 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
majorApr 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
majorApr 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
noneApr 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
majorApr 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
noneApr 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
majorApr 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
criticalApr 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
majorApr 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
Related Incident Histories
Get Supabase Outage Alerts
Be the first to know when Supabase go down.