THIS IS A SCHEDULED EVENT Oct <var data-var='date'>7</var>, <var data-var='time'>15:00</var> - <var data-var='time'>17:00</var> UTC Sep <var data-var='date'>30</var>, <var data-var='time'>22:08</var> UTC Scheduled - Starting October 7th, we are migrating our status page to a new platform to give you better visibility into Supabase's service status. What's changing: The status page URL will stay the same: https://status.supabase.com If you are subscribed via email, you will automatically be resubscribed, no action needed. If you are subscribed via any other method (SMS, Slack, webhook, RSS, etc.), you will need to resubscribe on the new page, since these subscriptions will not carry over automatically. Note that our new platform only offers Email, RSS, and Slack notifications. What's new: The new status page lets you choose exactly what you want updates about. Instead of getting notified about all products, services and regions, email subscribers can now subscribe to only the specific products, services, and regions relevant to them. You will hear about the incidents that actually affect you. Thanks, The Supabase Team

Statuspage Migration

Oct <var data-var='date'> 6</var>, <var data-var='time'>12:15</var> UTC Resolved - A fix for this issue has been implemented and our data shows previous impacted users have recovered. Oct <var data-var='date'> 5</var>, <var data-var='time'>18:45</var> UTC Monitoring - A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident. Oct <var data-var='date'> 2</var>, <var data-var='time'>21:06</var> UTC Update - While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available. Oct <var data-var='date'> 1</var>, <var data-var='time'>20:23</var> UTC Update - Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region. Sep <var data-var='date'>30</var>, <var data-var='time'>21:26</var> UTC Update - We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available. Sep <var data-var='date'>30</var>, <var data-var='time'>14:54</var> UTC Update - We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available. Sep <var data-var='date'>30</var>, <var data-var='time'>02:14</var> UTC Update - We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available. Sep <var data-var='date'>29</var>, <var data-var='time'>21:35</var> UTC Update - A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience. Sep <var data-var='date'>29</var>, <var data-var='time'>17:55</var> UTC Update - We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted. Sep <var data-var='date'>29</var>, <var data-var='time'>16:26</var> UTC Identified - We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.

Intermittent latency in Eastern US

Oct <var data-var='date'> 6</var>, <var data-var='time'>09:03</var> UTC Resolved - This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored. Oct <var data-var='date'> 6</var>, <var data-var='time'>08:13</var> UTC Monitoring - We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution. Oct <var data-var='date'> 6</var>, <var data-var='time'>07:55</var> UTC Update - We are continuing to investigate this issue. Oct <var data-var='date'> 6</var>, <var data-var='time'>07:53</var> UTC Investigating - We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.

Increased errors on management api leading to project operation failures

Sep <var data-var='date'>29</var>, <var data-var='time'>18:46</var> UTC Resolved - The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information: https://supabase.com/docs/guides/platform/upgrading Thank you again for your patience while we worked on resolving this issue. Sep <var data-var='date'>25</var>, <var data-var='time'>16:23</var> UTC Update - The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend. The new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue. Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade. Sep <var data-var='date'>23</var>, <var data-var='time'>07:26</var> UTC Update - We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions. Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue. Sep <var data-var='date'>17</var>, <var data-var='time'>19:30</var> UTC Update - To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue. We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade. Sep <var data-var='date'>11</var>, <var data-var='time'>23:41</var> UTC Update - We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue. Sep <var data-var='date'> 7</var>, <var data-var='time'>09:49</var> UTC Update - Testing results have been positive. Following some additional checks today, we plan to expand the rollout. We’ll continue to monitor progress and provide further updates as they become available. Sep <var data-var='date'> 2</var>, <var data-var='time'>19:38</var> UTC Update - A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out. Aug <var data-var='date'>31</var>, <var data-var='time'>19:52</var> UTC Update - We have seen reports that the JWT rejection issue persisted with 14.17, and due to <a href="https://status.supabase.com/incidents/bv4ntm4x0btf">some unintended performance side effects</a>, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon. Aug <var data-var='date'>28</var>, <var data-var='time'>23:44</var> UTC Update - We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue. To restart your project, go to the General settings page in the dashboard and select Restart project. Please contact our support team if the issue persists after a restart. Aug <var data-var='date'>27</var>, <var data-var='time'>17:17</var> UTC Update - PostgREST 14.17 has now been rolled out to all regions. Some customers have reported that restarting their project after the rollout resolved this issue. To restart your project, go to the General settings page in the dashboard and select Restart project. Please contact our support team if the issue persists after a restart. Aug <var data-var='date'>25</var>, <var data-var='time'>18:41</var> UTC Update - We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. This fix has been applied to the following regions: ap-east-1 ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2 ca-central-1 eu-central-1 eu-central-2 eu-north-1 eu-west-2 eu-west-3 We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful. Aug <var data-var='date'>21</var>, <var data-var='time'>17:21</var> UTC Update - We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue. Aug <var data-var='date'>20</var>, <var data-var='time'>16:37</var> UTC Update - As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided. Aug <var data-var='date'>18</var>, <var data-var='time'>18:38</var> UTC Update - Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed. Aug <var data-var='date'>14</var>, <var data-var='time'>07:53</var> UTC Update - Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users. Aug <var data-var='date'>14</var>, <var data-var='time'>02:23</var> UTC Identified - We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.

