studiosvc: p95 latency (ms) 1.8 min — 85.2× the fleet's usual 1.28 s (also p99 latency (ms) ≥ 2.0 min)
info
Service outlier
master
open
impact 18
Owner: Suresh Boddapati (backup: Madhava Mukkamala)
opened 84d ago · last observed 1d ago · observed 2381× · #149 · 333c1271e30e6d074d6b
What happened template
studiosvc differs from the other 12 services on 2 measures over six hours: p95 latency (ms) 1.8 min against the peers' 1.28 s (102.6 MADs above); p99 latency (ms) ≥ 2.0 min against the peers' 3.87 s (38.8 MADs above). Peer comparison is structural more often than it is news — a service that does more work per request will sit here for as long as it does — which is why this is informational unless it is about failures.
A service unlike the rest of the fleet on one measure (robust z against its peers).
The facts
| measures | {'measure': 'p95 latency (ms)', 'value': 108760.56338028153, 'value_fmt': '1.8 min', 'median': 1275.9683098591524, 'median_fmt': '1.28 s', 'mad': 1048.0800217391302, 'z': 102.55380585546126, 'direction': 'above', 'peers': 12}, {'measure': 'p99 latency (ms)', 'value': 120000.0, 'value_fmt': '≥ 2.0 min', 'median': 3873.749999999991, 'median_fmt': '3.87 s', 'mad': 2993.27492058822, 'z': 38.79571809500866, 'direction': 'above', 'peers': 12} |
| measure | p95 latency (ms) |
| value | 108,761 |
| value_fmt | 1.8 min |
| median | 1,276 |
| median_fmt | 1.28 s |
| z | 102.55 |
| direction | above |
| peers | 12 |
| rule | {"min_score": 3.5, "min_relative_pct": 35, "warn_on": []} |
| discriminator | |
| window | 2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC |
What is failing in studiosvc — the bad events, decomposed
“Bad events” are HTTP 5xx answers from studiosvc. In this finding's window (2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC) there were 3; every line links to the grouped errors behind it.
PUT /api/studio/responseSets/:id |
3 bad of 4 calls · 100% of the service's 5xx |
The error shapes behind them
| 249× | http error response returned to client since 2026-10-06 15:35:21 UTC |
| 3× | Request completed — 500 · response set with same title and variablename already exists since 2026-11-11 03:34:02 UTC |
| 3× | response set creation failed — response set with same title and variablename already exists since 2026-11-17 06:56:38 UTC |
History
Check it yourself
Every link carries the finding's own time window, so it shows tomorrow what it shows now.
Actions
Sign in (IAP) to acknowledge, snooze or resolve.
Where the numbers come from
| source | rollup |
| collected_at | 1794911364 |
| age_seconds | 678 |
| stale | False |
| shown | None |
| total | None |
| truncated | False |
| coverage_from | None |
| retain_days | None |
| note | None |
| detector | outliers |