Webshare Outage History

Started Nov 01, 2026, 08:25 PM UTC· resolved Nov 01, 2026, 09:16 PM UTC

1. investigating Nov 01, 2026, 08:25 PM UTC

   Since 19:40 UTC, the dashboard may load slowly or not load, and some proxy connections are slower than usual or fail. Our proxy assignment system is under heavy load. We have identified the area that causes it, and we are working on a fix. We will post an update in 30 minutes or sooner.

2. monitoring Nov 01, 2026, 08:40 PM UTC

   The dashboard is loading normally again. Proxy connections are recovering, and some requests may still be slower than usual for a short time. The degraded performance started at 19:40 UTC. We are monitoring the system and will post an update when it is fully resolved.

3. identified Nov 01, 2026, 08:47 PM UTC

   Since 19:40 UTC, some proxy connections have been slower than usual or have failed. We identified the cause in our proxy assignment system and applied a fix at 20:45 UTC. The system is starting to recover. Proxy connections may stay slower than usual for a short time. We will post another update within 30 minutes.

4. monitoring Nov 01, 2026, 09:11 PM UTC

   All affected services have been working normally since 21:00 UTC. We have completed the remaining recovery steps and restored full service to all customers. We are keeping the system under close monitoring and will mark this incident as resolved once we confirm it stays stable.

5. resolved Nov 01, 2026, 09:16 PM UTC

   This 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 have fixed it, and all services have been working normally since 21:00 UTC. We are sorry for the disruption

Read the full incident report →

Started Oct 21, 2026, 01:01 PM UTC· resolved Oct 21, 2026, 01:26 PM UTC

1. investigating Oct 21, 2026, 12:40 PM UTC

   We're observing an increased amount of proxy errors.

2. monitoring Oct 21, 2026, 12:46 PM UTC

   We have identified the cause of the issue and deployed a fix. We are monitoring to confirm that service is fully restored.

3. investigating Oct 21, 2026, 01:01 PM UTC

   We're investigating persistent proxy errors related to the original incident.

4. monitoring Oct 21, 2026, 01:26 PM UTC

   The secondary source of errors was identified and fixed. We're monitoring for errors.

5. resolved Oct 21, 2026, 02:45 PM UTC

   All systems are operational.

Read the full incident report →

Started Oct 10, 2026, 09:11 AM UTC· resolved Oct 10, 2026, 09:34 AM UTC

1. investigating Oct 10, 2026, 09:11 AM UTC

   We're investigating elevated error rates on new user signups.

2. monitoring Oct 10, 2026, 09:34 AM UTC

   The issue has been resolved and we're no longer observing increased error rates. The team is monitoring the situation.

3. resolved Oct 10, 2026, 09:52 AM UTC

   Confirmed the issues are resolved.

Read the full incident report →

Started Jul 28, 2026, 06:34 PM UTC· resolved Jul 28, 2026, 06:35 PM UTC

1. monitoring Jul 28, 2026, 06:34 PM UTC

   Between 17:01 and 17:54 UTC on July 28, customers experienced connection failures on proxy traffic and errors accessing the dashboard and API. The cause was an internal provisioning operation that placed excessive load on our proxy allocation system, which degraded proxy authentication. Service was fully restored at 17:54 UTC, after approximately 53 minutes of impact. We are following up internally to prevent a recurrence.

2. resolved Jul 28, 2026, 06:35 PM UTC

   Resolved at 17:54 UTC. Proxy traffic, dashboard and API are operating normally.

Read the full incident report →

Started Jun 28, 2026, 09:57 AM UTC· resolved Jun 28, 2026, 10:09 AM UTC

1. identified Jun 28, 2026, 10:08 AM UTC

   We've observed an increase in proxy and API error rate.

2. monitoring Jun 28, 2026, 10:11 AM UTC

   We've identified the source of the issue and applied a fix. We're monitoring to confirm full recovery.

3. resolved Jun 28, 2026, 10:29 AM UTC

   This incident is now resolved. The fix has been confirmed and all systems are operating normally.

Read the full incident report →

Started Jun 03, 2026, 04:46 PM UTC· resolved Jun 04, 2026, 01:43 AM UTC

1. investigating Jun 03, 2026, 04:46 PM UTC

   We're observing high proxy error rate.

2. identified Jun 03, 2026, 05:37 PM UTC

   We've identified the root cause and we're working on recovering our services.

3. monitoring Jun 03, 2026, 05:42 PM UTC

   All system metrics are back to normal.

4. investigating Jun 03, 2026, 06:21 PM UTC

   Proxy error rate is low, but users are reporting issues logging into dashboard.webshare.io.

5. investigating Jun 03, 2026, 06:24 PM UTC

   We're observing increased proxy error rate.

6. identified Jun 03, 2026, 09:58 PM UTC

   We're working to recover the system.

7. identified Jun 04, 2026, 01:36 AM UTC

   Proxy servers are back online and working normally. We are now working on bringing the dashboard back online as well.

