Orb: Elevated API latencies, now resolved
Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents
Orb’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted −13 min vs the first vendor naming Azure)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure west us<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>2 vendors, 1 blamed Azure<br/>JFrog, Optimizely"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 2 blamed Azure<br/>Wiz, Sumo Logic"]:::blames
root --> h4
later["Later<br/>1 vendor<br/>Contentstack"]:::names
root --> later
me["Orb (this incident)<br/>posted −13 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Customers may have experienced elevated API latencies from ~08:00–09:00Z and ~13:05–13:45Z, with some mild degradation in the timeframe in between. We've identified and mitigated the problematic underlying resource contention, and will continue to monitor. Note that this did not affect ingestion, and did not cause server-side timeouts for the vast majority of customers, but may have caused client-side timeouts.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).