Elastic favicon

Elastic Cloud outage on 2026-11-04

elastic.co
November 2026 4 Major incident

Elastic Cloud had a PrivateLink connectivity issue on 2026-11-04 that lasted 13h 32m. If your product sent APM data over AWS or Azure PrivateLink to the Serverless intake-v2 endpoint, that traffic was rejected for the whole window, and the fault sat on Elastic's side.

Started

12:08 UTC

Duration

Lasted 13h 32m

Source

IsDown

Next time

Elastic is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Elastic's status page opened this incident at 12:08 UTC, naming it the "mOLTP PrivateLink connectivity issue". The posted text said all private link traffic for AWS and Azure going to the Serverless intake-v2 endpoint, the `.apm` one, was not being accepted. It also noted that non-private-link traffic was flowing normally, so the problem was scoped to one transport path rather than the whole service. Elastic said they were working on a solution and would update the page once service was restored. No further progress updates were filed between the opening note and the resolution. The next entry on record is the resolved line at 01:36 UTC the following day, with no explanation of what the fix was. That gives a duration of 13h 32m for a single incident, with no breakdown of how the time split between diagnosis and remediation. Elastic's status page lists no affected components for this entry, which is consistent with the narrow scope described in the text rather than a sign the page is incomplete. No user reports were filed during the window on this record. Elastic's own history shows 22 incidents in the last 90 days with a median duration of 5 hours 55 minutes, so this one ran well past their typical resolution time. No post-mortem has been published, and the cause is not on the record.

Learning

This incident only affected traffic sent over AWS or Azure PrivateLink to one Serverless APM intake endpoint, while normal traffic kept flowing, so a standard uptime check hitting the public endpoint would have reported no problem throughout. UptimeRobot's own 30-day figures for Elastic Cloud show 8 incidents with 7 resolved and a median duration of 8h 14m, which tells you this kind of partial, path-specific failure is not unusual for this provider. If your monitoring only watches your application's own endpoints, it will show green exactly like this because your code isn't what failed, the private network path into Elastic was. That's the gap worth recognising: a dependency can be down for over half a day in a way that never shows up as an error in your own logs if the failure is isolated to a specific ingress route you don't poll directly. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.