Healthchecks.io Statut

Tous les services sont opérationnels

Besoin d'aide?

Contactez-nous
Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account. 

Statut actuel

Mise à jour à l'instant

Informations sur le systèmeJour  |  Semaine  |  Mois

  1. Processed pings

    556 pings/s

  2. Queued incoming pings

    3 in queue

  3. Notifications sent

    34.5 notifications/min

  4. Queued outgoing notifications

    0 in queue

Incidents précédents

  1. Aujourd'hui

    Tous les services sont opérationnels.

  2. 14 Nov

    Tous les services sont opérationnels.

  3. 13 Nov

    Tous les services sont opérationnels.

  4. 12 Nov

    Tous les services sont opérationnels.

  5. 11 Nov

    Tous les services sont opérationnels.

  6. 10 Nov

    Tous les services sont opérationnels.

  7. 9 Nov

    Tous les services sont opérationnels.

  8. 8 Nov

    Tous les services sont opérationnels.

  9. 7 Nov

    Tous les services sont opérationnels.

  10. 6 Nov

    Tous les services sont opérationnels.

  11. 5 Nov

    Tous les services sont opérationnels.

  12. 4 Nov

    Tous les services sont opérationnels.

  13. 3 Nov

    Tous les services sont opérationnels.

  14. 2 Nov

    1. A débuté:
      Durée:
      We are currently investigating intermittent connection timeouts on our ping endoints (hc-ping.com) and the main website(healthchecks.io).
      Retour d'expérience
      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.

      Identifié:

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

      Résolu:

      The issue is resolved.