Live

Jina AI

Jina AI is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

50

Days with an incident

9

Median duration

5 min

Longest incident

15 min

Components

15

Reranker Models

jina-reranker-m0 Operational
90 days ago1 day with an incidentToday
jina-reranker-v2-base-multilingual Operational
90 days agoNo incidentsToday
jina-reranker-v3 Operational
90 days agoNo incidentsToday
Rest Rerankers Operational
90 days agoNo incidentsToday

Embedding Models

jina-embeddings-v5-text-small Operational
90 days agoNo incidentsToday
jina-embeddings-v5-text-nano Operational
90 days agoNo incidentsToday
jina-embeddings-v4 Operational
90 days agoNo incidentsToday
jina-embeddings-v3 Operational
90 days agoNo incidentsToday
jina-clip-v2 Operational
90 days ago4 days with an incidentToday
jina-code-embeddings-500m Operational
90 days agoNo incidentsToday
jina-code-embeddings-1500m Operational
90 days agoNo incidentsToday
Rest Embeddings Operational
90 days ago3 days with an incidentToday

Reader

jina-vlm Operational
90 days ago1 day with an incidentToday
r.jina.ai Operational
90 days ago3 days with an incidentToday
s.jina.ai Operational
90 days ago5 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 22, 2026

Duration5 min16:35 to 16:40Partial outage: s.jina.aiDegraded

Service has recovered. Error rate: 0.00%

Duration15 min11:10 to 11:25Partial outage: s.jina.aiDegraded

Service has recovered. Error rate: 0.00%

Duration5 min11:05 to 11:10Degraded performance: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration10 min10:55 to 11:05Partial outage: s.jina.aiDegraded

Status changed to degraded_performance. See new incident for details.

Duration5 min10:50 to 10:55Service outage: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration5 min10:50 to 10:55Degraded performance: multi-embeddingsDegraded

Service has recovered. Error rate: 0.00%

Duration5 min10:45 to 10:50Partial outage: s.jina.aiDegraded

Status changed to major_outage. See new incident for details.

Duration5 min05:50 to 05:55Partial outage: s.jina.aiDegraded

Service has recovered. Error rate: 0.00%

Duration5 min05:45 to 05:50Degraded performance: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration5 min05:40 to 05:45Partial outage: s.jina.aiDegraded

Status changed to degraded_performance. See new incident for details.

Duration5 min05:35 to 05:40Degraded performance: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration5 min05:30 to 05:35Partial outage: s.jina.aiDegraded

Status changed to degraded_performance. See new incident for details.

Duration5 min05:25 to 05:30Degraded performance: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration5 min05:20 to 05:25Partial outage: s.jina.aiDegraded

Status changed to degraded_performance. See new incident for details.

Duration5 min05:15 to 05:20Degraded performance: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration14 min05:01 to 05:15Service outage: s.jina.aiDegraded

Status changed to degraded_performance. See new incident for details.

Duration6 min04:55 to 05:01Partial outage: s.jina.aiDegraded

Status changed to major_outage. See new incident for details.

Duration5 min04:50 to 04:55Service outage: s.jina.aiDegraded

Status changed to partial_outage. See new incident for details.

Duration5 min04:45 to 04:50Partial outage: s.jina.aiDegraded

Status changed to major_outage. See new incident for details.

Follow Jina AI

Your coding agent knows when Jina AI is down, and tells you when a failure is theirs, not yours. You can also get Jina AI incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "jina" and tell me if Jina AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=jina
Slack
/feed subscribe https://outages.cc/feed.xml?providers=jina

Go from tracking outages to fixing production issues with Polylane.

Try Polylane