Status

Past incidents

1. Apr, 2024

   1. Network issuesPing APIDashboard

      Started: 29 Apr, 11:09 UTC

      Duration: 48 minutes

      We are currently experiencing intermittent network connectivity issues, caused by a networking infrastructure fault in our hosting provider's network. 
      
      Status updates about the underlying issue: https://status.hetzner.com/incident/d3972134-e340-4082-b0ef-6ede4009c5a9

      Resolved: 29 Apr, 11:57 UTC

      The issue is resolved.
   2. Network fault affecting one of our load balancer'sPing APIDashboard

      Started: 26 Apr, 12:55 UTC

      Duration: 31 minutes

      There's a network fault in our hosting provider's network, affecting one of our load balancers. The load balancer's DNS records were automatically removed.
      
      The network fault: https://status.hetzner.com/incident/35ca1da9-49fb-4899-8ba6-86425f57431e

      Resolved: 26 Apr, 13:26 UTC

      The issue is resolved.
   3. Increased ping latency from clients in Hetzner networkPing APIDashboard

      Started: 17 Apr, 19:45 UTC

      Duration: 9 hours, 20 minutes

      We are currently seeing ping request latencies in the multi-second range from clients hosted in Hetzner network.
      
      Hetzner is currently performing backbone maintenance, which is the likely cause of the latency.

      Resolved: 18 Apr, 05:06 UTC

      The issue is resolved.

2. Mar, 2024

   1. Webhook delivery failuresNotification Sender

      Started: 11 Mar, 07:45 UTC

      Duration: 11 minutes

      Healthchecks.io was not delivering webhook notifications for about 10 minutes starting from 07:45 UTC. The issue was caused by a bad deploy, and has now been fixed.

      Resolved: 11 Mar, 07:56 UTC

      The issue is resolved.

3. Feb, 2024

   1. Signal notification delivery issueNotification Sender

      Started: 5 Feb, 20:40 UTC

      Duration: 16 hours, 31 minutes

      Starting from February 5, 20:40 UTC, Healthchecks.io was not delivering Signal notifications. The notification delivery is working now, but we are still digging into the cause of the issue.

      Resolved: 6 Feb, 13:11 UTC

      Starting from yesterday, Signal server was rejecting messages sent by signal-cli 0.12.7. The fix is to upgrade to signal-cli 0.12.8.
      
      More details: https://github.com/AsamK/signal-cli/issues/1439
      
      Healthchecks.io is running signal-cli 0.12.8 now.