Status

Past incidents

1. Dec, 2020

   1. Notifications to Telegram currently not workingNotification Sender

      Started: 16 Dec, 13:46 UTC

      Duration: 2 hours, 7 minutes

      Requests to Telegram API are currently timing out.

      Telegram on Twitter: “Some of our users, primarily in Europe and the Middle East are currently experiencing connection issues. We’re working to bring them back online. “

      Verifying: 16 Dec, 14:22 UTC

      Telegram API is responding again, monitoring.

      Resolved: 16 Dec, 15:54 UTC

      This incident has been resolved.

   2. Sporadic connection timeouts over IPv6Ping APIDashboard

      Started: 10 Dec, 14:57 UTC

      Duration: 3 hours, 13 minutes

      We are continuing to investigate this issue.

      Resolved: 10 Dec, 18:10 UTC

      We’re back to normal.

2. Nov, 2020

   All systems operational.

3. Oct, 2020

   1. CodeShip's Security Incident, Impact on Healthchecks.io

      Started: 23 Oct, 07:14 UTC

      Duration: 0 minutes

      Resolved: 23 Oct, 07:14 UTC

      Recently, CodeShip, a CI/CD service, reported a security incident: a database containing their production data had been exposed for over a year. CodeShip requests its customers to reset all keys, deployment credentials, and authorization tokens that may have been exposed.

      Although Healthchecks.io is not using CodeShip directly, CodeShip had access to a Bitbucket source code repository containing various secrets that the Healthchecks.io production environment uses. While there are no signs of any unauthorized access, we have taken several precautions: the secrets have been reset to new values, the secrets are now being stored in an encrypted form, and CodeShip’s access to the Bitbucket repository has been revoked.

      For more details, please read: https://blog.healthchecks.io/2020/10/codeship-security-incidents-impact-on-healthchecks-io/

      CodeShip’s security notification: https://www.codeshipstatus.com/incidents/91bvlfw9xlm9