Affected Components: SMS

Aug 12, 18:57:35 GMT+0
Scheduled - <p>Twilio is conducting a planned maintenance from 30 September 2026 at 20:00 PDT until 01 October 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers.</p>.

Affected Components: SMS

Aug 12, 18:57:19 GMT+0
Scheduled - <p>Twilio is conducting a planned maintenance from 23 September 2026 at 20:00 PDT until 24 September 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers.</p>.

Affected Components: SMS

Aug 12, 18:57:05 GMT+0
Scheduled - <p>Twilio is conducting a planned maintenance from 16 September 2026 at 20:00 PDT until 17 September 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers.</p>.

Affected Components: SMS

Aug 12, 18:56:46 GMT+0
Scheduled - <p>Twilio is conducting a planned maintenance from 09 September 2026 at 20:00 PDT until 10 September 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers.</p>.

Affected Components: SMS

Aug 12, 18:56:26 GMT+0
Scheduled - <p>Twilio is conducting a planned maintenance from 02 September 2026 at 20:00 PDT until 03 September 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers.</p>.

Affected Components: SMS

Jul 7, 02:26:33 GMT+0
Scheduled - Twilio is conducting a planned maintenance from 26 August 2026 at 20:00 PDT until 27 August 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of long codes and short codes..

Affected Components: SMS

Aug 21, 17:41:03 GMT+0
Scheduled - <p>A subset of small networks in the US are conducting a planned maintenance from 25 August 2026 at 21:00 PDT until 25 August 2026 at 23:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to small US carriers handsets.</p>.

Duration: 4 hours and 30 minutes

Affected Components: SMS

Aug 25, 06:53:57 GMT+0
Scheduled - <p>Our SMS carrier partner in the United States is conducting a planned maintenance from 25 August 2026 at 00:00 PDT until 25 August 2026 at 04:30 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from United States handsets via subset of United States long codes and short codes.</p> <p>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>.

Aug 25, 07:00:08 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 25, 11:30:08 GMT+0
Completed - The scheduled maintenance has been completed..

Duration: 6 hours and 55 minutes

Affected Components: SMS

Aug 24, 19:10:57 GMT+0
Scheduled - <p>The T-Mobile network in the United States is conducting an emergency maintenance from 24 August 2026 at 19:00 PDT until 25 August 2026 at 01:55 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes.</p> <p>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>.

Aug 25, 01:01:17 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

Aug 25, 02:00:11 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 25, 08:55:13 GMT+0
Completed - The scheduled maintenance has been completed..

Duration: 5 days and 26 minutes

Affected Components: Compute

Aug 24, 13:52:42 GMT+0
Investigating - We are investigating an issue affecting automatic disk resizing. Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations. We are working to identify the cause and will provide an update as soon as we have more information..

Aug 24, 14:47:53 GMT+0
Monitoring - A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring. We will continue to follow up directly with affected users who opened a support ticket..

Aug 24, 15:53:09 GMT+0
Resolved - The issue affecting automatic disk resizing has been resolved. We will continue to follow up directly with affected users who opened a support ticket..

Duration: 4 hours

Affected Components: SMS

Aug 21, 06:54:18 GMT+0
Scheduled - <p>The AT&T network in the United States is conducting a planned maintenance from 23 August 2026 at 00:00 PDT until 23 August 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from AT&T United States handsets when sending via long codes and short codes.</p>.

Aug 23, 06:00:39 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

Aug 23, 07:00:09 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 23, 11:00:07 GMT+0
Completed - The scheduled maintenance has been completed..

Duration: 4 hours

Affected Components: SMS

Jul 7, 02:25:58 GMT+0
Scheduled - Twilio is conducting a planned maintenance from 19 August 2026 at 20:00 PDT until 20 August 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of long codes and short codes..

Aug 20, 03:00:08 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 20, 02:00:34 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

Aug 20, 07:00:09 GMT+0
Completed - The scheduled maintenance has been completed..

Duration: 12 days, 20 hours and 26 minutes

