Healthchecks.io Durumu

Yardıma ihtiyacın?

Bize e-posta gönder
Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account. 

Önceki olaylar

Eyl, 2024
      
      
Ağu, 2024
   
 
Tem, 2024
    
  1. Eyl, 2024

    1. Database Outage Due to DC Switch FaultEmail DeliveryNotification SenderPing APIDashboard
      Başladı:
      Süre:
      There's a network fault (a switch fault) at our data-center affecting our primary database. This resulted in a complete outage: dashboard, ping endpoints, notification sender.

      We've failed over to a standby database.

      Doğrulanıyor:

      After fail-over to a standby database systems are back up. 
      We are monitoring the servers, and preparing a new standby.

      Çözüldü:

      The issue is resolved.
  2. Ağu, 2024

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

  3. Tem, 2024

    1. Başladı:
      Süre:
      We're investigating intermittent failing requests on healthchecks.io.

      Tanımlanmış:

      The HTTP request failures on https://healthchecks.io seem to be a knock-on effects of connectivity issues to our object storage provider.

      We have temporarily disabled API calls that retrieve ping bodies from object storage.

      Tanımlanmış:

      We have verified the failing requests on Healthchecks.io dashboard were indeed related to object storage availability issues. The temporary solution of disabling "get object" API calls has restored the dashboard functionality. Our object storage provider has acknowledged the issue and is working on it.

      Currently on Healthchecks.io dashboard, when you view details of a recent ping you will 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 for viewing eventually.

      Tanımlanmış:

      Our object storage provider have implemented a fix. We are currently working through a backlog of not yet uploaded ping bodies.

      Çözüldü:

      We have fully caught up with ping body backlog, and the service is now operating normally.