TursoStatus record
Latest recorded vendor status
Source checked
A recorded report, not a live test of your application.
Open official status pageCheck the product, region and time against your own logs.
Check counts and incident historyComponent records
Vendor products and regions, with issue records listed first.
| Product / region | Recorded status | Record last seen |
|---|---|---|
Dallas, Texas (US) | Major outage | |
Global | Major outage | |
Los Angeles, California (US) | Major outage | |
Secaucus, NJ (US) | Major outage | |
Stockholm, Sweden | Major outage | |
Amsterdam, Netherlands | Operational | |
Ashburn, Virginia (US) | Operational | |
AWS ap-northeast-1 (Tokyo) | Operational | |
AWS ap-south-1 (Mumbai) | Operational | |
AWS ap-southeast-2 | Operational | |
AWS ca-central-1 | Operational | |
AWS eu-north-1 | Operational |
- Major outage
Dallas, Texas (US)
Record last seen - Major outage
Global
Record last seen - Major outage
Los Angeles, California (US)
Record last seen - Major outage
Secaucus, NJ (US)
Record last seen - Major outage
Stockholm, Sweden
Record last seen - Operational
Amsterdam, Netherlands
Record last seen - Operational
Ashburn, Virginia (US)
Record last seen - Operational
AWS ap-northeast-1 (Tokyo)
Record last seen - Operational
AWS ap-south-1 (Mumbai)
Record last seen - Operational
AWS ap-southeast-2
Record last seen - Operational
AWS ca-central-1
Record last seen - Operational
AWS eu-north-1
Record last seen
1 to 12 of 29 components
“Last seen” is saved when a component changes or its record is refreshed. It is not the time of every status check. These records can differ from the vendor’s overall report.
Recent incidents
Past 30 days
Started or first observed in this window. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not confirm an ongoing outage.
No incident records in this window.
An empty feed does not establish uninterrupted service.
Maintenance and future scheduled work are excluded.
Explore reliability history