Monthly service review pack
As of 17 Oct 2026, 14:01 UTC · last 30 days · Signal Ledger demonstrator. Synthetic data, plus 13 captured records marked Live in the queue (not counted in the sections that need invented context). It reflects any edits you have made in this browser.
SLA by audience
| Audience | Attainment | Goal | Resolved | Open past target |
|---|---|---|---|---|
| Internal | 96% | 85% | 52 | 6 |
| Consumer | 75% | 90% | 40 | 0 |
| Partner | 60% | 95% | 30 | 0 |
Top correlation groups
- 97% confidence · 2 signals: KAN-4 and 7 · suggested cause (AI): A stale DNS resolver cache on the API gateway fleet caused intermittent lookup failures surfacing as sporadic 502s to partner callers.
- 90% confidence · 3 signals: INC-204, PC-303 and SD-103 · suggested cause (AI): The settlement batch job terminated before processing all partitions, so the report covers only part of the merchants.
- 89% confidence · 3 signals: INC-206, SEC-401 and SD-106 · suggested cause (AI): Both records track the same detected surge of failed sign-ins from unrecognised locations, handed from the security alert into incident management.
Change and recovery
Change failure rate 27% (7 of 26 changes rolled back or caused an incident) · incidents linked to a change within 4h 18% (24 of 131) · mean time to restore (high and critical) 7h 23m · mean time to resolve (all tickets) 1d 13h.
Supplier breaches
| Supplier | Signals | SLA breaches | Mean restore | Groups |
|---|---|---|---|---|
| Hollowfen Hosting | 19 | 5 | 2h 45m | 1 |
| Quillfeather Messaging | 13 | 5 | 5h 25m | 1 |
| Wrenmoor Batch Services | 14 | 0 | 3h 53m | 1 |
Overnight settlement batch: 3 of 7 runs breached the completion target.
Readiness overview
5 ready · 2 conditional · 3 not ready of 10 services. Not ready: partner portal, data platform and partner onboarding.
Status rule: Ready is all Met; Conditional has a Partial and no Not met; Not ready has any Not met.