Loggly driftsforstyrrelser

1. 6. oktober 2026 kl. 12.16 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker log indtagelse for en delmængde af kunder. Kunder, der bruger bestemte endepunkter for indtagelse, kan opleve forsinket behandling eller mislykket indtagelse af nye logdata. Tjenester, der ikke udnytter den berørte administrationsvej, forbliver operationelle. Vi vil levere en opdatering inden for en time.

2. 6. oktober 2026 kl. 13.19 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 6. oktober 2026 kl. 13.42 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

4. 6. oktober 2026 kl. 15.42 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

5. 6. oktober 2026 kl. 16.04 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 4. september 2026 kl. 20.37 UTCresolved

   Kundeeffekt Et lille antal kunder oplevede forsinkede data indtagelse og advarsler, der ikke blev behandlet i realtid. Ingen kundedata blev tabt. Hændelsesopdatering Den 3. september 2026, kl. 10: 52 UTC, blev en infrastrukturkomponent utilgængelig, hvilket resulterede i en behandlingsforsinkelse og forsinkelser i alarmhåndteringen. Et separat alarmgrupperingsnummer forsinkede meddelelsen til on-call teamet, hvilket udvidede tiden til at svare. Desuden forhindrede et problem med vores in- app beskeder os i at levere rettidige kundemeddelelser i app 'en. Hændelsen blev løst efter 18 timer og 49 minutter. Databehandling og alarmhåndtering er vendt tilbage til normal, og ingen kundedata blev tabt. Vi gennemgår vores alarm- gruppering adfærd, service-recovery procedurer, og kunde notification mekanismer til at reducere sandsynligheden og virkningen af lignende hændelser i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. august 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 22.21 UTCresolved

   This incident has been resolved.

1. 21. januar 2026 kl. 15.44 UTCinvestigating

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

2. 21. januar 2026 kl. 16.18 UTCidentified

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

3. 21. januar 2026 kl. 16.20 UTCmonitoring

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

4. 21. januar 2026 kl. 16.27 UTCresolved

   This incident has been resolved.

1. 18. november 2025 kl. 12.07 UTCinvestigating

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

2. 18. november 2025 kl. 12.19 UTCidentified

   We have identified an issue with an outside provider

3. 18. november 2025 kl. 12.22 UTCidentified

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

4. 18. november 2025 kl. 12.28 UTCmonitoring

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

5. 18. november 2025 kl. 14.25 UTCmonitoring

   We are continuing to monitor the issue

6. 18. november 2025 kl. 16.19 UTCresolved

   This incident has been resolved.

1. 4. februar 2025 kl. 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 kl. 18.05 UTCidentified

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

3. 4. februar 2025 kl. 19.01 UTCmonitoring

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

4. 4. februar 2025 kl. 19.29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4. februar 2025 kl. 19.59 UTCresolved

   This incident has been resolved.

1. 25. januar 2025 kl. 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 kl. 06.01 UTCidentified

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

3. 25. januar 2025 kl. 06.35 UTCmonitoring

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

4. 25. januar 2025 kl. 09.17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. januar 2025 kl. 12.14 UTCresolved

   This incident has been resolved.

1. 8. december 2024 kl. 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. december 2024 kl. 16.30 UTCidentified

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

3. 8. december 2024 kl. 19.20 UTCmonitoring

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

4. 9. december 2024 kl. 03.37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9. december 2024 kl. 03.39 UTCresolved

   This incident has been resolved.

1. 16. oktober 2024 kl. 12.35 UTCinvestigating

   We are currently investigating this issue.

2. 16. oktober 2024 kl. 12.40 UTCidentified

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

3. 16. oktober 2024 kl. 13.06 UTCmonitoring

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

4. 16. oktober 2024 kl. 13.20 UTCresolved

   This incident has been resolved.

1. 1. oktober 2024 kl. 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 kl. 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 kl. 05.09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24. august 2024 kl. 06.10 UTCidentified

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

4. 24. august 2024 kl. 07.08 UTCidentified

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

5. 24. august 2024 kl. 07.43 UTCmonitoring

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

6. 24. august 2024 kl. 12.49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24. august 2024 kl. 17.02 UTCresolved

   This incident has been resolved.

1. 21. august 2024 kl. 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 kl. 21.59 UTCidentified

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

3. 21. august 2024 kl. 23.20 UTCidentified

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

4. 21. august 2024 kl. 23.49 UTCmonitoring

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

5. 22. august 2024 kl. 00.19 UTCresolved

   This incident has been resolved.

1. 24. juli 2024 kl. 16.56 UTCinvestigating

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

2. 24. juli 2024 kl. 20.08 UTCidentified

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

3. 25. juli 2024 kl. 04.42 UTCidentified

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

4. 25. juli 2024 kl. 06.16 UTCmonitoring

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

5. 25. juli 2024 kl. 08.50 UTCmonitoring

   We are continuing to monitor.

6. 25. juli 2024 kl. 13.32 UTCresolved

   This incident has been resolved.

1. 18. oktober 2023 kl. 13.21 UTCinvestigating

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

2. 18. oktober 2023 kl. 16.01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. oktober 2023 kl. 16.51 UTCidentified

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

4. 18. oktober 2023 kl. 18.07 UTCmonitoring

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

5. 18. oktober 2023 kl. 18.29 UTCresolved

   This incident has been resolved.

1. 10. oktober 2023 kl. 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 kl. 12.47 UTCidentified

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

3. 10. oktober 2023 kl. 13.43 UTCmonitoring

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

4. 10. oktober 2023 kl. 13.54 UTCresolved

   This incident has been resolved.

1. 23. august 2023 kl. 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 kl. 19.21 UTCidentified

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

3. 23. august 2023 kl. 19.45 UTCmonitoring

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

4. 23. august 2023 kl. 20.40 UTCresolved

   This incident has been resolved.

1. 10. april 2023 kl. 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. marts 2023 kl. 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. marts 2023 kl. 14.51 UTCidentified

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

3. 3. marts 2023 kl. 15.29 UTCmonitoring

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

4. 3. marts 2023 kl. 17.34 UTCresolved

   This incident has been resolved.

1. 14. november 2022 kl. 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 kl. 11.25 UTCidentified

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

3. 14. november 2022 kl. 11.42 UTCmonitoring

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

4. 14. november 2022 kl. 13.05 UTCresolved

   This incident has been resolved.