Supabase Outage History

Started May 08, 2026, 12:50 AM UTC· resolved May 09, 2026, 04:49 AM UTC

1. investigating May 08, 2026, 12:50 AM UTC

   Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1

2. identified May 08, 2026, 01:06 AM UTC

   We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone.

3. identified May 08, 2026, 02:05 AM UTC

   We are waiting on a resolution from our upstream provider. We will provide an update in an hour.

4. identified May 08, 2026, 02:30 AM UTC

   We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.

5. identified May 08, 2026, 03:11 AM UTC

   We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider.

6. identified May 08, 2026, 04:21 AM UTC

   We are continuing to work on a fix for this issue.

7. identified May 08, 2026, 05:30 AM UTC

   We are continuing to work on a fix for this issue.

8. identified May 08, 2026, 05:31 AM UTC

   We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects.

9. identified May 08, 2026, 06:44 AM UTC

   Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

10. identified May 08, 2026, 07:59 AM UTC

    Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

11. identified May 08, 2026, 10:52 AM UTC

    Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

12. identified May 08, 2026, 12:09 PM UTC

    Our team is actively working to bring impacted projects back online as quickly and safely as possible. While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider. We appreciate your patience and will continue to share updates as more information becomes available.

13. identified May 08, 2026, 04:34 PM UTC

    Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.

14. identified May 09, 2026, 01:32 AM UTC

    Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.

15. identified May 09, 2026, 04:10 AM UTC

    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 automatically self-heal during recovery and is actively restoring them manually where needed. We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region. We are continuing to monitor platform stability closely and will provide additional updates as recovery progresses.

16. monitoring May 09, 2026, 04:34 AM UTC

    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, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability.

17. resolved May 09, 2026, 04:49 AM UTC

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

Read the full incident report →

Started May 03, 2026, 10:30 PM UTC· resolved May 03, 2026, 10:30 PM UTC

1. resolved May 04, 2026, 04:58 PM UTC

   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 failed errors. This has been resolved and Supavisor is fully available.

Read the full incident report →

Started Apr 28, 2026, 09:26 PM UTC· resolved Apr 28, 2026, 11:31 PM UTC

1. investigating Apr 28, 2026, 09:26 PM UTC

   We are investigating 403 errors for PostgREST requests across multiple regions.

2. identified Apr 28, 2026, 09:36 PM UTC

   The issue has been identified and we are working on a fix.

3. identified Apr 28, 2026, 09:40 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Apr 28, 2026, 10:24 PM UTC

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

5. monitoring Apr 28, 2026, 11:03 PM UTC

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

6. resolved Apr 28, 2026, 11:31 PM UTC

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

Read the full incident report →

Started Apr 27, 2026, 12:39 PM UTC· resolved Apr 27, 2026, 07:04 PM UTC

1. identified Apr 27, 2026, 12:39 PM UTC

   Posting this. “We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects”

2. identified Apr 27, 2026, 01:31 PM UTC

   The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the dashboard for your own projects at any time.

3. identified Apr 27, 2026, 01:38 PM UTC

   We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the dashboard for your own projects at any time.

4. identified Apr 27, 2026, 03:00 PM UTC

   The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the dashboard for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.

5. identified Apr 27, 2026, 04:22 PM UTC

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

6. monitoring Apr 27, 2026, 06:34 PM UTC

   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 issues arise. We appreciate your patience as we worked through this issue.

7. resolved Apr 27, 2026, 07:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 10:54 AM UTC· resolved Apr 27, 2026, 08:05 PM UTC

1. identified Apr 27, 2026, 10:54 AM UTC

   We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service.

2. identified Apr 27, 2026, 11:11 AM UTC

   We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

3. identified Apr 27, 2026, 11:40 AM UTC

   Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

4. monitoring Apr 27, 2026, 01:12 PM UTC

   All impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates.

5. identified Apr 27, 2026, 02:21 PM UTC

   We’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact.

6. identified Apr 27, 2026, 04:05 PM UTC

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

