Historial de interrupciones de Loggly

1. 6 de octubre de 2026 a las 12:16 UTCinvestigating

   Actualmente estamos investigando un problema que afecta la ingestión de registros para un subconjunto de clientes. Los clientes que utilizan ciertos puntos finales de la ingestión pueden experimentar el procesamiento retardado o la ingestión fallida de nuevos datos de registro. Los servicios que no utilizan la vía de ingestión afectada siguen funcionando. Proporcionaremos una actualización dentro de la hora.

2. 6 de octubre de 2026 a las 13:19 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 6 de octubre de 2026 a las 13:42 UTCidentified

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

4. 6 de octubre de 2026 a las 15:42 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

5. 6 de octubre de 2026 a las 16:04 UTCresolved

   Este incidente ha sido resuelto.

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

1. 4 de septiembre de 2026 a las 20:37 UTCresolved

   Impacto del cliente Un pequeño número de clientes experimentaron retrasos en la ingestión de datos y alertas que no se procesaron en tiempo real. No se perdieron datos de clientes. Actualización de incidentes El 3 de septiembre de 2026, a las 10:52 PM UTC, un componente de infraestructura no estaba disponible, lo que dio lugar a un proceso atrasado y retrasos en el manejo de alertas. Una notificación de demora en la agrupación de alertas separada al equipo de reserva, que amplía el tiempo a la respuesta. Además, un problema con nuestra mensajería en aplicación nos impidió proporcionar notificaciones oportunas al cliente dentro de la aplicación. El incidente se resolvió completamente después de 18 horas y 49 minutos. El procesamiento de datos y el tratamiento de alerta han regresado a la normalidad, y no se perdieron datos de clientes. Estamos revisando nuestro comportamiento de alerta, procedimientos de recuperación de servicios y mecanismos de notificación de clientes para reducir la probabilidad y el impacto de incidentes similares en el futuro.

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

1. 7 de agosto de 2026 a las 20:54 UTCresolved

   On July 12, 2026, we experienced delays in our alerting system, resulting in an interruption to alert processing for some Loggly customers. The issue was traced to a production scheduler service responsible for evaluating and scheduling alerts. Due to resource exhaustion on the host, the scheduler was unable to operate normally, preventing alert jobs from being process downstream. The team restored service by increasing the capacity of the affected host, returning resource utilization to healthy levels and allowing the scheduler to resume normal operation. Following the remediation, alert processing has since been operating normally.

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

1. 11 de mayo de 2026 a las 21:06 UTCmonitoring

   At 5:46 AM PDT we started experiencing delays in our alerting system caused by a network provider issue. The issue is resolved and we are monitoring the recovery.

2. 11 de mayo de 2026 a las 22:21 UTCresolved

   This incident has been resolved.

1. 21 de enero de 2026 a las 15:44 UTCinvestigating

   We are investigating an issue with our alerting system that started at 13:06 UTC.

2. 21 de enero de 2026 a las 16:18 UTCidentified

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

3. 21 de enero de 2026 a las 16:20 UTCmonitoring

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

4. 21 de enero de 2026 a las 16:27 UTCresolved

   This incident has been resolved.

1. 18 de noviembre de 2025 a las 12:07 UTCinvestigating

   We are experiencing issue with our Front-End application. Our engineers are investigating.

2. 18 de noviembre de 2025 a las 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 de noviembre de 2025 a las 12:22 UTCidentified

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

4. 18 de noviembre de 2025 a las 12:28 UTCmonitoring

   We have identified an issue with an outside provider and are monitoring the situation.

5. 18 de noviembre de 2025 a las 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 de noviembre de 2025 a las 16:19 UTCresolved

   This incident has been resolved.

1. 4 de febrero de 2025 a las 18:03 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 07:22 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 4 de febrero de 2025 a las 18:05 UTCidentified

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

3. 4 de febrero de 2025 a las 19:01 UTCmonitoring

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

4. 4 de febrero de 2025 a las 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 de febrero de 2025 a las 19:59 UTCresolved

   This incident has been resolved.

1. 25 de enero de 2025 a las 5:17 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 20:56 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 25 de enero de 2025 a las 6:01 UTCidentified

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

3. 25 de enero de 2025 a las 6:35 UTCmonitoring

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

4. 25 de enero de 2025 a las 9:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 de enero de 2025 a las 12:14 UTCresolved

   This incident has been resolved.

