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 | |
|---|---|---|---|---|---|---|
| Detect outage period described by Aegis The same thread cites six hours of lost visibility, but a March 10-18 window is not reconciled with that duration. | “March 10th through roughly the 18th” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Lisa Park | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Duration of complete loss of monitoring visibility Call recap describes the outage as March 10 through 18; Tyler says complete blindness lasted six hours from 11 PM on the 10th to 5 AM on the 11th. Not reconciled. | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Tyler Washington | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| Outage incident period Tyler also states six hours of complete blindness on the night of March 10-11; the longer period is not reconciled. | “March 10th through the 18th” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Tyler Washington | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 |