# Logz.io in March 2026: incidents, uptime and changes

> Logz.io in March 2026: 5 incidents on its status page (0 major or critical), 100% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Logz.io’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/logz-io/2026/03
Last updated: 2026-04-01T00:00:00Z

- Incidents posted: 5 (major/critical: 0) · Maintenance: 0
- By vendor impact label: minor 4, none 1
- Uptime (vendor-reported): 100% free of major/critical incidents, 99.16% free of any incident; outage time 0 min, incident time 6 h 12 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [February 2026](https://rewindex.com/company/logz-io/2026/02.md) · Next: [April 2026](https://rewindex.com/company/logz-io/2026/04.md) · [All months](https://rewindex.com/company/logz-io/reports.md) · [Logz.io](https://rewindex.com/company/logz-io.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Some Accounts in AWS US-East Region are Experiencing Alert Delay](https://rewindex.com/company/logz-io/incidents/2ll7jccxcr2z.md) | minor | 2026-03-03 16:02 UTC | 2026-03-03 18:47 UTC | 2.8 h | resolved |
| [Some Customers Experiencing Metrics Latency on us-east-1](https://rewindex.com/company/logz-io/incidents/999y1125wrqm.md) | minor | 2026-03-03 16:16 UTC | 2026-03-03 20:35 UTC | 4.3 h | resolved |
| [US-East - Delayed Alerting for Some Customers](https://rewindex.com/company/logz-io/incidents/089k0jj95mx0.md) | minor | 2026-03-10 19:34 UTC | 2026-03-10 20:03 UTC | 29 min | resolved |
| [Degraded Log Ingestion](https://rewindex.com/company/logz-io/incidents/06x5c0yvzsyv.md) | none | 2026-03-27 07:58 UTC | 2026-03-27 08:57 UTC | 59 min | resolved |
| [Some Customers Experiencing Lag for Rolled Up Metrics: eu-central-1](https://rewindex.com/company/logz-io/incidents/266h6l4tx3bx.md) | minor | 2026-03-30 13:21 UTC | 2026-03-30 14:30 UTC | 1.1 h | resolved |

## Cite this

Logz.io posted 5 status incidents in March 2026 (0 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/logz-io/2026/03
- Citation: Logz.io, “Logz.io in March 2026” (2026-03-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/logz-io/2026/03 (CC BY 4.0).
- Markdown link: `[Logz.io: Logz.io in March 2026 (2026-03-01)](https://rewindex.com/company/logz-io/2026/03)`


---
Canonical: https://rewindex.com/company/logz-io/2026/03 · Markdown: https://rewindex.com/company/logz-io/2026/03.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:57:27.967Z