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

> Logz.io in June 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/06
Last updated: 2019-07-01T00:00:00Z

- Incidents posted: 5 (major/critical: 0) · Maintenance: 0
- By vendor impact label: minor 5
- Uptime (vendor-reported): 100% free of major/critical incidents, 97.51% free of any incident; outage time 0 min, incident time 17 h 54 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [May 2019](https://rewindex.com/company/logz-io/2019/05.md) · Next: [July 2019](https://rewindex.com/company/logz-io/2019/07.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 of our Frankfurt region customers are experiencing elevated search error rates. We are working on resuming regular search service for all of our customers](https://rewindex.com/company/logz-io/incidents/11jnvtst9grv.md) | minor | 2019-06-01 09:45 UTC | 2019-06-01 10:31 UTC | 46 min | resolved |
| [Few customers are experiencing delays in log ingestion.](https://rewindex.com/company/logz-io/incidents/hwjhw4v2mhgv.md) | minor | 2019-06-03 05:47 UTC | 2019-06-03 06:01 UTC | 14 min | resolved |
| [Some customers in the Frankfurt region might experience elevated error rates when searching](https://rewindex.com/company/logz-io/incidents/zdds48mrk201.md) | minor | 2019-06-10 13:08 UTC | 2019-06-10 18:41 UTC | 5.5 h | resolved |
| [Indexing and API degradation for some of the customers in the Frankfurt region](https://rewindex.com/company/logz-io/incidents/mhvsjnb644jr.md) | minor | 2019-06-14 22:02 UTC | 2019-06-15 09:19 UTC | 11 h | resolved |
| [Some customers are getting delays with email alerts in the Frankfurt region. Other notification endpoints are working as they should](https://rewindex.com/company/logz-io/incidents/d3f44jqmqnpw.md) | minor | 2019-06-23 09:47 UTC | 2019-06-23 09:51 UTC | 4 min | resolved |

## Cite this

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

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


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