Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): mOLTP PrivateLink connectivity issue
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-11-05 01:36 UTC
Public — what happened
Summary
Elastic Cloud (Public) reported a major incident beginning at 12:08 UTC on 2026-11-04, in which private link traffic on AWS and Azure sent to the Serverless intake-v2 endpoint (.apm) was not being accepted. The company said traffic that did not use private link continued to flow normally. Elastic said it was working on a solution, and the incident was marked resolved at 01:36 on 2026-11-05. No cause was given in the text provided.
Timeline
- Started — 2026-11-04 12:08 UTC
- Investigating — 2026-11-04 12:08 UTC
- Resolved — 2026-11-05 01:36 UTC · 13h 28m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Elastic Cloud (Public) report →
More from Elastic Cloud (Public)
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.