ELASTIC

{ "skip": true } ``` This is scheduled maintenance, not an incident. Per the rules, we skip scheduled/planned maintenance events. (Auto-resolved: no updates in 24h)

⏰ Apr 15, 2026 Fixed (for now) spotted via status_rss

// The official story

Upcoming geoip.elastic.co storage backend migration

// Status page says

THIS IS A SCHEDULED EVENT Apr 22 , 16:00 - 17:00 UTC Apr 15 , 15:34 UTC Scheduled - The Elastic geoip service (geoip.elastic.co) will transition to serving downloads from a new storage backend. Please see this announcement post for more details: https://discuss.elastic.co/t/upcoming-geoip-elastic-co-storage-backend-migration/385901

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

https://status.elastic.co/incidents/17x5dhr1r0pw

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.