401 errors due to JWT rejections

Sep <var data-var='date'>28</var>, <var data-var='time'>14:36</var> UTC Resolved - Log ingestion is normal. Sep <var data-var='date'>28</var>, <var data-var='time'>14:00</var> UTC Monitoring - Log ingestion has recovered. We are monitoring for continued stability. Sep <var data-var='date'>28</var>, <var data-var='time'>13:52</var> UTC Identified - The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering. Sep <var data-var='date'>28</var>, <var data-var='time'>13:47</var> UTC Investigating - Log ingestion is experiencing some delays. Ingestion will be retried by clients.

Log Ingestion Degradation

Sep <var data-var='date'>24</var>, <var data-var='time'>17:38</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>17:12</var> UTC Monitoring - We are continuing to monitor to ensure ongoing stability. Sep <var data-var='date'>24</var>, <var data-var='time'>17:03</var> UTC Update - The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability. Sep <var data-var='date'>24</var>, <var data-var='time'>16:56</var> UTC Update - Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available. Sep <var data-var='date'>24</var>, <var data-var='time'>16:23</var> UTC Update - All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible. Sep <var data-var='date'>24</var>, <var data-var='time'>15:50</var> UTC Identified - We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations. Sep <var data-var='date'>24</var>, <var data-var='time'>15:36</var> UTC Investigating - We are investigating project lifecycle operation issues in eu-west-1.

Project Lifecycle Issues in eu-west-1

Sep <var data-var='date'>24</var>, <var data-var='time'>11:49</var> UTC Resolved - This incident has been resolved. Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix. Sep <var data-var='date'>24</var>, <var data-var='time'>11:08</var> UTC Monitoring - We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected. We are monitoring the results to ensure the issue is fully resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>10:50</var> UTC Identified - We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. We are working on a fix and will provide another update once it has been implemented. Sep <var data-var='date'>24</var>, <var data-var='time'>10:37</var> UTC Investigating - We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. This may prevent some users from managing their projects through the Dashboard. We are working to identify the cause and will provide further updates as they become available.

Permission errors in the Supabase Dashboard

Sep <var data-var='date'>24</var>, <var data-var='time'>10:01</var> UTC Resolved - Storage is now operating normally. We apologise for the disruption. Hardening measures are being put in place to prevent recurrence and will be communicated upon completion. Sep <var data-var='date'>23</var>, <var data-var='time'>10:20</var> UTC Monitoring - A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available. Sep <var data-var='date'>23</var>, <var data-var='time'>09:31</var> UTC Investigating - We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors. We are working to identify the root cause and will notify for any progress as soon as we have an update

Storage search failing for restored projects

