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 later reported that the service recovered. The incident is resolved and lasted about 15 minutes.
State
Resolved
Started
Lasted
15 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
15 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: 11660ms (baseline: 11660ms) - Current error rate: 1.15% (baseline: 1.15%) - Request count (5min): 1218 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11660ms (SLO: 5000ms)
Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11232ms (baseline: 11232ms) - Current error rate: 1.36% (baseline: 1.36%) - Request count (5min): 737 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11232ms (SLO: 5000ms)
Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11289ms (baseline: 11289ms) - Current error rate: 0.62% (baseline: 0.62%) - Request count (5min): 1124 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11289ms (SLO: 5000ms)
Affected components
1Jina AI in the last 90 days
Full historyIncidents in 90 days
65
Days with an incident
15
Median duration
5 min
This incident
2.9× the median
Other Jina AI incidents
All incidentsJina AI·Degraded performance: s.jina.ai-serp
Jina AI reports degraded performance on s.jina.ai and Reader - s.jina.ai in the us-central1 region. Jina AI reports that the incident is resolved. The incident lasted 5 minutes.
Jina AI·Degraded performance: jina-clip-v2
Jina AI reports degraded performance on the jina-clip-v2 embedding model in the us-central1 region. Jina AI resolved the incident after 5 minutes.
Jina AI·Degraded performance: jina-clip-v2
Jina AI reports degraded performance on jina-clip-v2 in the us-central1 region. The provider marked the incident as resolved after 5 minutes and reports an error rate of 0.00%.
Jina AI·Degraded performance: jina-clip-v2
Jina AI reports degraded performance on jina-clip-v2 in us-central1 for 5 minutes. Jina AI marked the incident as resolved at 10:45 UTC.
Jina AI·Degraded performance: jina-clip-v2
Jina AI reports degraded performance on jina-clip-v2 and the Embedding Models jina-clip-v2 component in us-central1. Jina AI resolved the incident after 5 minutes.
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