CompaniesElastic CloudMonthly reportsFebruary 2017
Elastic Cloud in February 2017: incidents, uptime and changes
6incidents posted
2labelled major or critical
99.10%free of major/critical
72.30%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 6 h 1 min, incident time 7.8 days. 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: Major 2 · Minor 4
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Cluster management console unavailable | Major | 3.3 h | resolved | 02-28 | |
| Snapshotting unavailable in us-east-1 | Major | 6.6 h | resolved | 02-28 |
Other incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Kernel issues in us-east-1 | Minor | 46 h | resolved | 02-02 | |
| Memory issues in all regions | Minor | 14 d | resolved | 02-02 | |
| Connectivity issues in eu-west-1 | Minor | 6.2 h | resolved | 02-17 | |
| Connectivity issues in eu-west-1 | Minor | 5.9 h | resolved | 02-18 |
Cite this
Elastic Cloud posted 6 status incidents in February 2017 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Elastic Cloud in February 2017
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/2017/02