Increased response times for requests

Final update

Response times have recovered in all regions. This issue is now resolved.

1. Resolved · Aug 31, 15:57 UTC
   Response times have recovered in all regions. This issue is now resolved.
2. Monitoring · Aug 29, 01:25 UTC
   Response times have recovered in all regions. We will continue to monitor throughout the weekend.
3. Monitoring · Aug 28, 21:06 UTC
   The rollout has been completed in all regions. We will continue to monitor.
4. Identified · Aug 28, 18:15 UTC
   The roll out has also been completed for us-east-1.
5. Identified · Aug 28, 17:21 UTC
   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.
6. Identified · Aug 28, 13:10 UTC
   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.
7. Identified · Aug 28, 01:38 UTC
   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.
8. Investigating · Aug 27, 20:37 UTC
   We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
9. Investigating · Aug 27, 18:55 UTC
   We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
10. Investigating · Aug 27, 17:57 UTC
    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.
11. Investigating · Aug 27, 17:20 UTC
    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.