1. 8 de diciembre de 2024 a las 16:25 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 06:02 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 8 de diciembre de 2024 a las 16:30 UTCidentified

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

3. 8 de diciembre de 2024 a las 19:20 UTCmonitoring

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

4. 9 de diciembre de 2024 a las 3:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 de diciembre de 2024 a las 3:39 UTCresolved

   This incident has been resolved.

1. 16 de octubre de 2024 a las 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 de octubre de 2024 a las 12:40 UTCidentified

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

3. 16 de octubre de 2024 a las 13:06 UTCmonitoring

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

4. 16 de octubre de 2024 a las 13:20 UTCresolved

   This incident has been resolved.

1. 1 de octubre de 2024 a las 23:03 UTCresolved

   At 1:56 PM PDT we were alerted that search was unavailable. We identified the problem and applied a fix and search is once again available.

1. 24 de agosto de 2024 a las 4:02 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 20:22 PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 24 de agosto de 2024 a las 5:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 de agosto de 2024 a las 6:10 UTCidentified

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

4. 24 de agosto de 2024 a las 7:08 UTCidentified

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

5. 24 de agosto de 2024 a las 7:43 UTCmonitoring

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

6. 24 de agosto de 2024 a las 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 de agosto de 2024 a las 17:02 UTCresolved

   This incident has been resolved.

1. 21 de agosto de 2024 a las 21:47 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 14:08 PDT. All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 21 de agosto de 2024 a las 21:59 UTCidentified

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

3. 21 de agosto de 2024 a las 23:20 UTCidentified

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

4. 21 de agosto de 2024 a las 23:49 UTCmonitoring

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

5. 22 de agosto de 2024 a las 0:19 UTCresolved

   This incident has been resolved.

1. 24 de julio de 2024 a las 16:56 UTCinvestigating

   We experienced an issue with our volume data reporting service and are working on restoring it.

2. 24 de julio de 2024 a las 20:08 UTCidentified

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

3. 25 de julio de 2024 a las 4:42 UTCidentified

   A fix is still being implemented and the next update will be 06:00 UTC

4. 25 de julio de 2024 a las 6:16 UTCmonitoring

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

5. 25 de julio de 2024 a las 8:50 UTCmonitoring

   We are continuing to monitor.

6. 25 de julio de 2024 a las 13:32 UTCresolved

   This incident has been resolved.

1. 18 de octubre de 2023 a las 13:21 UTCinvestigating

   We are experiencing issue with our Front-End application. Our engineers are investigating.

2. 18 de octubre de 2023 a las 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de octubre de 2023 a las 16:51 UTCidentified

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

4. 18 de octubre de 2023 a las 18:07 UTCmonitoring

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

5. 18 de octubre de 2023 a las 18:29 UTCresolved

   This incident has been resolved.

1. 10 de octubre de 2023 a las 12:45 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 5:28 AM PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 10 de octubre de 2023 a las 12:47 UTCidentified

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

3. 10 de octubre de 2023 a las 13:43 UTCmonitoring

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

4. 10 de octubre de 2023 a las 13:54 UTCresolved

   This incident has been resolved.

1. 23 de agosto de 2023 a las 19:13 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 11:54AM PDT . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 23 de agosto de 2023 a las 19:21 UTCidentified

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

3. 23 de agosto de 2023 a las 19:45 UTCmonitoring

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

4. 23 de agosto de 2023 a las 20:40 UTCresolved

   This incident has been resolved.

1. 10 de abril de 2023 a las 15:02 UTCresolved

   Issue started: 14:05 UTC Issue resolved: 14:54am UTC Issue with sending mail for account invites and password reset. Other mail notifications should have still worked.

1. 3 de marzo de 2023 a las 14:24 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 5:52 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 3 de marzo de 2023 a las 14:51 UTCidentified

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

3. 3 de marzo de 2023 a las 15:29 UTCmonitoring

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

4. 3 de marzo de 2023 a las 17:34 UTCresolved

   This incident has been resolved.

1. 14 de noviembre de 2022 a las 10:47 UTCinvestigating

   Our engineers have identified an issue with log ingestion starting at 2:25 PST . All customer data continues to be collected and stored, but indexing of all customer data is being delayed. Customer data from after this time will not appear in search results until we resolve this issue.

2. 14 de noviembre de 2022 a las 11:25 UTCidentified

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

3. 14 de noviembre de 2022 a las 11:42 UTCmonitoring

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

4. 14 de noviembre de 2022 a las 13:05 UTCresolved

   This incident has been resolved.