Healthchecks.io Status

Alle Systeme funktionieren

Brauchen Sie Hilfe?

Schreiben Sie uns eine 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. 

Aktueller Status

Gerade aktualisiert

SystemmetrikenTag  |  Woche  |  Monat

  1. Processed pings

    601 pings/s

  2. Queued incoming pings

    0 in queue

  3. Notifications sent

    34 notifications/min

  4. Queued outgoing notifications

    1 in queue

Vergangene Vorfälle

  1. Heute

    Alle Systeme funktionieren.

  2. 14 Nov

    Alle Systeme funktionieren.

  3. 13 Nov

    Alle Systeme funktionieren.

  4. 12 Nov

    Alle Systeme funktionieren.

  5. 11 Nov

    Alle Systeme funktionieren.

  6. 10 Nov

    Alle Systeme funktionieren.

  7. 9 Nov

    Alle Systeme funktionieren.

  8. 8 Nov

    Alle Systeme funktionieren.

  9. 7 Nov

    Alle Systeme funktionieren.

  10. 6 Nov

    Alle Systeme funktionieren.

  11. 5 Nov

    Alle Systeme funktionieren.

  12. 4 Nov

    Alle Systeme funktionieren.

  13. 3 Nov

    Alle Systeme funktionieren.

  14. 2 Nov

    1. Gestartet:
      Dauer:
      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.

      Identifiziert:

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

      Gelöst:

      The issue is resolved.