User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
loops.so · Productivity
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 197 ms · 1 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:15 | 0 | 0.0 | 159 ms | 0 |
| 04:30 | 0 | 0.0 | 387 ms | 0 |
| 04:45 | 0 | 0.0 | 320 ms | 0 |
| 05:00 | 0 | 0.0 | 315 ms | 0 |
| 05:15 | 0 | 0.0 | 635 ms | 0 |
| 05:30 | 0 | 0.0 | 348 ms | 0 |
| 05:45 | 0 | 0.0 | 174 ms | 0 |
| 06:00 | 0 | 0.0 | 354 ms | 0 |
| 06:15 | 0 | 0.0 | 307 ms | 0 |
| 06:30 | 0 | 0.0 | 333 ms | 0 |
| 06:45 | 0 | 0.0 | 245 ms | 0 |
| 07:00 | 0 | 0.0 | 369 ms | 0 |
| 07:15 | 0 | 0.0 | 421 ms | 0 |
| 07:30 | 0 | 0.0 | 375 ms | 0 |
| 07:45 | 0 | 0.0 | 408 ms | 0 |
| 08:00 | 0 | 0.0 | 422 ms | 0 |
| 08:15 | 0 | 0.0 | 460 ms | 0 |
| 08:30 | 0 | 0.0 | 401 ms | 0 |
| 08:45 | 0 | 0.0 | 132 ms | 0 |
| 09:00 | 0 | 0.0 | 540 ms | 0 |
| 09:15 | 0 | 0.0 | 716 ms | 0 |
| 09:30 | 0 | 0.0 | 261 ms | 0 |
| 09:45 | 0 | 0.0 | 489 ms | 0 |
| 10:00 | 0 | 0.0 | 82 ms | 0 |
| 10:15 | 0 | 0.0 | 685 ms | 0 |
| 10:30 | 0 | 0.0 | 560 ms | 0 |
| 10:45 | 0 | 0.0 | 513 ms | 0 |
| 11:00 | 0 | 0.0 | 495 ms | 0 |
| 11:15 | 0 | 0.0 | 346 ms | 0 |
| 11:30 | 0 | 0.0 | 176 ms | 0 |
| 11:45 | 0 | 0.0 | 517 ms | 0 |
| 12:00 | 0 | 0.0 | 424 ms | 0 |
| 12:15 | 0 | 0.0 | 287 ms | 0 |
| 12:30 | 0 | 0.0 | 340 ms | 0 |
| 12:45 | 0 | 0.0 | 505 ms | 0 |
| 13:00 | 0 | 0.0 | 89 ms | 0 |
| 13:15 | 0 | 0.0 | 651 ms | 0 |
| 13:30 | 0 | 0.0 | 581 ms | 0 |
| 13:45 | 0 | 0.0 | 526 ms | 0 |
| 14:00 | 0 | 0.0 | 498 ms | 0 |
| 14:15 | 0 | 0.0 | 282 ms | 0 |
| 14:30 | 0 | 0.0 | 300 ms | 0 |
| 14:45 | 0 | 0.0 | 439 ms | 0 |
| 15:00 | 0 | 0.0 | 386 ms | 0 |
| 15:15 | 0 | 0.0 | 497 ms | 0 |
| 15:30 | 0 | 0.0 | 314 ms | 0 |
| 15:45 | 0 | 0.0 | 344 ms | 0 |
| 16:00 | 0 | 0.0 | 197 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 Loops 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 Loops goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Loops 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 Loops 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 Loops'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.