Supabase Outage History

Supabase is up right now

Supabase had 77 outages in the last 2 years totaling 73h 58m of downtime — averaging 3.2 incidents per month.

There were 77 Supabase outages since December 24, 2025 totaling 73h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.supabase.com

Notice April 26, 2026

Inadvertently disabled pg_graphql for some projects

Detected by Pingoru
Apr 26, 2026, 05:52 PM UTC
Resolved
Apr 26, 2026, 05:52 PM UTC
Duration
Timeline · 1 update
  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 →

Major April 25, 2026

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

Detected by Pingoru
Apr 25, 2026, 04:16 AM UTC
Resolved
Apr 25, 2026, 05:47 AM UTC
Duration
1h 30m
Affected: ap-northeast-1us-east-2
Timeline · 5 updates
  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 →

Major April 24, 2026

Newly created projects may be unreachable

Detected by Pingoru
Apr 24, 2026, 11:21 AM UTC
Resolved
Apr 24, 2026, 02:36 PM UTC
Duration
3h 15m
Affected: Dashboard
Timeline · 4 updates
  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 →

Notice April 16, 2026

Transactional Email Delivery Delays

Detected by Pingoru
Apr 16, 2026, 07:05 PM UTC
Resolved
Apr 17, 2026, 05:00 PM UTC
Duration
21h 54m
Timeline · 4 updates
  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 →

Major April 12, 2026

Project creation failures in some APAC regions

Detected by Pingoru
Apr 12, 2026, 03:51 PM UTC
Resolved
Apr 12, 2026, 05:03 PM UTC
Duration
1h 12m
Affected: ap-south-1ap-southeast-1
Timeline · 3 updates
  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 →

Critical April 8, 2026

Logs currently inaccessible via the Dashboard and Log Drains

Detected by Pingoru
Apr 08, 2026, 07:10 PM UTC
Resolved
Apr 08, 2026, 08:05 PM UTC
Duration
54m
Affected: Analytics
Timeline · 4 updates
  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 →

Major April 2, 2026

Increased error rates for plan upgrades

Detected by Pingoru
Apr 02, 2026, 08:28 AM UTC
Resolved
Apr 02, 2026, 09:24 AM UTC
Duration
56m
Affected: Dashboard
Timeline · 4 updates
  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 →

Major April 1, 2026

Degraded logs ingestion

Detected by Pingoru
Apr 01, 2026, 12:13 AM UTC
Resolved
Apr 01, 2026, 01:11 AM UTC
Duration
58m
Affected: Analytics
Timeline · 3 updates
  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 →

Minor March 27, 2026

Supabase dashboard experiencing intermittent errors in Europe region

Detected by Pingoru
Mar 27, 2026, 05:58 PM UTC
Resolved
Mar 27, 2026, 06:43 PM UTC
Duration
44m
Timeline · 3 updates
  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 →

Minor March 27, 2026

Degraded Log Ingestion

Detected by Pingoru
Mar 27, 2026, 03:13 PM UTC
Resolved
Mar 27, 2026, 05:03 PM UTC
Duration
1h 50m
Timeline · 6 updates
  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 →

Major March 26, 2026

Realtime services unavailable

Detected by Pingoru
Mar 26, 2026, 11:41 PM UTC
Resolved
Mar 27, 2026, 02:58 AM UTC
Duration
3h 17m
Affected: Realtime
Timeline · 7 updates
  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 →

Minor March 24, 2026

Branching access issues

Detected by Pingoru
Mar 24, 2026, 03:13 PM UTC
Resolved
Mar 24, 2026, 03:56 PM UTC
Duration
43m
Timeline · 3 updates
  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 →

Minor March 23, 2026

Degraded Logging Ingestion impacting all regions

Detected by Pingoru
Mar 23, 2026, 04:28 PM UTC
Resolved
Mar 23, 2026, 06:56 PM UTC
Duration
2h 27m
Affected: Analytics
Timeline · 4 updates
  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 →

Minor March 23, 2026

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

Detected by Pingoru
Mar 23, 2026, 02:16 PM UTC
Resolved
Mar 23, 2026, 03:42 PM UTC
Duration
1h 25m
Affected: Edge Functions
Timeline · 3 updates
  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 →

Major March 19, 2026

Project creation failures across multiple regions

Detected by Pingoru
Mar 19, 2026, 08:55 PM UTC
Resolved
Mar 19, 2026, 10:00 PM UTC
Duration
1h 4m
Affected: Management API
Timeline · 4 updates
  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 →

Minor March 18, 2026

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

Detected by Pingoru
Mar 18, 2026, 04:27 PM UTC
Resolved
Mar 18, 2026, 06:21 PM UTC
Duration
1h 54m
Affected: Storage
Timeline · 5 updates
  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 →

Minor March 17, 2026

Issues propagating Postgres configuration updates

Detected by Pingoru
Mar 17, 2026, 04:50 AM UTC
Resolved
Mar 17, 2026, 07:41 AM UTC
Duration
2h 50m
Timeline · 4 updates
  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 →

Minor March 13, 2026

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

