rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: no transport client connectivity in AWS ap-southeast-2

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

Timeline of updates

  1. resolved

    The incident was remediated.

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-06-05 13:47 UTC, resolved after 1.0 h, 1 update(s).

Title
no transport client connectivity in AWS ap-southeast-2
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/company/elastic-cloud/incidents/w3gl3zs6pvwr

Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on June 5, 2020Elastic Cloud in June 2020MarkdownJSON