Reliability & operations
HansaChat system status.
Live availability, measured uptime, and every recorded incident — checked by an independent external monitor every five minutes.
- Availability target
- 99.9% monthly
- Chat uptime, last 30 days
- 100%
- Chat uptime, last 90 days
- 100%
- Monitoring
- Independent, every 5 minutes
Current status
Every core service, checked every five minutes.
The monitor calls the chat health endpoint and the public website directly and records the result of each core service separately.
Last check: 21:45 UTC · 520 ms response time
- Chat API Operational
- Database Operational
- Cache Operational
- Message queue Operational
- Realtime Operational
- Website Operational
Measured uptime
Ninety days of measurements, day by day.
Each bar is one day. Availability is the share of five-minute checks that succeeded — measured by the external monitor, not by HansaChat itself.
Chat service
30 days: 100% 90 days: 100%
8641 checks in 30 days
Website
30 days: 99.95% 90 days: 99.98%
Incident history
Every recorded incident, with post-mortems.
Incidents are opened automatically after three consecutive failed checks and closed when the next check succeeds. Significant incidents receive a published post-mortem.
-
Resolved Website Aug 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
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.
Independent monitor
Built to keep recording when HansaChat itself is down.
This status page is hosted together with the product. The measurements come from a separate worker on Cloudflare that is independent of HansaChat's DNS, hosting region, and infrastructure — if hansa.chat is ever unreachable, the monitor keeps checking and its own page keeps answering.