Need support?

E-mail us
Welcome to the status page. If there are interruptions to service, we will post a report here, and on our Mastodon account. 

Past incidents

Oct, 2020
Sep, 2020
Aug, 2020
  1. Oct, 2020

    1. Started:


      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 is not using CodeShip directly, CodeShip had access to a Bitbucket source code repository containing various secrets that the 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:

      CodeShip’s security notification:

  2. Sep, 2020

    1. Started:


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

  3. Aug, 2020

    1. Started:

      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.


      The issue was identified and fixed by Twilio.


      This incident has been resolved.