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 30 min 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 |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 240 ms | 0 |
| Mon 19 | 0 | 0.0 | 233 ms | 0 |
| Mon 21 | 0 | 0.0 | 343 ms | 0 |
| Mon 23 | 0 | 0.0 | 195 ms | 0 |
| Tue 01 | 0 | 0.0 | 185 ms | 0 |
| Tue 03 | 0 | 0.0 | 221 ms | 0 |
| Tue 05 | 0 | 0.0 | 201 ms | 0 |
| Tue 07 | 0 | 0.0 | 184 ms | 0 |
| Tue 09 | 0 | 0.0 | 322 ms | 0 |
| Tue 12 | 0 | 0.0 | 202 ms | 0 |
| Tue 14 | 0 | 0.0 | 203 ms | 0 |
| Tue 16 | 0 | 0.0 | 262 ms | 0 |
| Tue 18 | 0 | 0.0 | 175 ms | 0 |
| Tue 21 | 0 | 0.0 | 182 ms | 0 |
| Tue 23 | 0 | 0.0 | 279 ms | 0 |
| Wed 01 | 0 | 0.0 | 169 ms | 0 |
| Wed 03 | 0 | 0.0 | 203 ms | 0 |
| Wed 05 | 0 | 0.0 | 233 ms | 0 |
| Wed 08 | 0 | 0.0 | 291 ms | 0 |
| Wed 10 | 0 | 0.0 | 188 ms | 0 |
| Wed 12 | 0 | 0.0 | 272 ms | 0 |
| Wed 14 | 0 | 0.0 | 335 ms | 0 |
| Wed 16 | 0 | 0.0 | 147 ms | 0 |
| Wed 19 | 0 | 0.0 | 343 ms | 0 |
| Wed 21 | 0 | 0.0 | 184 ms | 0 |
| Wed 23 | 0 | 0.0 | 196 ms | 0 |
| Thu 01 | 0 | 0.0 | 209 ms | 0 |
| Thu 03 | 0 | 0.0 | 138 ms | 0 |
| Thu 05 | 0 | 0.0 | 280 ms | 0 |
| Thu 07 | 0 | 0.0 | 182 ms | 0 |
| Thu 09 | 0 | 0.0 | 188 ms | 0 |
| Thu 11 | 0 | 0.0 | 201 ms | 0 |
| Thu 13 | 0 | 0.0 | 183 ms | 0 |
| Thu 16 | 0 | 0.0 | 238 ms | 0 |
| Thu 18 | 0 | 0.0 | 308 ms | 0 |
| Thu 20 | 0 | 0.0 | 169 ms | 0 |
| Thu 22 | 0 | 0.0 | 224 ms | 0 |
| Fri 00 | 0 | 0.0 | 222 ms | 0 |
| Fri 02 | 0 | 0.0 | 204 ms | 0 |
| Fri 04 | 0 | 0.0 | 205 ms | 0 |
| Fri 06 | 0 | 0.0 | 158 ms | 0 |
| Fri 08 | 0 | 0.0 | 181 ms | 0 |
| Fri 10 | 0 | 0.0 | 167 ms | 0 |
| Fri 11 | 0 | 0.0 | 246 ms | 0 |
| Fri 13 | 0 | 0.0 | 417 ms | 0 |
| Fri 15 | 0 | 0.0 | 400 ms | 0 |
| Fri 17 | 0 | 0.0 | 222 ms | 0 |
| Fri 18 | 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: 230 ms average, 103–417 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 IPLoop incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
230 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.