Affected Components: SMS

Aug 19, 09:40:14 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Bell Aliant network subscribers in Canada. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available..

Aug 19, 10:41:33 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Bell Aliant network subscribers in Canada. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 19, 14:48:40 GMT+0
Resolved - The incident has been resolved and SMS delivery from a subset of Twilio Long Codes to Bell Aliant network subscribers in Canada is operating normally..

Aug 19, 12:44:57 GMT+0
Monitoring - We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to Bell Aliant network subscribers in Canada and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 19, 14:46:36 GMT+0
Monitoring - We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to Bell Aliant network subscribers in Canada and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available..

Duration: 10 hours

Affected Components: SMS

Aug 17, 19:43:20 GMT+0
Scheduled - <p>The T-Mobile network in the United States is conducting a planned maintenance from 18 August 2026 at 19:00 PDT until 19 August 2026 at 05:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes.</p>.

Aug 19, 02:00:08 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 19, 12:00:08 GMT+0
Completed - The scheduled maintenance has been completed..

Aug 19, 01:00:25 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

Duration: 2 hours

Affected Components: SMS

Aug 19, 01:25:11 GMT+0
Scheduled - <p>A subset of small networks in the US are conducting an emergency maintenance from 18 August 2026 at 19:00 PDT until 18 August 2026 at 21:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to small US carriers handsets when sending via long codes, long codes, short codes and toll free numbers.</p> <p>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>.

Aug 19, 02:01:07 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 19, 04:00:13 GMT+0
Completed - The scheduled maintenance has been completed..

Duration: 10 hours

Affected Components: SMS

Aug 18, 12:00:18 GMT+0
Completed - The scheduled maintenance has been completed..

Aug 18, 02:00:08 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Aug 17, 06:56:01 GMT+0
Scheduled - <p>The T-Mobile network in the United States is conducting a planned maintenance from 17 August 2026 at 19:00 PDT until 18 August 2026 at 05:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets.</p> <p>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>.

Aug 18, 01:00:23 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

Duration: 2 days, 7 hours and 18 minutes

Affected Components: SMS

Aug 17, 02:13:14 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio to Liberty Mobile network subscribers in Puerto Rico. Our team is actively investigating this issue. We will provide another update in 8 hours or as soon as more information becomes available..

Aug 16, 19:12:27 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio to Liberty Mobile network subscribers in Puerto Rico. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available..

Aug 16, 20:12:43 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio to Liberty Mobile network subscribers in Puerto Rico. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 16, 22:12:57 GMT+0
Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio to Liberty Mobile network subscribers in Puerto Rico. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available..

Aug 17, 06:22:43 GMT+0
Monitoring - We have observed a recovery in SMS delivery from Twilio to Liberty Mobile network subscribers in Puerto Rico and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 17, 08:31:46 GMT+0
Resolved - The incident has been resolved and SMS delivery from Twilio to Liberty Mobile network subscribers in Puerto Rico is operating normally..

Duration: 16 days, 16 hours and 59 minutes

Affected Components: SMS

Aug 12, 22:55:18 GMT+0
Investigating - Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Bell in Canada. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available..

Aug 12, 23:06:11 GMT+0
Identified - Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Bell in Canada. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available..

Aug 13, 00:07:44 GMT+0
Identified - Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Bell in Canada. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 13, 02:13:06 GMT+0
Identified - Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Bell in Canada. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available..

Aug 13, 02:55:00 GMT+0
Monitoring - We have observed a recovery in User Authentication Identity Gateway API failure increase for Bell in Canada and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available..

Aug 13, 05:01:00 GMT+0
Monitoring - We have observed a recovery in User Authentication Identity Gateway API failure increase for Bell in Canada and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available..

Aug 13, 05:36:17 GMT+0
Resolved - The incident has been resolved and User Authentication Identity Gateway API failure increase for Bell in Canada is operating normally..

Duration: 1 day, 15 hours and 42 minutes

Affected Components: Ardament Website & Landing Page Hosting

Aug 5, 08:26:18 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results..

