Historia awarii Loggly

1. 6 października 2026 12:16 UTCinvestigating

   Obecnie badamy problem wpływający na spożycie logarytmu dla podgrupy klientów. Klienci stosujący określone punkty końcowe spożycia mogą doświadczyć opóźnionego przetwarzania lub nieudanego spożycia nowych danych dziennika. Usługi niewykorzystujące danej ścieżki spożycia pozostają w mocy. Dostarczymy nowe informacje w ciągu godziny.

2. 6 października 2026 13:19 UTCinvestigating

   Nadal badamy tę kwestię.

3. 6 października 2026 13:42 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

4. 6 października 2026 15:42 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

5. 6 października 2026 16:04 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 4 września 2026 20:37 UTCresolved

   Wpływ na klienta Niewielka liczba klientów doświadczyła opóźnionego spożycia danych i ostrzeżeń, które nie były przetwarzane w czasie rzeczywistym. Nie utracono danych klientów. Aktualizacja zdarzeń W dniu 3 września 2026 r., o godzinie 10: 52 PM UTC, element infrastruktury stał się niedostępny, co spowodowało zaległości w przetwarzaniu i opóźnienia w obsłudze alarmowej. Oddzielny problem grupowania alarmów opóźnione powiadamianie zespołu on-call, wydłużając czas na odpowiedź. Ponadto problem z komunikacją in- app uniemożliwił nam terminowe powiadamianie klientów w aplikacji. Incydent został całkowicie rozwiązany po 18 godzinach i 49 minutach. Przetwarzanie danych i obsługa alarmowa wróciły do normy, a dane klientów nie zostały utracone. Przeglądamy nasze działania w ramach grup alarmowych, procedury odzyskiwania usług i mechanizmy powiadamiania klientów w celu zmniejszenia prawdopodobieństwa i wpływu podobnych incydentów w przyszłości.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 sierpnia 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 maja 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 maja 2026 22:21 UTCresolved

   This incident has been resolved.

1. 21 stycznia 2026 15:44 UTCinvestigating

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

2. 21 stycznia 2026 16:18 UTCidentified

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

3. 21 stycznia 2026 16:20 UTCmonitoring

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

4. 21 stycznia 2026 16:27 UTCresolved

   This incident has been resolved.

1. 18 listopada 2025 12:07 UTCinvestigating

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

2. 18 listopada 2025 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 listopada 2025 12:22 UTCidentified

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

4. 18 listopada 2025 12:28 UTCmonitoring

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

5. 18 listopada 2025 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 listopada 2025 16:19 UTCresolved

   This incident has been resolved.

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

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

3. 4 lutego 2025 19:01 UTCmonitoring

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

4. 4 lutego 2025 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 lutego 2025 19:59 UTCresolved

   This incident has been resolved.

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

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

3. 25 stycznia 2025 06:35 UTCmonitoring

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

4. 25 stycznia 2025 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 stycznia 2025 12:14 UTCresolved

   This incident has been resolved.

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

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

3. 8 grudnia 2024 19:20 UTCmonitoring

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

4. 9 grudnia 2024 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 grudnia 2024 03:39 UTCresolved

   This incident has been resolved.

1. 16 października 2024 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 października 2024 12:40 UTCidentified

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

3. 16 października 2024 13:06 UTCmonitoring

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

4. 16 października 2024 13:20 UTCresolved

   This incident has been resolved.

1. 1 października 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 sierpnia 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 sierpnia 2024 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 sierpnia 2024 06:10 UTCidentified

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

4. 24 sierpnia 2024 07:08 UTCidentified

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

5. 24 sierpnia 2024 07:43 UTCmonitoring

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

6. 24 sierpnia 2024 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 sierpnia 2024 17:02 UTCresolved

   This incident has been resolved.

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

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

3. 21 sierpnia 2024 23:20 UTCidentified

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

4. 21 sierpnia 2024 23:49 UTCmonitoring

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

5. 22 sierpnia 2024 00:19 UTCresolved

   This incident has been resolved.

1. 24 lipca 2024 16:56 UTCinvestigating

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

2. 24 lipca 2024 20:08 UTCidentified

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

3. 25 lipca 2024 04:42 UTCidentified

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

4. 25 lipca 2024 06:16 UTCmonitoring

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

5. 25 lipca 2024 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 lipca 2024 13:32 UTCresolved

   This incident has been resolved.

1. 18 października 2023 13:21 UTCinvestigating

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

2. 18 października 2023 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 października 2023 16:51 UTCidentified

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

4. 18 października 2023 18:07 UTCmonitoring

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

5. 18 października 2023 18:29 UTCresolved

   This incident has been resolved.

1. 10 października 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 października 2023 12:47 UTCidentified

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

3. 10 października 2023 13:43 UTCmonitoring

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

4. 10 października 2023 13:54 UTCresolved

   This incident has been resolved.

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

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

3. 23 sierpnia 2023 19:45 UTCmonitoring

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

4. 23 sierpnia 2023 20:40 UTCresolved

   This incident has been resolved.

1. 10 kwietnia 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 marca 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 marca 2023 14:51 UTCidentified

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

3. 3 marca 2023 15:29 UTCmonitoring

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

4. 3 marca 2023 17:34 UTCresolved

   This incident has been resolved.

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

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

3. 14 listopada 2022 11:42 UTCmonitoring

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

4. 14 listopada 2022 13:05 UTCresolved

   This incident has been resolved.