Cronologia delle interruzioni di Loggly

1. 6 ottobre 2026 alle ore 12:16 UTCinvestigating

   Stiamo attualmente indagando su un problema che riguarda l'ingestione dei registri per un sottoinsieme di clienti. I clienti che utilizzano determinati endpoint di ingestione possono sperimentare l'elaborazione ritardata o l'ingestione non riuscita di nuovi dati di registro. I servizi che non utilizzano il percorso di ingestione interessato rimangono operativi. Forniremo un aggiornamento entro l'ora.

2. 6 ottobre 2026 alle ore 13:19 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 6 ottobre 2026 alle ore 13:42 UTCidentified

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

4. 6 ottobre 2026 alle ore 15:42 UTCidentified

   Stiamo continuando a lavorare per risolvere questo problema.

5. 6 ottobre 2026 alle ore 16:04 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 4 settembre 2026 alle ore 20:37 UTCresolved

   Impatto del cliente Un piccolo numero di clienti ha sperimentato l'ingestione dei dati ritardata e avvisi che non sono stati elaborati in tempo reale. Nessun dato del cliente è stato perso. Aggiornamento incidente Il 3 settembre 2026, alle 10:52 PM UTC, un componente infrastrutturale non è disponibile, con conseguente un backlog di elaborazione e ritardi nella gestione degli avvisi. Un problema di gruppo di avvisi separato ha ritardato la notifica al team di chiamata, estendendo il tempo alla risposta. Inoltre, un problema con la nostra messaggistica in-app ci ha impedito di fornire le notifiche tempestive dei clienti all'interno dell'app. L'incidente è stato completamente risolto dopo 18 ore e 49 minuti. Il trattamento dei dati e la gestione degli avvisi sono tornati alla normalità e nessun dato del cliente è stato perso. Stiamo esaminando il nostro comportamento di gruppo di allerta, procedure di recupero dei servizi e meccanismi di notifica del cliente per ridurre la probabilità e l'impatto di incidenti simili in futuro.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 agosto 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 22:21 UTCresolved

   This incident has been resolved.

1. 21 gennaio 2026 alle ore 15:44 UTCinvestigating

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

2. 21 gennaio 2026 alle ore 16:18 UTCidentified

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

3. 21 gennaio 2026 alle ore 16:20 UTCmonitoring

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

4. 21 gennaio 2026 alle ore 16:27 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 alle ore 12:07 UTCinvestigating

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

2. 18 novembre 2025 alle ore 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 novembre 2025 alle ore 12:22 UTCidentified

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

4. 18 novembre 2025 alle ore 12:28 UTCmonitoring

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

5. 18 novembre 2025 alle ore 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 novembre 2025 alle ore 16:19 UTCresolved

   This incident has been resolved.

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

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

3. 4 febbraio 2025 alle ore 19:01 UTCmonitoring

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

4. 4 febbraio 2025 alle ore 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 febbraio 2025 alle ore 19:59 UTCresolved

   This incident has been resolved.

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

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

3. 25 gennaio 2025 alle ore 06:35 UTCmonitoring

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

4. 25 gennaio 2025 alle ore 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 gennaio 2025 alle ore 12:14 UTCresolved

   This incident has been resolved.

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

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

3. 8 dicembre 2024 alle ore 19:20 UTCmonitoring

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

4. 9 dicembre 2024 alle ore 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 dicembre 2024 alle ore 03:39 UTCresolved

   This incident has been resolved.

1. 16 ottobre 2024 alle ore 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 ottobre 2024 alle ore 12:40 UTCidentified

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

3. 16 ottobre 2024 alle ore 13:06 UTCmonitoring

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

4. 16 ottobre 2024 alle ore 13:20 UTCresolved

   This incident has been resolved.

1. 1 ottobre 2024 alle ore 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 agosto 2024 alle ore 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 agosto 2024 alle ore 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 agosto 2024 alle ore 06:10 UTCidentified

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

4. 24 agosto 2024 alle ore 07:08 UTCidentified

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

5. 24 agosto 2024 alle ore 07:43 UTCmonitoring

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

6. 24 agosto 2024 alle ore 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 agosto 2024 alle ore 17:02 UTCresolved

   This incident has been resolved.

1. 21 agosto 2024 alle ore 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 agosto 2024 alle ore 21:59 UTCidentified

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

3. 21 agosto 2024 alle ore 23:20 UTCidentified

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

4. 21 agosto 2024 alle ore 23:49 UTCmonitoring

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

5. 22 agosto 2024 alle ore 00:19 UTCresolved

   This incident has been resolved.

1. 24 luglio 2024 alle ore 16:56 UTCinvestigating

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

2. 24 luglio 2024 alle ore 20:08 UTCidentified

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

3. 25 luglio 2024 alle ore 04:42 UTCidentified

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

4. 25 luglio 2024 alle ore 06:16 UTCmonitoring

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

5. 25 luglio 2024 alle ore 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 luglio 2024 alle ore 13:32 UTCresolved

   This incident has been resolved.

1. 18 ottobre 2023 alle ore 13:21 UTCinvestigating

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

2. 18 ottobre 2023 alle ore 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 ottobre 2023 alle ore 16:51 UTCidentified

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

4. 18 ottobre 2023 alle ore 18:07 UTCmonitoring

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

5. 18 ottobre 2023 alle ore 18:29 UTCresolved

   This incident has been resolved.

1. 10 ottobre 2023 alle ore 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 ottobre 2023 alle ore 12:47 UTCidentified

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

3. 10 ottobre 2023 alle ore 13:43 UTCmonitoring

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

4. 10 ottobre 2023 alle ore 13:54 UTCresolved

   This incident has been resolved.

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

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

3. 23 agosto 2023 alle ore 19:45 UTCmonitoring

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

4. 23 agosto 2023 alle ore 20:40 UTCresolved

   This incident has been resolved.

1. 10 aprile 2023 alle ore 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 marzo 2023 alle ore 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 marzo 2023 alle ore 14:51 UTCidentified

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

3. 3 marzo 2023 alle ore 15:29 UTCmonitoring

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

4. 3 marzo 2023 alle ore 17:34 UTCresolved

   This incident has been resolved.

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

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

3. 14 novembre 2022 alle ore 11:42 UTCmonitoring

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

4. 14 novembre 2022 alle ore 13:05 UTCresolved

   This incident has been resolved.