Apr <var data-var='date'> 8</var>, <var data-var='time'>20:05</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'> 8</var>, <var data-var='time'>19:41</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>19:24</var> 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 <var data-var='date'> 8</var>, <var data-var='time'>19:11</var> UTC Identified - 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.

Logs currently inaccessible via the Dashboard and Log Drains

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

Increased error rates for plan upgrades

Apr <var data-var='date'> 1</var>, <var data-var='time'>01:11</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>00:47</var> UTC Monitoring - We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.Apr <var data-var='date'> 1</var>, <var data-var='time'>00:13</var> UTC Investigating - We are seeing degradation of logs and are currently investigating the cause of this issue.

Degraded logs ingestion

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

Supabase dashboard experiencing intermittent errors in Europe region

Mar <var data-var='date'>27</var>, <var data-var='time'>17:03</var> UTC Resolved - Log ingestion has returned to normalMar <var data-var='date'>27</var>, <var data-var='time'>16:17</var> UTC Monitoring - Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.Mar <var data-var='date'>27</var>, <var data-var='time'>16:12</var> 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 <var data-var='date'>27</var>, <var data-var='time'>15:52</var> UTC Update - 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.Mar <var data-var='date'>27</var>, <var data-var='time'>15:33</var> UTC Identified - 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.Mar <var data-var='date'>27</var>, <var data-var='time'>15:13</var> UTC Investigating - We are investigating a problem with log ingestion. Users may experience delay in current log data.

Degraded Log Ingestion

Mar <var data-var='date'>27</var>, <var data-var='time'>02:58</var> UTC Resolved - The issue has been resolved and Realtime services have returned to normal.Mar <var data-var='date'>27</var>, <var data-var='time'>02:48</var> UTC Monitoring - The fix has been implemented and we’re monitoring to ensure stability.Mar <var data-var='date'>27</var>, <var data-var='time'>01:44</var> UTC Update - We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.Mar <var data-var='date'>27</var>, <var data-var='time'>01:13</var> UTC Update - We are working on a fix and we’ll continue to provide updates as progress is made.Mar <var data-var='date'>27</var>, <var data-var='time'>00:46</var> UTC Identified - We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.Mar <var data-var='date'>27</var>, <var data-var='time'>00:20</var> UTC Update - We're still investigating network connectivity issues with Realtime.Mar <var data-var='date'>26</var>, <var data-var='time'>23:41</var> UTC Investigating - We are investigating network connectivity issues with Realtime.”

Realtime services unavailable

Mar <var data-var='date'>24</var>, <var data-var='time'>15:56</var> UTC Resolved - Branching access has returned to normal, this issue is resolved.Mar <var data-var='date'>24</var>, <var data-var='time'>15:27</var> UTC Monitoring - The fix has been implemented and branching access has returned to normal.Mar <var data-var='date'>24</var>, <var data-var='time'>15:13</var> 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.

Branching access issues

Mar <var data-var='date'>23</var>, <var data-var='time'>18:56</var> UTC Resolved - This issue is now resolved. All logging ingestion has resumed in all regions.Mar <var data-var='date'>23</var>, <var data-var='time'>17:05</var> UTC Monitoring - A fix has been implemented. The system is now operating normally, and we will continue to monitor.Mar <var data-var='date'>23</var>, <var data-var='time'>16:38</var> UTC Identified - The cause of the issue has been identified. Our engineering team is working on a fix.Mar <var data-var='date'>23</var>, <var data-var='time'>16:28</var> UTC Investigating - 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.

Degraded Logging Ingestion impacting all regions

Mar <var data-var='date'>23</var>, <var data-var='time'>15:42</var> UTC Resolved - Error rates have returned to normal. This incident has been resolved.Mar <var data-var='date'>23</var>, <var data-var='time'>14:32</var> 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 <var data-var='date'>23</var>, <var data-var='time'>14:16</var> UTC Investigating - We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

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

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

Project creation failures across multiple regions

Mar <var data-var='date'>18</var>, <var data-var='time'>18:21</var> UTC Resolved - The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.Mar <var data-var='date'>18</var>, <var data-var='time'>17:53</var> UTC Identified - The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.Mar <var data-var='date'>18</var>, <var data-var='time'>17:30</var> UTC Update - 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.Mar <var data-var='date'>18</var>, <var data-var='time'>16:58</var> UTC Update - 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.Mar <var data-var='date'>18</var>, <var data-var='time'>16:27</var> UTC Investigating - 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.

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

