Histórico de interrupções do Loggly

1. 6 Here 2026 da 12:16 UTCinvestigating

   Estamos atualmente investigando um problema que afeta a ingestão de log para um subconjunto de clientes. Os clientes que utilizam determinados parâmetros de avaliação da ingestão podem sofrer um tratamento tardio ou uma ingestão falhada de novos dados de registo. Os serviços que não utilizam o caminho de ingestão afetado permanecem operacionais. Nós forneceremos uma atualização dentro de uma hora.

2. 6 Here 2026 da 13:19 UTCinvestigating

   Continuamos a investigar esta questão.

3. 6 Here 2026 da 13:42 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

4. 6 Here 2026 da 15:42 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

5. 6 Here 2026 da 16:04 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Gwengolo 2026 da 20:37 UTCresolved

   Impacto do Cliente Um pequeno número de clientes experimentou demora na ingestão de dados e alertas que não foram processados em tempo real. Nenhum dado do cliente foi perdido. Actualização de Incidentes Em 3 de setembro de 2026, às 10:52 PM UTC, um componente de infraestrutura ficou indisponível, resultando em um atraso de processamento e atrasos no tratamento de alerta. Uma questão separada de agrupamento de alertas atrasou a notificação à equipe de plantão, estendendo o tempo para resposta. Além disso, um problema com nossas mensagens no aplicativo nos impediu de fornecer notificações oportunas de clientes dentro do aplicativo. O incidente foi totalmente resolvido após 18 horas e 49 minutos. O processamento de dados e o tratamento de alerta voltaram ao normal, e nenhum dado do cliente foi perdido. Estamos revisando nosso comportamento de agrupamento de alerta, procedimentos de recuperação de serviços e mecanismos de notificação ao cliente para reduzir a probabilidade e o impacto de incidentes semelhantes no futuro.

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Eost 2026 da 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 Mae 2026 da 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 Mae 2026 da 22:21 UTCresolved

   This incident has been resolved.

1. 21 Genver 2026 da 15:44 UTCinvestigating

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

2. 21 Genver 2026 da 16:18 UTCidentified

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

3. 21 Genver 2026 da 16:20 UTCmonitoring

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

4. 21 Genver 2026 da 16:27 UTCresolved

   This incident has been resolved.

1. 18 Du 2025 da 12:07 UTCinvestigating

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

2. 18 Du 2025 da 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 Du 2025 da 12:22 UTCidentified

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

4. 18 Du 2025 da 12:28 UTCmonitoring

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

5. 18 Du 2025 da 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 Du 2025 da 16:19 UTCresolved

   This incident has been resolved.

1. 4 Cʼhwevrer 2025 da 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 Cʼhwevrer 2025 da 18:05 UTCidentified

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

3. 4 Cʼhwevrer 2025 da 19:01 UTCmonitoring

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

4. 4 Cʼhwevrer 2025 da 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 Cʼhwevrer 2025 da 19:59 UTCresolved

   This incident has been resolved.

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

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

3. 25 Genver 2025 da 06:35 UTCmonitoring

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

4. 25 Genver 2025 da 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 Genver 2025 da 12:14 UTCresolved

   This incident has been resolved.

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

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

3. 8 Kerzu 2024 da 19:20 UTCmonitoring

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

4. 9 Kerzu 2024 da 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 Kerzu 2024 da 03:39 UTCresolved

   This incident has been resolved.

1. 16 Here 2024 da 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 Here 2024 da 12:40 UTCidentified

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

3. 16 Here 2024 da 13:06 UTCmonitoring

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

4. 16 Here 2024 da 13:20 UTCresolved

   This incident has been resolved.

1. 1 Here 2024 da 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 Eost 2024 da 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 Eost 2024 da 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 Eost 2024 da 06:10 UTCidentified

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

4. 24 Eost 2024 da 07:08 UTCidentified

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

5. 24 Eost 2024 da 07:43 UTCmonitoring

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

6. 24 Eost 2024 da 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 Eost 2024 da 17:02 UTCresolved

   This incident has been resolved.

1. 21 Eost 2024 da 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 Eost 2024 da 21:59 UTCidentified

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

3. 21 Eost 2024 da 23:20 UTCidentified

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

4. 21 Eost 2024 da 23:49 UTCmonitoring

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

5. 22 Eost 2024 da 00:19 UTCresolved

   This incident has been resolved.

1. 24 Gouere 2024 da 16:56 UTCinvestigating

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

2. 24 Gouere 2024 da 20:08 UTCidentified

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

3. 25 Gouere 2024 da 04:42 UTCidentified

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

4. 25 Gouere 2024 da 06:16 UTCmonitoring

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

5. 25 Gouere 2024 da 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 Gouere 2024 da 13:32 UTCresolved

   This incident has been resolved.

1. 18 Here 2023 da 13:21 UTCinvestigating

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

2. 18 Here 2023 da 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 Here 2023 da 16:51 UTCidentified

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

4. 18 Here 2023 da 18:07 UTCmonitoring

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

5. 18 Here 2023 da 18:29 UTCresolved

   This incident has been resolved.

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

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

3. 10 Here 2023 da 13:43 UTCmonitoring

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

4. 10 Here 2023 da 13:54 UTCresolved

   This incident has been resolved.

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

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

3. 23 Eost 2023 da 19:45 UTCmonitoring

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

4. 23 Eost 2023 da 20:40 UTCresolved

   This incident has been resolved.

1. 10 Ebrel 2023 da 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 Meurzh 2023 da 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 Meurzh 2023 da 14:51 UTCidentified

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

3. 3 Meurzh 2023 da 15:29 UTCmonitoring

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

4. 3 Meurzh 2023 da 17:34 UTCresolved

   This incident has been resolved.

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

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

3. 14 Du 2022 da 11:42 UTCmonitoring

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

4. 14 Du 2022 da 13:05 UTCresolved

   This incident has been resolved.