Aug 5, 08:42:17 GMT+0
Resolved - This incident has been resolved..

Aug 5, 08:15:03 GMT+0
Identified - The issue has been identified and a fix is being implemented..

Aug 5, 08:02:34 GMT+0
Investigating - Cloudflare is investigating an issue where uploads for Pages and Workers Assets have reduced availability. We are working to analyse and mitigate this problem. More updates to follow shortly..

Duration: 5 days, 5 hours and 5 minutes

Affected Components: , WundertreOS Database →

Aug 3, 16:19:52 GMT+0
Investigating - We are continuing to investigate project upgrade issues..

Aug 3, 15:28:10 GMT+0
Investigating - We are investigating a potential issue that could result in a delay or failure in some users' project upgrades..

Aug 3, 19:47:58 GMT+0
Identified - We are developing a fix for the upgrade issues..

Aug 3, 17:09:16 GMT+0
Identified - We have identified the cause of the upgrade delays and are working on a fix..

Aug 3, 22:46:03 GMT+0
Identified - We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours..

Aug 4, 15:30:47 GMT+0
Identified - The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied..

Aug 4, 23:38:20 GMT+0
Identified - We are continuing to test the fix to project upgrades. We will update again when the fix is applied..

Aug 5, 14:58:43 GMT+0
Monitoring - We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability..

Aug 5, 17:33:15 GMT+0
Resolved - Project upgrades have remained stable, we are resolving this incident..

Duration: 2 days, 10 hours and 22 minutes

Affected Components: , WundertreOS Database →

Jul 31, 12:41:51 GMT+0
Identified - We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available..

Jul 31, 12:27:54 GMT+0
Investigating - We're investigating issues updating DNS records for newly created, unpaused, or updated databases..

Jul 31, 13:26:16 GMT+0
Resolved - The incident has been resolved..

Jul 31, 12:55:52 GMT+0
Monitoring - The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available..

Duration: 2 days, 22 hours and 52 minutes

Affected Components: Ardament Website & Landing Page Hosting

Jul 31, 12:37:35 GMT+0
Investigating - Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate..

Jul 31, 12:43:57 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results..

Jul 31, 13:01:59 GMT+0
Resolved - This incident has been resolved..

Jul 31, 11:51:07 GMT+0
Investigating - Cloudflare is investigating reduced availability with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed..

Jul 31, 12:25:44 GMT+0
Investigating - We are continuing to investigate this issue..

Jul 31, 12:46:20 GMT+0
Monitoring - We are continuing to monitor for any further issues..

Duration: 18 days, 6 hours and 38 minutes

Affected Components: Functions

Jul 30, 18:16:21 GMT+0
Investigating - Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause..

Jul 30, 17:37:45 GMT+0
Investigating - We are aware of some users experiencing issues with Edge Function deployments..

Jul 30, 18:28:01 GMT+0
Investigating - We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully..

Jul 30, 21:02:49 GMT+0
Investigating - We are continuing to investigate this issue..

Jul 30, 19:46:12 GMT+0
Investigating - Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues..

Jul 31, 00:26:11 GMT+0
Identified - The issue has been identified and a fix is being implemented..

Jul 30, 22:21:19 GMT+0
Investigating - We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience..

Jul 30, 23:40:32 GMT+0
Investigating - We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions..

Jul 31, 03:13:26 GMT+0
Monitoring - Our fix has completed rollout and we are monitoring for full resolution..

Jul 31, 09:36:27 GMT+0
Identified - We are working on a permanent fix for issue affecting bulk Function deployments. In parallel, we are manually assisting customers who have reported the issue through support tickets..

Jul 31, 13:20:23 GMT+0
Resolved - A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected. As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident. All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation..

Duration: 1 day, 18 hours and 41 minutes

Affected Components: Auth

Jul 28, 21:24:22 GMT+0
Investigating - We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available..

Jul 28, 21:33:28 GMT+0
Identified - We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made..

Jul 28, 21:53:44 GMT+0
Monitoring - We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident..

