Skip to content

Outage tracker / Turso

Is Turso down?

I'm having a problem

Checks passingchecked 3 minutes ago

Our checks of Turso pass from all 4 regions we check.

As of Nov 5, 2026, 2:31 PM UTC, RealUptime's checks of Turso passed in all 4 regions that returned a reading.

Front-door and live API checks

Our checks of Turso did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show Turso works for users.

our check readinglive · checked Nov 5, 2026, 2:31 PM UTC
US-East889 msChecks passing
US-West702 msChecks passing
Europe425 msChecks passing
Asia-Pacific1502 msChecks passing
their status pagetheir claim, not our reading

Turso publishes no status feed we can read, so the only reading here is our check reading on the left.

Turso response time, by region

US-East
944msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 944ms
Oct 7Oct 21Nov 5
US-West
1.2sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Europe
793msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 587ms2026-11-03 UTC: p95 916ms2026-11-04 UTC: p95 934ms2026-11-05 UTC: p95 793ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Turso

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Turso. It cannot diagnose Turso's own systems.

What we measured, function by function

Turso answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Get an email when our checks of Turso fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Turso fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Turso's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 889msstatus code: 401checked: Nov 5, 2026, 2:30 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Turso normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 702msstatus code: 401checked: Nov 5, 2026, 2:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Turso normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionTurso is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionTurso is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionTurso is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 425msstatus code: 401checked: Nov 5, 2026, 2:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Turso normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionTurso is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1502msstatus code: 401checked: Nov 5, 2026, 2:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Turso normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionTurso is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionTurso is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Turso, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Turso yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Turso.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Turso since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Turso covering any window you pick, with our check readings and Turso's own claim at the time, side by side.

Full check history for Turso: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Turso uptime by RealUptime's checksLive, from this page's own readings.
[![Turso uptime by RealUptime's checks](https://realuptime.io/outages/turso/badge.svg?days=30)](https://realuptime.io/outages/turso)
<a href="https://realuptime.io/outages/turso"><img src="https://realuptime.io/outages/turso/badge.svg?days=30" alt="Turso uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Turso down?", https://realuptime.io/outages/turso. The readings change with every check, so give the date you read them.

How our checks compare with Turso's stated SLA

At or above your target

Our checks of Turso failed for none over the 72h 22m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Turso's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.turso.tech/v1/organizations
secondary
https://turso.tech/
secondary
https://status.turso.tech/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.turso.tech

RealUptime is not affiliated with Turso; the name identifies what we checked, and nothing here speaks for Turso's own team. We send a single web request to Turso from 4 regions on our own schedule and time the response. We do not see inside Turso's systems, do not use an account or real transaction, and are not the same signal Turso's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Turso is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Turso operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 3678 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.