Status

Incidentes passados

1. Set, 2024

   1. Database Outage Due to DC Switch FaultEmail DeliveryNotification SenderPing APIDashboard

      Começou: 29 Set, 08:01 UTC

      Duração: 1 hour, 20 minutes

      There's a network fault (a switch fault) at our data-center affecting our primary database. This resulted in a complete outage: dashboard, ping endpoints, notification sender.
      
      We've failed over to a standby database.

      Verificando: 29 Set, 08:40 UTC

      After fail-over to a standby database systems are back up. 
      We are monitoring the servers, and preparing a new standby.

      Resolvido: 29 Set, 09:21 UTC

      The issue is resolved.

2. Ago, 2024

   Todos os sistemas operacionais.

3. Jul, 2024

   1. Stability IssuesDashboard

      Começou: 11 Jul, 22:50 UTC

      Duração: 8 hours, 41 minutes

      We're investigating intermittent failing requests on healthchecks.io.

      Identificado: 11 Jul, 23:06 UTC

      The HTTP request failures on https://healthchecks.io seem to be a knock-on effects of connectivity issues to our object storage provider.
      
      We have temporarily disabled API calls that retrieve ping bodies from object storage.

      Identificado: 12 Jul, 00:20 UTC

      We have verified the failing requests on Healthchecks.io dashboard were indeed related to object storage availability issues. The temporary solution of disabling "get object" API calls has restored the dashboard functionality. Our object storage provider has acknowledged the issue and is working on it.
      
      Currently on Healthchecks.io dashboard, when you view details of a recent ping you will see  a "The request body data is not yet available, please check back later." message. The request bodies are not lost, and will be available for viewing eventually.

      Identificado: 12 Jul, 06:18 UTC

      Our object storage provider have implemented a fix. We are currently working through a backlog of not yet uploaded ping bodies.

      Resolvido: 12 Jul, 07:32 UTC

      We have fully caught up with ping body backlog, and the service is now operating normally.