Jul 28, 22:07:03 GMT+0
Resolved - The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected..

Duration: 5 days, 1 hour and 49 minutes

Affected Components: , WundertreOS Database →

Jul 27, 20:34:54 GMT+0
Investigating - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects..

Jul 27, 20:39:48 GMT+0
Identified - We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress..

Jul 27, 20:53:39 GMT+0
Identified - We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects..

Jul 27, 22:23:08 GMT+0
Monitoring - All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident..

Jul 27, 22:36:44 GMT+0
Resolved - This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records..

Duration: 1 day, 10 hours and 48 minutes

Affected Components: Auth

Jul 25, 14:45:52 GMT+0
Resolved - Authentication operations have returned to normal consistently..

Jul 25, 14:25:27 GMT+0
Monitoring - Authentication has returned to normal..

Jul 25, 14:11:04 GMT+0
Investigating - Some projects are experiencing authentication issues. We are actively investigating..

Jul 25, 14:21:05 GMT+0
Identified - We have implemented a fix to the authentication issue and are monitoring for recovery..

Duration: 18 days and 13 hours

Affected Components: Email

Duration: 6 days, 3 hours and 25 minutes

Affected Components: Email

Duration: 19 days, 15 hours and 46 minutes

Affected Components: , WundertreOS Database →

Jul 17, 19:20:33 GMT+0
Investigating - We are testing mitigation options to attempt to restore project action performance..

Jul 17, 18:16:46 GMT+0
Investigating - Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance..

Jul 17, 17:49:58 GMT+0
Investigating - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue..

Jul 17, 18:47:55 GMT+0
Investigating - We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel..

Jul 17, 19:45:29 GMT+0
Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results..

Jul 17, 20:21:37 GMT+0
Monitoring - The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality..

Jul 18, 01:41:45 GMT+0
Resolved - Project actions have been sustained at normal performance. This incident is resolved..

Duration: 2 days, 5 hours and 58 minutes

Affected Components: Storage Buckets

Jul 16, 18:32:02 GMT+0
Identified - We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress.

Jul 16, 17:55:02 GMT+0
Identified - We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue..

Jul 16, 18:23:28 GMT+0
Identified - A likely mitigation has been identified and we are discussing the proper implementation method..

Jul 16, 18:49:00 GMT+0
Resolved - This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests. The change has been reverted and issue is now fixed..

Duration: 3 days, 7 hours and 56 minutes

Affected Components: Functions

Jul 8, 18:37:52 GMT+0
Investigating - We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions.

Jul 8, 19:57:48 GMT+0
Resolved - Edge function operations are normal..

Jul 8, 19:16:17 GMT+0
Identified - We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects..

Jul 8, 19:28:06 GMT+0
Monitoring - A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance..

Affected Components: WundertreOS API

Jul 6, 16:00:26 GMT+0
Resolved - WundertreOS API is back up. This incident was automatically resolved by Instatus monitoring..

Jul 6, 15:55:14 GMT+0
Investigating - WundertreOS API is down at the moment. This incident was automatically created by Instatus monitoring..

Duration: 3 days, 4 hours and 34 minutes

Affected Components: Storage Buckets

Jul 1, 18:40:19 GMT+0
Monitoring - Provisioning times and project lifecycle operations have returned normal. We will continue to monitor..

Jul 1, 18:56:13 GMT+0
Resolved - This issue is now resolved. Provisioning times and project lifecycle operations have returned to normal..

Jul 1, 17:39:39 GMT+0
Identified - We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects. Customers may experience longer than expected provisioning times after creating a new project, and some project lifecycle operations may also be delayed while setup completes. Our team is has identified the issue and are working to restore normal provisioning times. We will provide another update as soon as we have more information..

Duration: 3 days, 19 hours and 40 minutes

Affected Components: Functions

Jul 1, 14:40:41 GMT+0
Investigating - We are currently investigating an issue affecting the Edge Function API requests. Our team is working on a fix, and we will provide another update as soon as more information becomes available..

