ELASTIC

🟠 Elastic's Serverless trifecta (Search, Ingest, EIS) decided to ghost users for 100 minutes. Root cause found and fixed, but that's what we call 'confidence building' in production. (Auto-resolved: no updates in 24h)

⏰ May 11, 2026 Fixed (for now) spotted via status_rss

// The official story

Temporarily unavailability of Serverless Projects Functionality

// Status page says

May 11 , 08:00 UTC Monitoring - We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable. The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.

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

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

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.