Historique des pannes de Loggly

1. 6 octobre 2026 à 12:16 UTCinvestigating

   Nous étudions actuellement un problème touchant l'ingestion de grumes pour un sous-ensemble de clients. Les clients qui utilisent certains paramètres d'ingestion peuvent subir un traitement retardé ou une ingestion ratée de nouvelles données de log. Les services qui n'utilisent pas la voie d'ingestion touchée demeurent opérationnels. Nous fournirons une mise à jour dans l'heure.

2. 6 octobre 2026 à 13:19 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 6 octobre 2026 à 13:42 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

4. 6 octobre 2026 à 15:42 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

5. 6 octobre 2026 à 16:04 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 4 septembre 2026 à 20:37 UTCresolved

   Impact client Un petit nombre de clients ont connu une ingestion tardive de données et des alertes qui n'ont pas été traitées en temps réel. Aucune donnée client n'a été perdue. Mise à jour des incidents Le 3 septembre 2026, à 22 h 52 UTC, une composante infrastructure est devenue indisponible, ce qui a entraîné un arriéré de traitement et des retards dans le traitement des alertes. Une question distincte de groupe d'alerte a retardé la notification à l'équipe de garde, prolongeant le délai de réponse. De plus, un problème avec nos messages dans l'application nous a empêchés de fournir des notifications opportunes des clients dans l'application. L'incident a été complètement résolu après 18 heures et 49 minutes. Le traitement des données et le traitement des alertes sont revenus à la normale, et aucune donnée client n'a été perdue. Nous examinons notre comportement de groupe d'alerte, nos procédures de recouvrement des services et nos mécanismes de notification des clients afin de réduire la probabilité et l'impact d'incidents semblables à l'avenir.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 août 2026 à 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.

1. 11 mai 2026 à 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 mai 2026 à 22:21 UTCresolved

   This incident has been resolved.

1. 21 janvier 2026 à 15:44 UTCinvestigating

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

2. 21 janvier 2026 à 16:18 UTCidentified

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

3. 21 janvier 2026 à 16:20 UTCmonitoring

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

4. 21 janvier 2026 à 16:27 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 à 12:07 UTCinvestigating

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

2. 18 novembre 2025 à 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 novembre 2025 à 12:22 UTCidentified

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

4. 18 novembre 2025 à 12:28 UTCmonitoring

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

5. 18 novembre 2025 à 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 novembre 2025 à 16:19 UTCresolved

   This incident has been resolved.

1. 4 février 2025 à 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 février 2025 à 18:05 UTCidentified

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

3. 4 février 2025 à 19:01 UTCmonitoring

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

4. 4 février 2025 à 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 février 2025 à 19:59 UTCresolved

   This incident has been resolved.

1. 25 janvier 2025 à 05: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 janvier 2025 à 06:01 UTCidentified

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

3. 25 janvier 2025 à 06:35 UTCmonitoring

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

4. 25 janvier 2025 à 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 janvier 2025 à 12:14 UTCresolved

   This incident has been resolved.

1. 8 décembre 2024 à 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 décembre 2024 à 16:30 UTCidentified

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

3. 8 décembre 2024 à 19:20 UTCmonitoring

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

4. 9 décembre 2024 à 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 décembre 2024 à 03:39 UTCresolved

   This incident has been resolved.

1. 16 octobre 2024 à 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 octobre 2024 à 12:40 UTCidentified

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

3. 16 octobre 2024 à 13:06 UTCmonitoring

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

4. 16 octobre 2024 à 13:20 UTCresolved

   This incident has been resolved.

1. 1 octobre 2024 à 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 août 2024 à 04: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 août 2024 à 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 août 2024 à 06:10 UTCidentified

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

4. 24 août 2024 à 07:08 UTCidentified

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

5. 24 août 2024 à 07:43 UTCmonitoring

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

6. 24 août 2024 à 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 août 2024 à 17:02 UTCresolved

   This incident has been resolved.

1. 21 août 2024 à 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 août 2024 à 21:59 UTCidentified

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

3. 21 août 2024 à 23:20 UTCidentified

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

4. 21 août 2024 à 23:49 UTCmonitoring

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

5. 22 août 2024 à 00:19 UTCresolved

   This incident has been resolved.

1. 24 juillet 2024 à 16:56 UTCinvestigating

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

2. 24 juillet 2024 à 20:08 UTCidentified

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

3. 25 juillet 2024 à 04:42 UTCidentified

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

4. 25 juillet 2024 à 06:16 UTCmonitoring

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

5. 25 juillet 2024 à 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 juillet 2024 à 13:32 UTCresolved

   This incident has been resolved.

1. 18 octobre 2023 à 13:21 UTCinvestigating

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

2. 18 octobre 2023 à 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 octobre 2023 à 16:51 UTCidentified

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

4. 18 octobre 2023 à 18:07 UTCmonitoring

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

5. 18 octobre 2023 à 18:29 UTCresolved

   This incident has been resolved.

1. 10 octobre 2023 à 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 octobre 2023 à 12:47 UTCidentified

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

3. 10 octobre 2023 à 13:43 UTCmonitoring

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

4. 10 octobre 2023 à 13:54 UTCresolved

   This incident has been resolved.

1. 23 août 2023 à 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 août 2023 à 19:21 UTCidentified

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

3. 23 août 2023 à 19:45 UTCmonitoring

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

4. 23 août 2023 à 20:40 UTCresolved

   This incident has been resolved.

1. 10 avril 2023 à 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 mars 2023 à 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 mars 2023 à 14:51 UTCidentified

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

3. 3 mars 2023 à 15:29 UTCmonitoring

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

4. 3 mars 2023 à 17:34 UTCresolved

   This incident has been resolved.

1. 14 novembre 2022 à 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 novembre 2022 à 11:25 UTCidentified

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

3. 14 novembre 2022 à 11:42 UTCmonitoring

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

4. 14 novembre 2022 à 13:05 UTCresolved

   This incident has been resolved.