Supabase reports multiple service issues

Response times have recovered in all regions. We will continue to monitor throughout the weekend.

The rollout has been completed in all regions. We will continue to monitor.

The roll out has also been completed for us-east-1.

PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions.

PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available.

The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.

We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

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

We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.

We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.

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.

Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.