8. monitoring Jun 04, 2026, 01:43 AM UTC

   All issues have been resolved. We are monitoring the system.

9. resolved Jun 04, 2026, 02:16 AM UTC

   All the issues are resolved, the system is back to normal.

Read the full incident report →

Started May 21, 2026, 08:15 AM UTC· resolved May 21, 2026, 08:35 AM UTC

1. identified May 21, 2026, 08:15 AM UTC

   During a maintenance operation on one of our cluster nodes, the orchestrator entered a retry loop trying to reassign tasks that referenced a previous node identity. This blocked new task placement across the cluster for approximately 30 minutes, briefly affecting the availability of some services.

2. monitoring May 21, 2026, 08:35 AM UTC

   The issue has been mitigated and our services have returned to normal capacity. We are continuing to monitor the platform closely to ensure full stability and will provide a final update shortly.

3. resolved May 21, 2026, 09:44 AM UTC

   All services have returned to normal capacity. We have confirmed stability throughout our monitoring period.

Read the full incident report →

Started May 14, 2026, 10:58 AM UTC· resolved May 14, 2026, 12:11 PM UTC

1. investigating May 14, 2026, 10:58 AM UTC

   We've observing increased error rates in proxy requests.

2. monitoring May 14, 2026, 11:55 AM UTC

   We've remedied the issue. We're actively monitoring our systems.

3. identified May 14, 2026, 12:02 PM UTC

   We're observing increased error rates again. We've identified the issue and we're working on a fix.

4. monitoring May 14, 2026, 12:11 PM UTC

   We've deployed a fix and error rates are back to normal.

5. resolved May 14, 2026, 12:30 PM UTC

   All systems are fully operational.

Read the full incident report →

Started May 06, 2026, 09:38 AM UTC· resolved May 06, 2026, 09:45 AM UTC

1. identified May 06, 2026, 09:20 AM UTC

   We've identified an issue causing elevated API error rates. A fix is being rolled out.

2. resolved May 06, 2026, 09:45 AM UTC

   We've rolled out a fix that resolved the issue.

Read the full incident report →

Started Apr 10, 2026, 11:45 PM UTC· resolved Apr 11, 2026, 12:51 AM UTC

1. investigating Apr 10, 2026, 11:45 PM UTC

   We are investigating an increase failure rate and slow dashboard

2. identified Apr 11, 2026, 12:44 AM UTC

   We've identified the issue and deployed a fix

3. monitoring Apr 11, 2026, 12:51 AM UTC

   We've implemented the fix and we are monitoring

4. resolved Apr 11, 2026, 01:01 AM UTC

   proxy server and dashboard fully operational

Read the full incident report →

Started Apr 10, 2026, 08:35 PM UTC· resolved Apr 10, 2026, 08:56 PM UTC

1. investigating Apr 10, 2026, 08:35 PM UTC

   We've identified an increased proxy error rate and we are identifying the root cause

2. identified Apr 10, 2026, 08:56 PM UTC

   We've identified the issue and implemented a fix

3. monitoring Apr 10, 2026, 08:56 PM UTC

   We are monitoring the system.

4. resolved Apr 10, 2026, 09:12 PM UTC

   Proxy server and dashboard fully operational

Read the full incident report →

Started Apr 10, 2026, 05:32 PM UTC· resolved Apr 10, 2026, 05:34 PM UTC

1. investigating Apr 10, 2026, 04:48 PM UTC

   We are experiencing issues with some of hour datacenters that affect the proxy usage and dashboard

2. identified Apr 10, 2026, 05:22 PM UTC

   We've identified the issue and implemented a fix

3. monitoring Apr 10, 2026, 05:25 PM UTC

   We are monitoring the system, proxy server and dashboard are operational.

4. resolved Apr 10, 2026, 05:40 PM UTC

   Platform is completely operational

Read the full incident report →

Started Apr 10, 2026, 07:03 AM UTC· resolved Apr 10, 2026, 07:49 AM UTC

1. investigating Apr 10, 2026, 07:03 AM UTC

   We are experiencing degraded performance in Dashboard and API. The incident is being investigated.

2. monitoring Apr 10, 2026, 07:27 AM UTC

   The problem has been identified and fixed. The service has recovered. We will continue monitoring the service.

3. resolved Apr 10, 2026, 07:49 AM UTC

   Systems are stable.

Read the full incident report →

Started Mar 23, 2026, 01:49 PM UTC· resolved Mar 23, 2026, 01:58 PM UTC

1. identified Mar 23, 2026, 01:49 PM UTC

   A deployment caused degraded API and proxy performance, we're reverting the changes to mitigate.

2. monitoring Mar 23, 2026, 01:58 PM UTC

   We've reverted the changes and are observing recovery. We'll continue to monitor the services as they fully recover.

3. resolved Mar 23, 2026, 02:19 PM UTC

   We've confirmed full recovery.

Read the full incident report →

