Status

Eerdere incidenten

1. Apr, 2026

   1. Signal notification delivery brokenNotification Sender

      Begonnen: 1 Apr, 13:30 UTC

      Duur: 17 uur, 46 minuten

      We are currently investigating an issue with the delivery of Signal notifications.

      Opgelost: 2 Apr, 07:16 UTC

      The problem has been fixed, Signal notifications are being delivered again.
      
      What happened:
      
      On April 1, 13:30 UTC, our signal account became unregistered. This was caused by a new Signal protocol feature – SPQR (Sparse Post-Quantum Ratchet) – becoming mandatory and our Signal client software not supporting it.
      
      The fix:
      
      Updated to the latest signal-cli version (0.14.1), registered a new account with the same old number, and re-added the linked devices.
      
      For more background information, here is an issue on the signal-cli issue tracker discussing the account de-registrations on April 1.

2. Mrt, 2026

   Alle systemen operationeel.

3. Feb, 2026

   1. Services downEmail DeliveryNotification SenderPing APIDashboard

      Begonnen: 25 Feb, 21:09 UTC

      Duur: 8 uur, 38 minuten

      Our services are currently down. Looks like there is no UDP connectivity between any of our servers. Investigating.

      Verifiëren: 25 Feb, 21:22 UTC

      The services are back up. The outage was caused by a Hetzner-wide network issue: https://status.hetzner.com/incident/5e901309-0873-42af-90c5-84f38304f592

      Opgelost: 26 Feb, 05:48 UTC

      The issue is resolved.
      
      From Hetzner's status page: 
      
      

      The issue was caused due an DDOS attack which was mitigated but blocked too much traffic affecting UDP. Due to the overblocking other services not directly using UDP were influenced too. The issue was solved, we will check further measures to avoid this in the future. All systems are accessible again.