Approved field record
Weekly archive
Real incidents. Full investigation paths. Reusable diagnostic principles.
- 01
Applications
Meta outage analysis
ThousandEyes examined a broad Meta outage affecting Facebook, Messenger, WhatsApp, and later Instagram. The most valuable reasoning move was showing that frontend network reachability remained normal while application errors and timeouts rose, which excluded one major fault domain immediately. - 02
AI & Automation
Google Gemini outage analysis
ThousandEyes analyzed a Gemini degradation where the chatbot failed to reply to some users. The high-value move was proving that frontend network reachability remained healthy, which bounded the issue to backend service behavior before Google’s own attribution landed. - 03
Cloud Infrastructure
Coinbase May 7, 2026 outage postmortem
A severe service outage interrupted trading and most customer-facing functions. The investigation had to trace a facility event through quorum loss, Kafka leader-election problems, and staged recovery blockers rather than stopping at the first platform symptom. - 04
AI & Automation
Microsoft Azure OpenAI multi-region latency and failures PIR
Azure OpenAI experienced multi-region latency and failures after an upstream API change caused retry amplification from an internal Microsoft 365 workload. The investigation initially followed a credible but wrong crash signature before a second regional wave revealed the real mechanism. - 05
Cloud Infrastructure
Microsoft Azure West US 2 power and cooling PIR
A severe thunderstorm caused power disturbances across multiple datacenters in West US 2, triggering cooling lockouts and protective shutdowns across two physical availability zones. The hard part of the investigation was proving why recovery remained slow after cooling returned: storage validation and telemetry backlog had become the new bottlenecks. - 06
Networking
Cloudflare .de DNSSEC outage response
Broken DNSSEC signatures at the .de TLD caused validating resolvers to return SERVFAIL for fresh lookups. Cloudflare had to distinguish cached success from fresh-resolution failure, account for retry-driven traffic inflation, and decide whether to bypass DNSSEC validation temporarily to restore service.