THIS IS A SCHEDULED EVENT Jun <var data-var='date'>1</var>, <var data-var='time'>13:00</var> - <var data-var='time'>15:00</var> UTC May <var data-var='date'>18</var>, <var data-var='time'>02:57</var> UTC Scheduled - There will be scheduled maintenance on 2026-06-03 from 13:00-15:00 UTC (09:00-11:00 EDT) on the Shared Pooler(V1) for the us-east-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-us-east-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-us-east-1.pooler.supabase.comare not affected by this maintenance. Please follow the status page for updates.

Upgrade Shared Pooler V1 to V2 for us-east-1 region

THIS IS A SCHEDULED EVENT Jun <var data-var='date'>1</var>, <var data-var='time'>13:00</var> - <var data-var='time'>15:00</var> UTC May <var data-var='date'>18</var>, <var data-var='time'>02:52</var> UTC Scheduled - There will be a scheduled maintenance on 2026-06-01 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-eu-west-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-eu-west-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.

Upgrade Shared Pooler V1 to V2 for eu-west-1 region

THIS IS A SCHEDULED EVENT May <var data-var='date'>28</var>, <var data-var='time'>16:00</var> - <var data-var='time'>18:00</var> UTC May <var data-var='date'>22</var>, <var data-var='time'>15:54</var> UTC Update - We will be undergoing scheduled maintenance during this time. May <var data-var='date'>18</var>, <var data-var='time'>02:55</var> UTC Scheduled - There will be scheduled maintenance on 2026-06-02 from 16:00-18:00 UTC (09:00-11:00 PDT) on the Shared Pooler(V1) for the us-west-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-us-west-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-us-west-1.pooler.supabase.comare not affected by this maintenance. Please follow the status page for updates.

Upgrade Shared Pooler V1 to V2 for us-west-1 region

THIS IS A SCHEDULED EVENT May <var data-var='date'>26</var>, <var data-var='time'>13:00</var> - <var data-var='time'>15:00</var> UTC May <var data-var='date'>23</var>, <var data-var='time'>04:39</var> UTC Update - We will be undergoing scheduled maintenance during this time. May <var data-var='date'>18</var>, <var data-var='time'>02:49</var> UTC Scheduled - There will be a scheduled maintenance on 2026-05-26 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-central-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-eu-central-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-eu-central-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.

Upgrade Shared Pooler V1 to V2 for eu-central-1 region

May <var data-var='date'>21</var>, <var data-var='time'>19:26</var> UTC Resolved - Branch creation continues to be stable. May <var data-var='date'>21</var>, <var data-var='time'>18:54</var> UTC Monitoring - Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident. May <var data-var='date'>21</var>, <var data-var='time'>17:45</var> UTC Update - We continue investigating different possible underlying causes and will provide updates as progress is made. May <var data-var='date'>21</var>, <var data-var='time'>16:46</var> UTC Investigating - We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.

Branch creation degradation

May <var data-var='date'>21</var>, <var data-var='time'>10:51</var> UTC Resolved - The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue. May <var data-var='date'>21</var>, <var data-var='time'>09:43</var> UTC Monitoring - We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability. May <var data-var='date'>21</var>, <var data-var='time'>09:26</var> UTC Update - A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses. May <var data-var='date'>21</var>, <var data-var='time'>08:49</var> UTC Identified - We have identified the issue as being related to a recent key rotation and are currently working on a fix. May <var data-var='date'>21</var>, <var data-var='time'>08:33</var> UTC Update - We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available. May <var data-var='date'>21</var>, <var data-var='time'>08:30</var> UTC Investigating - Users that are already logged in are not affected.

Login issues for SSO and Email accounts on Supabase Dashboard

May <var data-var='date'>21</var>, <var data-var='time'>04:44</var> UTC Resolved - Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved. May <var data-var='date'>21</var>, <var data-var='time'>04:23</var> UTC Monitoring - We have merged the fix and are monitoring for stability. May <var data-var='date'>21</var>, <var data-var='time'>03:49</var> UTC Update - We have developed a fix and it is currently being validated. We will provide more updates soon. May <var data-var='date'>21</var>, <var data-var='time'>01:12</var> UTC Update - Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made. May <var data-var='date'>20</var>, <var data-var='time'>23:41</var> UTC Update - Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made. May <var data-var='date'>20</var>, <var data-var='time'>22:48</var> UTC Identified - We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects. May <var data-var='date'>20</var>, <var data-var='time'>21:46</var> UTC Update - We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted. May <var data-var='date'>20</var>, <var data-var='time'>21:04</var> UTC Investigating - Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.

