Status

Wcześniejsze incydenty

1. Paź, 2020

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

      Rozpoczął się: 23 Paź, 07:14 UTC

      Czas trwania: 0 minut

      Rozwiązany: 23 Paź, 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

2. Wrz, 2020

   1. Database connectivity issue

      Rozpoczął się: 30 Wrz, 10:36 UTC

      Czas trwania: 0 minut

      Rozwiązany: 30 Wrz, 10:36 UTC

      Primary database server experienced a connectivity issue for about 2 minutes, starting 10:24 UTC.
      Currently back to normal and monitoring.

3. Sie, 2020

   1. WhatsApp notifications currently not getting deliveredNotification Sender

      Rozpoczął się: 4 Sie, 19:47 UTC

      Czas trwania: 3 godziny, 25 minut

      Our upstream provider for delivering WhatsApp notifications, is currently rejecting outbound WhatsApp messages with an error:

      63013 This message send failed because it violates Channel provider’s policy.

      Currently contacting them to figure out what has gone wrong.

      Weryfikacja: 4 Sie, 22:46 UTC

      The issue was identified and fixed by Twilio.

      Rozwiązany: 4 Sie, 23:13 UTC

      This incident has been resolved.