Changes / Logz.io / Data Ingestions Delays for Specific Regions

Logz.io: Major incident: Data Ingestions Delays for Specific Regions

Summary

Logz.io reported major log-delivery delays affecting some customers in AWS Canada (ca-central-1) and AWS London (eu-west-2). The incident started at 2026-02-18 18:59 UTC and was resolved at 2026-02-18 20:50 UTC, lasting 1 h 50 min; a fix was implemented at 02-18 20:22 UTC.

Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Data Ingestions Delays for Specific Regions
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-02-18 18:59 UTC
AddedResolved time#5
Before: not present
After: 2026-02-18 20:50 UTC
AddedAffected components#6
Before: not present
After: AWS Canada (ca-central-1) - Logs Ingestion, AWS London (eu-west-2) - Log Ingestion, Log Ingestion, Logs Ingestion
AddedUpdateinvestigating#7
Before: not present
After: Some customers have experienced delays in log delivery.
AddedUpdateidentified#8
Before: not present
After: The issue has been identified and a fix is being implemented.
AddedUpdateidentified#9
Before: not present
After: We are continuing to work on a fix for this issue.
AddedUpdatemonitoring#10
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#11
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Data Ingestions Delays for Specific Regions (this change)
Logz.io reported major log-delivery delays affecting some customers in AWS Canada (ca-central-1) and AWS London (eu-west-2). The incident started at 2026-02-18 18:59 UTC and was resolved at 2026-02-18 20:50 UTC, lasting 1 h 50 min; a fix was implemented at 02-18 20:22 UTC.
Major incident

All Logz.io changes → · Logz.io profile · Markdown · JSON