rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: Increased 502s in some GCP regions.

MinorStatus: resolvedStarted Resolved (2.9 h)1 updatestatus.elastic.co (opens in new tab)

Timeline of updates

  1. resolved

    We discovered that during the proxy deployment that there was a problem with one of the TLS versions being offered in conjunction with the size of bulk requests. While our engineers continue to drill in on specifics, we are going to continue to monitor error rates but at this time we consider the incident resolved. Please reach out to support immediately if you have any issues.

From Elastic Cloud’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.elastic.co (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Elastic Cloud, started 2020-05-07 15:51 UTC, resolved after 2.9 h, 1 update(s).

Title
Increased 502s in some GCP regions.
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/company/elastic-cloud/incidents/4b6njsbtc0xb

Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on May 7, 2020Elastic Cloud in May 2020MarkdownJSON