Betrouwbaarheid & bedrijfsvoering
Systeemstatus van HansaChat.
Live beschikbaarheid, gemeten uptime en elk geregistreerd incident — gecontroleerd door een onafhankelijke externe monitor elke vijf minuten.
- Chat-uptime, laatste 30 dagen
- 99.89%
- Chat-uptime, laatste 90 dagen
- 99.95%
- Beschikbaarheidsdoel
- 99,9% per maand
- Monitoring
- Onafhankelijk, elke 5 minuten
Actuele status
Elke kerndienst, elke vijf minuten gecontroleerd.
De monitor roept het health-endpoint van de chat en de openbare website rechtstreeks aan en registreert het resultaat van elke kerndienst afzonderlijk.
Laatste controle: 07:25 UTC · responstijd 493 ms
- Chat-API Operationeel
- Database Operationeel
- Cache Operationeel
- Berichtenwachtrij Operationeel
- Realtime Operationeel
- Website Operationeel
Gemeten uptime
Negentig dagen aan metingen, dag voor dag.
Elke balk is één dag. Beschikbaarheid is het aandeel geslaagde vijfminutencontroles — gemeten door de externe monitor, niet door HansaChat zelf. De serviceniveau-overeenkomst beoordeelt het beschikbaarheidsdoel per kalendermaand; de dagelijkse balken tonen rollende vensters van 30 en 90 dagen voor continu inzicht.
Chatservice
30 dagen: 99.89% 90 dagen: 99.95%
8,410 controles in 30 dagen
Website
30 dagen: 99.9% 90 dagen: 99.95%
Incidenthistorie
Elk geregistreerd incident, met post-mortems.
Incidenten worden automatisch geopend na drie opeenvolgende mislukte controles en gesloten zodra de volgende controle slaagt. Significante incidenten krijgen een gepubliceerde post-mortem.
-
Opgelost Website sep. 29, 2026, 08:00 UTC · 24min 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
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.
-
Opgelost Chatservice sep. 29, 2026, 08:00 UTC · 24min 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
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.
-
Opgelost Chatservice sep. 2, 2026, 09:15 UTC · 5min
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
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.
-
Opgelost Website aug. 14, 2026, 18:45 UTC · 9min 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
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.
Onafhankelijke monitor
Gebouwd om door te registreren wanneer HansaChat zelf plat ligt.
Deze statuspagina wordt samen met het product gehost. De metingen komen van een afzonderlijke worker op Cloudflare, onafhankelijk van de DNS, de hostingregio en de infrastructuur van HansaChat — als hansa.chat ooit onbereikbaar is, blijft de monitor controleren en blijft zijn eigen pagina antwoorden.