Damn, is it down?

All services / Cloud & developer

sleuth.io · Cloud & developer

Is Sleuth down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → sleuth.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 435 ms · 1 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10645 ms15:3021:3003:3009:1515:15
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:3000.0304 ms0
03:4500.0186 ms0
04:0000.0311 ms0
04:1500.0244 ms0
04:3000.0633 ms0
04:4500.0160 ms0
05:0000.0242 ms0
05:1500.0645 ms0
05:3000.0202 ms0
05:4500.0380 ms0
06:0000.0206 ms0
06:1500.0327 ms0
06:3000.0273 ms0
06:4500.0322 ms0
07:0000.0142 ms0
07:1500.0499 ms0
07:3000.077 ms0
07:4500.0330 ms0
08:0000.0407 ms0
08:1500.0131 ms0
08:3000.0336 ms0
08:4500.0362 ms0
09:0000.0159 ms0
09:1500.0277 ms0
09:3000.0187 ms0
09:4500.0115 ms0
10:0000.0357 ms0
10:1500.0309 ms0
10:3000.0203 ms0
10:4500.0288 ms0
11:0000.0140 ms0
11:1500.067 ms0
11:3000.0256 ms0
11:4500.0138 ms0
12:0000.0131 ms0
12:1500.0363 ms0
12:3000.0430 ms0
12:4500.032 ms0
13:0000.0206 ms0
13:1500.0144 ms0
13:3000.0430 ms0
13:4500.0455 ms0
14:0000.0264 ms0
14:1500.0522 ms0
14:3000.0232 ms0
14:4500.0527 ms0
15:0000.0313 ms0
15:1500.0574 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Sleuth status badge Embed a live Sleuth status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Sleuth status and 30-day uptime badge

Past outages

No outages on record for Sleuth yet. Outages of 10 minutes or more get their own page here.

All Sleuth outages · Every recent outage

Having trouble with Sleuth?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is Sleuth down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

Sleuth not working for me but the status is fine. What now?

If Sleuth is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Sleuth's side.

How does Damn is it down decide Sleuth's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is Sleuth checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.