Logz incident

AWS ap-northeast-1 - Some customers experiencing log ingestion lag

Resolved after 8 minutes, affecting Logs Ingestion and Logs Ingestion, on January 29, 2026.

monitoring Jan 29, 2026, 01:46 PM UTC

Jan 29, 15:46 IST Resolved - This incident has been resolved. Jan 29, 15:39 IST Identified - The issue has been identified and a fix is being implemented. Jan 29, 15:38 IST Investigating - We are currently investigating this issue.

Started
Jan 29, 2026, 01:38 PM UTC
Resolved
Jan 29, 2026, 01:46 PM UTC
Duration
8m
Detected by Pingoru
Jan 29, 2026, 01:38 PM UTC

Affected components

Logs IngestionLogs Ingestion

Update timeline

  1. investigating Jan 29, 2026, 01:38 PM UTC

    We are currently investigating this issue.

  2. identified Jan 29, 2026, 01:39 PM UTC

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

  3. monitoring Jan 29, 2026, 01:46 PM UTC

    Jan 29, 15:46 IST Resolved - This incident has been resolved. Jan 29, 15:39 IST Identified - The issue has been identified and a fix is being implemented. Jan 29, 15:38 IST Investigating - We are currently investigating this issue.

  4. resolved Jan 29, 2026, 01:46 PM UTC

    This incident has been resolved.

Your product runs on more than Logz

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →