Healthchecks.io Statut - Historique des incidents

Welcome to the Healthchecks.io status page. If there are interruptions to service, we will post a report here, and on our Mastodon account.

Incidents précédents

Oct, 2020

Sep, 2020

Aoû, 2020

Oct, 2020
1. CodeShip's Security Incident, Impact on Healthchecks.io
  A débuté: 23 Oct, 07:14 UTC
  Durée: 0 minute
  Résolu: 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
Sep, 2020
1. Database connectivity issue
  A débuté: 30 Sep, 10:36 UTC
  Durée: 0 minute
  Résolu: 30 Sep, 10:36 UTC
  Primary database server experienced a connectivity issue for about 2 minutes, starting 10:24 UTC.
  Currently back to normal and monitoring.
Aoû, 2020
1. WhatsApp notifications currently not getting deliveredNotification Sender
  A débuté: 4 Aoû, 19:47 UTC
  Durée: 3 heures, 25 minutes
  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.
  En vérification: 4 Aoû, 22:46 UTC
  The issue was identified and fixed by Twilio.
  Résolu: 4 Aoû, 23:13 UTC
  This incident has been resolved.