7. monitoring Apr 27, 2026, 05:31 PM UTC

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

8. resolved Apr 27, 2026, 08:05 PM UTC

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

Read the full incident report →

Started Apr 26, 2026, 05:52 PM UTC· resolved Apr 26, 2026, 05:52 PM UTC

1. resolved Apr 29, 2026, 05:52 PM UTC

   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 disable pg_graphql for projects that had not seen usage in the last 30 days. Due to a misconfiguration, this targeted more projects than intended. We are deeply sorry for the inconvenience and have since addressed the issue. For those using pg_graphql actively, you may have seen pg_graphql extension is not enabled in the logs for your project and you can safely re-enable this. If you have been impacted, or you are unable to re-enable pg_graphql, please contact [email protected]

Read the full incident report →

Started Apr 25, 2026, 04:16 AM UTC· resolved Apr 25, 2026, 05:47 AM UTC

1. identified Apr 25, 2026, 04:16 AM UTC

   We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information.

2. identified Apr 25, 2026, 04:26 AM UTC

   US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions.

3. identified Apr 25, 2026, 04:38 AM UTC

   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.

4. monitoring Apr 25, 2026, 05:14 AM UTC

   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.

5. resolved Apr 25, 2026, 05:47 AM UTC

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

Read the full incident report →

Started Apr 24, 2026, 11:21 AM UTC· resolved Apr 24, 2026, 02:36 PM UTC

1. investigating Apr 24, 2026, 11:21 AM UTC

   We are currently investigating reports that newly created projects may be unreachable. Initial findings indicate DNS resolution failures. We will provide an update as soon as more information is available.

2. identified Apr 24, 2026, 11:56 AM UTC

   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 we learn more.

3. monitoring Apr 24, 2026, 12:43 PM UTC

   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.

4. resolved Apr 24, 2026, 02:36 PM UTC

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

Read the full incident report →

Started Apr 24, 2026, 10:00 AM UTC· resolved Apr 24, 2026, 10:00 AM UTC

1. resolved Apr 28, 2026, 08:34 PM UTC

   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 surfaced under a generic SUPABASE_EDGE_RUNTIME_ERROR code. Timeline & Actions Sunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began. Monday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact. Tuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed). Current Status Mitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.

Read the full incident report →

Started Apr 17, 2026, 02:53 PM UTC· resolved Apr 18, 2026, 02:01 AM UTC

1. investigating Apr 17, 2026, 01:02 PM UTC

   We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.

2. investigating Apr 17, 2026, 01:31 PM UTC

   We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.

3. investigating Apr 17, 2026, 01:51 PM UTC

   We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America.

4. investigating Apr 17, 2026, 02:16 PM UTC

   We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as more information becomes available.

5. investigating Apr 17, 2026, 02:30 PM UTC

   We continue to work with partners and investigate.

6. investigating Apr 17, 2026, 02:53 PM UTC

   We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints

7. identified Apr 17, 2026, 03:09 PM UTC

   Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available.

8. identified Apr 17, 2026, 03:41 PM UTC

   Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information.

9. identified Apr 17, 2026, 04:31 PM UTC

   Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider.

10. identified Apr 17, 2026, 05:44 PM UTC

    Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information.

11. identified Apr 17, 2026, 06:34 PM UTC

    Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved.

12. identified Apr 17, 2026, 07:33 PM UTC

    The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them.

13. monitoring Apr 17, 2026, 08:10 PM UTC

    Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes.

14. identified Apr 17, 2026, 08:35 PM UTC

    Some users continue to experience errors. We are raising the issue with our provider.

15. identified Apr 17, 2026, 09:31 PM UTC

    We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved.

16. identified Apr 17, 2026, 11:08 PM UTC

    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 moment. We'll keep working on this until we have for sure reached a resolution.

17. monitoring Apr 18, 2026, 12:37 AM UTC

    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 bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience.

18. resolved Apr 18, 2026, 02:01 AM UTC

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

Read the full incident report →

