Jina AI
Jina AI is operational
History
Incidents in 90 days
50
Days with an incident
9
Median duration
5 min
Longest incident
15 min
Components
15Reranker Models
Embedding Models
Reader
Nov 1, 2026
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Oct 31, 2026
Oct 30, 2026
Oct 28, 2026
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Oct 26, 2026
Oct 24, 2026
Oct 22, 2026
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to major_outage. See new incident for details.status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to major_outage. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to major_outage. See new incident for details.status.jina.ai
Oct 21, 2026
Service has recovered. Error rate: 0.00%status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to major_outage. See new incident for details.status.jina.ai
Status changed to degraded_performance. See new incident for details.status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Service has recovered. Error rate: 0.00%status.jina.ai
Status changed to partial_outage. See new incident for details.status.jina.ai
Status changed to major_outage. See new incident for details.status.jina.ai
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.
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.
https://outages.cc/feed.xml?providers=jina/feed subscribe https://outages.cc/feed.xml?providers=jinaGo from tracking outages to fixing production issues with Polylane.
Try Polylane