logz.io Outage History

36 incidents recorded over the last 365 days, 35 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live logz.io status100.00% uptime history

Every Recorded logz.io Incident

logz.io incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Data Ingestions Delays For Some Customers - Degraded Performance - us-east-1This incident has been resolved.1h 0mResolved
Sep 9, 2026EU-Central-1: Some Customers Experiencing LagThis incident has been resolved.1h 2mResolved
Aug 25, 2026US-East-1: Some customers are experiencing ingestion issuesThis incident has been resolved.3h 29mResolved
Aug 21, 2026Canada - Data Ingestions Delays For Some CustomersThis incident has been resolved.56 minResolved
Aug 6, 2026Data Ingestions Delays For Some Customers - Degraded Performance - us-east-1Some customers have experienced delays in log delivery. We have identified the issue and have resolved it.-471 minResolved
Jul 11, 2026SSL Certificate RenewalThe scheduled maintenance has been completed.312h 0mScheduled
Jul 9, 2026US-East - Data Ingestions Delays For Some CustomersThis incident has been resolved.21 minResolved
Jul 8, 2026US-East - Data Ingestions Delays For Some CustomersThis incident has been resolved.1h 45mResolved
Jun 8, 2026Logs Ingestions Delays For Some Accounts - MonitoringThis incident has been resolved.3h 18mResolved
Jun 8, 2026US-EAST-1: Some Customers Experiencing Delayed Metrics IngestionThis incident has been resolved.4h 19mResolved
Jun 4, 2026Log Ingestions Delays In us-east-1 For Some AccountsThe data ingestion outage that affected some of our customers is resolved. All systems are operational.0 minResolved
May 13, 2026Some Customers on the EU Central Region are Experiencing Log Shipping IssuesWe are currently investigating this issue.-4596 minResolved
May 8, 2026US-East - Data Ingestions Delays Due to AWS outage for Some Customers - Degraded PerformanceThis incident has been resolved.7h 9mResolved
May 6, 2026OrionIQ Invocations Failures For Some CustomersThis incident has been resolved.1h 9mResolved
Apr 29, 2026US-East - Delayed Alerting for Some CustomersThis incident has been resolved.2h 51mResolved
Apr 10, 2026US-EAST: Delayed indexing in opensearch for some customersThis incident has been resolved.1h 14mResolved
Mar 30, 2026Some Customers Experiencing Lag for Rolled Up Metrics: eu-central-1This incident has been resolved.1h 9mResolved
Mar 27, 2026Degraded Log IngestionThis incident has been resolved.58 minResolved
Mar 10, 2026US-East - Delayed Alerting for Some CustomersThis incident has been resolved.28 minResolved
Mar 3, 2026Some Customers Experiencing Metrics Latency on us-east-1This incident has been resolved.4h 19mResolved
Mar 3, 2026Some Accounts in AWS US-East Region are Experiencing Alert DelayThis incident has been resolved.2h 45mResolved
Feb 26, 2026A few customers in US-East-1 are experiencing delays with log ingestionThis incident has been resolved.35 minResolved
Feb 23, 2026AWS eu-central-1 - Metrics - OutageThis incident has been resolved.21 minResolved
Feb 18, 2026Data Ingestions Delays for Specific RegionsThis incident has been resolved.1h 50mResolved
Jan 29, 2026AWS ap-northeast-1 - Some customers experiencing log ingestion lagThis incident has been resolved.8 minResolved
Jan 22, 2026Data Ingestions Delays For Some Customers - Degraded Performance - eu-centralThis incident has been resolved.3h 13mResolved
Jan 5, 2026Some Customers Experiencing Degraded Performance for MetricsThis incident has been resolved.4h 53mResolved
Dec 18, 2025Data Ingestions Delays For Some Customers - Degraded Performance - eu-centralThis incident has been resolved.38 minResolved
Dec 18, 2025Data Ingestions Delays For Some Customers - Degraded Performance - eu-centralWe have detected an issue that may affect some of our customers, and we are working to identify the cause and take the appropriate steps to remediate it.-90 minResolved
Dec 13, 2025Data Ingestions Delays For TRIAL Customers - Degraded Performance - Identified - us-east-1This incident has been resolved.34 minResolved
Dec 9, 2025Data Ingestions Delays - For Few Customers in en-central-1 - Degraded Performance - MonitoringThis incident has been resolved.1h 35mResolved
Dec 4, 2025Some Customers In us-east-1 Are Experiencing Data Ingestions Delays - Degraded Performance - IdentifiedThis incident has been resolved.39 minResolved
Dec 2, 2025Data Ingestions Delays for Some Customers in the US East RegionThis incident has been resolved.1h 16mResolved
Nov 25, 2025Data Ingestions Delays For Some Customers In eu-west-2This incident has been resolved.21 minResolved
Nov 18, 2025A few customers in US-East-1 are experiencing delays with logs ingestionThis incident has been resolved.22 minResolved
Nov 14, 2025A few customers in US-East-1 are experiencing delays with logs and metrics ingestionThis incident has been resolved.1h 25mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next logz.io incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This logz.io Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before logz.io acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single logz.io outage in this window ran 13d, against a mean recovery of 11h 9m. If you depend on logz.io in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.