Durumu

Önceki olaylar

1. Oca, 2026

   1. Network instabilityNotification SenderPing APIDashboard

      Başladı: 28 Oca, 23:26 UTC

      Süre: 7 saat, 36 dakika

      We are investigating network instability between our servers.

      Araştırma: 29 Oca, 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.

      Doğrulanıyor: 29 Oca, 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.
      
      
      

      Çözüldü: 29 Oca, 07:02 UTC

      The issue is resolved.
   2. Bakım onarım: HAProxy TLS Configuration UpgradePing APIDashboard

      Süre: 6 Oca, 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.

2. Ara, 2025

   Tüm sistemler çalışır durumda.

3. Kas, 2025

   1. Connection timeouts on hc-ping.com and healthchecks.ioPing APIDashboard

      Başladı: 2 Kas, 00:23 UTC

      Süre: 8 saat, 14 dakika

      We are currently investigating intermittent connection timeouts on our ping endoints (hc-ping.com) and the main website(healthchecks.io).

      Post-mortem

      Between November 1, 23:30 UTC and November 2, 1:10 UTC, Healthchecks.io (both the main website, healthchecks.io, and the ping endpoints, hc-ping.com) had intermittent connectivity issues in the form of some requests taking multiple seconds to finish, or timing out entirely. Usually, such symptoms are caused by infrastructure problems out of our control, but this time the problem was on our side: our load balancers were running out of available connection slots. Our load balancers were dealing with a flood of ping requests from a misconfigured client. The load balancers were using the “tarpit” rate-limiting to slow the client’s requests down. Unfortunately, this did not work as intended: the client did not slow down, but the load balancers were hitting their connection count limits and rejecting legitimate requests.
      
      Read full post-mortem here.

      Tanımlanmış: 2 Kas, 01:28 UTC

      We have identified and blocked network flood from a set of specific IP addresses.

      Çözüldü: 2 Kas, 08:37 UTC

      The issue is resolved.