Istoricul incidentelor Loggly

1. 6 octombrie 2026 la 12:16 UTCinvestigating

   Investigăm în prezent o problemă care afectează ingestie jurnal pentru un subset de clienți. Clienţii care utilizează anumite criterii de evaluare a ingestiei pot prezenta o prelucrare întârziată sau ingerare eşuată a noilor date din jurnal. Serviciile care nu utilizează calea de ingerare afectată rămân operaționale. Vom furniza o actualizare într-o oră.

2. 6 octombrie 2026 la 13:19 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 6 octombrie 2026 la 13:42 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

4. 6 octombrie 2026 la 15:42 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

5. 6 octombrie 2026 la 16:04 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 4 septembrie 2026 la 20:37 UTCresolved

   Impactul asupra clienților Un număr mic de clienți s-au confruntat cu ingestie întârziată de date și alerte care nu au fost prelucrate în timp real. Nu s-au pierdut date despre clienţi. Actualizare incident La 3 septembrie 2026, la ora 10:52 PM UTC, o componentă de infrastructură a devenit indisponibilă, ceea ce a dus la un backlog de procesare și întârzieri în manipularea alertelor. O problemă separată de grup de alertă a întârziat notificarea către echipa de gardă, prelungind timpul până la răspuns. În plus, o problemă cu mesajele noastre în aplicație ne-a împiedicat să furnizăm notificări ale clienților în timp util în cadrul aplicației. Incidentul a fost rezolvat complet după 18 ore şi 49 de minute. Prelucrarea datelor și manipularea alertelor au revenit la normal și nu s-au pierdut datele clienților. Ne revizuim comportamentul de grupare a alertelor, procedurile de recuperare a serviciilor și mecanismele de notificare a clienților pentru a reduce probabilitatea și impactul unor incidente similare în viitor.

Traducere automată din actualizarea oficială a incidentului.

1. 7 august 2026 la 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 mai 2026 la 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 mai 2026 la 22:21 UTCresolved

   This incident has been resolved.

1. 21 ianuarie 2026 la 15:44 UTCinvestigating

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

2. 21 ianuarie 2026 la 16:18 UTCidentified

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

3. 21 ianuarie 2026 la 16:20 UTCmonitoring

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

4. 21 ianuarie 2026 la 16:27 UTCresolved

   This incident has been resolved.

1. 18 noiembrie 2025 la 12:07 UTCinvestigating

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

2. 18 noiembrie 2025 la 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 noiembrie 2025 la 12:22 UTCidentified

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

4. 18 noiembrie 2025 la 12:28 UTCmonitoring

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

5. 18 noiembrie 2025 la 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 noiembrie 2025 la 16:19 UTCresolved

   This incident has been resolved.

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

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

3. 4 februarie 2025 la 19:01 UTCmonitoring

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

4. 4 februarie 2025 la 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 februarie 2025 la 19:59 UTCresolved

   This incident has been resolved.

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

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

3. 25 ianuarie 2025 la 06:35 UTCmonitoring

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

4. 25 ianuarie 2025 la 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 ianuarie 2025 la 12:14 UTCresolved

   This incident has been resolved.

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

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

3. 8 decembrie 2024 la 19:20 UTCmonitoring

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

4. 9 decembrie 2024 la 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 decembrie 2024 la 03:39 UTCresolved

   This incident has been resolved.

1. 16 octombrie 2024 la 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 octombrie 2024 la 12:40 UTCidentified

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

3. 16 octombrie 2024 la 13:06 UTCmonitoring

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

4. 16 octombrie 2024 la 13:20 UTCresolved

   This incident has been resolved.

1. 1 octombrie 2024 la 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 la 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 la 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 august 2024 la 06:10 UTCidentified

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

4. 24 august 2024 la 07:08 UTCidentified

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

5. 24 august 2024 la 07:43 UTCmonitoring

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

6. 24 august 2024 la 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 august 2024 la 17:02 UTCresolved

   This incident has been resolved.

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

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

3. 21 august 2024 la 23:20 UTCidentified

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

4. 21 august 2024 la 23:49 UTCmonitoring

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

5. 22 august 2024 la 00:19 UTCresolved

   This incident has been resolved.

1. 24 iulie 2024 la 16:56 UTCinvestigating

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

2. 24 iulie 2024 la 20:08 UTCidentified

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

3. 25 iulie 2024 la 04:42 UTCidentified

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

4. 25 iulie 2024 la 06:16 UTCmonitoring

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

5. 25 iulie 2024 la 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 iulie 2024 la 13:32 UTCresolved

   This incident has been resolved.

1. 18 octombrie 2023 la 13:21 UTCinvestigating

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

2. 18 octombrie 2023 la 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 octombrie 2023 la 16:51 UTCidentified

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

4. 18 octombrie 2023 la 18:07 UTCmonitoring

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

5. 18 octombrie 2023 la 18:29 UTCresolved

   This incident has been resolved.

1. 10 octombrie 2023 la 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 octombrie 2023 la 12:47 UTCidentified

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

3. 10 octombrie 2023 la 13:43 UTCmonitoring

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

4. 10 octombrie 2023 la 13:54 UTCresolved

   This incident has been resolved.

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

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

3. 23 august 2023 la 19:45 UTCmonitoring

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

4. 23 august 2023 la 20:40 UTCresolved

   This incident has been resolved.

1. 10 aprilie 2023 la 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 martie 2023 la 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 martie 2023 la 14:51 UTCidentified

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

3. 3 martie 2023 la 15:29 UTCmonitoring

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

4. 3 martie 2023 la 17:34 UTCresolved

   This incident has been resolved.

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

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

3. 14 noiembrie 2022 la 11:42 UTCmonitoring

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

4. 14 noiembrie 2022 la 13:05 UTCresolved

   This incident has been resolved.