Damn, is it down?

All services / Cloud & developer

sashido.io · Cloud & developer

Is SashiDo down?

Something is off: our checks are slower than usual or had a single recent failure.

What's broken? (optional)
Is it just me?
Degraded performance

What to try while SashiDo is having problems

  • Try a private/incognito window, or another browser or device.
  • Switch between Wi-Fi and mobile data to rule out your network.
  • Wait a few minutes; most incidents clear on their own.

Live diagnosis

Is it just me?

Tests sashido.io from your browser and compares it with our checks, the official status, and user reports.

Your browser → sashido.io—
Your browser → us—
Our checksSlow or flaky
Official · ReportsAll clear · Near baseline

Press Run testNothing leaves your browser except a request to the site and to us.

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

Slow or flaky

Last check reached it in 427 ms · 7 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10963 ms13:0019:0001:0006:4512:45
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:1500.0171 ms0
03:3000.0963 ms0
03:4500.0149 ms0
04:0000.0233 ms0
04:1500.0213 ms0
04:3000.0224 ms0
04:4500.0197 ms0
05:0000.0162 ms0
05:1500.0131 ms0
05:3000.0128 ms0
05:4500.0232 ms0
06:0000.0224 ms0
06:1500.0119 ms0
06:3000.0163 ms0
06:4500.0183 ms0
07:0000.0117 ms0
07:1500.0323 ms0
07:3000.0234 ms0
07:4500.0134 ms0
08:0000.0107 ms0
08:1500.098 ms0
08:3000.096 ms0
08:4500.0171 ms0
09:0000.0142 ms0
09:1500.0254 ms0
09:3000.0588 ms0
09:4500.0944 ms0
10:0000.0501 ms0
10:1500.0176 ms0
10:3000.0231 ms0
10:4500.0195 ms0
11:0000.0125 ms0
11:1500.079 ms0
11:3000.0355 ms0
11:4500.0131 ms0
12:0000.0242 ms0
12:1500.0226 ms0
12:3000.0864 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.

SashiDo status badge Embed a live SashiDo status badge

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

SashiDo status and 30-day uptime badge

Past outages

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

All SashiDo outages · Every recent outage

Having trouble with SashiDo?

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 SashiDo down right now?

Something is off: our checks are slower than usual or had a single recent failure.

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

If SashiDo 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 SashiDo's side.

How does Damn is it down decide SashiDo'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 SashiDo checked?

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