CompaniesElastic CloudMonthly reportsMay 2017
Elastic Cloud in May 2017: incidents, uptime and changes
5incidents posted
0labelled major or critical
100%free of major/critical
100%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 0 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: No impact listed 5
Incidents 5
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Intermittent console outage | No impact listed | 1.1 h | resolved | 05-01 | |
| Elevated error rates with console | No impact listed | 1.4 h | resolved | 05-02 | |
| Cluster provisioning and cluster changes in US East stalled | No impact listed | 6.2 h | resolved | 05-04 | |
| Connectivity issues with https://cloud.elastic.co | No impact listed | 42 min | resolved | 05-15 | |
| Identified an issue affecting a small percentage of Kibana clusters in us | No impact listed | 55 min | resolved | 05-29 |
Cite this
Elastic Cloud posted 5 status incidents in May 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Elastic Cloud in May 2017
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/2017/05