Started Apr 16, 2026, 07:05 PM UTC· resolved Apr 17, 2026, 05:00 PM UTC

1. monitoring Apr 16, 2026, 07:05 PM UTC

   We are experiencing delays in delivery of some of our email to customers related to transactions, including new welcome, oauth-approved, project-shutdown, and payment-failure notifications. This has caused some customers to receive notifications after their issue has been resolved (for example, payment failure notifications after payment has been issued). We are actively monitoring the email delivery queue and expect the delays to be eliminated over time. We will update this status as appropriate.

2. monitoring Apr 16, 2026, 07:37 PM UTC

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

3. monitoring Apr 16, 2026, 08:51 PM UTC

   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.

4. resolved Apr 17, 2026, 05:00 PM UTC

   Email queues have returned to normal.

Read the full incident report →

Started Apr 12, 2026, 03:51 PM UTC· resolved Apr 12, 2026, 05:03 PM UTC

1. investigating Apr 12, 2026, 03:51 PM UTC

   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 are not impacted. Our team is actively working to mitigate the issue and restore normal availability. We will share further updates as more information becomes available.

2. monitoring Apr 12, 2026, 04:19 PM UTC

   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.

3. resolved Apr 12, 2026, 05:03 PM UTC

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

Read the full incident report →

Started Apr 08, 2026, 07:10 PM UTC· resolved Apr 08, 2026, 08:05 PM UTC

1. identified Apr 08, 2026, 07:11 PM UTC

   Users may see errors when attempting to retrieve logs via the Supabase dashboard or may not see new logs arriving via log drains. The team has identified the issue and is working on a fix. Underlying projects are unaffected, this is only affecting the logging service.

2. identified Apr 08, 2026, 07:24 PM UTC

   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.

3. monitoring Apr 08, 2026, 07:41 PM UTC

   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.

4. resolved Apr 08, 2026, 08:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 02, 2026, 08:28 AM UTC· resolved Apr 02, 2026, 09:24 AM UTC

1. investigating Apr 02, 2026, 08:28 AM UTC

   We are currently investigating increased error rates affecting plan upgrades. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.

2. identified Apr 02, 2026, 08:40 AM UTC

   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.

3. monitoring Apr 02, 2026, 09:05 AM UTC

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

4. resolved Apr 02, 2026, 09:24 AM UTC

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

Read the full incident report →

Started Apr 01, 2026, 12:13 AM UTC· resolved Apr 01, 2026, 01:11 AM UTC

1. investigating Apr 01, 2026, 12:13 AM UTC

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

2. monitoring Apr 01, 2026, 12:47 AM UTC

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

3. resolved Apr 01, 2026, 01:11 AM UTC

   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.

Read the full incident report →

Started Mar 27, 2026, 05:58 PM UTC· resolved Mar 27, 2026, 06:43 PM UTC

1. identified Mar 27, 2026, 05:58 PM UTC

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

2. monitoring Mar 27, 2026, 06:18 PM UTC

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

3. resolved Mar 27, 2026, 06:43 PM UTC

   We have confirmed that project creation has returned to normal.

Read the full incident report →

Started Mar 27, 2026, 03:13 PM UTC· resolved Mar 27, 2026, 05:03 PM UTC

1. investigating Mar 27, 2026, 03:13 PM UTC

   We are investigating a problem with log ingestion. Users may experience delay in current log data.

2. identified Mar 27, 2026, 03:33 PM UTC

   We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.

3. identified Mar 27, 2026, 03:52 PM UTC

   We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.

4. identified Mar 27, 2026, 04:12 PM UTC

   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.

5. monitoring Mar 27, 2026, 04:17 PM UTC

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

6. resolved Mar 27, 2026, 05:03 PM UTC

   Log ingestion has returned to normal

Read the full incident report →

Started Mar 26, 2026, 11:41 PM UTC· resolved Mar 27, 2026, 02:58 AM UTC

1. investigating Mar 26, 2026, 11:41 PM UTC

   We are investigating network connectivity issues with Realtime.”