Network restrictions preventing read replica communication

May <var data-var='date'>20</var>, <var data-var='time'>19:41</var> UTC Resolved - The UI message incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>19:11</var> UTC Monitoring - This change has been reverted. We are monitoring to ensure things remain stable. May <var data-var='date'>20</var>, <var data-var='time'>17:41</var> UTC Update - The revert of the change is in process. May <var data-var='date'>20</var>, <var data-var='time'>16:17</var> UTC Identified - We’ve isolated the cause of the issue to a recent change and are working on reverting it now. May <var data-var='date'>20</var>, <var data-var='time'>15:40</var> UTC Investigating - We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard. The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date. For example: “All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still be available for download.” Please note this is a display issue only. Projects paused within the last 90 days can still be resumed successfully. All project data, including backups and storage objects, remains safe and unaffected.

Paused Projects Showing Incorrect Resume Deadline

May <var data-var='date'>19</var>, <var data-var='time'>00:10</var> UTC Resolved - This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this. May <var data-var='date'>18</var>, <var data-var='time'>23:58</var> UTC Monitoring - Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period. We will continue monitoring closely to ensure ongoing stability. May <var data-var='date'>18</var>, <var data-var='time'>23:26</var> UTC Investigating - Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

Log ingestion issues

May <var data-var='date'>15</var>, <var data-var='time'>19:18</var> UTC Resolved - All changes hav been applied. May <var data-var='date'>15</var>, <var data-var='time'>18:47</var> UTC Monitoring - The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability. May <var data-var='date'>15</var>, <var data-var='time'>18:11</var> UTC Identified - We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.

Auth Service Update

May <var data-var='date'>14</var>, <var data-var='time'>20:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>14</var>, <var data-var='time'>18:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 7</var>, <var data-var='time'>22:16</var> UTC Scheduled - There will be scheduled maintenance on May 14 from 18:00-20:00 UTC (15:00-17:00 BRT) on the Shared Pooler(V1) for the sa-east-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-sa-east-1.pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-sa-east-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.

Shared Pooler scheduled maintenance in sa-east-1

May <var data-var='date'>19</var>, <var data-var='time'>22:30</var> UTC Update - We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>22:23</var> UTC Identified - We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>16:37</var> UTC Update - We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution. May <var data-var='date'>14</var>, <var data-var='time'>15:54</var> UTC Update - We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>15:34</var> UTC Investigating - We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.

Access Issues From Some Providers in Brazil

May <var data-var='date'>13</var>, <var data-var='time'>20:35</var> UTC Resolved - We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved May <var data-var='date'>13</var>, <var data-var='time'>19:50</var> UTC Identified - Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side. May <var data-var='date'>13</var>, <var data-var='time'>17:31</var> UTC Update - We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses. May <var data-var='date'>13</var>, <var data-var='time'>16:46</var> UTC Update - We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more. May <var data-var='date'>13</var>, <var data-var='time'>16:15</var> UTC Investigating - We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.

Edge Traffic Issues

May <var data-var='date'>13</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>13</var>, <var data-var='time'>07:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 7</var>, <var data-var='time'>22:13</var> UTC Scheduled - There will be scheduled maintenance on May 13 from 7:00-9:00 UTC (15:00-17:00 SGT) on the Shared Pooler(V1) for the ap-southeast-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-ap-southeast-1.pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-ap-southeast-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.

Shared Pooler scheduled maintenance in ap-southeast-1

May <var data-var='date'> 9</var>, <var data-var='time'>15:00</var> UTC Resolved - Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode

Error spikes in one of the eu-central-1 Supavisor clusters

