Jina AI: Service outage: jina-reranker-m0
Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents
Jina AI’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +1 h 20 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["Jina AI (this incident)<br/>posted +1 h 20 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
Service has recovered. Error rate: 0.00%
From Jina AI’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.jina.ai (opens in new tab).