Mar <var data-var='date'>17</var>, <var data-var='time'>07:41</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'>17</var>, <var data-var='time'>07:07</var> UTC Monitoring - A fix has been implemented and we are monitoring.Mar <var data-var='date'>17</var>, <var data-var='time'>05:11</var> UTC Identified - We have identified the root cause and are currently working on a fix.Mar <var data-var='date'>17</var>, <var data-var='time'>04:50</var> 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 are running earlier Postgres versions, are not affected.

Issues propagating Postgres configuration updates

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

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

Mar <var data-var='date'>12</var>, <var data-var='time'>13:53</var> UTC Resolved - The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.Mar <var data-var='date'>12</var>, <var data-var='time'>12:54</var> 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 <var data-var='date'>12</var>, <var data-var='time'>12:51</var> UTC Investigating - We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs. The logs for these services may only be partially ingested. The services remain fully functional, this is only impacting logs. Postgres Logs are not impacted. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will share another update as soon as more information becomes available.

Mar <var data-var='date'>11</var>, <var data-var='time'>19:09</var> 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 <var data-var='date'>11</var>, <var data-var='time'>18:47</var> 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 <var data-var='date'>11</var>, <var data-var='time'>18:25</var> UTC Identified - We have identified the root cause and are currently working on a fix.Mar <var data-var='date'>11</var>, <var data-var='time'>18:08</var> UTC Investigating - We are currently investigating reports of projects failing to be created.

Projects failing to be created

Mar <var data-var='date'> 7</var>, <var data-var='time'>21:56</var> UTC Resolved - All storage operations have returned to normal.Mar <var data-var='date'> 7</var>, <var data-var='time'>21:16</var> 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 <var data-var='date'> 7</var>, <var data-var='time'>20:44</var> UTC Update - We are observing storage error rates returning to normal.Mar <var data-var='date'> 7</var>, <var data-var='time'>20:22</var> UTC Identified - We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue.Mar <var data-var='date'> 7</var>, <var data-var='time'>20:12</var> UTC Investigating - We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating.

Storage errors in EU-Central-2

Mar <var data-var='date'> 7</var>, <var data-var='time'>16:46</var> UTC Resolved - Error rates have returned to baseline and all regions are operating as expected.Mar <var data-var='date'> 7</var>, <var data-var='time'>16:16</var> 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 <var data-var='date'> 7</var>, <var data-var='time'>15:51</var> 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 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.Mar <var data-var='date'> 7</var>, <var data-var='time'>15:23</var> UTC Update - 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.Mar <var data-var='date'> 7</var>, <var data-var='time'>15:04</var> UTC Identified - 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.Mar <var data-var='date'> 7</var>, <var data-var='time'>14:59</var> UTC Update - 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.Mar <var data-var='date'> 7</var>, <var data-var='time'>14:48</var> UTC Investigating - 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.

Elevated Management API error rates across all regions

Mar <var data-var='date'> 7</var>, <var data-var='time'>13:58</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'> 7</var>, <var data-var='time'>13:23</var> 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 <var data-var='date'> 7</var>, <var data-var='time'>12:45</var> 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 information.Mar <var data-var='date'> 7</var>, <var data-var='time'>12:10</var> UTC Investigating - 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.

Subscription Plan changes currently unavailable

Mar <var data-var='date'> 6</var>, <var data-var='time'>19:36</var> UTC Resolved - Both regions are now working as usual.Mar <var data-var='date'> 6</var>, <var data-var='time'>15:56</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>15:46</var> 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 be provided as the rollout continues.Mar <var data-var='date'> 6</var>, <var data-var='time'>15:17</var> UTC Update - 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.Mar <var data-var='date'> 6</var>, <var data-var='time'>14:47</var> UTC Update - 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.Mar <var data-var='date'> 6</var>, <var data-var='time'>14:26</var> UTC Investigating - We are currently investigating the cause for increased response times.

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