May <var data-var='date'> 9</var>, <var data-var='time'>04:49</var> UTC Resolved - Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident. May <var data-var='date'> 9</var>, <var data-var='time'>04:34</var> UTC Monitoring - Our infrastructure provider has resolved the underlying incident, and impacted services have recovered. We have completed recovery efforts for affected projects, re-enabled project creation, pausing, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability. May <var data-var='date'> 9</var>, <var data-var='time'>04:10</var> UTC Update - Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered. Our team is currently working through the remaining projects that did not automatically self-heal during recovery and is actively restoring them manually where needed. We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region. We are continuing to monitor platform stability closely and will provide additional updates as recovery progresses. May <var data-var='date'> 9</var>, <var data-var='time'>01:32</var> UTC Update - Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available. May <var data-var='date'> 8</var>, <var data-var='time'>16:34</var> UTC Update - Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available. May <var data-var='date'> 8</var>, <var data-var='time'>12:09</var> UTC Update - Our team is actively working to bring impacted projects back online as quickly and safely as possible. While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider. We appreciate your patience and will continue to share updates as more information becomes available. May <var data-var='date'> 8</var>, <var data-var='time'>10:52</var> UTC Update - Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery. May <var data-var='date'> 8</var>, <var data-var='time'>07:59</var> UTC Update - Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery. May <var data-var='date'> 8</var>, <var data-var='time'>06:44</var> UTC Update - Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery. May <var data-var='date'> 8</var>, <var data-var='time'>05:31</var> UTC Update - We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects. May <var data-var='date'> 8</var>, <var data-var='time'>05:30</var> UTC Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 8</var>, <var data-var='time'>04:21</var> UTC Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 8</var>, <var data-var='time'>03:11</var> UTC Update - We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider. May <var data-var='date'> 8</var>, <var data-var='time'>02:30</var> UTC Update - We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner. May <var data-var='date'> 8</var>, <var data-var='time'>02:05</var> UTC Update - We are waiting on a resolution from our upstream provider. We will provide an update in an hour. May <var data-var='date'> 8</var>, <var data-var='time'>01:06</var> UTC Identified - We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone. May <var data-var='date'> 8</var>, <var data-var='time'>00:50</var> UTC Investigating - Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1

Network connectivity in us-east-1-az4

May <var data-var='date'> 8</var>, <var data-var='time'>16:13</var> UTC Resolved - Upgrade operations have returned to normal. May <var data-var='date'> 8</var>, <var data-var='time'>14:39</var> UTC Monitoring - We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention. Any future upgrades should complete successfully. We are continuing to monitor recovery and system stability closely. May <var data-var='date'> 8</var>, <var data-var='time'>13:46</var> UTC Update - We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process. As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully resolved. We will continue to provide updates as information becomes available. May <var data-var='date'> 8</var>, <var data-var='time'>13:26</var> UTC Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 8</var>, <var data-var='time'>13:25</var> UTC Identified - Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version. We advise that you do not upgrade your project until the incident is resolved.

Customer Projects Experiencing Upgrade Issues

May <var data-var='date'> 5</var>, <var data-var='time'>14:56</var> UTC Completed - The scheduled maintenance has now been completed. May <var data-var='date'> 5</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>29</var>, <var data-var='time'>13:27</var> UTC Update - We have postponed this maintenance to Tuesday, May 5 1400-1500 UTC. Apr <var data-var='date'>28</var>, <var data-var='time'>09:27</var> UTC Scheduled - We will be carrying out scheduled database migrations on our Management API on Wednesday, April 29, 2026 between 14:00 to 15:00 UTC. Existing customer projects will not be affected and will continue to operate normally. During the maintenance period, all write activity from our API, Dashboard and CLI, such as project creation or configuration updates, will be delayed and may time out. You can retry on timeout. Read activity across our Management API will remain unaffected.

Dashboard and Management API maintenance

May <var data-var='date'> 4</var>, <var data-var='time'>05:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'> 4</var>, <var data-var='time'>04:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>17:18</var> UTC Scheduled - Upstream provider regular scheduled maintenance on instances in us-east-1 and eu-central-1. We do not expect downtime or impact to Edge Functions invocations or deploys during this window. We will monitor and update its progress.

Edge Functions scheduled maintenance in eu-central-1 and us-east-1

May <var data-var='date'> 3</var>, <var data-var='time'>22:30</var> UTC Resolved - From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query failed errors. This has been resolved and Supavisor is fully available.

Supavisor connectivity in eu-central-1

Apr <var data-var='date'>28</var>, <var data-var='time'>23:31</var> UTC Resolved - This is now resolved. Thank you for your patience while we worked to resolve this issue. Apr <var data-var='date'>28</var>, <var data-var='time'>23:03</var> UTC Monitoring - The exceptions fix has been rolled out, and we are monitoring for continued stability. Apr <var data-var='date'>28</var>, <var data-var='time'>22:24</var> UTC Update - We are continuing to work on a fix. We’ll share further updates as progress is made. Apr <var data-var='date'>28</var>, <var data-var='time'>21:40</var> UTC Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'>28</var>, <var data-var='time'>21:36</var> UTC Identified - The issue has been identified and we are working on a fix. Apr <var data-var='date'>28</var>, <var data-var='time'>21:26</var> UTC Investigating - We are investigating 403 errors for PostgREST requests across multiple regions.