Jul 1, 14:59:10 GMT+0
Identified - The team has identified the root cause of the issue and is currently rolling out a fix across the platform. We will continue to monitor the rollout and provide another update once it has been completed..

Jul 1, 15:30:50 GMT+0
Monitoring - We have implemented a fix, and error rates have returned to expected levels. We are continuing to monitor the platform closely to ensure the issue is fully resolved..

Jul 1, 16:12:21 GMT+0
Resolved - Edge Function API requests have returned to normal. This issue is now resolved..

Duration: 22 days, 3 hours and 31 minutes

Affected Components: Compute

Jun 30, 02:43:49 GMT+0
Investigating - Project creation is impacted across multiple regions, we are investigating the root cause..

Jun 30, 02:38:13 GMT+0
Investigating - We are currently investigating an issue affecting project creation in multiple regions..

Jun 30, 03:38:57 GMT+0
Identified - We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information..

Jun 30, 03:08:41 GMT+0
Investigating - We have identified the issue and confirmed that impact extends beyond project creation. Project creation, project resizing, branch provisioning, and project restarts are currently affected across multiple regions. We will share another update as soon as we have more information..

Jun 30, 04:32:20 GMT+0
Identified - We are continuing to work on a fix for the issue and will provide updates as more information is available..

Jun 30, 05:11:59 GMT+0
Identified - We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses..

Jun 30, 06:49:02 GMT+0
Identified - We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses..

Jun 30, 11:20:04 GMT+0
Identified - Additional capacity has been made available in the majority of regions, and we're seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts. We are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1. As a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail. We are actively working to restore full capacity and will provide another update as soon as more information is available..

Jun 30, 18:58:41 GMT+0
Identified - We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available..

Jun 30, 22:22:56 GMT+0
Identified - We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available..

Jul 1, 03:23:43 GMT+0
Identified - We are continuing to remediate the capacity constraints affecting multiple regions (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, eu-central-2, eu-north-1, sa-east-1, us-east-1, us-east-2). Project operations that require capacity in these regions may continue to fail or require a re-try. We will provide another update as soon as more information is available..

Jul 1, 10:12:44 GMT+0
Identified - We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts. These operations may fail intermittently or require one or more retries to complete successfully. Our team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations. We will provide another update as soon as more information becomes available..

Jul 1, 16:58:37 GMT+0
Identified - We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations. Our team is actively implementing mitigation measures to increase capacity and restore normal service. We will provide further updates as the situation evolves. If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying. This issue does not affect existing running projects or their availability..

Jul 2, 01:30:02 GMT+0
Identified - We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations. Our team is actively implementing mitigation measures to increase capacity and restore normal service. We will provide further updates as the situation evolves. If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying. This issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades..

Jul 2, 05:53:07 GMT+0
Identified - We are seeing capacity improvements across all regions, but are continuing to work on a full mitigation for all users. Project creation, project resizing, project restarts, branch provisioning, and restores are slowly recovering and we are asking users to re-try their database actions. Please reach out to our Support if you continue to fail. Running projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade. We are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority..

Jul 2, 10:40:45 GMT+0
Identified - We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, branch revisioning, and restores are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures. Our team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts with stores or database upgrades while the incident has been in progress.

Jul 2, 15:08:17 GMT+0
Identified - We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, and branch operations are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures. We are working to recover subset of projects which are still down due to infrastructure compatibility constraints. Our team is actively working on solutions to restore these remaining affected projects and will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress..

Jul 3, 09:43:42 GMT+0
Identified - We currently have capacity available across all regions and are continuing to make progress on our remaining mitigation work, primarily by bringing additional capacity online. This is currently our top priority. We are also recovering a subset of projects which are still down due to infrastructure compatibility constraints. Our team is continuing to restore these remaining affected projects and will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress..

Jul 3, 16:03:14 GMT+0
Identified - Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority. We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses. The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121. New project deployments should succeed, but restarts or resizes for projects matching this profile may fail. Existing projects are not affected unless they have been restarted or resized during this incident..

