Jina AI

First posted only after it was over

0% 0 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Jina AI: lower than most vendors.

Time to resolve

5 min median; 9 in 10 within 25 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Jina AI: lower than most vendors.

Major or critical incidents

0.0 a month 0 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Jina AI: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Jina AI depends on

Runs in (named in its incidents): Google Cloud us-central1 (48), Google Cloud europe-west1 (1), Google Cloud us-east1 (1).

Outage events: Google Cloud us-central1, Sep 1 (timing), GitHub, Jul 24 (timing), Microsoft Azure west us, Jul 23 (timing), Cloudflare, Nov 18, 2025 (timing), Google Cloud, Jun 12, 2025 (timing), AWS, Jul 30, 2024 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

No notable changes yet. We compare every snapshot of Jina AI’s status page (taken every 10 minutes) and its 0 tracked pages.

Full Jina AI change history

No pricing, trust or legal pages tracked for Jina AI.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Jina AI incidents, last 90 daysJSONMarkdown