# Elastic Cloud in May 2018: incidents, uptime and changes

> Elastic Cloud in May 2018: 10 incidents on its status page (1 major or critical), 99.45% 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/2018/05
Last updated: 2018-06-01T23:29:00Z

- Incidents posted: 10 (major/critical: 1) · Maintenance: 4
- By vendor impact label: major 1, minor 3, none 6
- Uptime (vendor-reported): 99.45% free of major/critical incidents, 98.26% free of any incident; outage time 4 h 3 min, incident time 12 h 54 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [April 2018](https://rewindex.com/company/elastic-cloud/2018/04.md) · Next: [June 2018](https://rewindex.com/company/elastic-cloud/2018/06.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 |
| --- | --- | --- | --- | --- | --- |
| [Proxy disruption due to failover of coordination layer](https://rewindex.com/company/elastic-cloud/incidents/fmzsbfrr06g1.md) | major | 2018-05-03 23:59 UTC | 2018-05-04 04:02 UTC | 4.0 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Proxy disruption due to failover of coordination layer](https://rewindex.com/company/elastic-cloud/incidents/fmzsbfrr06g1.md) | major | 2018-05-03 23:59 UTC | 2018-05-04 04:02 UTC | 4.0 h | resolved |
| [\[Scheduled\] \[Scheduled\] AWS SA East Logging and Metrics Infrastructure](https://rewindex.com/company/elastic-cloud/incidents/42pspf9v3tlm.md) | none | 2018-05-21 13:00 UTC | 2018-05-23 11:40 UTC | 47 h | resolved |
| [\[Scheduled\] AWS Ireland Logging and Metrics Infrastructure](https://rewindex.com/company/elastic-cloud/incidents/rlyv2f8xr93r.md) | none | 2018-05-23 16:00 UTC | 2018-05-24 18:36 UTC | 27 h | resolved |
| [\[Scheduled\] User Console & API Maintenance Outage](https://rewindex.com/company/elastic-cloud/incidents/3346h6rg916y.md) | none | 2018-05-24 05:00 UTC | 2018-05-24 06:39 UTC | 1.6 h | resolved |
| [\[Scheduled\] User Console CDN Modifications](https://rewindex.com/company/elastic-cloud/incidents/6ly1kz35x8vh.md) | none | 2018-05-25 02:00 UTC | 2018-05-25 04:00 UTC | 2.0 h | resolved |
| [“We’re investigating delayed email delivery for certain customer requests”](https://rewindex.com/company/elastic-cloud/incidents/4fwgbjttvzbp.md) | none | 2018-05-29 15:15 UTC | 2018-05-30 14:12 UTC | 23 h | resolved |
| [“We are looking into increased response times on the platform user console”](https://rewindex.com/company/elastic-cloud/incidents/g1w36jk92qrw.md) | none | 2018-05-29 20:45 UTC | 2018-05-30 14:12 UTC | 17 h | resolved |
| [Cluster logs are not accessible](https://rewindex.com/company/elastic-cloud/incidents/knfz47g3pq1q.md) | minor | 2018-05-31 15:09 UTC | 2018-06-01 23:29 UTC | 32 h | resolved |
| [Cluster metrics in eu-west-1 may be delayed or missing](https://rewindex.com/company/elastic-cloud/incidents/1j01mvj74dg7.md) | minor | 2018-05-31 16:08 UTC | 2018-06-01 01:41 UTC | 9.6 h | resolved |
| [AWS N. Virginia Intermittent Outage](https://rewindex.com/company/elastic-cloud/incidents/7m04qgwct29r.md) | minor | 2018-05-31 23:52 UTC | 2018-06-01 01:42 UTC | 1.8 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] AWS Sao Paulo Proxy replacement](https://rewindex.com/company/elastic-cloud/incidents/f3y6wqvy7jm9.md) | maintenance | 2018-05-02 00:45 UTC | 2018-05-02 04:37 UTC | 3.9 h | resolved |
| [\[Scheduled\] AWS Singapore Proxy replacement](https://rewindex.com/company/elastic-cloud/incidents/c76bhzdwrwc6.md) | maintenance | 2018-05-07 00:31 UTC | 2018-05-07 04:30 UTC | 4.0 h | resolved |
| [\[Scheduled\] AWS Tokyo Proxy replacement](https://rewindex.com/company/elastic-cloud/incidents/wnkzj0rxrtyx.md) | maintenance | 2018-05-08 00:30 UTC | 2018-05-08 04:30 UTC | 4.0 h | resolved |
| [\[Scheduled\] AWS California Proxy replacement](https://rewindex.com/company/elastic-cloud/incidents/y7pyw5tj2461.md) | maintenance | 2018-05-09 03:00 UTC | 2018-05-09 07:01 UTC | 4.0 h | resolved |

## Cite this

Elastic Cloud posted 10 status incidents in May 2018 (1 major or critical); 0 price changes and 0 notable page changes observed.

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


---
Canonical: https://rewindex.com/company/elastic-cloud/2018/05 · Markdown: https://rewindex.com/company/elastic-cloud/2018/05.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:50:23.587Z