# Elastic Cloud in January 2019: incidents, uptime and changes

> Elastic Cloud in January 2019: 7 incidents on its status page (3 major or critical), 96.88% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Elastic Cloud’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/elastic-cloud/2019/01
Last updated: 2019-02-01T20:31:00Z

- Incidents posted: 7 (major/critical: 3) · Maintenance: 4
- By vendor impact label: critical 1, major 2, minor 1, none 3
- Uptime (vendor-reported): 96.88% free of major/critical incidents, 96.88% free of any incident; outage time 23 h 12 min, incident time 23 h 12 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2018](https://rewindex.com/company/elastic-cloud/2018/12.md) · Next: [February 2019](https://rewindex.com/company/elastic-cloud/2019/02.md) · [All months](https://rewindex.com/company/elastic-cloud/reports.md) · [Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

_Uptime: 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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Cluster connectivity issues in AWS eu-west-1 region](https://rewindex.com/company/elastic-cloud/incidents/01d59btqhy3c.md) | critical | 2019-01-18 10:22 UTC | 2019-01-18 17:56 UTC | 7.6 h | resolved |
| [Unable to create clusters in GCP us-central1](https://rewindex.com/company/elastic-cloud/incidents/dvcqkcwx7mqf.md) | major | 2019-01-07 07:00 UTC | 2019-01-07 14:55 UTC | 7.9 h | resolved |
| [Customers may experience issues provisioning clusters in AWS us-west-2](https://rewindex.com/company/elastic-cloud/incidents/hhghw5rwlhbp.md) | major | 2019-01-17 21:43 UTC | 2019-01-18 05:26 UTC | 7.7 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Unable to create clusters in GCP us-central1](https://rewindex.com/company/elastic-cloud/incidents/dvcqkcwx7mqf.md) | major | 2019-01-07 07:00 UTC | 2019-01-07 14:55 UTC | 7.9 h | resolved |
| ["Customer Console -  Availability Intermittent"](https://rewindex.com/company/elastic-cloud/incidents/cqbbxvj11l7c.md) | none | 2019-01-17 19:12 UTC | 2019-01-17 20:15 UTC | 1.1 h | resolved |
| [Customers may experience issues provisioning clusters in AWS us-west-2](https://rewindex.com/company/elastic-cloud/incidents/hhghw5rwlhbp.md) | major | 2019-01-17 21:43 UTC | 2019-01-18 05:26 UTC | 7.7 h | resolved |
| [Cluster connectivity issues in AWS eu-west-1 region](https://rewindex.com/company/elastic-cloud/incidents/01d59btqhy3c.md) | critical | 2019-01-18 10:22 UTC | 2019-01-18 17:56 UTC | 7.6 h | resolved |
| [Users may experience increased latency on cloud.elastic.co](https://rewindex.com/company/elastic-cloud/incidents/69m8gj6cwtr9.md) | minor | 2019-01-18 16:25 UTC | 2019-01-18 17:52 UTC | 1.4 h | resolved |
| [Potential disruption in eu-west-1](https://rewindex.com/company/elastic-cloud/incidents/x35ktnrj2l92.md) | none | 2019-01-24 14:35 UTC | 2019-01-24 19:53 UTC | 5.3 h | resolved |
| [Possible issues with creating and displaying cluster information from within the customer portal](https://rewindex.com/company/elastic-cloud/incidents/7lgyl0z3g0ph.md) | none | 2019-01-31 14:14 UTC | 2019-01-31 17:00 UTC | 2.8 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] Monitoring Infrastructure Update Maintenance](https://rewindex.com/company/elastic-cloud/incidents/9cp9wcckbgvb.md) | maintenance | 2019-01-16 21:00 UTC | 2019-01-17 00:13 UTC | 3.2 h | resolved |
| [\[Scheduled\] Monitoring Infrastructure Update Maintenance](https://rewindex.com/company/elastic-cloud/incidents/rrpddhbw1p4h.md) | maintenance | 2019-01-23 21:01 UTC | 2019-01-24 00:00 UTC | 3.0 h | resolved |
| [\[Scheduled\] Routine Patching](https://rewindex.com/company/elastic-cloud/incidents/n5dc6j6r5y85.md) | maintenance | 2019-01-25 20:31 UTC | 2019-02-14 18:15 UTC | 20 d | resolved |
| [\[Scheduled\] Monitoring Infrastructure Update Maintenance](https://rewindex.com/company/elastic-cloud/incidents/xpgfdjy7l916.md) | maintenance | 2019-01-31 02:30 UTC | 2019-01-31 05:30 UTC | 3.0 h | resolved |

## Cite this

Elastic Cloud posted 7 status incidents in January 2019 (3 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/elastic-cloud/2019/01
- Citation: Elastic Cloud, “Elastic Cloud in January 2019” (2019-01-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/elastic-cloud/2019/01 (CC BY 4.0).
- Markdown link: `[Elastic Cloud: Elastic Cloud in January 2019 (2019-01-01)](https://rewindex.com/company/elastic-cloud/2019/01)`


---
Canonical: https://rewindex.com/company/elastic-cloud/2019/01 · Markdown: https://rewindex.com/company/elastic-cloud/2019/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T12:52:23.060Z