User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
elev.io · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 529 ms · 3 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:15 | 0 | 0.0 | 464 ms | 0 |
| 04:30 | 0 | 0.0 | 488 ms | 0 |
| 04:45 | 0 | 0.0 | 452 ms | 0 |
| 05:00 | 0 | 0.0 | 126 ms | 0 |
| 05:15 | 0 | 0.0 | 596 ms | 0 |
| 05:30 | 0 | 0.0 | 634 ms | 0 |
| 05:45 | 0 | 0.0 | 475 ms | 0 |
| 06:00 | 0 | 0.0 | 421 ms | 0 |
| 06:15 | 0 | 0.0 | 397 ms | 0 |
| 06:30 | 0 | 0.0 | 382 ms | 0 |
| 06:45 | 0 | 0.0 | 834 ms | 0 |
| 07:00 | 0 | 0.0 | 648 ms | 0 |
| 07:15 | 0 | 0.0 | 250 ms | 0 |
| 07:30 | 0 | 0.0 | 452 ms | 0 |
| 07:45 | 0 | 0.0 | 188 ms | 0 |
| 08:00 | 0 | 0.0 | 446 ms | 0 |
| 08:15 | 0 | 0.0 | 591 ms | 0 |
| 08:30 | 0 | 0.0 | 221 ms | 0 |
| 08:45 | 0 | 0.0 | 131 ms | 0 |
| 09:00 | 0 | 0.0 | 240 ms | 0 |
| 09:15 | 0 | 0.0 | 580 ms | 0 |
| 09:30 | 0 | 0.0 | 127 ms | 0 |
| 09:45 | 0 | 0.0 | 460 ms | 0 |
| 10:00 | 0 | 0.0 | 421 ms | 0 |
| 10:15 | 0 | 0.0 | 552 ms | 0 |
| 10:30 | 0 | 0.0 | 593 ms | 0 |
| 10:45 | 0 | 0.0 | 430 ms | 0 |
| 11:00 | 0 | 0.0 | 475 ms | 0 |
| 11:15 | 0 | 0.0 | 516 ms | 0 |
| 11:30 | 0 | 0.0 | 520 ms | 0 |
| 11:45 | 0 | 0.0 | 933 ms | 0 |
| 12:00 | 0 | 0.0 | 296 ms | 0 |
| 12:15 | 0 | 0.0 | 600 ms | 0 |
| 12:30 | 0 | 0.0 | 183 ms | 0 |
| 12:45 | 0 | 0.0 | 527 ms | 0 |
| 13:00 | 0 | 0.0 | 518 ms | 0 |
| 13:15 | 0 | 0.0 | 549 ms | 0 |
| 13:30 | 0 | 0.0 | 647 ms | 0 |
| 13:45 | 0 | 0.0 | 482 ms | 0 |
| 14:00 | 0 | 0.0 | 162 ms | 0 |
| 14:15 | 0 | 0.0 | 654 ms | 0 |
| 14:30 | 0 | 0.0 | 381 ms | 0 |
| 14:45 | 0 | 0.0 | 566 ms | 0 |
| 15:00 | 0 | 0.0 | 264 ms | 0 |
| 15:15 | 0 | 0.0 | 670 ms | 0 |
| 15:30 | 0 | 0.0 | 496 ms | 0 |
| 15:45 | 0 | 0.0 | 570 ms | 0 |
| 16:00 | 0 | 0.0 | 529 ms | 0 |
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.
No outages on record for Elevio yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Elevio goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Elevio alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Elevio 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 Elevio's side.
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.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.