Is Turso down right now?
Real-time Turso status pulled from status.turso.tech. We refresh every 30 seconds and aggregate active incidents and recent history. For full incident details, visit the official Turso status page linked on the card above.
Major outage: AWS
Turso
Unable to verifyEdge SQLite (libSQL) with replicas.
Status from status.turso.tech · last fetched 5s ago
Developer Platforms
Upstream returned 404
Upstream returned 404
Atlassian source hosting and Pipelines.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
Upstream returned invalid JSON
Claude API, Claude.ai, Claude Code.
AI code editor — chat, tab, composer.
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
ChatGPT, GPT-4, GPT-5, DALL-E, Whisper APIs.
Run open-source ML models via API.
Cloud / Hosting
Service disruption: Increased Error Rates — started 5 days ago
Resolution Issues for .de Domains — started 2 hr ago
Elevated error rates on List Machines endpoint — started 13 min ago
Failures to load data across multiple services on the Vercel dashboard, API, and CLI — started 9 hr ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Compute, Storage, BigQuery, Cloud Run.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain) — started 65 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
SMS Delivery Delays from Twilio to Tigo Guatemala — started 1 hr ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Transactional + marketing email at scale.
Auth / Identity
Communication
No public machine-readable feed; consult the official status page.
Voice, video, text servers and DMs.
Team messaging, calls, huddles, Connect.
Zoom Phone/Zoom Contact Center General Underlying Provider Maintenance — started 4 days ago
Monitoring / Dev Tools
Upstream returned invalid JSON
Upstream returned invalid JSON
APM, infra, logs, RUM, synthetics.
Collaborative design, FigJam, Dev Mode.
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
Quick facts about Turso
- Turso publishes status at status.turso.tech.
- We refresh status every 30 seconds during operational hours.
- For authoritative incident details, always check the official status page.
Frequently asked questions
Why is Turso slow today?
If the dashboard above shows a degraded indicator for Turso, the slowness is on their side. If it shows operational, the issue is likely on your network or local configuration.
How do I know if it's Turso or my internet?
Open this page on a different network (mobile data is the easiest test). If Turso still appears down, it's a real outage. If the dashboard is green here, the issue is local.
Where can I report a Turso outage?
Check https://status.turso.tech for the official outage report channel. Most providers prefer support tickets over public reports.
Does Turso have a status API?
If Turso uses Atlassian Statuspage (most do), the JSON snapshot is at https://status.turso.tech/api/v2/summary.json — no auth required.