We started checking Elastic Cloud on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Elastic Cloud reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Elastic Cloud's own status page declared. Below it, any public chatter we saw about Elastic Cloud and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Elastic Cloud's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Elastic Cloud in the last 24 hours, which is not evidence that nothing is wrong.
Elastic Cloud's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Elastic Cloud's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Elastic Cloud next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts2 in the last hour (prior day averaged 0.4/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
583
US-West
99.56%
457
Europe
100.00%
412
Asia-Pacific
99.60%
249
Their declared record
Elastic Cloud's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Nov 4, 2026, 12:08 PM UTC to Nov 5, 2026, 1:36 AM UTC (13h 28m)resolved
their latest update (Nov 5, 2026, 1:36 AM UTC): This issue is now resolved.
Elastic Support Portal is unavailablePartial outage
Oct 23, 2026, 4:04 AM UTC to Oct 23, 2026, 6:33 AM UTC (2h 29m)resolved
their latest update (Oct 23, 2026, 6:33 AM UTC): The upstream provider has completed its fix, and access to the Elastic Support portal has been restored. Customers can authenticate to the support portal again. We are considering this issue resolved and will be providing no further updates. If you continue to have issues, please…
403 error when trying to access Autoops in newly created serverless projectsPartial outage
Oct 22, 2026, 11:19 AM UTC to Oct 22, 2026, 8:50 PM UTC (9h 31m)resolved
their latest update (Oct 22, 2026, 8:50 PM UTC): We resolved the issue affecting AutoOps at 12:30 UTC.
Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HT…
Elastic Cloud scaling issues in AzurePartial outage
Oct 20, 2026, 8:07 PM UTC to Oct 21, 2026, 3:05 AM UTC (6h 57m)resolved
their latest update (Oct 21, 2026, 3:05 AM UTC): Engineers have mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. Scaling is working as expected.
Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)Partial outage
Oct 20, 2026, 6:51 AM UTC to Oct 20, 2026, 9:54 PM UTC (15h 3m)resolved
their latest update (Oct 20, 2026, 9:54 PM UTC): The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone.
Elastic Cloud Hosted: Customers…
Delayed or Unavailable project operation in GCP us-central1Partial outage
Oct 8, 2026, 4:42 PM UTC to Oct 9, 2026, 12:54 AM UTC (8h 12m)resolved
their latest update (Oct 9, 2026, 12:54 AM UTC): The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.
Delayed Serverless Metrics in Azure UAE North regionPartial outage
Oct 6, 2026, 2:04 PM UTC to Oct 6, 2026, 5:54 PM UTC (3h 50m)resolved
their latest update (Oct 6, 2026, 5:54 PM UTC): The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.
Sep 23, 2026, 2:04 PM UTC to Sep 23, 2026, 4:03 PM UTC (1h 59m)resolved
their latest update (Sep 23, 2026, 4:03 PM UTC): This issue has been resolved.
AutoOps node metrics temporarily unavailable in some regionsPartial outage
Sep 17, 2026, 3:50 PM UTC to Sep 17, 2026, 4:31 PM UTC (41 min)resolved
their latest update (Sep 17, 2026, 4:31 PM UTC): The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.
Elastic Support Portal unavailablePartial outage
Sep 16, 2026, 1:17 PM UTC to Sep 16, 2026, 3:38 PM UTC (2h 21m)resolved
their latest update (Sep 16, 2026, 3:38 PM UTC): The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.
Showing the 10 most recent of 51 incidents Elastic Cloud has declared in the history we hold.
These entries are Elastic Cloud's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Elastic Cloud's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.