Jina AI: Service outage: r.jina.ai
Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents
Jina AI’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (hop 1, posted +2 h 33 min vs Google Cloud’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
root --> h1
h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
root --> h4
p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
root -.-> p0
k0["Bolt.new<br/>+24 min"]:::hop2
p0 -->|"blamed GitHub"| k0
p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
p1 -->|"blamed Twilio"| k1
me["Jina AI (this incident)<br/>posted +2 h 33 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
Status changed to partial_outage. See new incident for details.
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).