Logz incident

Data Ingestions Delays for Specific Regions

Major Resolved View vendor source →

Logz experienced a major incident on February 18, 2026 affecting Logs Ingestion and Log Ingestion and 1 more component, lasting 1h 50m. The incident has been resolved; the full update timeline is below.

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

    This incident has been resolved.