Sep <var data-var='date'>23</var>, <var data-var='time'>23:41</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>23</var>, <var data-var='time'>22:56</var> UTC Monitoring - We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring. Sep <var data-var='date'>23</var>, <var data-var='time'>22:36</var> UTC Identified - We've identified the cause and are working on a fix. Sep <var data-var='date'>23</var>, <var data-var='time'>21:58</var> UTC Investigating - We're seeing rate limiting issues causing Supabase CLI CI workflow failures

Supabase CLI CI workflow failures

Sep <var data-var='date'>23</var>, <var data-var='time'>10:49</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>23</var>, <var data-var='time'>09:54</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>23</var>, <var data-var='time'>09:39</var> UTC Identified - We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this. Sep <var data-var='date'>23</var>, <var data-var='time'>09:21</var> UTC Investigating - We are currently investigating this issue

Increased error rate in project creation and project restore

Sep <var data-var='date'>22</var>, <var data-var='time'>12:20</var> UTC Resolved - This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally. Sep <var data-var='date'>22</var>, <var data-var='time'>11:05</var> UTC Monitoring - The affected Supavisor node has been restarted, and error rates have returned to normal levels. We’ll continue to monitor the service to ensure stability. Sep <var data-var='date'>22</var>, <var data-var='time'>10:49</var> UTC Investigating - Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections. Our team is aware of the issue and actively working on a resolution. We’ll share further updates as they become available.

Supavisor connection disruptions in EU West 1 (Ireland)

Sep <var data-var='date'>22</var>, <var data-var='time'>09:05</var> UTC Resolved - The latency has recovered and the incident is now resolved. Sep <var data-var='date'>22</var>, <var data-var='time'>08:33</var> UTC Monitoring - We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC: ap-northeast-1 ap-northeast-2 eu-central-1 eu-central-2 eu-north-1 eu-west-1 eu-west-3 us-west-1 The latency has since recovered and our teams are monitoring for full recovery. Existing project availability has not been impacted.

Project creations are degraded in multiple regions

Sep <var data-var='date'>19</var>, <var data-var='time'>22:12</var> UTC Resolved - Project lifecycle operations are behaving normally. Sep <var data-var='date'>19</var>, <var data-var='time'>21:25</var> UTC Monitoring - Project lifecycle operations have remained stable. We will continue to monitor the platform. Sep <var data-var='date'>19</var>, <var data-var='time'>20:34</var> UTC Update - We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence. Sep <var data-var='date'>19</var>, <var data-var='time'>20:12</var> UTC Investigating - We are experiencing degradation of project lifecycle activities. We are investigating.

Project Lifecycle Activity Degradation

Sep <var data-var='date'>16</var>, <var data-var='time'>20:36</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>19:48</var> UTC Monitoring - The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability. Sep <var data-var='date'>16</var>, <var data-var='time'>19:17</var> UTC Update - The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made. Sep <var data-var='date'>16</var>, <var data-var='time'>18:32</var> UTC Update - We are continuing to work on a fix and will provide updates as things progress. Sep <var data-var='date'>16</var>, <var data-var='time'>17:53</var> UTC Identified - Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.

Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2

Sep <var data-var='date'>16</var>, <var data-var='time'>12:27</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>09:38</var> UTC Monitoring - Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors. Sep <var data-var='date'>16</var>, <var data-var='time'>09:24</var> UTC Investigating - We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.

Edge Function Latency

Sep <var data-var='date'>16</var>, <var data-var='time'>09:33</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>09:09</var> UTC Monitoring - We implemented a fix and are monitoring the system. Sep <var data-var='date'>16</var>, <var data-var='time'>08:29</var> UTC Update - We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue. Sep <var data-var='date'>16</var>, <var data-var='time'>07:17</var> UTC Identified - We have identified an issue related to the Auth service on some projects. We are actively working on a fix.

Auth Service Outage

