Previous incidents

• We had an issue with the proxy layer on Fly.io, that should be now resolved.
• Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected.

A long incident!

The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us be...

We have identified the issue and rolled out the fixes. All databases should be functional.