Where does this status come from?

From Turso's own status page API at https://status.turso.tech. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Turso's words.

How can my agent or app check Turso status?

Fetch https://upbutler.com/status/turso/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"turso"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Turso's?

Add "turso" to the dependencies of your UpButler workspace. When one of your monitors fails while Turso has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Turso down?

Right now

No. Turso is operational.

No incidents reported.

Read from status.turso.tech 5 min ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/turso/status.agent.json

MCP: upstream_status {"service":"turso"}

Hosted libSQL / SQLite databases.

What Turso reports

Operational

Taken as is from Turso's own status page API. Incident titles and component names below are theirs.

Open status.turso.tech

UpButler's independent probe

There is no keyless endpoint of Turso that says anything useful, so UpButler does not probe it. To check your own Turso account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Turso components

29 operational

Web and Platform

Turso WebsiteOperational
Turso APIOperational
AWS us-east-1 (N. Virginia)Operational
AWS us-east-2Operational
AWS us-west-2 (Oregon)Operational
AWS ca-central-1Operational
AWS sa-east-1Operational
AWS eu-west-1 (Ireland)Operational
AWS eu-north-1Operational
AWS ap-northeast-1 (Tokyo)Operational
AWS ap-south-1 (Mumbai)Operational
AWS ap-southeast-2Operational

Turso Fly Locations

GlobalOperational
Amsterdam, NetherlandsOperational
Ashburn, Virginia (US)Operational
Chicago, Illinois (US)Operational
Dallas, Texas (US)Operational
Frankfurt, GermanyOperational
Johannesburg, South AfricaOperational
London, United KingdomOperational
Los Angeles, California (US)Operational
Paris, FranceOperational
Sao Paulo, BrazilOperational
Secaucus, NJ (US)Operational
Singapore, SingaporeOperational
Stockholm, SwedenOperational
Sydney, AustraliaOperational
Tokyo, JapanOperational
Toronto, CanadaOperational

Turso incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Turso publishes for 90 days from the day it starts tracking a service.

Tell your outage from Turso's

Declare that your project depends on Turso. When one of your monitors fails while Turso has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - turso

Ask before you retry

curl -s https://upbutler.com/status/turso/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "turso",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Turso down right now?: No. As of 2026-10-10 05:08 UTC, Turso is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Turso's own status page API at https://status.turso.tech. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Turso's words.
How can my agent or app check Turso status?: Fetch https://upbutler.com/status/turso/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"turso"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Turso's?: Add "turso" to the dependencies of your UpButler workspace. When one of your monitors fails while Turso has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with Turso. Status and incident text belong to Turso and are read from their public status source; the probe result is UpButler's own measurement.