# Elastic Cloud: Kibana/APM network connectivity issues in AWS eu-central-1

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2019-06-07 10:47 UTC · Resolved: 2019-06-07 13:03 UTC · Duration: 2.3 h
- Updates: 1
- [Vendor status page: https://status.elastic.co/incidents/vnjnnns534cy](https://status.elastic.co/incidents/vnjnnns534cy)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

## Timeline of updates

- **resolved** 2019-06-07 13:03 UTC: Based on the data gathered over the past hour we can conclude the connectivity between Kibana/APM and Elasticsearch clusters has been successfully restored. Customers should not experience any issues with connectivity to Kibana instances. What happened: The Elastic Cloud Proxy tier is currently at the end of an implementation phase which has introduced a new Cloud Proxy for handling client requests. Part of the implementation phase involved using haproxy to conditionally route traffic between the old and new proxies so that we could introduce the change gradually and with least impact. As part of the work to remove haproxy from this stack a configuration change was made to the AWS eu-central-1 region which resulted in inter-deployment (Kibana -> Elasticsearch; APM -> Elasticsearch) communication issues. This change has now been reverted.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/elastic-cloud/incidents/vnjnnns534cy · Markdown: https://rewindex.com/company/elastic-cloud/incidents/vnjnnns534cy.md · JSON: https://rewindex.com/api/v1/companies/elastic-cloud/incidents/vnjnnns534cy · Generated 2026-10-18T09:38:30.127Z