# Logz.io in February 2019: incidents, uptime and changes

> Logz.io in February 2019: 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/2019/02
Last updated: 2019-03-01T00:00:00Z

- Incidents posted: 5 (major/critical: 0) · Maintenance: 1
- By vendor impact label: minor 5
- Uptime (vendor-reported): 100% free of major/critical incidents, 99.22% free of any incident; outage time 0 min, incident time 5 h 14 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2019](https://rewindex.com/company/logz-io/2019/01.md) · Next: [April 2019](https://rewindex.com/company/logz-io/2019/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 |
| --- | --- | --- | --- | --- | --- |
| [User Interface Degraded Performance](https://rewindex.com/company/logz-io/incidents/j61lhw2nlz12.md) | minor | 2019-02-04 07:10 UTC | 2019-02-04 07:32 UTC | 22 min | resolved |
| [Some customers in the Frankfurt datacenter are receiving inconsistent results from the user-interface](https://rewindex.com/company/logz-io/incidents/jswww837xcrp.md) | minor | 2019-02-04 07:12 UTC | 2019-02-04 07:26 UTC | 14 min | resolved |
| [A subset of customers is experiencing slow ingestion rates](https://rewindex.com/company/logz-io/incidents/sq29hvdcx2rs.md) | minor | 2019-02-19 18:28 UTC | 2019-02-19 19:38 UTC | 1.2 h | resolved |
| [Some users are experiencing issues with our Web UI](https://rewindex.com/company/logz-io/incidents/t5873cbpkh1r.md) | minor | 2019-02-20 14:46 UTC | 2019-02-20 15:03 UTC | 17 min | resolved |
| [Some customers have slow ingestion times](https://rewindex.com/company/logz-io/incidents/493hwdqjm96m.md) | minor | 2019-02-23 13:17 UTC | 2019-02-23 16:42 UTC | 3.4 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] Logz.io Scheduled Maintenance - Feb 16 - All Regions](https://rewindex.com/company/logz-io/incidents/d6g6k9p4g8l2.md) | maintenance | 2019-02-16 14:00 UTC | 2019-02-16 14:09 UTC | 9 min | resolved |

## Cite this

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

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


---
Canonical: https://rewindex.com/company/logz-io/2019/02 · Markdown: https://rewindex.com/company/logz-io/2019/02.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:29:12.269Z