Mar <var data-var='date'> 4</var>, <var data-var='time'>21:02</var> UTC Resolved - We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter. Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders, developers, and businesses across India.Mar <var data-var='date'> 3</var>, <var data-var='time'>19:12</var> UTC Monitoring - We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter. Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders,  developers, and businesses across India. If you were previously affected, you should now be able to access your Supabase projects without any interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Additionally, please allow up to 24 hours for the provider-side changes to propagate. If you continue to see access problems after 24 hours, let us know! Thank you for your patience while we worked through this incident.Mar <var data-var='date'> 3</var>, <var data-var='time'>14:42</var> UTC Update - We have continuing contact with the relevant authorities to address the connectivity issues impacting some users in India. Decision makers are involved on all sides. While we don’t have a confirmed timeline to share just yet, this is top priority for our team and leadership. We will post an update once the issue is resolved or additional information becomes available.Mar <var data-var='date'> 2</var>, <var data-var='time'>14:22</var> UTC Update - We continue to work closely with the relevant authorities to address the connectivity issues impacting some users in India. Our discussions are progressing, and we’re seeing constructive engagement as we work towards a resolution. While we don’t have a confirmed timeline to share just yet, this is top priority for our team. We will post an update once the issue is resolved or additional information becomes available.Feb <var data-var='date'>28</var>, <var data-var='time'>16:02</var> UTC Update - We acknowledge the ongoing impact this issue is having on our users in India. We have made important progress in our contact with the relevant authorities and continue to actively work towards a resolution. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.Feb <var data-var='date'>27</var>, <var data-var='time'>17:39</var> UTC Update - We understand many users in India continue to be blocked from accessing Supabase. We acknowledge the difficulties this is causing for our users there. Supabase continues to follow up through all available channels to resolve this issue. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.Feb <var data-var='date'>26</var>, <var data-var='time'>23:36</var> UTC Update - Affected customers who are using the Custom Domain feature may be able to restore connectivity by switching their Custom Domain's DNS to an alternative DNS and enabling proxying. We advise affected customers to continue to report the issue to their ISP.Feb <var data-var='date'>26</var>, <var data-var='time'>14:56</var> UTC Update - We have received some reports that other ISPs in India may be impacted by access limitations. We continue to follow up through all available channels to resolve this issue. We have engaged multiple teams at Supabase communicating with multiple entities in India in an effort to do all we can to resolve the access issues our users in India are experiencing. We advise affected customers to continue to report the issue to their ISP and to use an alternative DNS provider or a VPN as a workaround in the interim. We will post an update once the issue is resolved or additional information becomes available.Feb <var data-var='date'>25</var>, <var data-var='time'>18:27</var> UTC Update - We continue to follow up through all available channels to work with the ISP to resolve this issue. We advise affected customers to also report the issue to their ISP and to use an alternative DNS provider as a workaround. We will post an updated once the ISP has confirmed that the issue is resolved or additional information becomes available.Feb <var data-var='date'>24</var>, <var data-var='time'>16:39</var> UTC Update - We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational. We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers. We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/ Alternatively users can use a VPN to avoid this issue We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.Feb <var data-var='date'>24</var>, <var data-var='time'>16:08</var> UTC Update - We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/Feb <var data-var='date'>24</var>, <var data-var='time'>16:00</var> UTC Update - We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.Feb <var data-var='date'>24</var>, <var data-var='time'>15:42</var> UTC Update - We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.Feb <var data-var='date'>24</var>, <var data-var='time'>15:13</var> UTC Identified - A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.Feb <var data-var='date'>24</var>, <var data-var='time'>14:46</var> UTC Investigating - We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

Users Experiencing Network Connectivity Problems (India Region)

Mar <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'> 4</var>, <var data-var='time'>10:36</var> UTC Monitoring - Service has been fully recovered and we're continuing to monitor.Mar <var data-var='date'> 4</var>, <var data-var='time'>10:30</var> UTC Identified - 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.Mar <var data-var='date'> 4</var>, <var data-var='time'>10:16</var> UTC Investigating - Existing projects seem to be unaffected

Supabase Dashboard and Management API inaccessible

Mar <var data-var='date'> 3</var>, <var data-var='time'>06:31</var> UTC Resolved - Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners.Mar <var data-var='date'> 3</var>, <var data-var='time'>04:08</var> UTC Monitoring - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment.Mar <var data-var='date'> 3</var>, <var data-var='time'>03:14</var> UTC Update - We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/generalMar <var data-var='date'> 3</var>, <var data-var='time'>02:41</var> UTC Identified - We’ve identified that this affects only a subset of projects in us-east-2.  We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/generalMar <var data-var='date'> 3</var>, <var data-var='time'>02:10</var> UTC Investigating - We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate.

Database issues in us-east-2

