CompaniesElastic CloudUptime
Elastic Cloud uptime
From vendor reports 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.
93.85%free of major or critical incidents, last 30 days
67.84%free of major or critical incidents, last 90 days
67.76%free of any incident, last 90 days
21incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 8 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 9 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 10 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 11 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 12 (UTC day): 8 h 59 min with a major or critical incident open, 8 h 59 min with any incident openAug 13 (UTC day): 20 h 2 min with a major or critical incident open, 20 h 2 min with any incident open, 2 incidents startedAug 14 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 15 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 16 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 17 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 18 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 19 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 20 (UTC day): 17 h 10 min with a major or critical incident open, 19 h with any incident open, 2 incidents startedAug 21 (UTC day): no vendor-reported incident openAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): 1 h 22 min with a major or critical incident open, 1 h 22 min with any incident open, 1 incident startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): 15 h 44 min with a major or critical incident open, 15 h 44 min with any incident open, 2 incidents startedSep 2 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 3 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 4 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 5 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 6 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 7 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 8 (UTC day): 8 h 16 min with a major or critical incident open, 8 h 16 min with any incident openSep 9 (UTC day): 3 h 15 min with a major or critical incident open, 3 h 15 min with any incident open, 1 incident startedSep 10 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 11 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 12 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 13 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 14 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 15 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 16 (UTC day): 20 h 45 min with a major or critical incident open, 20 h 45 min with any incident open, 1 incident startedSep 17 (UTC day): 41 min with a major or critical incident open, 41 min with any incident open, 1 incident startedSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 1 h 59 min with a major or critical incident open, 1 h 59 min with any incident open, 1 incident startedSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): no vendor-reported incident openSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): 3 h 50 min with a major or critical incident open, 3 h 50 min with any incident open, 1 incident startedOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): 7 h 17 min with a major or critical incident open, 7 h 17 min with any incident open, 1 incident startedOct 9 (UTC day): 54 min with a major or critical incident open, 54 min with any incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): no vendor-reported incident openOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): no vendor-reported incident openOct 20 (UTC day): 17 h 9 min with a major or critical incident open, 17 h 9 min with any incident open, 2 incidents startedOct 21 (UTC day): 3 h 5 min with a major or critical incident open, 3 h 5 min with any incident openOct 22 (UTC day): 9 h 31 min with a major or critical incident open, 9 h 31 min with any incident open, 1 incident startedOct 23 (UTC day): 2 h 29 min with a major or critical incident open, 2 h 29 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): no vendor-reported incident openOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): no vendor-reported incident openNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 93.85% | 93.85% | 44 h 15 min | 44 h 15 min | 6 |
| Last 90 days | 67.84% | 67.76% | 28.9 days | 29.0 days | 21 |
This is what Elastic Cloud itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: Elastic Cloud status history · last 90 days · Elastic Cloud status page (opens in new tab) · Markdown