Historial de interrupciones de Webshare

1. July 28, 2026 at 6:34 PM UTCmonitoring

   Entre 17:01 y 17:54 UTC el 28 de julio, los clientes experimentaron fallas de conexión en el tráfico proxy y errores accediendo al dashboard y API. La causa fue una operación de provisión interna que puso carga excesiva en nuestro sistema de asignación proxy, que degrada la autenticación proxy. El servicio fue totalmente restaurado a las 17:54 UTC, después de aproximadamente 53 minutos de impacto. Estamos siguiendo internamente para prevenir una recurrencia.

2. July 28, 2026 at 6:35 PM UTCresolved

   Resuelto a las 17:54 UTC. El tráfico proxy, dashboard y API están operando normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 28, 2026 at 10:08 AM UTCidentified

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

2. June 28, 2026 at 10:11 AM UTCmonitoring

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

3. June 28, 2026 at 10:29 AM UTCresolved

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

1. June 3, 2026 at 4:46 PM UTCinvestigating

   We're observing high proxy error rate.

2. June 3, 2026 at 5:37 PM UTCidentified

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

3. June 3, 2026 at 5:42 PM UTCmonitoring

   All system metrics are back to normal.

4. June 3, 2026 at 6:21 PM UTCinvestigating

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

5. June 3, 2026 at 6:24 PM UTCinvestigating

   We're observing increased proxy error rate.

6. June 3, 2026 at 9:58 PM UTCidentified

   We're working to recover the system.

7. June 4, 2026 at 1:36 AM UTCidentified

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

8. June 4, 2026 at 1:43 AM UTCmonitoring

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

9. June 4, 2026 at 2:16 AM UTCresolved

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

1. May 21, 2026 at 8:15 AM 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. May 21, 2026 at 8:35 AM 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. May 21, 2026 at 9:44 AM UTCresolved

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

1. May 14, 2026 at 10:58 AM UTCinvestigating

   We've observing increased error rates in proxy requests.

2. May 14, 2026 at 11:55 AM UTCmonitoring

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

3. May 14, 2026 at 12:02 PM UTCidentified

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

4. May 14, 2026 at 12:11 PM UTCmonitoring

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

5. May 14, 2026 at 12:30 PM UTCresolved

   All systems are fully operational.

1. May 6, 2026 at 9:38 AM UTCidentified

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

2. May 6, 2026 at 9:45 AM UTCresolved

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

1. April 10, 2026 at 11:45 PM UTCinvestigating

   We are investigating an increase failure rate and slow dashboard

2. April 11, 2026 at 12:44 AM UTCidentified

   We've identified the issue and deployed a fix

3. April 11, 2026 at 12:51 AM UTCmonitoring

   We've implemented the fix and we are monitoring

4. April 11, 2026 at 1:01 AM UTCresolved

   proxy server and dashboard fully operational

1. April 10, 2026 at 8:35 PM UTCinvestigating

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

2. April 10, 2026 at 8:56 PM UTCidentified

   We've identified the issue and implemented a fix

3. April 10, 2026 at 8:56 PM UTCmonitoring

   We are monitoring the system.

4. April 10, 2026 at 9:12 PM UTCresolved

   Proxy server and dashboard fully operational

1. April 10, 2026 at 5:32 PM UTCinvestigating

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

2. April 10, 2026 at 5:34 PM UTCidentified

   We've identified the issue and implemented a fix

3. April 10, 2026 at 5:35 PM UTCmonitoring

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

4. April 10, 2026 at 5:40 PM UTCresolved

   Platform is completely operational

1. April 10, 2026 at 7:03 AM UTCinvestigating

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

2. April 10, 2026 at 7:27 AM UTCmonitoring

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

3. April 10, 2026 at 7:49 AM UTCresolved

   Systems are stable.

1. March 23, 2026 at 1:49 PM UTCidentified

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

2. March 23, 2026 at 1:58 PM UTCmonitoring

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

3. March 23, 2026 at 2:19 PM UTCresolved

   We've confirmed full recovery.

1. March 18, 2026 at 3:44 PM UTCinvestigating

   We're investigating degraded dashboard and proxy performance.

2. March 18, 2026 at 4:06 PM UTCmonitoring

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

3. March 18, 2026 at 4:16 PM UTCresolved

   Systems are stable.

1. March 12, 2026 at 1:35 PM UTCinvestigating

   Proxy list might load slow

2. March 12, 2026 at 1:39 PM UTCmonitoring

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

3. March 12, 2026 at 1:51 PM UTCresolved

   Dashboard is fully operational.

1. March 11, 2026 at 2:00 PM UTCinvestigating

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

2. March 11, 2026 at 2:30 PM UTCmonitoring

   We've fixed the issue and we are monitoring.

3. March 11, 2026 at 3:04 PM UTCresolved

   All systems are operating normally.

1. March 5, 2026 at 8:27 AM UTCidentified

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

2. March 5, 2026 at 8:33 AM UTCmonitoring

   We've fixed the issue. We are monitoring.

3. March 5, 2026 at 9:14 AM UTCresolved

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

1. February 26, 2026 at 6:15 PM UTCinvestigating

   We're investigating degraded API and proxy performance.

2. February 26, 2026 at 7:48 PM UTCmonitoring

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

3. February 26, 2026 at 7:58 PM UTCresolved

   Issue is resolved

1. February 26, 2026 at 10:54 AM UTCinvestigating

   We're investigating degraded API and proxy performance.

2. February 26, 2026 at 12:26 PM UTCmonitoring

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

3. February 26, 2026 at 12:41 PM UTCresolved

   Issues resolved

1. February 25, 2026 at 9:30 AM UTCinvestigating

   We're investigating degraded API and proxy performance.

2. February 25, 2026 at 9:41 AM UTCidentified

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

3. February 25, 2026 at 10:06 AM UTCmonitoring

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

4. February 26, 2026 at 12:52 AM UTCresolved

   Issues resolved.

1. February 21, 2026 at 10:42 PM UTCmonitoring

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

2. February 21, 2026 at 10:54 PM UTCresolved

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

1. February 19, 2026 at 10:15 AM UTCidentified

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

2. February 19, 2026 at 10:19 AM UTCmonitoring

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

3. February 19, 2026 at 10:52 AM UTCresolved

   All systems are operational.