Sep <var data-var='date'>15</var>, <var data-var='time'>21:45</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>15</var>, <var data-var='time'>21:42</var> UTC Verifying - Verification is underway for the maintenance items. Sep <var data-var='date'>15</var>, <var data-var='time'>21:20</var> UTC Update - Scheduled maintenance is currently in progress. We will provide updates as necessary. During the maintenance, support ticket creation will be suspended. Sep <var data-var='date'>15</var>, <var data-var='time'>21:15</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'> 7</var>, <var data-var='time'>15:18</var> UTC Scheduled - We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades. Maintenance Window: - Start time: 21:15 UTC on September 15, 2026 - End time: 21:45 UTC on September 15, 2026 Impact: - Running projects *are not affected* but Management API operations may fail or be delayed. - Various platform operations may fail or be delayed during this window. - These may include project creation and initial configuration/setup.

Scheduled Platform Maintenance - 15th September, 2026

Sep <var data-var='date'>15</var>, <var data-var='time'>12:48</var> UTC Resolved - We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks Sep <var data-var='date'> 9</var>, <var data-var='time'>18:29</var> UTC Update - We continue to try to resolve this issue. We have made official requests for resolution to the appropriate parties in Myanmar. Sep <var data-var='date'> 2</var>, <var data-var='time'>19:05</var> UTC Monitoring - Supabase has taken the steps it can to address the blockage. We recommend customers contact their ISP for assistance: https://supabase.com/blog/navigating-regional-network-blocks Aug <var data-var='date'>25</var>, <var data-var='time'>23:31</var> UTC Update - We continue to reach out and make contact with the ISPs that have been involved in the connectivity challenges for some users in Myanmar. We are continuing to work to address the issue. Aug <var data-var='date'>20</var>, <var data-var='time'>12:18</var> UTC Identified - We have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue. Aug <var data-var='date'>19</var>, <var data-var='time'>17:08</var> UTC Update - The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue. Aug <var data-var='date'>19</var>, <var data-var='time'>15:52</var> UTC Investigating - We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.

Network access issues affecting a limited number of users in Myanmar

Sep <var data-var='date'>11</var>, <var data-var='time'>19:06</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>11</var>, <var data-var='time'>06:19</var> UTC Update - We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal. Sep <var data-var='date'>11</var>, <var data-var='time'>03:44</var> UTC Monitoring - We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors. Sep <var data-var='date'>10</var>, <var data-var='time'>19:41</var> UTC Update - We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects. Sep <var data-var='date'>10</var>, <var data-var='time'>17:59</var> UTC Update - Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally. Sep <var data-var='date'>10</var>, <var data-var='time'>17:13</var> UTC Update - A refined fix is being rolled out to specific regions, we are assessing the impact of the fix. Sep <var data-var='date'>10</var>, <var data-var='time'>15:46</var> UTC Identified - We have identified why projects are becoming unresponsive and are implementing a mitigation. Sep <var data-var='date'>10</var>, <var data-var='time'>15:26</var> UTC Investigating - We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

Unresponsive Projects

Sep <var data-var='date'>11</var>, <var data-var='time'>17:00</var> UTC Resolved - We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.

Latency issues resulting in 504 errors

Sep <var data-var='date'> 9</var>, <var data-var='time'>08:47</var> UTC Resolved - Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

Brief connection disruptions in us-east-1 (N. Virginia)

Sep <var data-var='date'> 4</var>, <var data-var='time'>08:18</var> UTC Resolved - Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal. Sep <var data-var='date'> 4</var>, <var data-var='time'>04:28</var> UTC Monitoring - Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal. We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve. Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally. Sep <var data-var='date'> 4</var>, <var data-var='time'>03:41</var> UTC Update - We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Sep <var data-var='date'> 4</var>, <var data-var='time'>03:01</var> UTC Update - Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users. We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Sep <var data-var='date'> 4</var>, <var data-var='time'>02:02</var> UTC Update - We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Sep <var data-var='date'> 4</var>, <var data-var='time'>01:37</var> UTC Update - The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. We will provide additional updates as we have more information. Sep <var data-var='date'> 4</var>, <var data-var='time'>00:58</var> UTC Update - The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information. Sep <var data-var='date'> 4</var>, <var data-var='time'>00:30</var> UTC Identified - We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information. Sep <var data-var='date'> 4</var>, <var data-var='time'>00:15</var> UTC Investigating - We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information

