ELASTIC

🟡 Bekitzur-hosted services (maps, ML models, redirect shortener) decided to ghost users after someone's Terraform config got creative. Kibana maps and ML features now permanently on vacation, elastic-agent wondering what happened to go.elastic.co. Engineers currently reading Terraform docs they should've read yesterday. (Auto-resolved: no updates in 24h)

⏰ Jun 29, 2026 Fixed (for now) spotted via status_rss

// The official story

Bekitzur hosted services are down

// Status page says

Jun 29 , 16:14 UTC Investigating - We are currently investigating an issue affecting several Bekitzur-hosted services, including maps.elastic.co, ml-models.elastic.co, go.elastic.co, and related staging endpoints. This is impacting parts of Kibana (maps, ML models) as well as elastic-agent and other Go-based products that rely on go.elastic.co. Our team has identified the root cause — a Terraform configuration change inadv

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

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

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.