Started Mar 18, 2026, 03:44 PM UTC· resolved Mar 18, 2026, 04:16 PM UTC

1. investigating Mar 18, 2026, 03:44 PM UTC

   We're investigating degraded dashboard and proxy performance.

2. monitoring Mar 18, 2026, 04:06 PM UTC

   We've addressed the issue and are monitoring the situation.

3. resolved Mar 18, 2026, 04:16 PM UTC

   Systems are stable.

Read the full incident report →

Started Mar 12, 2026, 01:35 PM UTC· resolved Mar 12, 2026, 01:39 PM UTC

1. investigating Mar 12, 2026, 01:35 PM UTC

   Proxy list might load slow

2. monitoring Mar 12, 2026, 01:39 PM UTC

   We've identified the issue, fixed it and we are monitoring it.

3. resolved Mar 12, 2026, 01:51 PM UTC

   Dashboard is fully operational.

Read the full incident report →

Started Mar 11, 2026, 02:00 PM UTC· resolved Mar 11, 2026, 02:23 PM UTC

1. investigating Mar 11, 2026, 02:00 PM UTC

   We have identified a slower proxylist load times and we are investigating the cause.

2. monitoring Mar 11, 2026, 02:30 PM UTC

   We've fixed the issue and we are monitoring.

3. resolved Mar 11, 2026, 03:04 PM UTC

   All systems are operating normally.

Read the full incident report →

Started Mar 05, 2026, 08:27 AM UTC· resolved Mar 05, 2026, 08:33 AM UTC

1. identified Mar 05, 2026, 08:27 AM UTC

   We are experiencing degraded performance, we've identified the issue and fixing it.

2. monitoring Mar 05, 2026, 08:33 AM UTC

   We've fixed the issue. We are monitoring.

3. resolved Mar 05, 2026, 09:14 AM UTC

   After monitoring for a while, everything is working as expected.

Read the full incident report →

Started Feb 26, 2026, 06:15 PM UTC· resolved Feb 26, 2026, 07:48 PM UTC

1. investigating Feb 26, 2026, 06:15 PM UTC

   We're investigating degraded API and proxy performance.

2. monitoring Feb 26, 2026, 07:48 PM UTC

   All systems are operational. We're actively monitoring for further issues.

3. resolved Feb 26, 2026, 07:58 PM UTC

   Issue is resolved

Read the full incident report →

Started Feb 26, 2026, 10:54 AM UTC· resolved Feb 26, 2026, 12:26 PM UTC

1. investigating Feb 26, 2026, 10:54 AM UTC

   We're investigating degraded API and proxy performance.

2. monitoring Feb 26, 2026, 12:26 PM UTC

   All systems are operational. We're actively monitoring for further issues.

3. resolved Feb 26, 2026, 12:41 PM UTC

   Issues resolved

Read the full incident report →

Started Feb 25, 2026, 09:30 AM UTC· resolved Feb 25, 2026, 09:49 AM UTC

1. investigating Feb 25, 2026, 09:30 AM UTC

   We're investigating degraded API and proxy performance.

2. identified Feb 25, 2026, 09:41 AM UTC

   We've paused updates to proxy lists while we implement a fix. Proxies are back to normal operation.

3. monitoring Feb 25, 2026, 10:06 AM UTC

   All systems are operational. We're actively monitoring for further issues.

4. resolved Feb 25, 2026, 11:00 AM UTC

   Issues resolved.

Read the full incident report →

Started Feb 21, 2026, 10:18 PM UTC· resolved Feb 21, 2026, 10:54 PM UTC

1. monitoring Feb 21, 2026, 10:30 PM UTC

   due to some internal network issue, our proxy infrastructure went down

2. resolved Feb 21, 2026, 10:54 PM UTC

   We had an internal network outage from 22:18-22:25 UTC. Proxies were unusable for that time.

Read the full incident report →

Started Feb 19, 2026, 10:01 AM UTC· resolved Feb 19, 2026, 10:16 AM UTC

1. identified Feb 19, 2026, 10:15 AM UTC

   We're working to fix to make the API available again.

2. monitoring Feb 19, 2026, 10:19 AM UTC

   API error levels are back to normal. We're monitoring the situation.

3. resolved Feb 19, 2026, 10:52 AM UTC

   All systems are operational.

Read the full incident report →

Started Feb 16, 2026, 09:14 AM UTC· resolved Feb 16, 2026, 09:34 AM UTC

1. investigating Feb 16, 2026, 09:14 AM UTC

   Our servers are inaccessible from certain geographical regions.

2. monitoring Feb 16, 2026, 09:34 AM UTC

   One of our infrastructure providers had a network outage between 9.11 UTC and 9.16 UTC. Our system automatically recovered from that incident, ramping up traffic until it was back to fully operational at 9.28 UTC.

3. resolved Feb 16, 2026, 09:56 AM UTC

   All systems are operational.

Read the full incident report →

Started Jan 23, 2026, 09:52 AM UTC· resolved Jan 23, 2026, 10:52 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →