Webshare Proxy Outage History

29 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Webshare Proxy Incident

Webshare Proxy incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026Connectivity issues with some Static Residential proxies in Ashburn and Arlington, USAll systems are operational.35h 37mResolved
Nov 1, 2026Degraded performance on the dashboard and proxy connectionsThis incident has been resolved. Between 19:40 and 21:00 UTC, some proxy connections were slow or failed, and the dashboard could load slowly. The cause was an unusually heavy load on our proxy assignment system. We…51 minResolved
Oct 21, 2026Increased amount of proxy errorsAll systems are operational.2h 5mResolved
Oct 10, 2026Elevated errors during new user signupsConfirmed the issues are resolved.41 minResolved
Jul 28, 2026Proxy Error Rate Too HighResolved at 17:54 UTC. Proxy traffic, dashboard and API are operating normally.1 minResolved
Jun 28, 2026Increased error rateThis incident is now resolved. The fix has been confirmed and all systems are operating normally.20 minResolved
Jun 3, 2026Increased proxy error rateAll the issues are resolved, the system is back to normal.9h 29mResolved
May 21, 2026Cluster orchestrator placement degradation.All services have returned to normal capacity. We have confirmed stability throughout our monitoring period.1h 29mResolved
May 14, 2026Proxy error rate too highAll systems are fully operational.1h 31mResolved
May 6, 2026Elevated API error rates.We've rolled out a fix that resolved the issue.7 minResolved
Apr 10, 2026proxy server increased failure rate and slow dashboardproxy server and dashboard fully operational1h 15mResolved
Apr 10, 2026increased proxy error rateProxy server and dashboard fully operational37 minResolved
Apr 10, 2026increased error error rate for proxy requestsPlatform is completely operational8 minResolved
Apr 10, 2026Dashboard and API degraded performanceSystems are stable.45 minResolved
Mar 23, 2026Degrated API and proxy performanceWe've confirmed full recovery.30 minResolved
Mar 18, 2026Degraded dashboard and proxy performanceSystems are stable.31 minResolved
Mar 12, 2026We have investigating and issue affecting the some parts of the dashboardDashboard is fully operational.15 minResolved
Mar 11, 2026Dashboard proxylist page slow load timeAll systems are operating normally.1h 4mResolved
Mar 5, 2026Proxies and dashboard experiencing degraded performanceAfter monitoring for a while, everything is working as expected.46 minResolved
Feb 26, 2026Proxy and API performance degradedIssue is resolved1h 43mResolved
Feb 26, 2026Proxy and API performance degradedIssues resolved1h 47mResolved
Feb 25, 2026Proxy and API performance degradedIssues resolved.1h 29mResolved
Feb 21, 2026proxies inoperable for a few minutesWe had an internal network outage from 22:18-22:25 UTC. Proxies were unusable for that time.12 minResolved
Feb 19, 2026API is unavailableAll systems are operational.36 minResolved
Feb 16, 2026Systems are inaccessible from certain geographical regionsAll systems are operational.42 minResolved
Jan 23, 2026Proxy error rate increaseProxies are fully operational.1h 0mResolved
Jan 19, 2026Slow load timesAll systems are fully operational.58 minResolved
Jan 18, 2026Proxy list updates taking longer than usualProxy list update times are stable again.26 minResolved
Dec 14, 2025Slow response times and elevated proxy errors from Australian proxiesThe response times and proxy error rate are back to normal.1h 23mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Webshare Proxy incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Webshare Proxy Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Webshare Proxy acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Webshare Proxy outage in this window ran 1d 11h, against a mean recovery of 2h 21m. If you depend on Webshare Proxy in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.