Detected by Pingoru
Mar 13, 2026, 08:54 AM UTC
Resolved
Mar 13, 2026, 10:19 AM UTC
Duration
1h 24m
Affected: Connection Pooler
Timeline · 4 updates
  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 →

Major March 11, 2026

Projects failing to be created

Detected by Pingoru
Mar 11, 2026, 06:08 PM UTC
Resolved
Mar 11, 2026, 07:09 PM UTC
Duration
1h
Affected: Management API
Timeline · 4 updates
  1. investigating Mar 11, 2026, 06:08 PM UTC

    We are currently investigating reports of projects failing to be created.

  2. identified Mar 11, 2026, 06:25 PM UTC

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

  3. monitoring Mar 11, 2026, 06:47 PM UTC

    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.

  4. resolved Mar 11, 2026, 07:09 PM UTC

    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.

Read the full incident report →

Minor March 7, 2026

Storage errors in EU-Central-2

Detected by Pingoru
Mar 07, 2026, 08:12 PM UTC
Resolved
Mar 07, 2026, 09:56 PM UTC
Duration
1h 43m
Affected: Storage
Timeline · 5 updates
  1. investigating Mar 07, 2026, 08:12 PM UTC

    We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating.

  2. identified Mar 07, 2026, 08:22 PM UTC

    We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue.

  3. identified Mar 07, 2026, 08:44 PM UTC

    We are observing storage error rates returning to normal.

  4. monitoring Mar 07, 2026, 09:16 PM UTC

    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.

  5. resolved Mar 07, 2026, 09:56 PM UTC

    All storage operations have returned to normal.

Read the full incident report →

Major March 7, 2026

Elevated Management API error rates across all regions

Detected by Pingoru
Mar 07, 2026, 02:48 PM UTC
Resolved
Mar 07, 2026, 04:46 PM UTC
Duration
1h 58m
Affected: DashboardManagement API
Timeline · 7 updates
  1. investigating Mar 07, 2026, 02:48 PM UTC

    We are currently investigating the cause, but users may see issues creating projects across all regions. Existing projects are not affected and remain up and stable.

  2. investigating Mar 07, 2026, 02:59 PM UTC

    We've expanded this to all management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions would also be impacted. Error rates are currently improving, but the team is investigating the root cause to ensure continued stability. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  3. identified Mar 07, 2026, 03:04 PM UTC

    We have identified the source of the increased error rates, and are working on a fix now. All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  4. identified Mar 07, 2026, 03:23 PM UTC

    The team is continuing to deploy mitigations, and we are seeing error rates improve, but are not back to baseline yet. All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  5. identified Mar 07, 2026, 03:51 PM UTC

    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 rates spike, management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  6. monitoring Mar 07, 2026, 04:16 PM UTC

    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.

  7. resolved Mar 07, 2026, 04:46 PM UTC

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

Read the full incident report →

Minor March 7, 2026

Subscription Plan changes currently unavailable

Detected by Pingoru
Mar 07, 2026, 12:10 PM UTC
Resolved
Mar 07, 2026, 01:58 PM UTC
Duration
1h 48m
Timeline · 4 updates
  1. investigating Mar 07, 2026, 12:10 PM UTC

    We are currently experiencing issues with subscription plan changes and have contacted our upstream billing provider to help investigate. Subscription Plan changes are temporarily disabled while we investigate.

  2. investigating Mar 07, 2026, 12:45 PM UTC

    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 more information.

  3. monitoring Mar 07, 2026, 01:23 PM UTC

    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.

  4. resolved Mar 07, 2026, 01:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 6, 2026

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

Detected by Pingoru
Mar 06, 2026, 02:26 PM UTC
Resolved
Mar 06, 2026, 07:36 PM UTC
Duration
5h 9m
Affected: Edge Functions
Timeline · 6 updates
  1. investigating Mar 06, 2026, 02:26 PM UTC

    We are currently investigating the cause for increased response times.

  2. investigating Mar 06, 2026, 02:47 PM UTC

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

  3. investigating Mar 06, 2026, 03:17 PM UTC

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

  4. identified Mar 06, 2026, 03:46 PM UTC

    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 provided as the rollout continues.

  5. monitoring Mar 06, 2026, 03:56 PM UTC

    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.

  6. resolved Mar 06, 2026, 07:36 PM UTC

    Both regions are now working as usual.

Read the full incident report →

Critical March 4, 2026

Supabase Dashboard and Management API inaccessible

Detected by Pingoru
Mar 04, 2026, 10:16 AM UTC
Resolved
Mar 04, 2026, 01:00 PM UTC
Duration
2h 43m
Affected: DashboardManagement API
Timeline · 4 updates
  1. investigating Mar 04, 2026, 10:16 AM UTC

    Existing projects seem to be unaffected

  2. identified Mar 04, 2026, 10:30 AM UTC

    We've identified and reverted the change that is causing the issue, and are in the process of recovering the systems affected. Existing projects are unaffected.

  3. monitoring Mar 04, 2026, 10:36 AM UTC

    Service has been fully recovered and we're continuing to monitor.

  4. resolved Mar 04, 2026, 01:00 PM UTC

    This incident has been resolved.

Read the full incident report →