For 2 hours and 32 minutes on 23 October 2026, Elastic's own Support Portal was unreachable. Elastic traced the fault to an upstream provider, not to its own systems, and authentication to the portal was affected throughout.
Started
04:04 UTC
Duration
Lasted 2h 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 logged one incident on this day, starting at 04:04 UTC. The first update said customers might have trouble authenticating to the Elastic Support portal, with investigation underway. By 04:59, Elastic had identified the cause as an upstream provider issue, and said that provider had already confirmed a fix and restored access for some affected environments while rolling it out to the rest. At 06:33, Elastic marked the incident resolved, stating the upstream provider had completed its fix and that customers could authenticate to the support portal again. That gives a total outage window of 2 hours and 32 minutes, entirely on the support portal, not on Elastic Cloud's core data or search infrastructure. No components are listed as affected in Elastic's own status breakdown for this incident. No user reports were filed during the window. Elastic's statement puts the root cause outside its own stack, naming an unspecified upstream provider rather than its own code or infrastructure, and that single filing is the only account on record, there's no separate post-mortem. Over the past 90 days, Elastic has logged 22 incidents with a median duration of 5 hours 55 minutes, so this one resolved faster than the recent typical outage. Across all time, Elastic has recorded 393 incidents, an average of 6.1 per month.
Learning
This incident only affected the Support Portal, the place you'd go to open a ticket if something else broke, not the Elastic Cloud clusters serving your search or logging traffic. That distinction matters because a support channel going dark doesn't necessarily mean your data plane is down, and vice versa, checking your own endpoints would tell you nothing about whether you could reach Elastic for help if you needed it. Elastic's own clock shows the gap between first word of trouble and full resolution: identification within under an hour, resolution within two and a half hours of it starting. The underlying cause sat with an unnamed upstream provider, a layer entirely outside Elastic's own application code and outside anything a customer's monitoring could probe directly. Over 30 days, independent monitoring has recorded 8 incidents against Elastic Cloud with a median duration of 8 hours 14 minutes, a different picture from Elastic's own 90-day median of 5 hours 55 minutes, which simply reflects that the two are watching different things from different angles. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.