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.
| What was claimed | As spoken?The value exactly as it was spoken on the call, not a parsed number. | Metric | Stated by | Account | Call | |
|---|---|---|---|---|---|---|
| Number of days without human response on ticket Derek earlier estimated the wait as 'a couple days' in turn 1. | “five-day gap” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Sarah Chen | Crestline Wealth | Support Case #7615 - Crestline Wealth G… 27 Apr 2026 | |
| Sofia's estimated deployment duration for Aegis Identity Sofia also projected early July deployment, consistent with the duration. | “roughly ten to twelve weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Sofia Petrov | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| Derek's target completion date before internal compliance review Sofia projected early July, which is earlier. | “end of July at the latest” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Derek Owens | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| Sofia's projected full deployment date Earlier than Derek's end-of-July target. | “early July range” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Sofia Petrov | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| Overbilled amount per customer estimate Differs from vendor's $255 calculation because customer used 28 days instead of 30 in proration. | “$340” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Michelle Tan | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Overbilled amount per vendor calculation Differs from customer's $340 estimate because Aegis uses a 30-day proration basis. | “$255” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | David Kim | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Number of customers affected by Comply report timeout More customers expected to be affected as more attempt to generate reports. | “three” | Account Count?The number of customer accounts or organizations. | Sofia Petrov | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| 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 | |
| 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 | |
| Total page count shown in the PDF footer The footer's stated total (twelve) does not match the document's actual length as reported by Oliver; Marcus confirmed the mismatch. | “page one of twelve or something, but the document is clearly more than twelve pages” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Oliver Grant | Pinnacle Insurance | Support Case #3296 - Pinnacle Insurance… 8 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 | |
| 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 |