Vendor record
Turso
Checked
Front door check counts and Turso’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Turso endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,875 of 2,875 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
4 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.turso.tech
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Turso product, region or your app worked.
How we count front door checksTurso says
Incident posts from Turso’s status page, with its titles, impact levels and times. They say what Turso chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents Turso posted, last 7 days
Most recent records · all dates
Elevated errors of 502 on database queries
Not specifiedTurso’s postStarted, per Turso
Closed in our record(48m)
Turso API unavailable
Not specifiedTurso’s postStarted, per Turso
Closed in our record(19m)
Some databases affected by the US-EAST-1 outage
Not specifiedTurso’s postStarted, per Turso
Closed in our record(2h)
Authentication issues with turso dashboard
Not specifiedTurso’s postStarted, per Turso
Closed in our record(0m)
Issues with fly.io databases
Not specifiedTurso’s postStarted, per Turso
Closed in our record(14h 44m)
5 older records
Fly.io incident in SJC region
MajorStarted, per Turso
Closed in our record(233d 5h)
problems creating new databases
MajorStarted, per Turso
Closed in our record(255d 5h)
us-east-1 partial unavailability
MajorStarted, per Turso
Closed in our record(255d 13h)
Database and group token generation unavailable
MajorStarted, per Turso
Closed in our record(318d 5h)
Network issues in IAD Fly region
MajorStarted, per Turso
Closed in our record(356d 1h)
Your code, your dependencies
See which of your code paths call Turso
Connect GitHub or GitLab to find where your public or private repository uses Turso. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Turso status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Turso currently down?
Turso's latest recorded status is Major Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Turso last have an outage?
The most recent closed incident record began 72 days ago and spans 48 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Turso?
No. CheckUpstream checks Turso’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Turso in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Turso?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.