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 2 hr ago. Last stored result reached it in 317 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 351 ms | 0 |
| Nov 7 | 0 | 0.0 | 207 ms | 0 |
| Nov 7 | 0 | 0.0 | 177 ms | 0 |
| Nov 7 | 0 | 0.0 | 165 ms | 0 |
| Nov 7 | 0 | 0.0 | 211 ms | 0 |
| Nov 8 | 0 | 0.0 | 303 ms | 0 |
| Nov 8 | 0 | 0.0 | 197 ms | 0 |
| Nov 8 | 0 | 0.0 | 190 ms | 0 |
| Nov 8 | 0 | 0.0 | 189 ms | 0 |
| Nov 9 | 0 | 0.0 | 179 ms | 0 |
| Nov 9 | 0 | 0.0 | 210 ms | 0 |
| Nov 9 | 0 | 0.0 | 207 ms | 0 |
| Nov 9 | 0 | 0.0 | 233 ms | 0 |
| Nov 10 | 0 | 0.0 | 201 ms | 0 |
| Nov 10 | 0 | 0.0 | 253 ms | 0 |
| Nov 10 | 0 | 0.0 | 203 ms | 0 |
| Nov 10 | 0 | 0.0 | 182 ms | 0 |
| Nov 11 | 0 | 0.0 | 182 ms | 0 |
| Nov 11 | 0 | 0.0 | 240 ms | 0 |
| Nov 11 | 0 | 0.0 | 241 ms | 0 |
| Nov 11 | 0 | 0.0 | 196 ms | 0 |
| Nov 12 | 0 | 0.0 | 209 ms | 0 |
| Nov 12 | 0 | 0.0 | 188 ms | 0 |
| Nov 12 | 0 | 0.0 | 211 ms | 0 |
| Nov 12 | 0 | 0.0 | 201 ms | 0 |
| Nov 13 | 0 | 0.0 | 205 ms | 0 |
| Nov 13 | 0 | 0.0 | 176 ms | 0 |
| Nov 13 | 0 | 0.0 | 400 ms | 0 |
| Nov 13 | 0 | 0.0 | 317 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for IPLoop 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 IPLoop goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IPLoop alerts to Slack, Discord or a webhook — free.
We track IPLoop (iploop.io) as part of the Cloud & developer group. Access residential proxies across 195+ countries with flexible per-GB pricing for web scraping, market research, SEO monitoring, and data collection.
IPLoop publishes an official status page at status.iploop.io; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 235 ms average, 103–417 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public IPLoop incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
235 ms on average over the last 24 hours (103–417 ms).
Yes, at https://status.iploop.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 IPLoop here at once, the problem is on IPLoop'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 IPLoop. 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.