← Back to the carnage
ELASTIC
🟡 Elastic's internal monitoring decided to stream data at dial-up speeds across Azure regions. Your deployment metrics are basically playing hide-and-seek with the UI. They're still there, just *very* committed to the suspense. (Auto-resolved: no updates in 24h)
// The official story
Internal Monitoring Data Delay
// Status page says
Jul 1 , 15:39 UTC Investigating - We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual. What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions. What's not affected: Your deploym
🔗 Official status page (for the PR-approved version)
https://status.elastic.co/incidents/m00rqvz4d74qElastic'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.