Healthchecks.io Status

Potrzebować wsparcia?

Wyślij do nas e-mail
Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account. 

Wcześniejsze incydenty

Kwi, 2024
     
Mar, 2024
    
Lut, 2024
   
   
  1. Kwi, 2024

    1. Network issuesPing APIDashboard
      Rozpoczął się:
      Czas trwania:
      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:

      The issue is resolved.
    2. Rozpoczął się:
      Czas trwania:
      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:

      The issue is resolved.
    3. Rozpoczął się:
      Czas trwania:
      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:

      The issue is resolved.
  2. Mar, 2024

    1. Webhook delivery failuresNotification Sender
      Rozpoczął się:
      Czas trwania:
      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.

      Rozwiązany:

      The issue is resolved.
  3. Lut, 2024

    1. Rozpoczął się:
      Czas trwania:
      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.

      Rozwiązany:

      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.