User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
urllo.com · Money
Something is off: our checks are slower than usual or had a single recent failure.
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.
Reachable from all 4 regions we check from.
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.
Slow or flaky
Last check reached it in 301 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 467 ms | 0 |
| 08:15 | 0 | 0.0 | 484 ms | 0 |
| 08:30 | 0 | 0.0 | 746 ms | 0 |
| 08:45 | 0 | 0.0 | 172 ms | 0 |
| 09:00 | 0 | 0.0 | 123 ms | 0 |
| 09:15 | 0 | 0.0 | 758 ms | 0 |
| 09:30 | 0 | 0.0 | 151 ms | 0 |
| 09:45 | 0 | 0.0 | 328 ms | 0 |
| 10:00 | 0 | 0.0 | 731 ms | 0 |
| 10:15 | 0 | 0.0 | 322 ms | 0 |
| 10:30 | 0 | 0.0 | 1307 ms | 0 |
| 10:45 | 0 | 0.0 | 206 ms | 0 |
| 11:00 | 0 | 0.0 | 489 ms | 0 |
| 11:15 | 0 | 0.0 | 759 ms | 0 |
| 11:30 | 0 | 0.0 | 334 ms | 0 |
| 11:45 | 0 | 0.0 | 966 ms | 0 |
| 12:00 | 0 | 0.0 | 600 ms | 0 |
| 12:15 | 0 | 0.0 | 803 ms | 0 |
| 12:30 | 0 | 0.0 | 162 ms | 0 |
| 12:45 | 0 | 0.0 | 298 ms | 0 |
| 13:00 | 0 | 0.0 | 438 ms | 0 |
| 13:15 | 0 | 0.0 | 289 ms | 0 |
| 13:30 | 0 | 0.0 | 923 ms | 0 |
| 13:45 | 0 | 0.0 | 256 ms | 0 |
| 14:00 | 0 | 0.0 | 217 ms | 0 |
| 14:15 | 0 | 0.0 | 1024 ms | 0 |
| 14:30 | 0 | 0.0 | 369 ms | 0 |
| 14:45 | 0 | 0.0 | 849 ms | 0 |
| 15:00 | 0 | 0.0 | 192 ms | 0 |
| 15:15 | 0 | 0.0 | 778 ms | 0 |
| 15:30 | 0 | 0.0 | 260 ms | 0 |
| 15:45 | 0 | 0.0 | 662 ms | 0 |
| 16:00 | 0 | 0.0 | 1162 ms | 0 |
| 16:15 | 0 | 0.0 | 190 ms | 0 |
| 16:30 | 0 | 0.0 | 630 ms | 0 |
| 16:45 | 0 | 0.0 | 777 ms | 0 |
| 17:00 | 0 | 0.0 | 114 ms | 0 |
| 17:15 | 0 | 0.0 | 224 ms | 0 |
| 17:30 | 0 | 0.0 | 1162 ms | 0 |
| 17:45 | 0 | 0.0 | 116 ms | 0 |
| 18:00 | 0 | 0.0 | 816 ms | 0 |
| 18:15 | 0 | 0.0 | 571 ms | 0 |
| 18:30 | 0 | 0.0 | 508 ms | 0 |
| 18:45 | 0 | 0.0 | 169 ms | 0 |
| 19:00 | 0 | 0.0 | 620 ms | 0 |
| 19:15 | 0 | 0.0 | 373 ms | 0 |
| 19:30 | 0 | 0.0 | 961 ms | 0 |
| 19:45 | 0 | 0.0 | 301 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 EasyRedir 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 EasyRedir goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send EasyRedir alerts to Slack, Discord or a webhook — free.
Something is off: our checks are slower than usual or had a single recent failure.
If EasyRedir 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 EasyRedir'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.