ELASTIC

🟠 Elastic's inference engine decided EMEA doesn't exist. GCP and Azure customers in that region are experiencing what we in the industry call 'the silent treatment.' Investigation ongoing, which is corporate-speak for 'we're checking the logs and muttering.'. (Auto-resolved: no updates in 24h)

⏰ Jul 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Partial outage - Elastic Inference Service (EIS)

// Status page says

Jul 1 , 22:44 UTC Update - We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions. Jul 1 , 22:43 UTC Investigating - We are currently investigating a partial outage affecting the Elastic Integration Service (EIS) for Elastic Cloud customers with depl

🔗 Official status page (for the PR-approved version)

https://status.elastic.co/incidents/ktdtzqfbml4c

Elastic's Greatest Hits

🟢 ELASTIC 5d ago

🟡 Elastic's GCP us-central1 region decided projects should come with a 'read receipts disabled' feature. Some Serverless deployments are either moving at geological timescales or vanishing entirely. The status page says 'investigating' which is tech speak for 'we're refreshing our monitors and hoping it fixes itself.'. (Auto-resolved: no updates in 24h)

🟢 ELASTIC Sep 17, 2026

🟡 Elastic's AutoOps can't find its node metrics (CPU, memory, disk) in certain regions—they're just gone from recent time ranges. The good news: your data's fine, cluster health is fine, everything else is fine. It's just the one thing you need to see that's MIA. ETA on the scavenger hunt: 2 hours. (Auto-resolved: no updates in 24h)

🟢 ELASTIC Sep 16, 2026

🟡 Elastic's own support portal decided to become unsupported. The company that helps you monitor everything apparently turned off monitoring for, well, everything. They're 'investigating' with their provider—translation: playing hot potato with blame while customers scream into the void. (Auto-resolved: no updates in 24h)

⚪ ELASTIC Aug 27, 2026

⚪ Someone deployed a DNS config change that yeet'd .apm endpoints into the void. Serverless customers got the silent treatment for ~9 hours until engineers remembered these endpoints existed. Elastic's internal DNS provider apparently needed a nap.