Degraded performance: s.jina.ai
Jina AI reports degraded performance on s.jina.ai and Reader - s.jina.ai. The provider stated that the service has recovered. The incident is resolved and lasted 5 minutes.
State
Resolved
Started
Lasted
5 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
5 min 100%
Updates
Times in UTCAs posted by Jina AI
Service has recovered. Error rate: 0.00%
Service s.jina.ai is experiencing issues. - Current P99 latency: 21663ms (baseline: 21663ms) - Current error rate: 12.35% (baseline: 12.35%) - Request count (5min): 405 - Region: us-central1 Status: Degraded Performance Reason: Error rate above SLO: 12.35% (SLO: 10.00%)
Affected components
2Jina AI in the last 90 days
Full historyIncidents in 90 days
56
Days with an incident
11
Median duration
5 min
This incident
About the median
Other Jina AI incidents
All incidentsJina AI·Degraded performance: s.jina.ai
s.jina.ai and Reader - s.jina.ai had degraded performance in region us-central1. Jina AI reported an error rate above the SLO. Jina AI resolved the incident after 10 minutes.
Jina AI·Partial outage: s.jina.ai
Jina AI reports a partial outage on the s.jina.ai component and the Reader - s.jina.ai component in the us-central1 region. Jina AI reports that the incident is resolved. The incident lasted about 5 minutes.
Jina AI·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.
Jina 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.
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