Loggly の障害履歴

1. 2026年10月6日 12:16 UTCinvestigating

   現在、お客様のサブセットのログ摂取に影響を及ぼす問題について調査しています。 特定の摂取エンドポイントを使用しているお客様は、新しいログデータの処理を遅らせるか、または失敗した摂取が発生することがあります。 影響を受けた摂取経路を利用しないサービスが稼働しています。 時間内にアップデートを行います.

2. 2026年10月6日 13:19 UTCinvestigating

   今後もこの問題について調査を続けてまいります.

3. 2026年10月6日 13:42 UTCidentified

   問題が特定され、修正が実装されています.

4. 2026年10月6日 15:42 UTCidentified

   この問題の修正には引き続き取り組んでいます。

5. 2026年10月6日 16:04 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月4日 20:37 UTCresolved

   顧客の影響 顧客数が少ないため、リアルタイムで処理されていないデータ摂取やアラートが遅延しました。 顧客データが失われない インシデント・アップデート 2026年9月3日(水)10:52 PM UTCにてインフラコンポーネントが利用できなくなったため、バックログ処理とアラート処理の遅延が発生しました。 別のアラートグループの問題は、オンコールチームに通知を遅らせ、応答に時間を延ばします。 また、アプリ内メッセージングの問題は、アプリ内でタイムリーな顧客の通知を提供することを防止しました。 事故は18時間と49分後に解決しました。 データの処理とアラート処理が正常に戻り、顧客データが失われません。 アラートグループ化の行動、サービス回復の手順、および顧客の通知メカニズムを見直し、将来同様の事件の可能性と影響を削減します.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月7日 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. 2026年5月11日 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. 2026年5月11日 22:21 UTCresolved

   This incident has been resolved.

1. 2026年1月21日 15:44 UTCinvestigating

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

2. 2026年1月21日 16:18 UTCidentified

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

3. 2026年1月21日 16:20 UTCmonitoring

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

4. 2026年1月21日 16:27 UTCresolved

   This incident has been resolved.

1. 2025年11月18日 12:07 UTCinvestigating

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

2. 2025年11月18日 12:19 UTCidentified

   We have identified an issue with an outside provider

3. 2025年11月18日 12:22 UTCidentified

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

4. 2025年11月18日 12:28 UTCmonitoring

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

5. 2025年11月18日 14:25 UTCmonitoring

   We are continuing to monitor the issue

6. 2025年11月18日 16:19 UTCresolved

   This incident has been resolved.

1. 2025年2月4日 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. 2025年2月4日 18:05 UTCidentified

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

3. 2025年2月4日 19:01 UTCmonitoring

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

4. 2025年2月4日 19:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025年2月4日 19:59 UTCresolved

   This incident has been resolved.

1. 2025年1月25日 5: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. 2025年1月25日 6:01 UTCidentified

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

3. 2025年1月25日 6:35 UTCmonitoring

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

4. 2025年1月25日 9:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025年1月25日 12:14 UTCresolved

   This incident has been resolved.

1. 2024年12月8日 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. 2024年12月8日 16:30 UTCidentified

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

3. 2024年12月8日 19:20 UTCmonitoring

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

4. 2024年12月9日 3:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2024年12月9日 3:39 UTCresolved

   This incident has been resolved.

1. 2024年10月16日 12:35 UTCinvestigating

   We are currently investigating this issue.

2. 2024年10月16日 12:40 UTCidentified

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

3. 2024年10月16日 13:06 UTCmonitoring

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

4. 2024年10月16日 13:20 UTCresolved

   This incident has been resolved.

1. 2024年10月1日 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. 2024年8月24日 4: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. 2024年8月24日 5:09 UTCinvestigating

   We are continuing to investigate the issue.

3. 2024年8月24日 6:10 UTCidentified

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

4. 2024年8月24日 7:08 UTCidentified

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

5. 2024年8月24日 7:43 UTCmonitoring

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

6. 2024年8月24日 12:49 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 2024年8月24日 17:02 UTCresolved

   This incident has been resolved.

1. 2024年8月21日 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. 2024年8月21日 21:59 UTCidentified

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

3. 2024年8月21日 23:20 UTCidentified

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

4. 2024年8月21日 23:49 UTCmonitoring

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

5. 2024年8月22日 0:19 UTCresolved

   This incident has been resolved.

1. 2024年7月24日 16:56 UTCinvestigating

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

2. 2024年7月24日 20:08 UTCidentified

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

3. 2024年7月25日 4:42 UTCidentified

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

4. 2024年7月25日 6:16 UTCmonitoring

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

5. 2024年7月25日 8:50 UTCmonitoring

   We are continuing to monitor.

6. 2024年7月25日 13:32 UTCresolved

   This incident has been resolved.

1. 2023年10月18日 13:21 UTCinvestigating

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

2. 2023年10月18日 16:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023年10月18日 16:51 UTCidentified

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

4. 2023年10月18日 18:07 UTCmonitoring

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

5. 2023年10月18日 18:29 UTCresolved

   This incident has been resolved.

1. 2023年10月10日 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. 2023年10月10日 12:47 UTCidentified

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

3. 2023年10月10日 13:43 UTCmonitoring

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

4. 2023年10月10日 13:54 UTCresolved

   This incident has been resolved.

1. 2023年8月23日 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. 2023年8月23日 19:21 UTCidentified

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

3. 2023年8月23日 19:45 UTCmonitoring

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

4. 2023年8月23日 20:40 UTCresolved

   This incident has been resolved.

1. 2023年4月10日 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. 2023年3月3日 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. 2023年3月3日 14:51 UTCidentified

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

3. 2023年3月3日 15:29 UTCmonitoring

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

4. 2023年3月3日 17:34 UTCresolved

   This incident has been resolved.

1. 2022年11月14日 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. 2022年11月14日 11:25 UTCidentified

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

3. 2022年11月14日 11:42 UTCmonitoring

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

4. 2022年11月14日 13:05 UTCresolved

   This incident has been resolved.