Webshare status history
Current state: operational — “All Systems Operational” per https://status.webshare.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Webshare incidents last?
From 25 incidents with a vendor-posted start and resolve time. Longest on record: Increased proxy error rate — 9.5 h (2026-06-03 16:46 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-28 18:34 UTC | Proxy Error Rate Too High | resolved | minor | 1 min |
| 2026-06-28 10:08 UTC | Increased error rate | resolved | minor | 20 min |
| 2026-06-03 16:46 UTC | Increased proxy error rate | resolved | critical | 9 h 29 min |
| 2026-05-21 08:15 UTC | Cluster orchestrator placement degradation. | resolved | minor | 1 h 29 min |
| 2026-05-14 10:58 UTC | Proxy error rate too high | resolved | major | 1 h 31 min |
| 2026-05-06 09:38 UTC | Elevated API error rates. | resolved | minor | 7 min |
| 2026-04-10 23:45 UTC | proxy server increased failure rate and slow dashboard | resolved | major | 1 h 15 min |
| 2026-04-10 20:35 UTC | increased proxy error rate | resolved | minor | 37 min |
| 2026-04-10 17:32 UTC | increased error error rate for proxy requests | resolved | minor | 8 min |
| 2026-04-10 07:03 UTC | Dashboard and API degraded performance | resolved | minor | 45 min |
| 2026-03-23 13:49 UTC | Degrated API and proxy performance | resolved | minor | 30 min |
| 2026-03-18 15:44 UTC | Degraded dashboard and proxy performance | resolved | none | 31 min |
| 2026-03-12 13:35 UTC | We have investigating and issue affecting the some parts of the dashboard | resolved | minor | 15 min |
| 2026-03-11 14:00 UTC | Dashboard proxylist page slow load time | resolved | minor | 1 h 04 min |
| 2026-03-05 08:27 UTC | Proxies and dashboard experiencing degraded performance | resolved | minor | 46 min |
| 2026-02-26 18:15 UTC | Proxy and API performance degraded | resolved | minor | 1 h 43 min |
| 2026-02-26 10:54 UTC | Proxy and API performance degraded | resolved | minor | 1 h 47 min |
| 2026-02-25 09:30 UTC | Proxy and API performance degraded | resolved | minor | 1 h 29 min |
| 2026-02-21 22:42 UTC | proxies inoperable for a few minutes | resolved | major | 12 min |
| 2026-02-19 10:15 UTC | API is unavailable | resolved | critical | 36 min |
| 2026-02-16 09:14 UTC | Systems are inaccessible from certain geographical regions | resolved | minor | 42 min |
| 2026-01-23 09:52 UTC | Proxy error rate increase | resolved | minor | 1 h 00 min |
| 2026-01-19 13:02 UTC | Slow load times | resolved | minor | 58 min |
| 2026-01-18 15:00 UTC | Proxy list updates taking longer than usual | resolved | minor | 26 min |
| 2025-12-14 20:18 UTC | Slow response times and elevated proxy errors from Australian proxies | resolved | minor | 1 h 23 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Webshare with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"webshare"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}