INC178267415370318

P3resolvedai_assisted

Elevated latency at CDN edge nodes, high cache-miss ratio

Pipeline Status

Context Assembly

Diagnose Agent

Severity / Routing Agent

Scenario Match

Remediate Agent

Confidence Gate

Gate Decisionauto executed

Execute Action

Verify Agent

Resolution

Assembled Context — bounded to last 30 minutes

Rolling logs

[cdn-edge-us-east] WARN cache hit ratio dropped to 41% (baseline 92%)

[cdn-edge-us-east] INFO p95 latency 890ms (baseline 120ms)

[origin] INFO origin request volume up 6x

Recent commits

(none in lookback window)

Similar past incidents

INC17808817359342 · network/P3 · 20d ago — Elevated latency at CDN edge nodes, high cache-miss ratio

INC17764233514098 · network/P3 · 71d ago — Elevated latency at CDN edge nodes, high cache-miss ratio

INC17826524955161 · network/P3 · -2d ago — Elevated latency at CDN edge nodes, high cache-miss ratio

Diagnosis Agent

ran in parallel

A sudden surge in origin request volume caused a dramatic drop in CDN cache‑hit ratio, forcing edge nodes to fetch most content from the origin and resulting in elevated latency.

[cdn-edge-us-east] WARN cache hit ratio dropped to 41% (baseline 92%)
[cdn-edge-us-east] INFO p95 latency 890ms (baseline 120ms)
[origin] INFO origin request volume up 6x

Assessed: P3 / network

Self-reported confidence: 90% (audit-only — not used by the gate)

openai/gpt-oss-120b · 1639ms

Severity / Routing Agent

ran in parallel

P3 / network

Routed to: CDN-Operations

The incident indicates a degradation in cache performance at the edge layer causing increased latency and origin load. While performance is significantly impacted, the service remains functional for users, consistent with the P3 severity of similar historical incidents.

Self-reported confidence: 95% (audit-only — not used by the gate)

gemini-flash-lite-latest · 1006ms

Scenario Matcher

deterministic, pre-LLM

Elevated latency from CDN edge saturation

Edge saturation with a high cache-miss ratio often resolves by clearing the CDN cache layer to force re-population from a healthy origin.

Match score: 83% · Recommended action: clear_cache

Matched tags: cdn, latency, edge

Remediate Agent

grounded by runbook match, pre-gate

Proposed action: clear_cache

team: CDN-Operations · reason: High cache miss ratio causing elevated latency · message: Clearing CDN cache to improve hit ratio · cacheLayer: cdn · serviceName: CDN · justification: Runbook recommendation and observed drop in cache hit ratio

Clearing the CDN cache aligns with the matched runbook and addresses the high cache‑miss ratio that is driving latency; no contradictory evidence suggests another action.

openai/gpt-oss-120b · 1553ms

Confidence Gate

auto_executed

Computed from 4 measurable signals — not the model's self-reported confidence.

Severity match rate100%

Runbook coverage83%

Data completeness67%

Recency100%

Computed confidence (v1)89%

Auto-execute threshold: 75%

Proposed action: clear_cache

Verify Agent

runs after execution

Resolved · residual risk: low

Follow-up: none

The cache clearance successfully addressed the high cache-miss ratio, which was the primary driver of the latency. Latency metrics have returned to nominal levels, and the system is stable.

Self-reported confidence: 95% (audit-only — not used by the gate)

gemini-flash-lite-latest · 692ms