Project Lifecycle Actions Showing increased error rates across all regions

Sep <var data-var='date'> 1</var>, <var data-var='time'>10:34</var> UTC Resolved - This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally. Projects and non-Dashboard traffic were unaffected throughout the incident. Sep <var data-var='date'> 1</var>, <var data-var='time'>09:20</var> UTC Monitoring - A recent change affected users ability to log in to the Supabase Dashboard. We’ve reverted the change, and testing indicates that the issue is resolved. Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry. Projects and non-Dashboard traffic remained unaffected. Sep <var data-var='date'> 1</var>, <var data-var='time'>08:51</var> UTC Update - We’re investigating an issue preventing users from logging in to the Supabase Dashboard. Users who were logged into the dashboard were logged out. Dashboard actions are currently not available. Projects remain online and available. Non-Dashboard traffic is not impacted. We’ll share another update as soon as we have more information. Sep <var data-var='date'> 1</var>, <var data-var='time'>08:45</var> UTC Investigating - We are currently investigating an issue where users are unable to login to the Supabase dashboard

User unable to log in to Supabase Dashboard

Aug <var data-var='date'>31</var>, <var data-var='time'>19:06</var> UTC Resolved - Project creation has returned to baseline consistently. Aug <var data-var='date'>31</var>, <var data-var='time'>18:29</var> UTC Monitoring - Project creation is reporting as recovered across the platform. We will monitor for stability in the near term. Aug <var data-var='date'>31</var>, <var data-var='time'>18:01</var> UTC Identified - We are seeing the mitigation steps having the desired effect. Project creation is recovering. Aug <var data-var='date'>31</var>, <var data-var='time'>17:49</var> UTC Update - While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation. Aug <var data-var='date'>31</var>, <var data-var='time'>17:20</var> UTC Update - We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations. Aug <var data-var='date'>31</var>, <var data-var='time'>16:53</var> UTC Update - We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance. Aug <var data-var='date'>31</var>, <var data-var='time'>16:28</var> UTC Investigating - Project creation is failing for new projects on the platform. We are investigating.

Project Creation Failures

Aug <var data-var='date'>31</var>, <var data-var='time'>15:57</var> UTC Resolved - Response times have recovered in all regions. This issue is now resolved. Aug <var data-var='date'>29</var>, <var data-var='time'>01:25</var> UTC Update - Response times have recovered in all regions. We will continue to monitor throughout the weekend. Aug <var data-var='date'>28</var>, <var data-var='time'>21:06</var> UTC Monitoring - The rollout has been completed in all regions. We will continue to monitor. Aug <var data-var='date'>28</var>, <var data-var='time'>18:15</var> UTC Update - The roll out has also been completed for us-east-1. Aug <var data-var='date'>28</var>, <var data-var='time'>17:21</var> UTC Update - PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions. Aug <var data-var='date'>28</var>, <var data-var='time'>13:10</var> UTC Update - We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available. Aug <var data-var='date'>28</var>, <var data-var='time'>01:38</var> UTC Identified - The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix. Aug <var data-var='date'>27</var>, <var data-var='time'>20:37</var> UTC Update - We are continuing to investigate this issue and we’ll share more information as soon as it becomes available. Aug <var data-var='date'>27</var>, <var data-var='time'>18:55</var> UTC Update - We are continuing to investigate this issue and we’ll share more information as soon as it becomes available. Aug <var data-var='date'>27</var>, <var data-var='time'>17:57</var> UTC Update - We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details. Aug <var data-var='date'>27</var>, <var data-var='time'>17:20</var> UTC Investigating - We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.

Is Supabase down?

Supabase status is UP

Lastest published events

Intermittent latency in Eastern US

Increased errors on management api leading to project operation failures

401 errors due to JWT rejections

Supabase Services, Components and Regions

Recent Supabase events

Statuspage Migration

Intermittent latency in Eastern US

Increased errors on management api leading to project operation failures

401 errors due to JWT rejections

Log Ingestion Degradation

Project Lifecycle Issues in eu-west-1