WundertreOS - Notice history

Project creation has returned to baseline consistently.

Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.

We are seeing the mitigation steps having the desired effect. Project creation is recovering.

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.

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.

We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.

The incident has been resolved and SMS delivery receipts from Twilio Long Codes to Liberty network subscribers in Puerto Rico are operating normally.

We have observed a recovery in SMS delivery receipts from Twilio Long Codes to Liberty 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.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 24 hours or as soon as more information becomes available.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 16 hours or as soon as more information becomes available.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 8 hours or as soon as more information becomes available.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 4 hours or as soon as more information becomes available.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 2 hours or as soon as more information becomes available.

Twilio customers may be experiencing SMS delivery receipt delays from Twilio Long Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.

The fix has remained stable across all regions, and the issue has been resolved.

A fix has been rolled out across all regions, and results are positive.
We will continue monitoring to ensure the service remains stable.
Moving this incident to monitoring.

An enhanced automated solution is currently being tested in staging.
It is expected to be more effective and efficient than the approach used previously.
Once testing has completed successfully, we will use this approach to roll out the fix in production.
We will provide further updates as this work progresses.

We are continuing to rollout the fix to further regions.

This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.

Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.

The incident has been resolved.

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.

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate.

We are continuing to investigate this issue.

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.

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.

Our fix has completed rollout and we are monitoring for full resolution.

The issue has been identified and a fix is being implemented.

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.

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.

We are continuing to investigate this issue.

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.

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.

Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.

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.

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.

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.

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.

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.

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.

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.