rewindex

CompaniesElastic CloudMonthly reportsFebruary 2020

Elastic Cloud in February 2020: incidents, uptime and changes

5incidents posted
2labelled major or critical
99.14%free of major/critical
99.05%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 5 h 55 min, incident time 6 h 33 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: Critical 2 · Minor 2 · No impact listed 1

Major and critical incidents 2

IncidentImpactStartedDurationStatusDay
Issues creation of new deployments and accessing Cloud ConsoleCritical1.9 hresolved02-19
APM connectivity issues GCP Oregon and Frankfurt regionsCritical4.0 hresolved02-24

Other incidents 3

IncidentImpactStartedDurationStatusDay
Increased latency in Cloud user consoleNo impact listed41 minresolved02-03
Coordination Layer Maintenance in GCP N. Virginia RegionMinor38 minresolved02-14
Network configuration issues for deployment nodes in AWS.Minor0 minresolved02-18

Maintenance 2

Show scheduled maintenance

Cite this

Elastic Cloud posted 5 status incidents in February 2020 (2 major or critical); 0 price changes and 0 notable page changes observed.

Title
Elastic Cloud in February 2020
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/company/elastic-cloud/2020/02

All Elastic Cloud monthsRecent incidentsMarkdown