Feb <var data-var='date'>28</var>, <var data-var='time'>14:29</var> UTC Resolved - The issue affecting Edge Functions has now been fully resolved, and users have reported Edge Functions operating as expected. The root cause was a denial-of-service event that led to elevated error rates and 504 responses across impacted regions. Mitigations have been implemented to restore stability. We will be publishing a full post-mortem with additional details, once our internal review is complete. Thank you for your patience while we worked to resolve this issue.Feb <var data-var='date'>28</var>, <var data-var='time'>14:09</var> UTC Monitoring - The fix has been implemented and early indicators suggest it has resolved the 504 errors affecting Edge Functions. We are continuing to monitor system performance closely to ensure stability and confirm full recovery across all affected regions. We will provide a final update once we are confident the issue is fully resolved.Feb <var data-var='date'>28</var>, <var data-var='time'>14:04</var> UTC Identified - We believe we have identified the underlying cause of the 504 errors affecting Edge Functions across multiple regions. The team are currently implementing corrective measures to address the issue and restore service stability.Feb <var data-var='date'>28</var>, <var data-var='time'>13:48</var> UTC Update - We are continuing to investigate reports of Edge Functions returning 504 errors across multiple 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.Feb <var data-var='date'>28</var>, <var data-var='time'>13:03</var> UTC Investigating - We are currently investigating reports of Edge Functions returning 504 errors across multiple regions. The team has been alerted and is actively investigating the root cause. We are working to identify the scope of affected regions. We will provide an update as soon as we have more information.

Increased Edge Function Errors across multiple regions

Feb <var data-var='date'>26</var>, <var data-var='time'>02:23</var> UTC Resolved - Things have remained stable, and all systems looking good. This issue has been resolved.Feb <var data-var='date'>26</var>, <var data-var='time'>01:53</var> UTC Monitoring - Project Pause requests and Replica configuration changes are back to normal. We're monitoring to ensure stability.Feb <var data-var='date'>26</var>, <var data-var='time'>01:28</var> UTC Update - The job queue is continuing to decrease. The team is making further changes to help it complete faster. Note: The impact of this remains project pause and read replica configuration change delays. All projects remain up and accessible.Feb <var data-var='date'>26</var>, <var data-var='time'>00:51</var> UTC Update - The queued jobs are being processed, and pause events and read replica configuration changes will complete as expected once the jobs are processed. The team is, in parallel, looking into making some adjustments to help these processes complete faster.Feb <var data-var='date'>26</var>, <var data-var='time'>00:19</var> UTC Identified - We've identified a spike in queued jobs in the region, which are resulting in pause and read replica actions delayed. The team is looking into this spike and remediation options.Feb <var data-var='date'>25</var>, <var data-var='time'>23:58</var> UTC Investigating - We are seeing delays when attempting to pause projects and/or add or remove replicas in EU-West-1. The team is currently looking into this and will update

Delays in pausing projects and making read replica configuration changes in EU-West-1

Feb <var data-var='date'>26</var>, <var data-var='time'>02:00</var> UTC Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>26</var>, <var data-var='time'>01:01</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>25</var>, <var data-var='time'>18:07</var> UTC Scheduled - Our upstream billing provider is doing some <a href="https://status.withorb.com/incidents/71lzjrg9j87k">important maintenance</a> on February 26, 2026. Their maintenance window is, very conservatively, from 0100-0500 UTC. They estimate that services will be impacted for approximately the first 5 minutes of this window. We have set this maintenance window for 1 hour from our side, but do not expect the impact to be longer than 5 minutes. Project availability, compute add-on changes, disk scaling, and other project configuration changes ARE NOT IMPACTED. All Postgres and Data API access WILL REMAIN FUNCTIONAL. Additionally Auth, Realtime, Storage, Edge Functions, and all other features will remain functional. The impact for Supabase will be that the following activities will be restricted during this ~5 minute period: Organization creation Subscription plan changes (e.g. upgrades/downgrades) Credit top-ups and redemptions Billing-related API requests (e.g. the billing dashboard pages for your organization) We will be disabling these features starting at 01:00 UTC, and plan to re-enable them at 01:05 UTC, pending positive healthchecks from the upstream billing APIs.

Is Supabase down?

Supabase status is UP

Lastest published events

Logs currently inaccessible via the Dashboard and Log Drains

Increased error rates for plan upgrades

Degraded logs ingestion

Supabase Services, Components and Regions

Recent Supabase events

Logs currently inaccessible via the Dashboard and Log Drains

Increased error rates for plan upgrades

Degraded logs ingestion

Supabase dashboard experiencing intermittent errors in Europe region

Degraded Log Ingestion

Realtime services unavailable

Get your FREE account now,
5 monitors included!

Is Supabase down?

Supabase status is UP

Lastest published events

Logs currently inaccessible via the Dashboard and Log Drains

Increased error rates for plan upgrades

Degraded logs ingestion

Supabase Services, Components and Regions

Recent Supabase events

Logs currently inaccessible via the Dashboard and Log Drains

Increased error rates for plan upgrades

Degraded logs ingestion

Supabase dashboard experiencing intermittent errors in Europe region

Degraded Log Ingestion

Realtime services unavailable

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!