Healthchecks.io Status - Incident history

Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account.

Past incidents

Feb, 2026

Jan, 2026

Dec, 2025

Feb, 2026
1. Services downEmail DeliveryNotification SenderPing APIDashboard
  Started: 25 Feb, 21:09 UTC
  Duration: 8 hours, 38 minutes
  Our services are currently down. Looks like there is no UDP connectivity between any of our servers. Investigating.
  Verifying: 25 Feb, 21:22 UTC
  The services are back up. The outage was caused by a Hetzner-wide network issue: https://status.hetzner.com/incident/5e901309-0873-42af-90c5-84f38304f592
  Resolved: 26 Feb, 05:48 UTC
  The issue is resolved.
  
  From Hetzner's status page:
  
  The issue was caused due an DDOS attack which was mitigated but blocked too much traffic affecting UDP. Due to the overblocking other services not directly using UDP were influenced too. The issue was solved, we will check further measures to avoid this in the future. All systems are accessible again.
Jan, 2026
1. Network instabilityNotification SenderPing APIDashboard
  Started: 28 Jan, 23:26 UTC
  Duration: 7 hours, 36 minutes
  We are investigating network instability between our servers.
  Investigating: 29 Jan, 00:09 UTC
  The network instability manifested as UDP packet loss between specific server pairs. Currently all servers can contact each other again, and pings are being processed normally. We do not yet know what was causing the packet loss.
  Verifying: 29 Jan, 00:23 UTC
  Hetzner has posted an incident report about a core router fault. The incident start time (23:05 UTC) lines up precisely with the moment we started seeing packet loss, so this is most likely the cause of the packet loss.
  
  Resolved: 29 Jan, 07:02 UTC
  The issue is resolved.
2. Maintenance: HAProxy TLS Configuration UpgradePing APIDashboard
  Duration: 6 Jan, 12:00 - 18:00 UTC
  We will be upgrading HAProxy on our load balancer servers on Tuesday, January 6, 2026. Planned changes:
  
  * Upgrade HAProxy to version 3.2
  * Update the list of accepted SSL/TLS ciphers from a hand-picked list to HAProxy defaults
  * Later in the week, gradually enable HTTP/3.
  
  These changes should not affect the vast majority clients, but could in theory cause connection issues for very old legacy clients. If you notice persistent ping request failures starting from January 6, please let us know.
Dec, 2025
All systems operational.