Logz incident

Data Ingestions Delays for Specific Regions

Resolved after 1 hour 50 minutes, affecting Logs Ingestion and Log Ingestion and 1 more, on February 18, 2026.

monitoring Feb 18, 2026, 08:50 PM UTC

Feb 18, 22:50 IST Resolved - This incident has been resolved. Feb 18, 22:22 IST Monitoring - A fix has been implemented and we are monitoring the results. Feb 18, 22:06 IST Update - We are continuing to work on a fix for this issue. Feb 18, 21:32 IST Identified - The issue has been identified and a fix is being implemented. Feb 18, 20:59 IST Investigating - Some customers have experienced delays in log delivery.

Started
Feb 18, 2026, 06:59 PM UTC
Resolved
Feb 18, 2026, 08:50 PM UTC
Duration
1h 50m
Detected by Pingoru
Feb 18, 2026, 06:59 PM UTC

Affected components

Logs IngestionLog IngestionLogs Ingestion

Update timeline

  1. investigating Feb 18, 2026, 06:59 PM UTC

    Some customers have experienced delays in log delivery.

  2. identified Feb 18, 2026, 07:32 PM UTC

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

  3. identified Feb 18, 2026, 08:06 PM UTC

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

  4. monitoring Feb 18, 2026, 08:22 PM UTC

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

  5. monitoring Feb 18, 2026, 08:50 PM UTC

    Feb 18, 22:50 IST Resolved - This incident has been resolved. Feb 18, 22:22 IST Monitoring - A fix has been implemented and we are monitoring the results. Feb 18, 22:06 IST Update - We are continuing to work on a fix for this issue. Feb 18, 21:32 IST Identified - The issue has been identified and a fix is being implemented. Feb 18, 20:59 IST Investigating - Some customers have experienced delays in log delivery.

  6. resolved Feb 18, 2026, 08:50 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 →