Störungsverlauf von Webshare

1. 28. Juli 2026 um 18:34 UTCmonitoring

   Zwischen 17:01 und 17:54 UTC am 28. Juli erlebten Kunden Verbindungsfehler beim Proxy-Verkehr und Fehler beim Zugriff auf das Dashboard und die API. Die Ursache war eine interne Bereitstellungsoperation, die unser Proxy-Zuweisungssystem übermäßig belastete, was die Proxy-Authentifizierung beeinträchtigte. Der Service wurde um 17:54 UTC nach etwa 53 Minuten Aufprall vollständig wiederhergestellt. Wir verfolgen intern, um eine Wiederholung zu verhindern.

2. 28. Juli 2026 um 18:35 UTCresolved

   Gelöst um 17:54 UTC. Proxy Traffic, Dashboard und API funktionieren normal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 28. Juni 2026 um 10:08 UTCidentified

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

2. 28. Juni 2026 um 10:11 UTCmonitoring

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

3. 28. Juni 2026 um 10:29 UTCresolved

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

1. 3. Juni 2026 um 16:46 UTCinvestigating

   We're observing high proxy error rate.

2. 3. Juni 2026 um 17:37 UTCidentified

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

3. 3. Juni 2026 um 17:42 UTCmonitoring

   All system metrics are back to normal.

4. 3. Juni 2026 um 18:21 UTCinvestigating

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

5. 3. Juni 2026 um 18:24 UTCinvestigating

   We're observing increased proxy error rate.

6. 3. Juni 2026 um 21:58 UTCidentified

   We're working to recover the system.

7. 4. Juni 2026 um 01:36 UTCidentified

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

8. 4. Juni 2026 um 01:43 UTCmonitoring

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

9. 4. Juni 2026 um 02:16 UTCresolved

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

1. 21. Mai 2026 um 08:15 UTCidentified

   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. 21. Mai 2026 um 08:35 UTCmonitoring

   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. 21. Mai 2026 um 09:44 UTCresolved

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

1. 14. Mai 2026 um 10:58 UTCinvestigating

   We've observing increased error rates in proxy requests.

2. 14. Mai 2026 um 11:55 UTCmonitoring

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

3. 14. Mai 2026 um 12:02 UTCidentified

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

4. 14. Mai 2026 um 12:11 UTCmonitoring

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

5. 14. Mai 2026 um 12:30 UTCresolved

   All systems are fully operational.

1. 6. Mai 2026 um 09:38 UTCidentified

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

2. 6. Mai 2026 um 09:45 UTCresolved

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

1. 10. April 2026 um 23:45 UTCinvestigating

   We are investigating an increase failure rate and slow dashboard

2. 11. April 2026 um 00:44 UTCidentified

   We've identified the issue and deployed a fix

3. 11. April 2026 um 00:51 UTCmonitoring

   We've implemented the fix and we are monitoring

4. 11. April 2026 um 01:01 UTCresolved

   proxy server and dashboard fully operational

1. 10. April 2026 um 20:35 UTCinvestigating

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

2. 10. April 2026 um 20:56 UTCidentified

   We've identified the issue and implemented a fix

3. 10. April 2026 um 20:56 UTCmonitoring

   We are monitoring the system.

4. 10. April 2026 um 21:12 UTCresolved

   Proxy server and dashboard fully operational

1. 10. April 2026 um 17:32 UTCinvestigating

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

2. 10. April 2026 um 17:34 UTCidentified

   We've identified the issue and implemented a fix

3. 10. April 2026 um 17:35 UTCmonitoring

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

4. 10. April 2026 um 17:40 UTCresolved

   Platform is completely operational

1. 10. April 2026 um 07:03 UTCinvestigating

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

2. 10. April 2026 um 07:27 UTCmonitoring

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

3. 10. April 2026 um 07:49 UTCresolved

   Systems are stable.

1. 23. März 2026 um 13:49 UTCidentified

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

2. 23. März 2026 um 13:58 UTCmonitoring

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

3. 23. März 2026 um 14:19 UTCresolved

   We've confirmed full recovery.

1. 18. März 2026 um 15:44 UTCinvestigating

   We're investigating degraded dashboard and proxy performance.

2. 18. März 2026 um 16:06 UTCmonitoring

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

3. 18. März 2026 um 16:16 UTCresolved

   Systems are stable.

1. 12. März 2026 um 13:35 UTCinvestigating

   Proxy list might load slow

2. 12. März 2026 um 13:39 UTCmonitoring

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

3. 12. März 2026 um 13:51 UTCresolved

   Dashboard is fully operational.

1. 11. März 2026 um 14:00 UTCinvestigating

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

2. 11. März 2026 um 14:30 UTCmonitoring

   We've fixed the issue and we are monitoring.

3. 11. März 2026 um 15:04 UTCresolved

   All systems are operating normally.

1. 5. März 2026 um 08:27 UTCidentified

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

2. 5. März 2026 um 08:33 UTCmonitoring

   We've fixed the issue. We are monitoring.

3. 5. März 2026 um 09:14 UTCresolved

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

1. 26. Februar 2026 um 18:15 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 26. Februar 2026 um 19:48 UTCmonitoring

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

3. 26. Februar 2026 um 19:58 UTCresolved

   Issue is resolved

1. 26. Februar 2026 um 10:54 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 26. Februar 2026 um 12:26 UTCmonitoring

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

3. 26. Februar 2026 um 12:41 UTCresolved

   Issues resolved

1. 25. Februar 2026 um 09:30 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 25. Februar 2026 um 09:41 UTCidentified

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

3. 25. Februar 2026 um 10:06 UTCmonitoring

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

4. 26. Februar 2026 um 00:52 UTCresolved

   Issues resolved.

1. 21. Februar 2026 um 22:42 UTCmonitoring

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

2. 21. Februar 2026 um 22:54 UTCresolved

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

1. 19. Februar 2026 um 10:15 UTCidentified

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

2. 19. Februar 2026 um 10:19 UTCmonitoring

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

3. 19. Februar 2026 um 10:52 UTCresolved

   All systems are operational.