Cronologia delle interruzioni di Logz

1. 25 agosto 2026 alle ore 00:42 UTCinvestigating

   Stiamo attualmente indagando su questo problema.

2. 25 agosto 2026 alle ore 01:03 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 25 agosto 2026 alle ore 02:01 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 25 agosto 2026 alle ore 02:23 UTCmonitoring

   Stiamo continuando a monitorare eventuali ulteriori problemi.

5. 25 agosto 2026 alle ore 04:12 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 21 agosto 2026 alle ore 15:29 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

2. 21 agosto 2026 alle ore 16:26 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 6 agosto 2026 alle ore 06:51 UTCresolved

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

1. 9 luglio 2026 alle ore 01:05 UTCidentified

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

2. 9 luglio 2026 alle ore 01:27 UTCresolved

   This incident has been resolved.

1. 8 luglio 2026 alle ore 16:51 UTCinvestigating

   We are currently investigating this issue.

2. 8 luglio 2026 alle ore 17:27 UTCidentified

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

3. 8 luglio 2026 alle ore 18:28 UTCmonitoring

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

4. 8 luglio 2026 alle ore 18:37 UTCresolved

   This incident has been resolved.

1. 8 giugno 2026 alle ore 13:21 UTCmonitoring

   We’ll continue to monitor the service.

2. 8 giugno 2026 alle ore 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 8 giugno 2026 alle ore 16:40 UTCresolved

   This incident has been resolved.

1. 8 giugno 2026 alle ore 12:21 UTCinvestigating

   We are currently investigating this issue.

2. 8 giugno 2026 alle ore 16:40 UTCresolved

   This incident has been resolved.

1. 4 giugno 2026 alle ore 06:14 UTCresolved

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

1. 13 maggio 2026 alle ore 18:06 UTCresolved

   We are currently investigating this issue.

1. 8 maggio 2026 alle ore 00:53 UTCinvestigating

   We are currently investigating this issue.

2. 8 maggio 2026 alle ore 02:40 UTCidentified

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

3. 8 maggio 2026 alle ore 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 maggio 2026 alle ore 08:03 UTCresolved

   This incident has been resolved.

1. 6 maggio 2026 alle ore 10:39 UTCidentified

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

2. 6 maggio 2026 alle ore 10:43 UTCidentified

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

3. 6 maggio 2026 alle ore 11:49 UTCresolved

   This incident has been resolved.

1. 29 aprile 2026 alle ore 21:34 UTCidentified

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

2. 30 aprile 2026 alle ore 00:26 UTCresolved

   This incident has been resolved.

1. 10 aprile 2026 alle ore 16:37 UTCinvestigating

   We are currently investigating this issue.

2. 10 aprile 2026 alle ore 17:52 UTCresolved

   This incident has been resolved.

1. 30 marzo 2026 alle ore 13:21 UTCinvestigating

   We are currently investigating this issue.

2. 30 marzo 2026 alle ore 14:30 UTCresolved

   This incident has been resolved.

1. 27 marzo 2026 alle ore 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 marzo 2026 alle ore 08:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 marzo 2026 alle ore 08:57 UTCresolved

   This incident has been resolved.

1. 10 marzo 2026 alle ore 19:34 UTCinvestigating

   We are currently investigating this issue.

2. 10 marzo 2026 alle ore 19:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 marzo 2026 alle ore 20:03 UTCresolved

   This incident has been resolved.

1. 3 marzo 2026 alle ore 16:16 UTCinvestigating

   We are currently investigating this issue.

2. 3 marzo 2026 alle ore 16:45 UTCidentified

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

3. 3 marzo 2026 alle ore 20:35 UTCresolved

   This incident has been resolved.

1. 3 marzo 2026 alle ore 16:02 UTCidentified

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

2. 3 marzo 2026 alle ore 18:47 UTCresolved

   This incident has been resolved.

1. 26 febbraio 2026 alle ore 22:33 UTCinvestigating

   We are currently investigating this issue.

2. 26 febbraio 2026 alle ore 23:09 UTCresolved

   This incident has been resolved.

1. 23 febbraio 2026 alle ore 17:38 UTCinvestigating

   We are currently investigating this issue.

2. 23 febbraio 2026 alle ore 17:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 febbraio 2026 alle ore 17:59 UTCresolved

   This incident has been resolved.