2. investigating Mar 27, 2026, 12:20 AM UTC

   We're still investigating network connectivity issues with Realtime.

3. identified Mar 27, 2026, 12:46 AM UTC

   We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.

4. identified Mar 27, 2026, 01:13 AM UTC

   We are working on a fix and we’ll continue to provide updates as progress is made.

5. identified Mar 27, 2026, 01:44 AM UTC

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

6. monitoring Mar 27, 2026, 02:48 AM UTC

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

7. resolved Mar 27, 2026, 02:58 AM UTC

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

Read the full incident report →

Started Mar 24, 2026, 03:13 PM UTC· resolved Mar 24, 2026, 03:56 PM UTC

1. identified Mar 24, 2026, 03:13 PM UTC

   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 being deployed. We will provide an update once resolved.

2. monitoring Mar 24, 2026, 03:27 PM UTC

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

3. resolved Mar 24, 2026, 03:56 PM UTC

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

Read the full incident report →

Started Mar 23, 2026, 04:28 PM UTC· resolved Mar 23, 2026, 06:56 PM UTC

1. investigating Mar 23, 2026, 04:28 PM UTC

   We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services. Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all. Projects remain fully functional. This issue is limited to logging only. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will provide further updates as more information becomes available.

2. identified Mar 23, 2026, 04:38 PM UTC

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

3. monitoring Mar 23, 2026, 05:05 PM UTC

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

4. resolved Mar 23, 2026, 06:56 PM UTC

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

Read the full incident report →

Started Mar 23, 2026, 02:16 PM UTC· resolved Mar 23, 2026, 03:42 PM UTC

1. investigating Mar 23, 2026, 02:16 PM UTC

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

2. monitoring Mar 23, 2026, 02:32 PM UTC

   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.

3. resolved Mar 23, 2026, 03:42 PM UTC

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

Read the full incident report →

Started Mar 19, 2026, 08:55 PM UTC· resolved Mar 19, 2026, 10:00 PM UTC

1. investigating Mar 19, 2026, 08:55 PM UTC

   We are currently investigating project creation failures across multiple regions.

2. identified Mar 19, 2026, 09:08 PM UTC

   We have identified the issue and a fix is underway.

3. monitoring Mar 19, 2026, 09:21 PM UTC

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

4. resolved Mar 19, 2026, 10:00 PM UTC

   Project creation in all regions are now successful.

Read the full incident report →

Started Mar 18, 2026, 04:27 PM UTC· resolved Mar 18, 2026, 06:21 PM UTC

1. investigating Mar 18, 2026, 04:27 PM UTC

   We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time. We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.

2. investigating Mar 18, 2026, 04:58 PM UTC

   We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time. Our team is actively working to determine the root cause and assess the full impact. We will provide further updates as more information becomes available.

3. investigating Mar 18, 2026, 05:30 PM UTC

   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 findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry. Our team is actively working to determine the root cause and will provide further updates as more information becomes available.

4. identified Mar 18, 2026, 05:53 PM UTC

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

5. resolved Mar 18, 2026, 06:21 PM UTC

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

Read the full incident report →

Started Mar 17, 2026, 04:50 AM UTC· resolved Mar 17, 2026, 07:41 AM UTC

1. investigating Mar 17, 2026, 04:50 AM UTC

   Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.

2. identified Mar 17, 2026, 05:11 AM UTC

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

3. monitoring Mar 17, 2026, 07:07 AM UTC

   A fix has been implemented and we are monitoring.

4. resolved Mar 17, 2026, 07:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 13, 2026, 08:54 AM UTC· resolved Mar 13, 2026, 10:19 AM UTC

1. investigating Mar 13, 2026, 08:54 AM UTC

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

2. investigating Mar 13, 2026, 09:25 AM UTC

   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.

3. monitoring Mar 13, 2026, 09:40 AM UTC

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

4. resolved Mar 13, 2026, 10:19 AM UTC

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

Read the full incident report →