Degraded performance: jina-clip-v2
Jina AI reports degraded performance for jina-clip-v2 in the us-central1 region. The P99 latency was above the SLO. Jina AI reports that the incident is resolved and that it lasted 10 minutes.
State
Resolved
Started
1 h ago
2026-11-02 10:50 UTC
Lasted
10 min
until 2026-11-02 11:00 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
10 min 100%
Updates
Times in UTCAs posted by Jina AI
Service has recovered. Error rate: 0.00%
Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11628ms (baseline: 11628ms) - Current error rate: 0.37% (baseline: 0.37%) - Request count (5min): 1071 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11628ms (SLO: 5000ms)
Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11202ms (baseline: 11202ms) - Current error rate: 0.15% (baseline: 0.15%) - Request count (5min): 1318 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11202ms (SLO: 5000ms)
Affected components
1Jina AI in the last 90 days
Full historyIncidents in 90 days
53
Days with an incident
10
Median duration
5 min
This incident
2.0× the median
Other Jina AI incidents
All incidentsJina AI·Degraded performance: s.jina.ai
Jina AI reports degraded performance on s.jina.ai and Reader - s.jina.ai in the us-east1 region. Jina AI resolved the incident after about 10 minutes.
Jina AI·Partial outage: s.jina.ai
Jina AI reports a partial outage on s.jina.ai and Reader - s.jina.ai in the us-east1 region. Jina AI investigated an elevated error rate of 20.8 percent. Jina AI resolved the incident after 5 minutes.
Jina AI·Degraded performance: s.jina.ai
Service has recovered. Error rate: 0.00%
Jina AI·Partial outage: s.jina.ai
Status changed to degraded_performance. See new incident for details.
Jina AI·Degraded performance: s.jina.ai
Status changed to partial_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.
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.live/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.live/feed.xml?providers=jina/feed subscribe https://outages.live/feed.xml?providers=jinaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane