← Back to the carnage
ELASTIC

⚪ 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.

⏰ Aug 27, 2026 FYI spotted via status_rss

// The official story

[RESOLVED - 2026-08-26] APM endpoints for serverless projects not available

// Status page says

Aug 27 , 17:11 UTC Monitoring - On August 26, at around 00:00 UTC we deployed a change in Managed Inputs that affected some rules in our internal DNS provider, removing the .apm endpoints some of our Serverless customers. The service was restored around 9AM UTC on the same day. During this time, some customers would have experienced unavailability of the .apm endpoint, for a period in the 9 hour window. We are putting some checks and

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

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

Elastic's Greatest Hits

🟢 ELASTIC Oct 23, 2026
🟡 Elastic's support portal decided to ghost its own customers mid-morning UTC. Ironic timing for a company literally named after flexibility. If you need help, well... that's the joke, isn't it?. (Auto-resolved: no updates in 24h)
🟢 ELASTIC Oct 20, 2026
🟠 Google's London infrastructure decided to take a unscheduled nap, leaving Elastic Cloud customers in europe-west2-b scrambling. When your cloud provider's availability zone becomes unavailable, the irony is so thick you could mine it. Elastic's playing damage control while their customers refresh status pages like slot machines. (Auto-resolved: no updates in 24h)
🟢 ELASTIC Oct 08, 2026
🟡 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)