execsvc p95 1.21 s vs a normal 98 ms ± 100 ms for Sat 12:00 UTC (3 of the last 4 checks)
info
Latency anomaly
test27
resolved
impact 11
Owner: Madhava Mukkamala (backup: Shashank Agrawal)
opened 76d ago · last observed 4d ago · observed 74× · #638 · 58345fb72759568fefc1
What happened template
execsvc's p95 is 1.2 s on test27, above a normal of 98 ms ± 100 ms for this hour of the week (3 of the last 4 five-minute buckets, z = 11.1, 2 weeks of history). Whether users noticed depends on which endpoints carried it — the service page shows the split. A p95 that stays under a second is never reported — below that nobody notices, whatever the deviation.
p95 far above its hour-of-week normal — and at least 1 s; under a second is noise.
The facts
| measure | api_p95_ms |
| unit | ms |
| value | 1,210 |
| expected_median | 97.50 |
| expected_mad | 100.00 |
| z | 11.12 |
| rel | 11.41 |
| buckets_hit | 3 |
| n | 24 |
| weeks | 2 |
| slot | Sat 12:00 UTC |
| bucket | 2026-11-14 12:25:00 UTC (4d ago) |
| floor_ms | 1,000 |
| discriminator | api_p95_ms |
| window | 2026-11-14 12:10:00 UTC → 2026-11-14 12:30:00 UTC |
What is failing in execsvc — the bad events, decomposed
“Bad events” are HTTP 5xx answers from execsvc. In this finding's window (2026-11-14 12:10:00 UTC → 2026-11-14 12:30:00 UTC) there were 0; every line links to the grouped errors behind it.
The error shapes behind them
| 12× | failed to get Study db123b3c-1ad0-4e7c-a444-f8e4c850ecc2. Error: object Study {tildaid:$a_tildaid} is marked deleted since 2026-10-26 13:59:24 UTC |
| 7× | error anchor visit index has not been set. Does this study have an anchor visit? continuing without setting day/date ran… since 2026-11-12 15:42:02 UTC |
| 6× | could not list DutyPlans for Study 85333258-21d0-4c47-92b2-da3a9fa8428f: passed Study was not found since 2026-10-12 17:57:06 UTC |
| 1× | Failed to fetch activity graph with subgraphs — failed to fetch activity graph: failed to fetch graph 16fc5aae: no nodes… since 2026-11-15 22:22:12 UTC |
| 1× | Failed to fetch activity details — failed to fetch activity graph with subgraphs: failed to fetch activity graph: failed… since 2026-11-15 22:22:12 UTC |
History
- 2026-11-14 12:26:21 UTCreopened x-ray · severity=info was=info title=execsvc p95 1.28 s vs a normal 98 ms ± 100 ms for Sat 12:00 UTC (3 of the last 4 checks) level=low was_level=low finding={'id': 638, 'fingerprint': '58345fb72759568fefc1', 'kind': 'anomaly.latency', 'severity': 'info', 'cluster': 'test27', 'subject': 'execsvc', 'title': 'execsvc p95 1.28 s vs a normal 98 ms ± 100 ms for Sat 12:00 UTC (3 of the last 4 checks)', 'facts': {'measure': 'api_p95_ms', 'unit': 'ms', 'value': 1281.25, 'expected_median': 97.5, 'expected_mad': 100.0, 'z': 11.8375, 'rel': 12.14102564102564, 'buckets_hit': 3, 'n': 24, 'weeks': 2, 'slot': 'Sat 12:00 UTC', 'bucket': 1794658500, 'window': [1794657600, 1794658800], 'floor_ms': 1000, 'recent_deploys': [], 'discriminator': 'api_p95_ms'}, 'evidence': [{'label': 'Service', 'href': '/service/execsvc?cluster=test27&from=1794636000&to=1794658800'}, {'label': 'Fleet vs normal', 'href': '/fleet?cluster=test27&from=1794636000&to=1794658800'}], 'provenance': {'source': 'rollup', 'collected_at': 1794659180, 'age_seconds': 12, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 5.4, 'status': 'open', 'first_seen': 1788411370, 'last_seen': 1794659181, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 72, 'narrative': "execsvc's p95 is 3.2 s on test27, above a normal of 410 ms ± 329 ms for this hour of the week (3 of the last 4 five-minute buckets, z = 8.5, 5 weeks of history). Whether users noticed depends on which endpoints carried it — the service page shows the split. A p95 that stays under a second is never reported — below that nobody notices, whatever the deviation.", 'narrative_kind': 'template', 'discriminator': 'api_p95_ms', 'level': 'low', 'told_level': None, 'episode_at': 1794659181, 'chat_thread': None, 'kind_label': 'Latency anomaly', 'group': 'Anomalies', 'age_s': 6247822, 'stale_s': 11}
- 2026-11-15 06:36:59 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 638, 'fingerprint': '58345fb72759568fefc1', 'kind': 'anomaly.latency', 'severity': 'info', 'cluster': 'test27', 'subject': 'execsvc', 'title': 'execsvc p95 1.21 s vs a normal 98 ms ± 100 ms for Sat 12:00 UTC (3 of the last 4 checks)', 'facts': {'measure': 'api_p95_ms', 'unit': 'ms', 'value': 1209.9999999999995, 'expected_median': 97.5, 'expected_mad': 100.0, 'z': 11.124999999999995, 'rel': 11.410256410256405, 'buckets_hit': 3, 'n': 24, 'weeks': 2, 'slot': 'Sat 12:00 UTC', 'bucket': 1794659100, 'window': [1794658200, 1794659400], 'floor_ms': 1000, 'recent_deploys': [], 'discriminator': 'api_p95_ms'}, 'evidence': [{'label': 'Service', 'href': '/service/execsvc?cluster=test27&from=1794636600&to=1794659400'}, {'label': 'Fleet vs normal', 'href': '/fleet?cluster=test27&from=1794636600&to=1794659400'}], 'provenance': {'source': 'rollup', 'collected_at': 1794659948, 'age_seconds': 14, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': None}, 'impact': 10.6, 'status': 'resolved', 'first_seen': 1788411370, 'last_seen': 1794659949, 'resolved_at': 1794724619, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 74, 'narrative': "execsvc's p95 is 1.2 s on test27, above a normal of 98 ms ± 100 ms for this hour of the week (3 of the last 4 five-minute buckets, z = 11.1, 2 weeks of history). Whether users noticed depends on which endpoints carried it — the service page shows the split. A p95 that stays under a second is never reported — below that nobody notices, whatever the deviation.", 'narrative_kind': 'template', 'discriminator': 'api_p95_ms', 'level': 'low', 'told_level': None, 'episode_at': 1794659181, 'chat_thread': None, 'kind_label': 'Latency anomaly', 'group': 'Anomalies', 'age_s': 6313259, 'stale_s': 64680}
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 | 1794659948 |
| age_seconds | 14 |
| stale | False |
| shown | None |
| total | None |
| truncated | False |
| coverage_from | None |
| retain_days | None |
| note | None |
| detector | seasonal |