Webshare 中断历史

1. 2026年10月21日 UTC 12:40investigating

   我们观测到代理错误的增加.

2. 2026年10月21日 UTC 12:46monitoring

   我们查明了问题的根源,并确定了解决办法。 我们正在监测,以确认服务完全恢复.

3. 2026年10月21日 UTC 13:01investigating

   我们正在调查与原事件相关的持续代理错误.

4. 2026年10月21日 UTC 13:26monitoring

   错误的次要来源已查明并固定。 我们在监视错误.

5. 2026年10月21日 UTC 14:45resolved

   所有系统都已投入运作.

自动翻译自官方事件更新。

1. 2026年10月10日 UTC 09:11investigating

   我们正在调查新用户注册的 高误差率.

2. 2026年10月10日 UTC 09:34monitoring

   这个问题已经解决了,我们不再观察到错误率的增加. 该小组正在监测局势.

3. 2026年10月10日 UTC 09:52resolved

   确认问题已经解决.

自动翻译自官方事件更新。

1. 2026年7月28日 UTC 18:34monitoring

   在协调世界时7月28日17:01至17:54之间,客户在代理流量上遭遇了连接故障并错误地访问仪表板和API. 其原因是内部供货操作给我们的代理分配系统带来过重的负荷,这削弱了代理认证. 在协调世界时17:54,经过约53分钟的撞击后,服务被完全恢复. 我们正在内部采取后续行动,以防止再次发生.

2. 2026年7月28日 UTC 18:35resolved

   协调世界时17:54决定. 代理流量,仪表板和API正常运行.

自动翻译自官方事件更新。

1. 2026年6月28日 UTC 10:08identified

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

2. 2026年6月28日 UTC 10:11monitoring

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

3. 2026年6月28日 UTC 10:29resolved

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

1. 2026年6月3日 UTC 16:46investigating

   We're observing high proxy error rate.

2. 2026年6月3日 UTC 17:37identified

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

3. 2026年6月3日 UTC 17:42monitoring

   All system metrics are back to normal.

4. 2026年6月3日 UTC 18:21investigating

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

5. 2026年6月3日 UTC 18:24investigating

   We're observing increased proxy error rate.

6. 2026年6月3日 UTC 21:58identified

   We're working to recover the system.

7. 2026年6月4日 UTC 01:36identified

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

8. 2026年6月4日 UTC 01:43monitoring

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

9. 2026年6月4日 UTC 02:16resolved

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

1. 2026年5月21日 UTC 08:15identified

   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. 2026年5月21日 UTC 08:35monitoring

   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. 2026年5月21日 UTC 09:44resolved

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

1. 2026年5月14日 UTC 10:58investigating

   We've observing increased error rates in proxy requests.

2. 2026年5月14日 UTC 11:55monitoring

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

3. 2026年5月14日 UTC 12:02identified

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

4. 2026年5月14日 UTC 12:11monitoring

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

5. 2026年5月14日 UTC 12:30resolved

   All systems are fully operational.

1. 2026年5月6日 UTC 09:38identified

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

2. 2026年5月6日 UTC 09:45resolved

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

1. 2026年4月10日 UTC 23:45investigating

   We are investigating an increase failure rate and slow dashboard

2. 2026年4月11日 UTC 00:44identified

   We've identified the issue and deployed a fix

3. 2026年4月11日 UTC 00:51monitoring

   We've implemented the fix and we are monitoring

4. 2026年4月11日 UTC 01:01resolved

   proxy server and dashboard fully operational

1. 2026年4月10日 UTC 20:35investigating

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

2. 2026年4月10日 UTC 20:56identified

   We've identified the issue and implemented a fix

3. 2026年4月10日 UTC 20:56monitoring

   We are monitoring the system.

4. 2026年4月10日 UTC 21:12resolved

   Proxy server and dashboard fully operational

1. 2026年4月10日 UTC 17:32investigating

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

2. 2026年4月10日 UTC 17:34identified

   We've identified the issue and implemented a fix

3. 2026年4月10日 UTC 17:35monitoring

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

4. 2026年4月10日 UTC 17:40resolved

   Platform is completely operational

1. 2026年4月10日 UTC 07:03investigating

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

2. 2026年4月10日 UTC 07:27monitoring

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

3. 2026年4月10日 UTC 07:49resolved

   Systems are stable.

1. 2026年3月23日 UTC 13:49identified

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

2. 2026年3月23日 UTC 13:58monitoring

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

3. 2026年3月23日 UTC 14:19resolved

   We've confirmed full recovery.

1. 2026年3月18日 UTC 15:44investigating

   We're investigating degraded dashboard and proxy performance.

2. 2026年3月18日 UTC 16:06monitoring

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

3. 2026年3月18日 UTC 16:16resolved

   Systems are stable.

1. 2026年3月12日 UTC 13:35investigating

   Proxy list might load slow

2. 2026年3月12日 UTC 13:39monitoring

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

3. 2026年3月12日 UTC 13:51resolved

   Dashboard is fully operational.

1. 2026年3月11日 UTC 14:00investigating

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

2. 2026年3月11日 UTC 14:30monitoring

   We've fixed the issue and we are monitoring.

3. 2026年3月11日 UTC 15:04resolved

   All systems are operating normally.

1. 2026年3月5日 UTC 08:27identified

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

2. 2026年3月5日 UTC 08:33monitoring

   We've fixed the issue. We are monitoring.

3. 2026年3月5日 UTC 09:14resolved

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

1. 2026年2月26日 UTC 18:15investigating

   We're investigating degraded API and proxy performance.

2. 2026年2月26日 UTC 19:48monitoring

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

3. 2026年2月26日 UTC 19:58resolved

   Issue is resolved

1. 2026年2月26日 UTC 10:54investigating

   We're investigating degraded API and proxy performance.

2. 2026年2月26日 UTC 12:26monitoring

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

3. 2026年2月26日 UTC 12:41resolved

   Issues resolved

1. 2026年2月25日 UTC 09:30investigating

   We're investigating degraded API and proxy performance.

2. 2026年2月25日 UTC 09:41identified

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

3. 2026年2月25日 UTC 10:06monitoring

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

4. 2026年2月26日 UTC 00:52resolved

   Issues resolved.