We're rolling out an upgrade to our API that distributes more database traffic to local read replicas in each region.

What changes for you

For read operations, you can expect a significant performance improvement depending on the endpoint and your region.
Write operations also benefit from this change through reduced authentication latency and less load on the primary databases.
We’ve also built in safeguards to handle reads-after-writes carefully so you won't run into consistency issues.

For the vast majority of use cases — content delivery, reads in publishing workflows, and API-driven rendering — this difference is imperceptible.

Timeline

Parts of these changes are already live, the main change will take effect on 1st of July.
No action is required on your end.