Numbers
Every figure quoted on a call, shown exactly as it was spoken. 194 claims in this window — the place to check what uptime, recovery times, or dollar amounts we have actually committed to out loud.
All 194Duration57Count23Outage Duration23Date16Effort14Money11Response Time9Account Count8Percentage8People Count7Recovery Time5Threshold5Event Count3Throughput3Data Volume1Uptime1Flagged inconsistent14?The model recorded a note where a figure appeared to conflict with something else said on the same call.
| What was claimed | As spoken?The value exactly as it was spoken on the call, not a parsed number. | Metric | Stated by | Account | Call | |
|---|---|---|---|---|---|---|
| Gap between event timestamp and alert-sent timestamp in Aegis payload Falls within the 20-45 minute range reported by Alicia. | “20-plus minutes” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Gregory Fisk | Summit Trust | Support Case #6147 - Summit Trust Detec… 15 Apr 2026 | |
| p99 latency at 50 concurrent Exceeds stated SLO target of 15 seconds. | “around 22 seconds” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Nina Kowalski | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| SLO target for p99 latency Unit seconds inferred from context. | “15” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Nina Kowalski | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 |