User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
webshare.io · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 2509 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 805 ms | 0 |
| 03:15 | 0 | 0.0 | 563 ms | 0 |
| 03:30 | 0 | 0.0 | 381 ms | 0 |
| 03:45 | 0 | 0.0 | 416 ms | 0 |
| 04:00 | 0 | 0.0 | 752 ms | 0 |
| 04:15 | 0 | 0.0 | 465 ms | 0 |
| 04:30 | 0 | 0.0 | 424 ms | 0 |
| 04:45 | 0 | 0.0 | 576 ms | 0 |
| 05:00 | 0 | 0.0 | 612 ms | 0 |
| 05:15 | 0 | 0.0 | 564 ms | 0 |
| 05:30 | 0 | 0.0 | 726 ms | 0 |
| 05:45 | 0 | 0.0 | 323 ms | 0 |
| 06:00 | 0 | 0.0 | 92 ms | 0 |
| 06:15 | 0 | 0.0 | 559 ms | 0 |
| 06:30 | 0 | 0.0 | 224 ms | 0 |
| 06:45 | 0 | 0.0 | 389 ms | 0 |
| 07:00 | 0 | 0.0 | 759 ms | 0 |
| 07:15 | 0 | 0.0 | 381 ms | 0 |
| 07:30 | 0 | 0.0 | 948 ms | 0 |
| 07:45 | 0 | 0.0 | 245 ms | 0 |
| 08:00 | 0 | 0.0 | 526 ms | 0 |
| 08:15 | 0 | 0.0 | 415 ms | 0 |
| 08:30 | 0 | 0.0 | 562 ms | 0 |
| 08:45 | 0 | 0.0 | 750 ms | 0 |
| 09:00 | 0 | 0.0 | 86 ms | 0 |
| 09:15 | 0 | 0.0 | 1082 ms | 0 |
| 09:30 | 0 | 0.0 | 357 ms | 0 |
| 09:45 | 0 | 0.0 | 337 ms | 0 |
| 10:00 | 0 | 0.0 | 536 ms | 0 |
| 10:15 | 0 | 0.0 | 510 ms | 0 |
| 10:30 | 0 | 0.0 | 482 ms | 0 |
| 10:45 | 0 | 0.0 | 442 ms | 0 |
| 11:00 | 0 | 0.0 | 329 ms | 0 |
| 11:15 | 0 | 0.0 | 1031 ms | 0 |
| 11:30 | 0 | 0.0 | 235 ms | 0 |
| 11:45 | 0 | 0.0 | 723 ms | 0 |
| 12:00 | 0 | 0.0 | 175 ms | 0 |
| 12:15 | 0 | 0.0 | 396 ms | 0 |
| 12:30 | 0 | 0.0 | 279 ms | 0 |
| 12:45 | 0 | 0.0 | 216 ms | 0 |
| 13:00 | 0 | 0.0 | 489 ms | 0 |
| 13:15 | 0 | 0.0 | 1453 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Webshare 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 Webshare goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Webshare alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Webshare is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Webshare's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.