403 errors for PostgREST requests

Apr <var data-var='date'>27</var>, <var data-var='time'>20:05</var> UTC Resolved - All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated. Apr <var data-var='date'>27</var>, <var data-var='time'>17:31</var> UTC Monitoring - The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched. Apr <var data-var='date'>27</var>, <var data-var='time'>16:05</var> UTC Update - The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service. Apr <var data-var='date'>27</var>, <var data-var='time'>14:21</var> UTC Identified - We’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact. Apr <var data-var='date'>27</var>, <var data-var='time'>13:12</var> UTC Monitoring - All impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates. Apr <var data-var='date'>27</var>, <var data-var='time'>11:40</var> UTC Update - Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved. Apr <var data-var='date'>27</var>, <var data-var='time'>11:11</var> UTC Update - We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved. Apr <var data-var='date'>27</var>, <var data-var='time'>10:54</var> UTC Identified - We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service.

Some Projects Unreachable following Project Restart

Apr <var data-var='date'>27</var>, <var data-var='time'>19:04</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>27</var>, <var data-var='time'>18:34</var> UTC Monitoring - We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue. Apr <var data-var='date'>27</var>, <var data-var='time'>16:22</var> UTC Update - The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed. Apr <var data-var='date'>27</var>, <var data-var='time'>15:00</var> UTC Update - The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon. Apr <var data-var='date'>27</var>, <var data-var='time'>13:38</var> UTC Update - We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. Apr <var data-var='date'>27</var>, <var data-var='time'>13:31</var> UTC Update - The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. Apr <var data-var='date'>27</var>, <var data-var='time'>12:39</var> UTC Identified - We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects

Some projects unavailable across multiple regions

Apr <var data-var='date'>26</var>, <var data-var='time'>17:52</var> UTC Resolved - A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to disable pg_graphql for projects that had not seen usage in the last 30 days. Due to a misconfiguration, this targeted more projects than intended. We are deeply sorry for the inconvenience and have since addressed the issue. For those using pg_graphql actively, you may have seen pg_graphql extension is not enabled in the logs for your project and you can safely re-enable this. If you have been impacted, or you are unable to re-enable pg_graphql, please contact success@supabase.io

Inadvertently disabled pg_graphql for some projects

Apr <var data-var='date'>25</var>, <var data-var='time'>05:47</var> UTC Resolved - This issue has now been resolved and projects have returned to normal. Apr <var data-var='date'>25</var>, <var data-var='time'>05:14</var> UTC Monitoring - Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability. Apr <var data-var='date'>25</var>, <var data-var='time'>04:38</var> UTC Update - Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event. Apr <var data-var='date'>25</var>, <var data-var='time'>04:26</var> UTC Update - US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions. Apr <var data-var='date'>25</var>, <var data-var='time'>04:16</var> UTC Identified - We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information.

Is Supabase down?

Supabase status is UP

Lastest published events

Branch creation degradation

Login issues for SSO and Email accounts on Supabase Dashboard

Network restrictions preventing read replica communication

Supabase Services, Components and Regions

Recent Supabase events

Upgrade Shared Pooler V1 to V2 for us-east-1 region

Upgrade Shared Pooler V1 to V2 for eu-west-1 region

Upgrade Shared Pooler V1 to V2 for us-west-1 region

Upgrade Shared Pooler V1 to V2 for eu-central-1 region

Branch creation degradation

Login issues for SSO and Email accounts on Supabase Dashboard

Get your FREE account now,
5 monitors included!

Is Supabase down?

Supabase status is UP

Lastest published events

Branch creation degradation

Login issues for SSO and Email accounts on Supabase Dashboard

Network restrictions preventing read replica communication

Supabase Services, Components and Regions

Recent Supabase events

Upgrade Shared Pooler V1 to V2 for us-east-1 region

Upgrade Shared Pooler V1 to V2 for eu-west-1 region

Upgrade Shared Pooler V1 to V2 for us-west-1 region

Upgrade Shared Pooler V1 to V2 for eu-central-1 region

Branch creation degradation

Login issues for SSO and Email accounts on Supabase Dashboard

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!