outages.live
Live

Turso

Turso is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

29

Web and Platform

Turso Website Operational
90 days agoNo incidentsToday
Turso API Operational
90 days agoNo incidentsToday
AWS us-east-1 (N. Virginia) Operational
90 days agoNo incidentsToday
AWS us-east-2 Operational
90 days agoNo incidentsToday
AWS us-west-2 (Oregon) Operational
90 days agoNo incidentsToday
AWS ca-central-1 Operational
90 days agoNo incidentsToday
AWS sa-east-1 Operational
90 days agoNo incidentsToday
AWS eu-west-1 (Ireland) Operational
90 days agoNo incidentsToday
AWS eu-north-1 Operational
90 days agoNo incidentsToday
AWS ap-northeast-1 (Tokyo) Operational
90 days agoNo incidentsToday
AWS ap-south-1 (Mumbai) Operational
90 days agoNo incidentsToday
AWS ap-southeast-2 Operational
90 days agoNo incidentsToday

Turso Fly Locations

Global Operational
90 days agoNo incidentsToday
Amsterdam, Netherlands Operational
90 days agoNo incidentsToday
Ashburn, Virginia (US) Operational
90 days agoNo incidentsToday
Chicago, Illinois (US) Operational
90 days agoNo incidentsToday
Dallas, Texas (US) Operational
90 days agoNo incidentsToday
Frankfurt, Germany Operational
90 days agoNo incidentsToday
Johannesburg, South Africa Operational
90 days agoNo incidentsToday
London, United Kingdom Operational
90 days agoNo incidentsToday
Los Angeles, California (US) Operational
90 days agoNo incidentsToday
Paris, France Operational
90 days agoNo incidentsToday
Sao Paulo, Brazil Operational
90 days agoNo incidentsToday
Secaucus, NJ (US) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Turso

Your coding agent knows when Turso is down, and tells you when a failure is theirs, not yours. You can also get Turso incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "turso" and tell me if Turso has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=turso
Slack
/feed subscribe https://outages.cc/feed.xml?providers=turso

Go from tracking outages to fixing production issues with Polylane.

Try Polylane