outages.live
Live
TursoIncident ·

Major outage

ResolvedOfficial update
0

Turso reports a major outage in AWS us-west-2 (Oregon). Turso reports that the incident is resolved. The outage lasted 24 minutes.

State

Resolved

Started

Lasted

24 min

Worst impact

Major outage

Timeline

2 updates
06:1206:1806:2406:3006:36
Major outageUpdate postedTimes in UTC

Components degraded

24 min 100%

Updates

Times in UTC

As posted by Turso

Resolved
Components degraded

Affected components

1
AWS us-west-2 (Oregon)

Turso in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 2 min

This incident

61% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 h 7 min
median 1 h 2 min
90 days agoToday

Other Turso incidents

All incidents

Turso·Elevated error rates and latencies in us-west-2

In us-west-2, there was a 24-minute period of elevated latencies and error rates for database, group and token creations as well as some control plane read operations. The issue has been resolved.

Resolved

Turso·Elevated timeouts in us-east-1

A malfunctioning load balancer in us-east-1 caused intermittent timeouts. We moved traffic to a new load balancer and requests are completing normally again.

Resolved

Turso·Degraded for Fly regions

The issue is resolved and databases on Fly are back to healthy status.

Resolved

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.live/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.live/feed.xml?providers=turso
Slack
/feed subscribe https://outages.live/feed.xml?providers=turso

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane