Supabase

Apr 12, 17:03 UTC Resolved - Capacity has been fully restored in the impacted APAC regions, and project creation is operating normally. Apr 12, 16:19 UTC 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, 15:51 UTC Investigating - We are currently investigating an issue affecting project creation in some APAC regions. Users may experience failures when attem...

Apr 8, 20:05 UTC Resolved - This incident has been resolved. Apr 8, 19:41 UTC 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, 19:24 UTC Update - 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. Apr 8, 19:11 UTC Identified - Users may see e...

Apr 2, 09:24 UTC Resolved - The issue causing increased error rates during plan upgrades has been resolved. All systems are operating normally. Apr 2, 09:05 UTC Monitoring - A fix has been applied, and we are monitoring to ensure stability. Apr 2, 08:40 UTC 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. Apr 2, 08:28 UTC Investigating - We are currently investigating inc...

Apr 1, 01:11 UTC Resolved - Log ingestion has recovered and the incident is considered resolved. Some log data was lost during the incident between around 11pm to 11:45pm ETC on March 31. Apr 1, 00:47 UTC Monitoring - We have identified the issue and a fix is in place. We will continue to monitor to ensure stability. Apr 1, 00:13 UTC Investigating - We are seeing degradation of logs and are currently investigating the cause of this issue.

Mar 27, 18:43 UTC Resolved - We have confirmed that project creation has returned to normal. Mar 27, 18:18 UTC Monitoring - Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency. Mar 27, 17:58 UTC Identified - We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.

Mar 27, 17:03 UTC Resolved - Log ingestion has returned to normal Mar 27, 16:17 UTC Monitoring - Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal. Mar 27, 16:12 UTC Update - 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. Mar 27, 15:52 UTC Update - We have implemented increase capacity and logs are returning to ...

Mar 27, 02:58 UTC Resolved - The issue has been resolved and Realtime services have returned to normal. Mar 27, 02:48 UTC Monitoring - The fix has been implemented and we’re monitoring to ensure stability. Mar 27, 01:44 UTC Update - We appreciate your patience as we continue to work on a fix. We will provide updates as they become available. Mar 27, 01:13 UTC Update - We are working on a fix and we’ll continue to provide updates as progress is made. Mar 27, 00:46 UTC Identified - We've identifie...

Mar 24, 15:56 UTC Resolved - Branching access has returned to normal, this issue is resolved. Mar 24, 15:27 UTC Monitoring - The fix has been implemented and branching access has returned to normal. Mar 24, 15:13 UTC Identified - We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is being deployed. We will provide an update once resolved.

Mar 23, 18:56 UTC Resolved - This issue is now resolved. All logging ingestion has resumed in all regions. Mar 23, 17:05 UTC Monitoring - A fix has been implemented. The system is now operating normally, and we will continue to monitor. Mar 23, 16:38 UTC Identified - The cause of the issue has been identified. Our engineering team is working on a fix. Mar 23, 16:28 UTC Investigating - We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some ser...

Mar 23, 15:42 UTC Resolved - Error rates have returned to normal. This incident has been resolved. Mar 23, 14:32 UTC Monitoring - We carried out a controlled redeployment of the affected services to restore stability. The system is now operating normally, and we will continue to monitor. Mar 23, 14:16 UTC Investigating - We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Mar 19, 22:00 UTC Resolved - Project creation in all regions are now successful. Mar 19, 21:21 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 19, 21:08 UTC Identified - We have identified the issue and a fix is underway. Mar 19, 20:55 UTC Investigating - We are currently investigating project creation failures across multiple regions.

Mar 18, 18:21 UTC Resolved - The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services. Mar 18, 17:53 UTC Identified - The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix. Mar 18, 17:30 UTC Update - We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still obse...

Mar 17, 07:41 UTC Resolved - This incident has been resolved. Mar 17, 07:07 UTC Monitoring - A fix has been implemented and we are monitoring. Mar 17, 05:11 UTC Identified - We have identified the root cause and are currently working on a fix. Mar 17, 04:50 UTC Investigating - 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 a...

Mar 13, 10:19 UTC Resolved - Error rates have returned to normal, and connectivity has stabilised. Mar 13, 09:40 UTC Monitoring - A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability. Mar 13, 09:25 UTC Update - 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. Mar 13, 08:54 UTC Investigating - We ar...

Mar 12, 13:53 UTC Resolved - The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation. Mar 12, 12:54 UTC Monitoring - A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to normal. Mar 12, 12:51 UTC Investigating - We are currently investigating an issue affecting Supabase Log...

Mar 11, 19:09 UTC Resolved - Project creation recovery has been confirmed across all regions. Regional dashboards show error rates returned to normal, and previously failing project creation operations are succeeding again. Mar 11, 18:47 UTC Monitoring - A fix has been implemented and we are seeing project creation recovery across regions. We're moving the incident to monitoring while we confirm full stability. Mar 11, 18:25 UTC Identified - We have identified the root cause and are currently wo...

Mar 7, 21:56 UTC Resolved - All storage operations have returned to normal. Mar 7, 21:16 UTC Monitoring - The upstream incident has been resolved and we have not observed any additional errors. We will continue to monitor our storage infrastructure for continued stable operations. Mar 7, 20:44 UTC Update - We are observing storage error rates returning to normal. Mar 7, 20:22 UTC Identified - We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working ...

Mar 7, 16:46 UTC Resolved - Error rates have returned to baseline and all regions are operating as expected. Mar 7, 16:16 UTC Monitoring - We've seen error rates return to normal levels, and all regions are now holding steady. We will continue to monitor to make sure things remain stable. Mar 7, 15:51 UTC Update - 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 g...

Mar 7, 13:58 UTC Resolved - This incident has been resolved. Mar 7, 13:23 UTC Monitoring - A fix has been applied by our upstream provider and we have re-enabled subscription plan upgrades and paid organization creation. We are monitoring to confirm full recovery. Mar 7, 12:45 UTC Update - 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 ...

Mar 6, 19:36 UTC Resolved - Both regions are now working as usual. Mar 6, 15:56 UTC Monitoring - Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised. We will continue to monitor the systems closely to ensure stability. Mar 6, 15:46 UTC Identified - Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts. We are currently rolling out the fix to the ap-northeast-2 (Seoul) region. Further updates will b...