История сбоев Loggly

1. 6 октября 2026 г. в 12:16 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую проглатывание журнала для подмножества клиентов. Клиенты, использующие определенные конечные точки приема, могут испытывать задержку в обработке или неудавшийся прием новых данных журнала. Услуги, не использующие затронутый путь приема, остаются работоспособными. Мы предоставим обновление в течение часа.

2. 6 октября 2026 г. в 13:19 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 6 октября 2026 г. в 13:42 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

4. 6 октября 2026 г. в 15:42 UTCidentified

   Мы продолжаем работать над решением этой проблемы.

5. 6 октября 2026 г. в 16:04 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 4 сентября 2026 г. в 20:37 UTCresolved

   Влияние клиента Небольшое количество клиентов испытывали задержку приема данных и оповещения, которые не обрабатывались в режиме реального времени. Данные клиентов не были потеряны. Обновление инцидента 3 сентября 2026 года в 10:52 вечера UTC инфраструктурный компонент стал недоступен, что привело к отставанию в обработке и задержкам в обработке оповещения. Отдельная проблема с группировкой оповещений задержала уведомление команды по вызову, увеличив время до ответа. Кроме того, проблема с обменом сообщениями в приложении помешала нам предоставлять своевременные уведомления клиентов в приложении. Инцидент был полностью урегулирован через 18 часов и 49 минут. Обработка данных и обработка предупреждений вернулись к норме, и данные клиентов не были потеряны. Мы пересматриваем наше поведение по группировке предупреждений, процедуры восстановления обслуживания и механизмы уведомления клиентов, чтобы уменьшить вероятность и влияние подобных инцидентов в будущем.

Автоматический перевод официального обновления инцидента.

1. 7 августа 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 22:21 UTCresolved

   This incident has been resolved.

1. 21 января 2026 г. в 15:44 UTCinvestigating

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

2. 21 января 2026 г. в 16:18 UTCidentified

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

3. 21 января 2026 г. в 16:20 UTCmonitoring

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

4. 21 января 2026 г. в 16:27 UTCresolved

   This incident has been resolved.

1. 18 ноября 2025 г. в 12:07 UTCinvestigating

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

2. 18 ноября 2025 г. в 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 18 ноября 2025 г. в 12:22 UTCidentified

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

4. 18 ноября 2025 г. в 12:28 UTCmonitoring

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

5. 18 ноября 2025 г. в 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 18 ноября 2025 г. в 16:19 UTCresolved

   This incident has been resolved.

1. 4 февраля 2025 г. в 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 февраля 2025 г. в 18:05 UTCidentified

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

3. 4 февраля 2025 г. в 19:01 UTCmonitoring

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

4. 4 февраля 2025 г. в 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 февраля 2025 г. в 19:59 UTCresolved

   This incident has been resolved.

1. 25 января 2025 г. в 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 января 2025 г. в 06:01 UTCidentified

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

3. 25 января 2025 г. в 06:35 UTCmonitoring

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

4. 25 января 2025 г. в 09:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 января 2025 г. в 12:14 UTCresolved

   This incident has been resolved.

1. 8 декабря 2024 г. в 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 декабря 2024 г. в 16:30 UTCidentified

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

3. 8 декабря 2024 г. в 19:20 UTCmonitoring

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

4. 9 декабря 2024 г. в 03:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 декабря 2024 г. в 03:39 UTCresolved

   This incident has been resolved.

1. 16 октября 2024 г. в 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 16 октября 2024 г. в 12:40 UTCidentified

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

3. 16 октября 2024 г. в 13:06 UTCmonitoring

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

4. 16 октября 2024 г. в 13:20 UTCresolved

   This incident has been resolved.

1. 1 октября 2024 г. в 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 августа 2024 г. в 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 августа 2024 г. в 05:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 24 августа 2024 г. в 06:10 UTCidentified

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

4. 24 августа 2024 г. в 07:08 UTCidentified

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

5. 24 августа 2024 г. в 07:43 UTCmonitoring

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

6. 24 августа 2024 г. в 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 24 августа 2024 г. в 17:02 UTCresolved

   This incident has been resolved.

1. 21 августа 2024 г. в 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 августа 2024 г. в 21:59 UTCidentified

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

3. 21 августа 2024 г. в 23:20 UTCidentified

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

4. 21 августа 2024 г. в 23:49 UTCmonitoring

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

5. 22 августа 2024 г. в 00:19 UTCresolved

   This incident has been resolved.

1. 24 июля 2024 г. в 16:56 UTCinvestigating

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

2. 24 июля 2024 г. в 20:08 UTCidentified

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

3. 25 июля 2024 г. в 04:42 UTCidentified

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

4. 25 июля 2024 г. в 06:16 UTCmonitoring

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

5. 25 июля 2024 г. в 08:50 UTCmonitoring

   We are continuing to monitor.

6. 25 июля 2024 г. в 13:32 UTCresolved

   This incident has been resolved.

1. 18 октября 2023 г. в 13:21 UTCinvestigating

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

2. 18 октября 2023 г. в 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 октября 2023 г. в 16:51 UTCidentified

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

4. 18 октября 2023 г. в 18:07 UTCmonitoring

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

5. 18 октября 2023 г. в 18:29 UTCresolved

   This incident has been resolved.

1. 10 октября 2023 г. в 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 октября 2023 г. в 12:47 UTCidentified

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

3. 10 октября 2023 г. в 13:43 UTCmonitoring

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

4. 10 октября 2023 г. в 13:54 UTCresolved

   This incident has been resolved.

1. 23 августа 2023 г. в 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 августа 2023 г. в 19:21 UTCidentified

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

3. 23 августа 2023 г. в 19:45 UTCmonitoring

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

4. 23 августа 2023 г. в 20:40 UTCresolved

   This incident has been resolved.

1. 10 апреля 2023 г. в 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 марта 2023 г. в 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 марта 2023 г. в 14:51 UTCidentified

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

3. 3 марта 2023 г. в 15:29 UTCmonitoring

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

4. 3 марта 2023 г. в 17:34 UTCresolved

   This incident has been resolved.

1. 14 ноября 2022 г. в 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 ноября 2022 г. в 11:25 UTCidentified

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

3. 14 ноября 2022 г. в 11:42 UTCmonitoring

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

4. 14 ноября 2022 г. в 13:05 UTCresolved

   This incident has been resolved.