User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 25 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 178 ms | 0 |
| Mon 21 | 0 | 0.0 | 212 ms | 0 |
| Mon 23 | 0 | 0.0 | 335 ms | 0 |
| Tue 01 | 0 | 0.0 | 256 ms | 0 |
| Tue 03 | 0 | 0.0 | 348 ms | 0 |
| Tue 05 | 0 | 0.0 | 329 ms | 0 |
| Tue 07 | 0 | 0.0 | 245 ms | 0 |
| Tue 10 | 0 | 0.0 | 195 ms | 0 |
| Tue 12 | 0 | 0.0 | 204 ms | 0 |
| Tue 14 | 0 | 0.0 | 207 ms | 0 |
| Tue 16 | 0 | 0.0 | 311 ms | 0 |
| Tue 18 | 0 | 0.0 | 382 ms | 0 |
| Tue 21 | 0 | 0.0 | 251 ms | 0 |
| Tue 23 | 0 | 0.0 | 306 ms | 0 |
| Wed 01 | 0 | 0.0 | 364 ms | 0 |
| Wed 03 | 0 | 0.0 | 407 ms | 0 |
| Wed 06 | 0 | 0.0 | 241 ms | 0 |
| Wed 08 | 0 | 0.0 | 303 ms | 0 |
| Wed 10 | 0 | 0.0 | 362 ms | 0 |
| Wed 12 | 0 | 0.0 | 212 ms | 0 |
| Wed 14 | 0 | 0.0 | 399 ms | 0 |
| Wed 16 | 0 | 0.0 | 339 ms | 0 |
| Wed 19 | 0 | 0.0 | 352 ms | 0 |
| Wed 21 | 0 | 0.0 | 138 ms | 0 |
| Wed 23 | 0 | 0.0 | 175 ms | 0 |
| Thu 01 | 0 | 0.0 | 418 ms | 0 |
| Thu 03 | 0 | 0.0 | 494 ms | 0 |
| Thu 05 | 0 | 0.0 | 418 ms | 0 |
| Thu 07 | 0 | 0.0 | 119 ms | 0 |
| Thu 09 | 0 | 0.0 | 366 ms | 0 |
| Thu 12 | 0 | 0.0 | 361 ms | 0 |
| Thu 14 | 0 | 0.0 | 328 ms | 0 |
| Thu 16 | 0 | 0.0 | 233 ms | 0 |
| Thu 18 | 0 | 0.0 | 249 ms | 0 |
| Thu 20 | 0 | 0.0 | 688 ms | 0 |
| Thu 22 | 0 | 0.0 | 306 ms | 0 |
| Fri 00 | 0 | 0.0 | 154 ms | 0 |
| Fri 02 | 0 | 0.0 | 273 ms | 0 |
| Fri 04 | 0 | 0.0 | 511 ms | 0 |
| Fri 06 | 0 | 0.0 | 300 ms | 0 |
| Fri 08 | 0 | 0.0 | 160 ms | 0 |
| Fri 10 | 0 | 0.0 | 342 ms | 0 |
| Fri 12 | 0 | 0.0 | 255 ms | 0 |
| Fri 14 | 0 | 0.0 | 464 ms | 0 |
| Fri 17 | 0 | 0.0 | 338 ms | 0 |
| Fri 19 | 0 | 0.0 | 349 ms | 0 |
| Fri 20 | 0 | 0.0 | 467 ms | 0 |
| Fri 22 | 0 | 0.0 | 159 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Louper 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 Louper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Louper alerts to Slack, Discord or a webhook — free.
Louper is listed in our Cloud & developer category and checked at louper.io. Livestream and collaborate on post-production sessions in up to 4K - easily and securely.
Louper publishes an official status page at status.louper.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 296 ms average, 25–511 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Louper incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
296 ms on average over the last 24 hours (25–511 ms).
Yes, at https://status.louper.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Louper here at once, the problem is on Louper's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Louper. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.