User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 151 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 187 ms | 0 |
| Mon 15 | 0 | 0.0 | 111 ms | 0 |
| Mon 18 | 0 | 0.0 | 135 ms | 0 |
| Mon 20 | 0 | 0.0 | 226 ms | 0 |
| Mon 22 | 0 | 0.0 | 43 ms | 0 |
| Tue 00 | 0 | 0.0 | 235 ms | 0 |
| Tue 02 | 0 | 0.0 | 122 ms | 0 |
| Tue 04 | 0 | 0.0 | 162 ms | 0 |
| Tue 06 | 0 | 0.0 | 71 ms | 0 |
| Tue 08 | 0 | 0.0 | 36 ms | 0 |
| Tue 11 | 0 | 0.0 | 365 ms | 0 |
| Tue 13 | 0 | 0.0 | 163 ms | 0 |
| Tue 15 | 0 | 0.0 | 221 ms | 0 |
| Tue 17 | 0 | 0.0 | 144 ms | 0 |
| Tue 20 | 0 | 0.0 | 308 ms | 0 |
| Tue 22 | 0 | 0.0 | 203 ms | 0 |
| Wed 00 | 0 | 0.0 | 125 ms | 0 |
| Wed 02 | 0 | 0.0 | 443 ms | 0 |
| Wed 05 | 0 | 0.0 | 304 ms | 0 |
| Wed 07 | 0 | 0.0 | 75 ms | 0 |
| Wed 09 | 0 | 0.0 | 306 ms | 0 |
| Wed 11 | 0 | 0.0 | 103 ms | 0 |
| Wed 13 | 0 | 0.0 | 226 ms | 0 |
| Wed 16 | 0 | 0.0 | 235 ms | 0 |
| Wed 17 | 0 | 0.0 | 100 ms | 0 |
| Wed 20 | 0 | 0.0 | 110 ms | 0 |
| Wed 22 | 0 | 0.0 | 150 ms | 0 |
| Thu 00 | 0 | 0.0 | 198 ms | 0 |
| Thu 02 | 0 | 0.0 | 259 ms | 0 |
| Thu 04 | 0 | 0.0 | 182 ms | 0 |
| Thu 06 | 0 | 0.0 | 122 ms | 0 |
| Thu 08 | 0 | 0.0 | 58 ms | 0 |
| Thu 10 | 0 | 0.0 | 113 ms | 0 |
| Thu 13 | 0 | 0.0 | 98 ms | 0 |
| Thu 15 | 0 | 0.0 | 306 ms | 0 |
| Thu 17 | 0 | 0.0 | 322 ms | 0 |
| Thu 19 | 0 | 0.0 | 360 ms | 0 |
| Thu 21 | 0 | 0.0 | 171 ms | 0 |
| Thu 23 | 0 | 0.0 | 167 ms | 0 |
| Fri 01 | 0 | 0.0 | 154 ms | 0 |
| Fri 03 | 0 | 0.0 | 374 ms | 0 |
| Fri 04 | 0 | 0.0 | 80 ms | 0 |
| Fri 06 | 0 | 0.0 | 111 ms | 0 |
| Fri 08 | 0 | 0.0 | 147 ms | 0 |
| Fri 10 | 0 | 0.0 | 105 ms | 0 |
| Fri 11 | 0 | 0.0 | 105 ms | 0 |
| Fri 13 | 0 | 0.0 | 75 ms | 0 |
| Fri 15 | 0 | 0.0 | 151 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 Zenrows 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 Zenrows goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zenrows alerts to Slack, Discord or a webhook — free.
Zenrows is listed in our AI category and checked at zenrows.com. AI web data infrastructure for agents, applications, and data teams. Fetch, extract, crawl, batch, and operate the live web, including protected pages.
Zenrows publishes an official status page at status.zenrows.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 162 ms average, 33–374 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Zenrows incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
162 ms on average over the last 24 hours (33–374 ms).
Yes, at https://status.zenrows.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Zenrows here at once, the problem is on Zenrows'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 Zenrows. 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.