Live / Elastic Cloud (Public) / Incident
Elastic Cloud (Public): Elastic Cloud scaling issues in Azure
Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-10-21 03:05 UTC
Public — what happened
Summary
Elastic Cloud (Public) said that customers running Elastic Cloud Hosted deployments and Serverless projects on Azure had trouble scaling them up or down, and that creating new ones in Azure could be slow. The company began investigating at 20:07 UTC on October 20, and by 21:24 UTC it said it had identified the issue and engineers were working on a fix. At 22:27 UTC it reported the problem was mitigated and that it was monitoring to confirm things stayed normal, and the incident was marked resolved at 03:05 UTC on October 21.
Timeline
- Started — 2026-10-20 20:07 UTC
- Investigating — 2026-10-20 20:07 UTC
- Identified — 2026-10-20 21:24 UTC
- Monitoring — 2026-10-20 22:27 UTC
- Resolved — 2026-10-21 03:05 UTC · 6h 57m 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 44, 2026, our weekly internet health report.