Historial de interrupciones de Logz

1. 25 de agosto de 2026 a las 0:42 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 25 de agosto de 2026 a las 1:03 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 25 de agosto de 2026 a las 2:01 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 25 de agosto de 2026 a las 2:23 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. 25 de agosto de 2026 a las 4:12 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de agosto de 2026 a las 15:29 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. 21 de agosto de 2026 a las 16:26 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 6 de agosto de 2026 a las 6:51 UTCresolved

   Algunos clientes han experimentado retrasos en la entrega de registros. Hemos identificado la cuestión y la hemos resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 9 de julio de 2026 a las 1:05 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 9 de julio de 2026 a las 1:27 UTCresolved

   This incident has been resolved.

1. 8 de julio de 2026 a las 16:51 UTCinvestigating

   We are currently investigating this issue.

2. 8 de julio de 2026 a las 17:27 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 de julio de 2026 a las 18:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 8 de julio de 2026 a las 18:37 UTCresolved

   This incident has been resolved.

1. 8 de junio de 2026 a las 13:21 UTCmonitoring

   We’ll continue to monitor the service.

2. 8 de junio de 2026 a las 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 8 de junio de 2026 a las 16:40 UTCresolved

   This incident has been resolved.

1. 8 de junio de 2026 a las 12:21 UTCinvestigating

   We are currently investigating this issue.

2. 8 de junio de 2026 a las 16:40 UTCresolved

   This incident has been resolved.

1. 4 de junio de 2026 a las 6:14 UTCresolved

   The data ingestion outage that affected some of our customers is resolved. All systems are operational.

1. 13 de mayo de 2026 a las 18:06 UTCresolved

   We are currently investigating this issue.

1. 8 de mayo de 2026 a las 0:53 UTCinvestigating

   We are currently investigating this issue.

2. 8 de mayo de 2026 a las 2:40 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 de mayo de 2026 a las 4:58 UTCidentified

   Mitigation efforts are currently underway. Customers should begin to see gradual improvement shortly while we continue monitoring and working toward full resolution.

4. 8 de mayo de 2026 a las 8:03 UTCresolved

   This incident has been resolved.

1. 6 de mayo de 2026 a las 10:39 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 6 de mayo de 2026 a las 10:43 UTCidentified

   We are continuing to work on a fix for this issue.

3. 6 de mayo de 2026 a las 11:49 UTCresolved

   This incident has been resolved.

1. 29 de abril de 2026 a las 21:34 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 30 de abril de 2026 a las 0:26 UTCresolved

   This incident has been resolved.

1. 10 de abril de 2026 a las 16:37 UTCinvestigating

   We are currently investigating this issue.

2. 10 de abril de 2026 a las 17:52 UTCresolved

   This incident has been resolved.

1. 30 de marzo de 2026 a las 13:21 UTCinvestigating

   We are currently investigating this issue.

2. 30 de marzo de 2026 a las 14:30 UTCresolved

   This incident has been resolved.

1. 27 de marzo de 2026 a las 7:58 UTCinvestigating

   We are currently experiencing reduced log ingestion rates in Us-east Our team is actively investigating and working to restore full performance

2. 27 de marzo de 2026 a las 8:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 de marzo de 2026 a las 8:57 UTCresolved

   This incident has been resolved.

1. 10 de marzo de 2026 a las 19:34 UTCinvestigating

   We are currently investigating this issue.

2. 10 de marzo de 2026 a las 19:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 de marzo de 2026 a las 20:03 UTCresolved

   This incident has been resolved.

1. 3 de marzo de 2026 a las 16:16 UTCinvestigating

   We are currently investigating this issue.

2. 3 de marzo de 2026 a las 16:45 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 3 de marzo de 2026 a las 20:35 UTCresolved

   This incident has been resolved.

1. 3 de marzo de 2026 a las 16:02 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 3 de marzo de 2026 a las 18:47 UTCresolved

   This incident has been resolved.

1. 26 de febrero de 2026 a las 22:33 UTCinvestigating

   We are currently investigating this issue.

2. 26 de febrero de 2026 a las 23:09 UTCresolved

   This incident has been resolved.

1. 23 de febrero de 2026 a las 17:38 UTCinvestigating

   We are currently investigating this issue.

2. 23 de febrero de 2026 a las 17:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 de febrero de 2026 a las 17:59 UTCresolved

   This incident has been resolved.