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. 

以前的事件

八月, 2024
   
 
七月, 2024
    
六月, 2024
     

  1. 八月, 2024

    所有系统运行.

  2. 七月, 2024

    1. 开始时间:
      为期:
      We're investigating intermittent failing requests on healthchecks.io.

      找到:

      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.

      找到:

      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.

      找到:

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

      解决了:

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

  3. 六月, 2024

    1. Delayed ping body processingNotification SenderDashboard
      开始时间:
      为期:
      Our object storage provider is currently performing maintenance (scheduled on June 18th, 2024, from 18:00 UTC to 03:00 UTC). Some percentage of object storage API calls are currently failing, which causes the following problems for Healthchecks.io:

      * There's a delay in ping body uploads to object storage. When you view details of a recent ping you may 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 eventually.
      * Our notification sender process can crash (and silently drop the notification it was about to send) when it hits an unexpected error from object storage. We're currently working on handling these errors. 

      找到:

      We have deployed a fix for the notification sender process crashing when it hits an unexpected error from object storage.

      解决了:

      Our object storage provider has completed the maintenance. Ping body processing is now back to working normally with no delays.