Status

Wcześniejsze incydenty

1. Cze, 2024

   1. Delayed ping body processingNotification SenderDashboard

      Rozpoczął się: 18 Cze, 20:46 UTC

      Czas trwania: 8 godzin, 14 minut

      Our object storage provider is currently performing maintenance (scheduled on June 18th, 2024, from 18:00 UTC to 03:00 UTC). Some percentage of object storage API calls are currently failing, which causes the following problems for Healthchecks.io:
      
      * There's a delay in ping body uploads to object storage. When you view details of a recent ping you may see  a "The request body data is not yet available, please check back later." message. The request bodies are not lost, and will be available eventually.
      * Our notification sender process can crash (and silently drop the notification it was about to send) when it hits an unexpected error from object storage. We're currently working on handling these errors. 

      Zidentyfikowane: 18 Cze, 21:11 UTC

      We have deployed a fix for the notification sender process crashing when it hits an unexpected error from object storage.

      Rozwiązany: 19 Cze, 05:00 UTC

      Our object storage provider has completed the maintenance. Ping body processing is now back to working normally with no delays.

2. Maj, 2024

   1. Database connectivity isssueNotification SenderPing APIDashboard

      Rozpoczął się: 3 Maj, 13:24 UTC

      Czas trwania: 1 godzina, 4 minuty

      We're investigating an issue with our database.

      Dochodzenie: 3 Maj, 13:39 UTC

      We have failed over to a standby database instance.

      Weryfikacja: 3 Maj, 13:46 UTC

      The systems are back up and working through a backlog of outgoing notifications (caused by pings missed during the downtime).

      Rozwiązany: 3 Maj, 14:29 UTC

      All systems are operational again. We are currently setting up a new standby database server, to replace the standby that was promoted to primary.
      
      The root cause of the outage was hardware failure: a broken power supply of one of the neighboring servers triggered a fuse in the database server's rack.

3. Kwi, 2024

   1. Network issuesPing APIDashboard

      Rozpoczął się: 29 Kwi, 11:09 UTC

      Czas trwania: 48 minut

      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

      Rozwiązany: 29 Kwi, 11:57 UTC

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

      Rozpoczął się: 26 Kwi, 12:55 UTC

      Czas trwania: 31 minut

      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

      Rozwiązany: 26 Kwi, 13:26 UTC

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

      Rozpoczął się: 17 Kwi, 19:45 UTC

      Czas trwania: 9 godzin, 20 minut

      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.

      Rozwiązany: 18 Kwi, 05:06 UTC

      The issue is resolved.