Previous incidents
Outage on Fly.io regions
Resolved May 03 at 07:38am UTC
- 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...
Downtime for databases hosted in Fly regions
Resolved May 03 at 06:10am UTC
We have identified the issue and rolled out the fixes. All databases should be functional.
1 previous update
Writes for DBs at AWS region ap-northeast-1 are partially unavilable
Resolved Apr 16 at 05:34pm UTC
We are seeing increasing error rates for writes to S3 Express One Zone in ap-northeast-1 region.
Issue partially affects writes to the DBs in that region. We are actively investigating the issue with AWS support team.
Writes for DBs at AWS region ap-northeast-1 are unavilable
Resolved Apr 15 at 08:43am UTC
AWS has connectivity issues at ap-northeast-1 AZ at the moment and this incident affects S3 Express One Zone: https://health.aws.amazon.com/health/status
database creation may fail for certain users
Resolved Apr 04 at 01:12am UTC
We have resolved the issue and database creation should work normally now