← Back to the carnage
ELASTIC
🔴 ELASTIC - AutoOps deployments marked as Inactive in AWS us-east-1 region. (Auto-resolved: no updates in 24h)
// The official story
AutoOps deployments marked as Inactive in AWS us-east-1 region
// Status page says
Mar 27 , 04:33 UTC Investigating - We are currently investigating an outage of AutoOps in AWS us-east-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.
🔗 Official status page (for the PR-approved version)
https://status.elastic.co/incidents/1q9m81gy7jc2Elastic'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.