Supabase

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

• Intermittent 502/503 errors for pg_net calls to Edge FunctionsNov 5 23:12 UTC · resolved · minor impact
  Restoration reported
  1. Nov 5 23:12 UTC investigating: We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.
  2. Nov 5 23:55 UTC resolved: The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.
• Storage issues in us-east-1 and eu-central-1Nov 4 18:43 UTC · resolved · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Nov 4 18:43 UTC investigating: We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
  2. Nov 4 19:18 UTC investigating: We are still investigating increased error rates for storage requests, and have expanded the investigation to eu-central-1 as well. The team has identified higher-than-usual load in some areas of the storage infrastructure and is currently working on remediation options.
  3. Nov 4 20:05 UTC monitoring: The cause of the issue has been identified as directly related to load. We will be doing maintenance on our platform to address this issue. As of now, storage response has returned to normal. We will continue to monitor the environment.
  4. Nov 4 21:53 UTC monitoring: We will be conducting maintenance to address storage service improvements between 0800 and 0900 UTC on 5 November 2026. There may be an interruption of storage services in us-east-1 at some point during that window. The impact will be of a short duration and limited to us-east-1.
  5. Nov 5 08:30 UTC monitoring: The planned database capacity increase for Storage in us-east-1 was completed at 08:06 UTC. Some requests to Storage in us-east-1 may have failed briefly while the database switched over during the change. Storage in us east-1 and eu-central-1 is operating normally. We are...
  6. Nov 5 11:02 UTC resolved: The incident has been resolved.
• Intermittent errors on Supavisor Shared Pooler in us-east-2Nov 4 03:48 UTC · resolved · minor impact
  No classified wording
  1. Nov 4 03:48 UTC monitoring: Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" =>...
  2. Nov 4 04:17 UTC resolved: Errors have subsided and connections are back to normal.
• Management API Postgres config updates overwriting previous updatesNov 3 04:56 UTC · resolved
  Service taken offlineRestoration reported
  1. Nov 3 04:56 UTC investigating: We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management...
  2. Nov 3 05:16 UTC investigating: We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.
  3. Nov 3 06:17 UTC monitoring: We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
  4. Nov 3 06:24 UTC monitoring: A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
  5. Nov 3 07:04 UTC resolved: Connection Logging feature is working fine for all customers now.
• Storage uploads failing in us-east-1Nov 2 21:34 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Nov 2 21:34 UTC investigating: We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.
  2. Nov 2 21:48 UTC identified: We have identified the issue causing Storage uploads to fail and are working on a fix. We will provide more updates as things progress.
  3. Nov 2 22:23 UTC monitoring: The fix has been implemented, and we are seeing Storage uploads return to normal. We will continue monitoring to ensure stability.
  4. Nov 2 22:48 UTC resolved: Storage uploads have remained stable, and this issue is now resolved.
• PG15 -> PG17 Upgrade FailuresOct 31 20:06 UTC · resolved
  Investigation mentionedRestoration reported
  1. Oct 31 20:06 UTC identified: We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
  2. Oct 31 20:42 UTC monitoring: We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
  3. Oct 31 21:14 UTC resolved: This issue is now resolved.
• Logs degraded in multiple regionsOct 30 11:38 UTC · resolved
  Service restricted or degradedInvestigation mentioned
  1. Oct 30 11:38 UTC investigating: We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API. Other services, including your database and APIs, are not affected at this time. Our team is actively...
  2. Oct 30 11:56 UTC identified: We have identified the cause of the Logs degradation and a fix is being prepared. Other services remain unaffected. We'll post another update as soon as we have one.
  3. Oct 30 12:11 UTC monitoring: A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.
  4. Oct 30 12:29 UTC resolved: We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
• Delayed Log Delivery from 14:10 - 15:30 UTCOct 28 16:21 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  1. Oct 28 16:21 UTC monitoring: Between 14:10 - 15:30 UTC we have experienced an issue in delivering logs, leading to a delay of about 7–8 minutes. Most affected events have now been recovered - a small subset of events is still being re-inserted and we will confirm once completed.
  2. Oct 28 17:13 UTC resolved: This issue has been resolved and log delivery is operational again.
• Log Drain IssuesOct 22 18:03 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Oct 22 18:03 UTC investigating: Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
  2. Oct 22 18:22 UTC monitoring: The rollback has restored log drains to normal operation. We will monitor for continued functionality.
  3. Oct 22 18:50 UTC resolved: This issue is now resolved.
• Elevated Mgmt API Error Rates in Multiple RegionsOct 22 17:01 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Oct 22 17:01 UTC investigating: We have noticed issues with requests coming to our API gateway. We are investigating.
  2. Oct 22 17:28 UTC identified: We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
  3. Oct 22 17:57 UTC monitoring: The mitigations have managed the demand spike. We are monitoring for continued stability.
  4. Oct 22 18:17 UTC monitoring: We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
  5. Oct 23 10:54 UTC monitoring: We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
  6. Oct 26 10:16 UTC resolved: This issue has been resolved and our response times are back to operational.
• Elevated Mgmt API Error Rates in Multiple RegionsOct 22 11:29 UTC · resolved · major impact
  Sign-in disruptionInvestigation mentionedRestoration reported
• Project lifecycle operation errors in the EU regionOct 22 03:53 UTC · resolved · major impact
  Restoration reported
• Intermittent connection errors via the connection pooler in us-east-1Oct 21 16:27 UTC · resolved
  Restoration reported
• Project lifecycle operations such as project creation, pausing, and restoration, in all regionsOct 21 15:36 UTC · resolved · major impact
  Investigation mentionedRestoration reported
• Projects stuck in restarting stateOct 20 21:59 UTC · resolved
  Investigation mentioned
• Support Form ErrorsOct 19 17:13 UTC · resolved · minor impact
  No classified wording
• Project creation errors ap-ne1Oct 17 06:27 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
• Realtime latencyOct 12 22:59 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
• Edge Function DegradationOct 12 19:49 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
• Log ingestion impairedOct 12 19:39 UTC · resolved · minor impact
  Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
• Upgrade IssuesOct 6 15:23 UTC · resolved
  Service restricted or degradedInvestigation mentionedRestoration reported
• Increased errors on management api leading to project operation failuresOct 6 07:53 UTC · resolved · minor impact
  Provider used security languageSign-in disruptionInvestigation mentionedRestoration reported
• Intermittent latency in Eastern USSep 29 16:26 UTC · resolved · minor impact
  Restoration reported
• Log Ingestion DegradationSep 28 13:47 UTC · resolved
  Service restricted or degradedSign-in disruptionRestoration reported
• Project Lifecycle Issues in eu-west-1Sep 24 15:36 UTC · resolved · minor impact
  Investigation mentionedRestoration reported