Healthchecks.io 상태

모든 시스템이 작동 중입니다

지원이 필요하십니까?

이메일을 보내주세요
Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account. 

과거 사건

6월, 2022
  
   
5월, 2022
      
     
4월, 2022
    
 

  1. 6월, 2022

    모든 시스템이 작동 중입니다.

  2. 5월, 2022

    모든 시스템이 작동 중입니다.

  3. 4월, 2022

    1. Major stability problemsNotification SenderPing APIDashboard
      시작됨:
      지속:
      Major stability problems – investigating
      Post-mortem
      Here's a quick recap of this outage. 

      Yesterday, Hetzner datacenters in Falkenstein were hit with by a large DDOS attack. As a mitigation, Hetzner throttled UDP traffic on ports 9000 and above.

      Healthchecks.io uses Wireguard for private communication between servers (load balancers to web servers, web servers to database servers). Wireguard works over UDP, and, after the throttling started, the available bandwidth between servers dropped to below 1Mbit/s. 

      After figuring out what had happened, I updated Wireguard configuration to use a port number below 9000. After deploying the change, Healthchecks resumed normal operation.

      The outage lasted almost 2 hours. During the outage, the ping API was accepting and processing some but not all pings. The web UI and the notification sender was completely non-operational. When normal operation resumed, Healthchecks sent out a wave of false alerts due to pings that were not received on time. 

      This was an unfortunate event, I apologize for the trouble caused by failing pings, non-operational management API, and the eventual false alerts. Still, there are also several positive aspects, in the "it could have been worse" sense, I would like to acknowledge:

      • TCP was still working. I could access the servers over SSH the whole time, so I had at least some control over the situation.
      • The Wireguard port change worked as a workaround. Without it, the outage would have continued several more hours.
      • The primary database server got a long overdue reboot, and is now running a newer kernel. 
      • When the problem hit, I was at home, awake, and able to respond immediately. 

      PS. If you notice any lingering issues, have any suggestions or questions, please let me know at contact@healthchecks.io. Thank you!

      –Pēteris

      조사:

      We're still experiencing major issues. Ping handler is working somewhat, web dashboard is down. 
      The root issue is a slowdown of UDP traffic between servers in the datacenter.

      Status update from Hetzner: https://status.hetzner.com/incident/129728ce-ba25-49b6-96cc-aafcd39ab0b7

      확인 중:

      Updated Wireguard configuration to use a port number below 9000. Service is back online, we're hopefully back on track.

      해결됨:

      The issue is resolved.
    2. 시작됨:
      지속:
      Our object storage provider is experiencing a degraded performance, there is currently a backlog of ping bodies not yet uploaded to object storage. No ping bodies are lost, and will be available for viewing and download eventually.

      해결됨:

      The issue is resolved.
    3. Issues with ougoing emailsNotification Sender
      시작됨:
      지속:
      Unfortunately our SMTP provider is having another outage. Message from them: "Our server has a temporary delivery issue. Our developers are aware of them and they are working on a solution."

      확인 중:

      The SMTP service seems to be back up and more or less caught up with the backlog. The sending delay is still higher than usual.

      해결됨:

      The issue is resolved.
    4. 시작됨:
      지속:
      We're currently unable to send Signal messages to some Signal users (first-time messages to users that we have never sent messages in the past). The error messages from Signal indicate a rate-limiting issue. Previously, we could temporarily work around the rate-limiting by manually solving a CAPTCHA, but currently the issue persists even after solving CAPTCHA. 

      확인됨:

      The Signal servers apply rate-limits per sender account, and, obviously in retrospect, also per sender IP. If server A hits a rate-limit, and we submit a CAPTCHA solution from server B, it will not work. We're making changes on our side to take that into account. 

      해결됨:

      The issue is resolved.
    5. Issues with ougoing emailsNotification Sender
      시작됨:
      지속:
      Our SMTP relay provider is experiencing issues, looking into it.

      해결됨:

      The issue is resolved.
    6. Issues with outgoing emailNotification Sender
      시작됨:
      지속:
      We're seeing issues with outgoing email, looking into it.

      확인됨:

      Received an update from SMTP relay provider's support: "Our developers are currently performing a demanding system deploy which may be influencing these SSL errors."

      해결됨:

      Received an update from the SMTP relay provider (Elastic Email) – the email delivery issue has been resolved.

      During the incident, email delivery was failing intermittently, some connections to the SMTP relay went through, some failed. In total, 363 send attempts failed. Although Healthchecks retries failed email deliveries, the retry window is short, so some email messages were unfortunately lost during the outage.

      I will try to get more details about the outage from Elastic Email, and will investigate fallback options.