Jul 3, 19:57:30 GMT+0
Identified - We're continuing to work through elevated capacity errors affecting some restart and resize operations. Availability for smaller compute sizes has improved across most regions, and error rates are trending down. Capacity for some smaller compute sizes remains constrained in a number of regions, most notably Medium. We are actively adding capacity across all regions to relieve this. If your project is on Postgres 17.6.1.121 or earlier, upgrading to 17.6.1.121 or higher gives it access to additional machine types, which improves the likelihood of a successful restart or resize in affected regions. You can check your current version and start an upgrade from your project's infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes..

Jul 4, 04:34:48 GMT+0
Identified - Update - Availability for smaller compute sizes has improved across most regions, and error rates are trending down. We are continuing to monitor available capacity in all regions. If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes..

Jul 4, 22:40:14 GMT+0
Identified - We are continuing to monitor available capacity in all regions. If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes..

Jul 6, 11:32:36 GMT+0
Identified - Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system. The remaining impact is limited to projects running a Postgres version older than 17.6.1.121. These older versions can only run on a narrower set of instance types, which are the ones still under capacity pressure, so a restart or resize may fail or need a retry. Projects on 17.6.1.121 or newer can run on a wider set of instance types and are much less likely to be affected. If a restart or resize is failing, upgrading to Postgres 17.6.1.121 or newer resolves it in most cases. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If you're still unable to resize or restart after upgrading, our support team can help. We will update this page as the situation materially changes..

Jul 6, 16:36:49 GMT+0
Monitoring - Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system. We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types. We will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely. If you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page..

Jul 8, 16:41:39 GMT+0
Monitoring - We continue to monitor capacity recovery across all regions. We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types. We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely..

Jul 10, 18:41:44 GMT+0
Monitoring - We continue to monitor capacity across all regions. The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency. We will continue monitoring closely to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely..

Jul 13, 16:00:12 GMT+0
Resolved - Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident. Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage..

Duration: 11 days, 7 hours and 8 minutes

Affected Components: , WundertreOS Database →

Jun 25, 14:41:28 GMT+0
Investigating - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays..

Jun 25, 16:03:11 GMT+0
Identified - We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters..

Jun 25, 14:20:31 GMT+0
Investigating - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps..

Jun 25, 17:03:54 GMT+0
Identified - We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems..

Jun 25, 15:01:28 GMT+0
Identified - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources..

Jun 25, 15:32:53 GMT+0
Identified - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades..

Jun 25, 16:27:00 GMT+0
Identified - We are implementing operational mitigations to try to improve upgrade performance..

Jun 25, 17:46:27 GMT+0
Identified - We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet..

Jun 25, 18:08:06 GMT+0
Monitoring - We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support..

Jun 25, 18:51:40 GMT+0
Resolved - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved..

Duration: 2 days, 1 hour and 24 minutes

Affected Components: Email

Duration: 3 days, 3 hours and 41 minutes

Affected Components: , WundertreOS Database →

Jun 23, 15:16:57 GMT+0
Investigating - We are investigating errors in creating and unpausing projects in the eu-west-1 region..

Jun 23, 15:26:40 GMT+0
Identified - We have identified the issue is related to keys and are preparing a mitigation..

Jun 23, 15:43:13 GMT+0
Identified - Multiple mitigations have been deployed and project create performance is improving..

Jun 23, 15:46:38 GMT+0
Identified - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect..

Jun 23, 16:01:57 GMT+0
Monitoring - Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes..

Jun 23, 16:32:38 GMT+0
Resolved - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes..

Duration: 6 days, 14 hours and 5 minutes

Affected Components: Email

Duration: 1 hour

Affected Components: Functions

May 4, 03:00:07 GMT+0
Scheduled - Maintenance will begin as scheduled in 60 minutes..

May 4, 05:00:08 GMT+0
Completed - The scheduled maintenance has been completed..

May 1, 17:18:29 GMT+0
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..

May 4, 04:00:07 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..