Estado del sistema de HansaChat.

Tiempo de actividad medido

Noventa días de mediciones, día a día.

Cada barra es un día. La disponibilidad es la proporción de comprobaciones de cinco minutos que han tenido éxito: la mide el monitor externo, no el propio HansaChat. El SLA evalúa el objetivo de disponibilidad por mes natural; las barras diarias muestran ventanas móviles de 30 y 90 días para una visibilidad continua.

Historial de incidencias

Cada incidencia registrada, con análisis post-mortem.

Las incidencias se abren automáticamente tras tres comprobaciones fallidas consecutivas y se cierran cuando la siguiente comprobación tiene éxito. Las incidencias significativas reciben un análisis post-mortem publicado.

1. Resuelta Sitio web sep. 29, 2026, 08:00 UTC · 24m 50s

   HansaChat Status Alert Landing Page has been DOWN for 3 consecutive checks. Affected services: Landing Page Last error: HTTP 504 Time: 2026-09-29T08:00:39.412Z

   Análisis post-mortem

   Summary On 2026-09-29 both the chat API and the landing page were unavailable for about 30 minutes. Automated 5-minute checks recorded continuous HTTP 502/504 gateway failures between 07:50 and 08:25 UTC. Root cause An IONOS Cloud incident: partial connectivity degradation to the control plane affecting Kubernetes operations. See https://status.ionos.cloud/incidents/zprjxl2b1kmy for details. No defect in HansaChat application code was involved. Impact Around 30 minutes of downtime for both the chat API and the landing page; all incoming requests failed with HTTP 502/504 gateway errors. Resolution Service recovered automatically once the IONOS incident ended. Monitoring confirmed full recovery at 08:25 UTC; no HansaChat-side intervention was required.

2. Resuelta Servicio de chat sep. 29, 2026, 08:00 UTC · 24m 49s

   HansaChat Status Alert Chat service has been DOWN for 3 consecutive checks. Affected services: Chat API Last error: HTTP 504 Time: 2026-09-29T08:00:38.344Z

   Análisis post-mortem

   Summary On 2026-09-29 both the chat API and the landing page were unavailable for about 30 minutes. Automated 5-minute checks recorded continuous HTTP 502/504 gateway failures between 07:50 and 08:25 UTC. Root cause An IONOS Cloud incident: partial connectivity degradation to the control plane affecting Kubernetes operations. See https://status.ionos.cloud/incidents/zprjxl2b1kmy for details. No defect in HansaChat application code was involved. Impact Around 30 minutes of downtime for both the chat API and the landing page; all incoming requests failed with HTTP 502/504 gateway errors. Resolution Service recovered automatically once the IONOS incident ended. Monitoring confirmed full recovery at 08:25 UTC; no HansaChat-side intervention was required.

3. Resuelta Servicio de chat sep. 2, 2026, 09:15 UTC · 5m

   HansaChat Status Alert Chat service has been DOWN for 3 consecutive checks. Affected services: Chat API Last error: HTTP 502 Time: 2026-09-02T09:15:53.599Z

   Análisis post-mortem

   Summary The real-time chat API was unavailable for about 15 minutes on 2026-09-02 (09:05-09:20 UTC). Requests to the chat API returned HTTP 502 because the queue processor worker could not start. The landing page stayed reachable apart from a single failed probe during the same window. Root cause HansaChat started as a startup, and the initial credentials-injection implementation fetched credentials from the upstream API on every request, without any caching. During an unusually intense development day more than 1,000 items were requested in a short window, which exhausted the upstream API's rate limit. Without credentials available the queue processor worker could not start, which took the real-time chat API down with it. Impact Roughly 15 minutes of real-time chat API downtime (09:05-09:20 UTC); queued message processing was stalled for the same window. The landing page was not materially affected. Resolution Service recovered once the upstream rate limit window reset (09:20 UTC). Credentials injection now uses an in-cluster cache, so a temporary upstream rate limit can no longer prevent worker startup.

4. Resuelta Sitio web ago. 14, 2026, 18:45 UTC · 9m 45s

   HansaChat Status Alert Landing Page has been DOWN for 4 consecutive checks. Affected services: Landing Page Last error: The operation was aborted due to timeout Time: 2026-08-14T18:45:41.129Z

   Análisis post-mortem

   Summary The landing page was unavailable for about 20 minutes on 2026-08-14 (18:35-18:55 UTC). Chat services recorded no downtime during the incident. Root cause The underlying Kubernetes node failed and its pods were rescheduled. Traefik kept routing correctly to the old pods, which were still serving while being drained. After the deployment of the new landing version, Traefik could not find the new pods' IP addresses, so landing traffic was sent to endpoints that no longer existed. Impact Landing page downtime of roughly 20 minutes. No chat downtime was recorded.

Monitor independiente

Construido para seguir registrando cuando el propio HansaChat está caído.

Esta página de estado está alojada junto con el producto. Las mediciones provienen de un worker separado en Cloudflare que es independiente del DNS, la región de alojamiento y la infraestructura de HansaChat: si hansa.chat no estuviera accesible en algún momento, el monitor sigue comprobando y su propia página sigue respondiendo.