rewindex

CompaniesLogz.ioMonthly reportsMarch 2016

Logz.io in March 2016: incidents, uptime and changes

8incidents posted
0labelled major or critical
100%free of major/critical
94.58%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 0 min, incident time 40 h 16 min. 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. Last 90 days.

By vendor label: Minor 7 · No impact listed 1

Incidents 8

IncidentImpactStartedDurationStatusDay
S3 fetching is slower than usualNo impact listed40 minresolved03-04
Log shipping increased error rate in log shippingMinor36 minresolved03-06
S3 fetching is slower than usualMinor1.2 hresolved03-11
Data Processing Delays - Reporting Tools AffectedMinor32 hresolved03-16
Data Processing Delays - Reporting Tools AffectedMinor4.4 hresolved03-20
[Scheduled] Logz.io Scheduled Maintenance - Mar. 27thMinor43 minresolved03-27
Data Ingestions DelaysMinor34 minresolved03-30
Data Ingestions DelaysMinor27 minresolved03-31

Cite this

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

Title
Logz.io in March 2016
Vendor
Logz.io
Date
URL
https://rewindex.com/company/logz-io/2016/03

All Logz.io monthsRecent incidentsMarkdown