Logz driftsforstyrrelser

1. 25. august 2026 kl. 00.42 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 25. august 2026 kl. 01.03 UTCidentified

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

3. 25. august 2026 kl. 02.01 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 25. august 2026 kl. 02.23 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 25. august 2026 kl. 04.12 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. august 2026 kl. 15.29 UTCidentified

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

2. 21. august 2026 kl. 16.26 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. august 2026 kl. 06.51 UTCresolved

   Some customers have experienced delays in log delivery. We have identified the issue and have resolved it.

1. 9. juli 2026 kl. 01.05 UTCidentified

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

2. 9. juli 2026 kl. 01.27 UTCresolved

   This incident has been resolved.

1. 8. juli 2026 kl. 16.51 UTCinvestigating

   We are currently investigating this issue.

2. 8. juli 2026 kl. 17.27 UTCidentified

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

3. 8. juli 2026 kl. 18.28 UTCmonitoring

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

4. 8. juli 2026 kl. 18.37 UTCresolved

   This incident has been resolved.

1. 8. juni 2026 kl. 13.21 UTCmonitoring

   We’ll continue to monitor the service.

2. 8. juni 2026 kl. 13.52 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 8. juni 2026 kl. 16.40 UTCresolved

   This incident has been resolved.

1. 8. juni 2026 kl. 12.21 UTCinvestigating

   We are currently investigating this issue.

2. 8. juni 2026 kl. 16.40 UTCresolved

   This incident has been resolved.

1. 4. juni 2026 kl. 06.14 UTCresolved

   The data ingestion outage that affected some of our customers is resolved. All systems are operational.

1. 13. maj 2026 kl. 18.06 UTCresolved

   We are currently investigating this issue.

1. 8. maj 2026 kl. 00.53 UTCinvestigating

   We are currently investigating this issue.

2. 8. maj 2026 kl. 02.40 UTCidentified

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

3. 8. maj 2026 kl. 04.58 UTCidentified

   Mitigation efforts are currently underway. Customers should begin to see gradual improvement shortly while we continue monitoring and working toward full resolution.

4. 8. maj 2026 kl. 08.03 UTCresolved

   This incident has been resolved.

1. 6. maj 2026 kl. 10.39 UTCidentified

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

2. 6. maj 2026 kl. 10.43 UTCidentified

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

3. 6. maj 2026 kl. 11.49 UTCresolved

   This incident has been resolved.

1. 29. april 2026 kl. 21.34 UTCidentified

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

2. 30. april 2026 kl. 00.26 UTCresolved

   This incident has been resolved.

1. 10. april 2026 kl. 16.37 UTCinvestigating

   We are currently investigating this issue.

2. 10. april 2026 kl. 17.52 UTCresolved

   This incident has been resolved.

1. 30. marts 2026 kl. 13.21 UTCinvestigating

   We are currently investigating this issue.

2. 30. marts 2026 kl. 14.30 UTCresolved

   This incident has been resolved.

1. 27. marts 2026 kl. 07.58 UTCinvestigating

   We are currently experiencing reduced log ingestion rates in Us-east Our team is actively investigating and working to restore full performance

2. 27. marts 2026 kl. 08.56 UTCinvestigating

   We are continuing to investigate this issue.

3. 27. marts 2026 kl. 08.57 UTCresolved

   This incident has been resolved.

1. 10. marts 2026 kl. 19.34 UTCinvestigating

   We are currently investigating this issue.

2. 10. marts 2026 kl. 19.44 UTCinvestigating

   We are continuing to investigate this issue.

3. 10. marts 2026 kl. 20.03 UTCresolved

   This incident has been resolved.

1. 3. marts 2026 kl. 16.16 UTCinvestigating

   We are currently investigating this issue.

2. 3. marts 2026 kl. 16.45 UTCidentified

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

3. 3. marts 2026 kl. 20.35 UTCresolved

   This incident has been resolved.

1. 3. marts 2026 kl. 16.02 UTCidentified

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

2. 3. marts 2026 kl. 18.47 UTCresolved

   This incident has been resolved.

1. 26. februar 2026 kl. 22.33 UTCinvestigating

   We are currently investigating this issue.

2. 26. februar 2026 kl. 23.09 UTCresolved

   This incident has been resolved.

1. 23. februar 2026 kl. 17.38 UTCinvestigating

   We are currently investigating this issue.

2. 23. februar 2026 kl. 17.52 UTCinvestigating

   We are continuing to investigate this issue.

3. 23. februar 2026 kl. 17.59 UTCresolved

   This incident has been resolved.