Network / Connectivity Degradation Risk
Detect path-level degradation across Qumulo, Azure and customer-facing endpoints.
Unacknowledged
Risk score
41/ 100Elevated
+11 vs. 24h ago
Status
Elevated risk
Confidence: 60%
Estimated lead time
Observed now
Observed in current data
Risk score trend
Evidence
Cross-AZ RTTprobe
p95 RTT between zones 1 and 2 doubled in East US 2
Packet lossprobe
0.4% on service-to-storage probes
How this risk score works
- What it is
- A 0–100 estimate of how likely Network / Connectivity are to cause customer impact soon. Higher means more signals are moving away from normal at the same time.
- How it is calculated
- Each signal is compared with its own baseline (same hour, last 14 days). The further it is above baseline, the more points it adds, up to a fixed weight per signal. The points add up to the score, capped at 100. Method: read-only network probes + baseline deviation.
- This score
- Cross-AZ RTT (p95) +15, Packet loss +13, TCP connect success +8, other signals +5 = 41 (Elevated), +11 vs. 24h ago.
- 0–25 Normal26–50 Elevated51–75 High76–100 Critical
- What it tells you
- The risk is already visible in current data. Start with Cross-AZ RTT (p95), which adds the most points. Confidence 60% reflects how many expected data feeds reported.
Contributing signals
Score breakdown41 / 100
| Signal | Current | Baseline | Points | Impact |
|---|---|---|---|---|
| Cross-AZ RTT (p95) | 3.8 ms | 1.9 ms | +15 | medium |
| Packet loss | 0.4% | 0.05% | +13 | medium |
| TCP connect success | 99.2% | 99.9% | +8 | low |
| DNS resolution (p95) | 48 ms | 22 ms | +5 | low |
Affected resources (3)
| Resource | Type | Region / AZ | Current Risk |
|---|---|---|---|
| rg-anq-prod-eus2-c0388 | Qumulo Cluster | East US 2 / 2 | 64 |
| rg-anq-prod-eus2-c0451 | Qumulo Cluster | East US 2 / 1 | 58 |
| vnet-anq-prod-eus2 | VNet | East US 2 / — | 41 |
Affected clusters (2)
| Cluster | Resource group | Current Risk |
|---|---|---|
| ANQ-0388 · Retail & Distribution | rg-anq-prod-eus2-c0388 | 64 |
| ANQ-0451 · Manufacturing | rg-anq-prod-eus2-c0451 | 58 |
Recommended actions
- 1Compare probe results from zones 1 and 2 to isolate the degraded path.
- 2Check Azure Network Watcher for the East US 2 core VNet.
- 3Correlate with storage latency before escalating to Microsoft.