Jina incident

Degraded performance: jina-clip-v2

Minor Resolved View vendor source →

Jina experienced a minor incident on September 17, 2026 affecting jina-clip-v2, lasting 19m. The incident has been resolved; the full update timeline is below.

Started
Sep 17, 2026, 05:25 PM UTC
Resolved
Sep 17, 2026, 05:45 PM UTC
Duration
19m
Detected by Pingoru
Sep 17, 2026, 05:25 PM UTC

Affected components

jina-clip-v2

Update timeline

  1. investigating Sep 17, 2026, 05:25 PM UTC

    Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11729ms (baseline: 11729ms) - Current error rate: 0.29% (baseline: 0.29%) - Request count (5min): 695 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11729ms (SLO: 5000ms)

  2. investigating Sep 17, 2026, 05:30 PM UTC

    Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11753ms (baseline: 11753ms) - Current error rate: 0.12% (baseline: 0.12%) - Request count (5min): 818 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11753ms (SLO: 5000ms)

  3. investigating Sep 17, 2026, 05:35 PM UTC

    Service jina-clip-v2 is experiencing issues. - Current P99 latency: 12271ms (baseline: 12271ms) - Current error rate: 0.10% (baseline: 0.10%) - Request count (5min): 973 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=12271ms (SLO: 5000ms)

  4. investigating Sep 17, 2026, 05:40 PM UTC

    Service jina-clip-v2 is experiencing issues. - Current P99 latency: 11549ms (baseline: 11549ms) - Current error rate: 0.10% (baseline: 0.10%) - Request count (5min): 978 - Region: us-central1 Status: Degraded Performance Reason: Latency above SLO: P99=11549ms (SLO: 5000ms)

  5. resolved Sep 17, 2026, 05:45 PM UTC

    Service has recovered. Error rate: 0.00%