🟡 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)

🟠 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'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'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'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)