User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
webscrapingapi.com · Cloud & developer
Is WebScrapingAPI down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → webscrapingapi.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 2190 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 20 | 0 | 0.0 | 2460 ms | 0 |
| Tue 22 | 0 | 0.0 | 3727 ms | 0 |
| Wed 00 | 0 | 0.0 | 2115 ms | 0 |
| Wed 03 | 0 | 0.0 | 4771 ms | 0 |
| Wed 05 | 0 | 0.0 | 3419 ms | 0 |
| Wed 07 | 0 | 0.0 | 2816 ms | 0 |
| Wed 09 | 0 | 0.0 | 3814 ms | 0 |
| Wed 12 | 0 | 0.0 | 3536 ms | 0 |
| Wed 14 | 0 | 0.0 | 2261 ms | 0 |
| Wed 16 | 0 | 0.0 | 956 ms | 0 |
| Wed 18 | 0 | 0.0 | 1010 ms | 0 |
| Wed 20 | 0 | 0.0 | 3581 ms | 0 |
| Wed 23 | 0 | 0.0 | 4955 ms | 0 |
| Thu 01 | 0 | 0.0 | 3391 ms | 0 |
| Thu 03 | 0 | 0.0 | 3479 ms | 0 |
| Thu 05 | 0 | 0.0 | 5038 ms | 0 |
| Thu 07 | 0 | 0.0 | 2561 ms | 0 |
| Thu 09 | 0 | 0.0 | 534 ms | 0 |
| Thu 11 | 0 | 0.0 | 3800 ms | 0 |
| Thu 13 | 0 | 0.0 | 2810 ms | 0 |
| Thu 15 | 0 | 0.0 | 3702 ms | 0 |
| Thu 17 | 0 | 0.0 | 491 ms | 0 |
| Thu 18 | 0 | 0.0 | 3557 ms | 0 |
| Thu 20 | 0 | 0.0 | 1701 ms | 0 |
| Thu 22 | 0 | 0.0 | 2575 ms | 0 |
| Fri 00 | 0 | 0.0 | 1893 ms | 0 |
| Fri 02 | 0 | 0.0 | 1434 ms | 0 |
| Fri 04 | 0 | 0.0 | 272 ms | 0 |
| Fri 06 | 0 | 0.0 | 3304 ms | 0 |
| Fri 08 | 0 | 0.0 | 1438 ms | 0 |
| Fri 10 | 0 | 0.0 | 219 ms | 0 |
| Fri 11 | 0 | 0.0 | 1872 ms | 0 |
| Fri 13 | 0 | 0.0 | 330 ms | 0 |
| Fri 15 | 0 | 0.0 | 3610 ms | 0 |
| Fri 17 | 0 | 0.0 | 498 ms | 0 |
| Fri 18 | 0 | 0.0 | 3288 ms | 0 |
| Fri 20 | 0 | 0.0 | 337 ms | 0 |
| Fri 21 | 0 | 0.0 | 3079 ms | 0 |
| Fri 23 | 0 | 0.0 | 2936 ms | 0 |
| Sat 00 | 0 | 0.0 | 5707 ms | 0 |
| Sat 02 | 0 | 0.0 | 191 ms | 0 |
| Sat 04 | 0 | 0.0 | 2578 ms | 0 |
| Sat 06 | 0 | 0.0 | 2420 ms | 0 |
| Sat 07 | 0 | 0.0 | 754 ms | 0 |
| Sat 08 | 0 | 0.0 | 2336 ms | 0 |
| Sat 10 | 0 | 0.0 | 2201 ms | 0 |
| Sat 13 | 0 | 0.0 | 2417 ms | 0 |
| Sat 15 | 0 | 0.0 | 2190 ms | 0 |
Reliability
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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live WebScrapingAPI badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for WebScrapingAPI yet. Outages of 10 minutes or more get their own page here.
Having trouble with WebScrapingAPI?
One report per service every 10 minutes from this network. No account.
Follow WebScrapingAPI
Get an email when WebScrapingAPI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
About WebScrapingAPI
WebScrapingAPI is listed in our Cloud & developer category and checked at webscrapingapi.com. Send a URL, get HTML or JSON back. We run proxy rotation, retries and JavaScript rendering across 195 countries. Start free with 5,000 requests.
WebScrapingAPI publishes an official status page at status.webscrapingapi.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 2126 ms average, 191–5707 ms range across 16 successful checks.
Questions
Is WebScrapingAPI down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was WebScrapingAPI last down?
We have not recorded a public WebScrapingAPI incident since monitoring began 9 days ago.
What is WebScrapingAPI's uptime?
From our own checks: 100% over 9 days of checks.
How fast does WebScrapingAPI respond?
2126 ms on average over the last 24 hours (191–5707 ms).
Does WebScrapingAPI have an official status page?
Yes, at https://status.webscrapingapi.com.
WebScrapingAPI not working for me but the status is fine. What now?
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 WebScrapingAPI here at once, the problem is on WebScrapingAPI'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 WebScrapingAPI. 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.