User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
loopup.com · Telecom
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests loopup.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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 1121 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 1190 ms | 0 |
| 03:15 | 0 | 0.0 | 1898 ms | 0 |
| 03:30 | 0 | 0.0 | 1663 ms | 0 |
| 03:45 | 0 | 0.0 | 1325 ms | 0 |
| 04:00 | 0 | 0.0 | 1214 ms | 0 |
| 04:15 | 0 | 0.0 | 2654 ms | 0 |
| 04:30 | 0 | 0.0 | 1856 ms | 0 |
| 04:45 | 0 | 0.0 | 937 ms | 0 |
| 05:00 | 0 | 0.0 | 1925 ms | 0 |
| 05:15 | 0 | 0.0 | 1459 ms | 0 |
| 05:30 | 0 | 0.0 | 948 ms | 0 |
| 05:45 | 0 | 0.0 | 1414 ms | 0 |
| 06:00 | 0 | 0.0 | 1164 ms | 0 |
| 06:15 | 0 | 0.0 | 1604 ms | 0 |
| 06:30 | 0 | 0.0 | 3150 ms | 0 |
| 06:45 | 0 | 0.0 | 1642 ms | 0 |
| 07:00 | 0 | 0.0 | 2025 ms | 0 |
| 07:15 | 0 | 0.0 | 1642 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 Loopup 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 Loopup goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Loopup 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 Loopup 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 Loopup'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.