Historial de interrupciones de Webshare

1. 21 de octubre de 2026 a las 12:40 UTCinvestigating

   Estamos observando una mayor cantidad de errores proxy.

2. 21 de octubre de 2026 a las 12:46 UTCmonitoring

   Hemos identificado la causa de la cuestión y hemos implementado una solución. Estamos monitoreando para confirmar que el servicio está completamente restaurado.

3. 21 de octubre de 2026 a las 13:01 UTCinvestigating

   Estamos investigando errores de proxy persistentes relacionados con el incidente original.

4. 21 de octubre de 2026 a las 13:26 UTCmonitoring

   Se identificó y fijó la fuente secundaria de errores. Estamos monitoreando errores.

5. 21 de octubre de 2026 a las 14:45 UTCresolved

   Todos los sistemas están operativos.

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

1. 10 de octubre de 2026 a las 9:11 UTCinvestigating

   Estamos investigando tasas de error elevadas en nuevos registros de usuarios.

2. 10 de octubre de 2026 a las 9:34 UTCmonitoring

   El problema ha sido resuelto y ya no estamos observando mayores tasas de error. El equipo está vigilando la situación.

3. 10 de octubre de 2026 a las 9:52 UTCresolved

   Confirmado los problemas se resuelven.

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

1. 28 de julio de 2026 a las 18:34 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. 28 de julio de 2026 a las 18:35 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. 28 de junio de 2026 a las 10:08 UTCidentified

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

2. 28 de junio de 2026 a las 10:11 UTCmonitoring

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

3. 28 de junio de 2026 a las 10:29 UTCresolved

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

1. 3 de junio de 2026 a las 16:46 UTCinvestigating

   We're observing high proxy error rate.

2. 3 de junio de 2026 a las 17:37 UTCidentified

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

3. 3 de junio de 2026 a las 17:42 UTCmonitoring

   All system metrics are back to normal.

4. 3 de junio de 2026 a las 18:21 UTCinvestigating

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

5. 3 de junio de 2026 a las 18:24 UTCinvestigating

   We're observing increased proxy error rate.

6. 3 de junio de 2026 a las 21:58 UTCidentified

   We're working to recover the system.

7. 4 de junio de 2026 a las 1:36 UTCidentified

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

8. 4 de junio de 2026 a las 1:43 UTCmonitoring

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

9. 4 de junio de 2026 a las 2:16 UTCresolved

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

1. 21 de mayo de 2026 a las 8: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 de mayo de 2026 a las 8: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 de mayo de 2026 a las 9:44 UTCresolved

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

1. 14 de mayo de 2026 a las 10:58 UTCinvestigating

   We've observing increased error rates in proxy requests.

2. 14 de mayo de 2026 a las 11:55 UTCmonitoring

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

3. 14 de mayo de 2026 a las 12:02 UTCidentified

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

4. 14 de mayo de 2026 a las 12:11 UTCmonitoring

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

5. 14 de mayo de 2026 a las 12:30 UTCresolved

   All systems are fully operational.

1. 6 de mayo de 2026 a las 9:38 UTCidentified

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

2. 6 de mayo de 2026 a las 9:45 UTCresolved

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

1. 10 de abril de 2026 a las 23:45 UTCinvestigating

   We are investigating an increase failure rate and slow dashboard

2. 11 de abril de 2026 a las 0:44 UTCidentified

   We've identified the issue and deployed a fix

3. 11 de abril de 2026 a las 0:51 UTCmonitoring

   We've implemented the fix and we are monitoring

4. 11 de abril de 2026 a las 1:01 UTCresolved

   proxy server and dashboard fully operational

1. 10 de abril de 2026 a las 20:35 UTCinvestigating

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

2. 10 de abril de 2026 a las 20:56 UTCidentified

   We've identified the issue and implemented a fix

3. 10 de abril de 2026 a las 20:56 UTCmonitoring

   We are monitoring the system.

4. 10 de abril de 2026 a las 21:12 UTCresolved

   Proxy server and dashboard fully operational

1. 10 de abril de 2026 a las 17:32 UTCinvestigating

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

2. 10 de abril de 2026 a las 17:34 UTCidentified

   We've identified the issue and implemented a fix

3. 10 de abril de 2026 a las 17:35 UTCmonitoring

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

4. 10 de abril de 2026 a las 17:40 UTCresolved

   Platform is completely operational

1. 10 de abril de 2026 a las 7:03 UTCinvestigating

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

2. 10 de abril de 2026 a las 7:27 UTCmonitoring

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

3. 10 de abril de 2026 a las 7:49 UTCresolved

   Systems are stable.

1. 23 de marzo de 2026 a las 13:49 UTCidentified

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

2. 23 de marzo de 2026 a las 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 de marzo de 2026 a las 14:19 UTCresolved

   We've confirmed full recovery.

1. 18 de marzo de 2026 a las 15:44 UTCinvestigating

   We're investigating degraded dashboard and proxy performance.

2. 18 de marzo de 2026 a las 16:06 UTCmonitoring

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

3. 18 de marzo de 2026 a las 16:16 UTCresolved

   Systems are stable.

1. 12 de marzo de 2026 a las 13:35 UTCinvestigating

   Proxy list might load slow

2. 12 de marzo de 2026 a las 13:39 UTCmonitoring

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

3. 12 de marzo de 2026 a las 13:51 UTCresolved

   Dashboard is fully operational.

1. 11 de marzo de 2026 a las 14:00 UTCinvestigating

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

2. 11 de marzo de 2026 a las 14:30 UTCmonitoring

   We've fixed the issue and we are monitoring.

3. 11 de marzo de 2026 a las 15:04 UTCresolved

   All systems are operating normally.

1. 5 de marzo de 2026 a las 8:27 UTCidentified

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

2. 5 de marzo de 2026 a las 8:33 UTCmonitoring

   We've fixed the issue. We are monitoring.

3. 5 de marzo de 2026 a las 9:14 UTCresolved

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

1. 26 de febrero de 2026 a las 18:15 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 26 de febrero de 2026 a las 19:48 UTCmonitoring

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

3. 26 de febrero de 2026 a las 19:58 UTCresolved

   Issue is resolved

1. 26 de febrero de 2026 a las 10:54 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 26 de febrero de 2026 a las 12:26 UTCmonitoring

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

3. 26 de febrero de 2026 a las 12:41 UTCresolved

   Issues resolved

1. 25 de febrero de 2026 a las 9:30 UTCinvestigating

   We're investigating degraded API and proxy performance.

2. 25 de febrero de 2026 a las 9:41 UTCidentified

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

3. 25 de febrero de 2026 a las 10:06 UTCmonitoring

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

4. 26 de febrero de 2026 a las 0:52 UTCresolved

   Issues resolved.