Störungsverlauf von Loggly

1. 6. Oktober 2026 um 12:16 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das die Protokollaufnahme für eine Teilmenge von Kunden betrifft. Kunden, die bestimmte Ingestion-Endpunkte verwenden, können eine verzögerte Verarbeitung oder eine fehlgeschlagene Aufnahme neuer Protokolldaten erfahren. Dienste, die den betroffenen Einnahmepfad nicht nutzen, bleiben funktionsfähig. Wir werden innerhalb einer Stunde ein Update bereitstellen.

2. 6. Oktober 2026 um 13:19 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 6. Oktober 2026 um 13:42 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 6. Oktober 2026 um 15:42 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

5. 6. Oktober 2026 um 16:04 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. September 2026 um 20:37 UTCresolved

   Customer Impact Eine kleine Anzahl von Kunden erlebte eine verzögerte Datenaufnahme und Warnungen, die nicht in Echtzeit verarbeitet wurden. Es gingen keine Kundendaten verloren. Ereignisaktualisierung Am 3. September 2026, um 10:52 Uhr UTC, wurde eine Infrastrukturkomponente nicht mehr verfügbar, was zu einem Verarbeitungsrückstand und Verzögerungen bei der Alarmbehandlung führte. Ein separates Warnmeldungsproblem verzögerte die Benachrichtigung des Bereitschaftsteams und verlängerte die Reaktionszeit. Darüber hinaus verhinderte ein problem mit unserem in-app-messaging, dass wir zeitnahe kundenbenachrichtigungen innerhalb der app bereitstellen konnten. Der Vorfall wurde nach 18 Stunden und 49 Minuten vollständig behoben. Die Datenverarbeitung und die Alarmbehandlung haben sich wieder normalisiert, und es gingen keine Kundendaten verloren. Wir überprüfen unser Alarmgruppierungsverhalten, unsere Servicewiederherstellungsverfahren und Kundenbenachrichtigungsmechanismen, um die Wahrscheinlichkeit und die Auswirkungen ähnlicher Vorfälle in der Zukunft zu reduzieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. August 2026 um 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 um 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 um 22:21 UTCresolved

   This incident has been resolved.

1. 21. Januar 2026 um 15:44 UTCinvestigating

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

2. 21. Januar 2026 um 16:18 UTCidentified

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

3. 21. Januar 2026 um 16:20 UTCmonitoring

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

4. 21. Januar 2026 um 16:27 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 12:07 UTCinvestigating

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

2. 18. November 2025 um 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18. November 2025 um 12:22 UTCidentified

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

4. 18. November 2025 um 12:28 UTCmonitoring

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

5. 18. November 2025 um 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18. November 2025 um 16:19 UTCresolved

   This incident has been resolved.

1. 4. Februar 2025 um 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. Februar 2025 um 18:05 UTCidentified

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

3. 4. Februar 2025 um 19:01 UTCmonitoring

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

4. 4. Februar 2025 um 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4. Februar 2025 um 19:59 UTCresolved

   This incident has been resolved.

1. 25. Januar 2025 um 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. Januar 2025 um 06:01 UTCidentified

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

3. 25. Januar 2025 um 06:35 UTCmonitoring

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

4. 25. Januar 2025 um 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. Januar 2025 um 12:14 UTCresolved

   This incident has been resolved.

1. 8. Dezember 2024 um 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. Dezember 2024 um 16:30 UTCidentified

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

3. 8. Dezember 2024 um 19:20 UTCmonitoring

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

4. 9. Dezember 2024 um 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9. Dezember 2024 um 03:39 UTCresolved

   This incident has been resolved.

1. 16. Oktober 2024 um 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16. Oktober 2024 um 12:40 UTCidentified

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

3. 16. Oktober 2024 um 13:06 UTCmonitoring

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

4. 16. Oktober 2024 um 13:20 UTCresolved

   This incident has been resolved.

1. 1. Oktober 2024 um 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. August 2024 um 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. August 2024 um 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24. August 2024 um 06:10 UTCidentified

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

4. 24. August 2024 um 07:08 UTCidentified

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

5. 24. August 2024 um 07:43 UTCmonitoring

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

6. 24. August 2024 um 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24. August 2024 um 17:02 UTCresolved

   This incident has been resolved.

1. 21. August 2024 um 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. August 2024 um 21:59 UTCidentified

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

3. 21. August 2024 um 23:20 UTCidentified

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

4. 21. August 2024 um 23:49 UTCmonitoring

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

5. 22. August 2024 um 00:19 UTCresolved

   This incident has been resolved.

1. 24. Juli 2024 um 16:56 UTCinvestigating

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

2. 24. Juli 2024 um 20:08 UTCidentified

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

3. 25. Juli 2024 um 04:42 UTCidentified

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

4. 25. Juli 2024 um 06:16 UTCmonitoring

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

5. 25. Juli 2024 um 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25. Juli 2024 um 13:32 UTCresolved

   This incident has been resolved.

1. 18. Oktober 2023 um 13:21 UTCinvestigating

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

2. 18. Oktober 2023 um 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. Oktober 2023 um 16:51 UTCidentified

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

4. 18. Oktober 2023 um 18:07 UTCmonitoring

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

5. 18. Oktober 2023 um 18:29 UTCresolved

   This incident has been resolved.

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

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

3. 10. Oktober 2023 um 13:43 UTCmonitoring

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

4. 10. Oktober 2023 um 13:54 UTCresolved

   This incident has been resolved.

1. 23. August 2023 um 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. August 2023 um 19:21 UTCidentified

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

3. 23. August 2023 um 19:45 UTCmonitoring

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

4. 23. August 2023 um 20:40 UTCresolved

   This incident has been resolved.

1. 10. April 2023 um 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. März 2023 um 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. März 2023 um 14:51 UTCidentified

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

3. 3. März 2023 um 15:29 UTCmonitoring

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

4. 3. März 2023 um 17:34 UTCresolved

   This incident has been resolved.

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

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

3. 14. November 2022 um 11:42 UTCmonitoring

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

4. 14. November 2022 um 13:05 UTCresolved

   This incident has been resolved.