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 | |
|---|---|---|---|---|---|---|
| Duration of March outage without threat visibility | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Ravi Gupta | Internal | Detect Team - Reliability Sprint Retro 28 Apr 2026 | |
| Quarterly audit documentation time before Comply | “probably close to two weeks every quarter” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Wayne Keller | Atlas Precision | Aegis / Atlas Precision - Annual Review… 28 Apr 2026 | |
| Detect outage duration in March | “Six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Wayne Keller | Atlas Precision | Aegis / Atlas Precision - Annual Review… 28 Apr 2026 | |
| Target failover time for redundant nodes | “under thirty seconds” | Recovery Time?Time-related targets for data recovery, including RPO and RTO. | Ravi Gupta | Internal | Detect Team - Reliability Sprint Retro 28 Apr 2026 | |
| Observed failover time for redundant nodes in testing | “twelve, fourteen seconds” | Recovery Time?Time-related targets for data recovery, including RPO and RTO. | Ravi Gupta | Internal | Detect Team - Reliability Sprint Retro 28 Apr 2026 | |
| Duration of IT director's IAM complaints | “eight months” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Wayne Keller | Atlas Precision | Aegis / Atlas Precision - Annual Review… 28 Apr 2026 | |
| Number of threshold configurations tried before settling | “three” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Ravi Gupta | Internal | Detect Team - Reliability Sprint Retro 28 Apr 2026 | |
| Delay in policy/provisioning sync propagation | “four, five hours” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Derek Owens | Crestline Wealth | Support Case #7615 - Crestline Wealth G… 27 Apr 2026 | |
| Number of users in the directory | “800 users” | People Count?The number of people, including users, seats, and staff. | Derek Owens | Crestline Wealth | Support Case #7615 - Crestline Wealth G… 27 Apr 2026 | |
| Sync worker polling interval | “sixty seconds” | 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 | |
| Time for dedicated worker provisioning to propagate | “30 to 45 minutes” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Sarah Chen | Crestline Wealth | Support Case #7615 - Crestline Wealth G… 27 Apr 2026 | |
| Expected brief sync pause during cutover | “two or three minutes” | 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 | |
| Threshold for acceptable sync delay on dedicated worker | “ten minutes” | Threshold?A numeric limit or trigger value that initiates an action. | Sarah Chen | Crestline Wealth | Support Case #7615 - Crestline Wealth G… 27 Apr 2026 | |
| P1 investigation SLA for root cause determination | “48 hours” | 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 | |
| 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 | |
| Time spent pulling logs and documentation for prior HIPAA audit | “three weeks” | Effort?An estimate of work required, in time, points, or other units. | Thomas Hargrove | Redwood Clinical | Aegis / Redwood Clinical - ISO 27001 Pr… 26 Apr 2026 | |
| Duration of the main Detect outage event | “six-hour gap” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Ravi Gupta | Internal | All Hands - April Update 26 Apr 2026 | |
| Time from call date to targeted ISO 27001 audit | “roughly eight or nine months” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Thomas Hargrove | Redwood Clinical | Aegis / Redwood Clinical - ISO 27001 Pr… 26 Apr 2026 | |
| Window of Detect instability | “March 10th through the 18th” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Ravi Gupta | Internal | All Hands - April Update 26 Apr 2026 | |
| Redwood IT time required to enable Comply v2 | “maybe an hour” | Effort?An estimate of work required, in time, points, or other units. | Kevin O'Brien | Redwood Clinical | Aegis / Redwood Clinical - ISO 27001 Pr… 26 Apr 2026 | |
| Customer escalations after Detect outage | “three customer escalations” | Event Count?The number of events, alerts, or incident notifications. | Hannah Liu | Internal | All Hands - April Update 26 Apr 2026 | |
| Timeframe for running the first baseline report | “in the first two weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kevin O'Brien | Redwood Clinical | Aegis / Redwood Clinical - ISO 27001 Pr… 26 Apr 2026 | |
| Reproducibility rate of the Comply v2 reporting timeout | “two out of five tries” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Nina Kowalski | Internal | All Hands - April Update 26 Apr 2026 | |
| Threshold for triggering the timeout in Comply v2 | “more than three reports” | Threshold?A numeric limit or trigger value that initiates an action. | Nina Kowalski | Internal | All Hands - April Update 26 Apr 2026 | |
| Number of users at Frostbyte | “about 1,400 users across the organization” | People Count?The number of people, including users, seats, and staff. | Victor Zheng | Frostbyte | Aegis / Frostbyte AI - Product Feedback 25 Apr 2026 | |
| Number of frameworks supported in Comply v2 | “four” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Priya Patel | Blackridge Investments | Support Case #8811 - Blackridge Investm… 25 Apr 2026 | |
| Time required to complete the early access intake form | “ten minutes” | Effort?An estimate of work required, in time, points, or other units. | Priya Patel | Blackridge Investments | Support Case #8811 - Blackridge Investm… 25 Apr 2026 | |
| Length of time Frostbyte has used Aegis Identity | “about seven months? Maybe closer to eight” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Victor Zheng | Frostbyte | Aegis / Frostbyte AI - Product Feedback 25 Apr 2026 | |
| closed-lost opportunities in Q1 | “34” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| Number of users in current directory | “about 340” | People Count?The number of people, including users, seats, and staff. | Derek Owens | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| Users in elevated or admin roles | “around 40” | People Count?The number of people, including users, seats, and staff. | Derek Owens | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| combined ACV of closed-lost opportunities | “around 2.1 million” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| closed-lost opportunities with named competitor reason | “22” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| Users on legacy SMS-based MFA | “20, maybe 25” | People Count?The number of people, including users, seats, and staff. | Derek Owens | Crestline Wealth | Aegis / Crestline Wealth - Identity Mod… 24 Apr 2026 | |
| losses to SentinelShield | “9” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 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 | |
| losses to VaultEdge | “6” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 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 | |
| losses to CyberNova | “4” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 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 | |
| Next internal compliance review timing | “August” | 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 | |
| late-stage deals that slipped or went cold around the March outage | “at least five” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| losses explicitly citing the outage | “two” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| duration of threat visibility outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| VaultEdge's claimed recovery time objective | “sub-15-minute” | Recovery Time?Time-related targets for data recovery, including RPO and RTO. | Kevin O'Brien | Internal | Win/Loss Analysis - Q1 24 Apr 2026 | |
| Duration of the March Detect monitoring outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Evelyn Park | Bridgeport Health | Aegis / Bridgeport Health - Renewal Fin… 23 Apr 2026 | |
| Maximum additional seats allowed under the expansion rider | “twenty percent” | People Count?The number of people, including users, seats, and staff. | James Mitchell | Bridgeport Health | Aegis / Bridgeport Health - Renewal Fin… 23 Apr 2026 | |
| Number of modules included in the renewal | “four” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | James Mitchell | Bridgeport Health | Aegis / Bridgeport Health - Renewal Fin… 23 Apr 2026 | |
| Peak event volume processed by Aegis Detect | “somewhere between eight and twelve thousand events per minute” | Event Count?The number of events, alerts, or incident notifications. | Damien Rowe | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Unique tenants generating at least one on-demand report as of April 21 | “847” | Account Count?The number of customer accounts or organizations. | Megan Lawson | Internal | Comply v2 - Adoption Metrics Review 22 Apr 2026 | |
| Duration of the March Aegis Detect monitoring outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Kendra Wallace | Brightpath Commerce | Aegis / Brightpath Commerce - Competiti… 22 Apr 2026 | |
| Duration of March outage with no visibility | “Six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Damien Rowe | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Eligible accounts for Comply v2 | “roughly 2,200” | Account Count?The number of customer accounts or organizations. | Megan Lawson | Internal | Comply v2 - Adoption Metrics Review 22 Apr 2026 | |
| Duration of Brightpath's broader security vendor evaluation | “six weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kendra Wallace | Brightpath Commerce | Aegis / Brightpath Commerce - Competiti… 22 Apr 2026 | |
| Adoption rate at two-week mark | “38, 39 percent” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Tom Bradley | Internal | Comply v2 - Adoption Metrics Review 22 Apr 2026 | |
| Time saved by the Comply v2 on-demand SOC 2 report | “two days of work” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kendra Wallace | Brightpath Commerce | Aegis / Brightpath Commerce - Competiti… 22 Apr 2026 | |
| Period of incomplete LogVault data | “four days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Damien Rowe | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Expected timeframe for SentinelShield pricing proposal | “next week or two” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kendra Wallace | Brightpath Commerce | Aegis / Brightpath Commerce - Competiti… 22 Apr 2026 | |
| Time to apply and validate streaming mode configuration | “fifteen minutes” | Effort?An estimate of work required, in time, points, or other units. | David Kim | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Internal benchmark adoption at two-week mark | “25 percent” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Megan Lawson | Internal | Comply v2 - Adoption Metrics Review 22 Apr 2026 | |
| Length of Aegis-Brightpath working relationship | “two years” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kendra Wallace | Brightpath Commerce | Aegis / Brightpath Commerce - Competiti… 22 Apr 2026 | |
| Share of reports using SOC 2 framework | “nearly half” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Megan Lawson | Internal | Comply v2 - Adoption Metrics Review 22 Apr 2026 | |
| Expected data forwarding pause during switchover | “under a minute” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | David Kim | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Time for full backfill to complete | “one to two hours” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | David Kim | Stratos Cloud | Support Case #3536 - Stratos Cloud LogV… 22 Apr 2026 | |
| Time Julia spent on evidence gathering before the last audit | “two full weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Julia Tran | Blackridge Investments | Aegis / Blackridge Investments - HIPAA… 21 Apr 2026 | |
| How long Blackridge has run Aegis Protect and Identity | “eight months” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Warren Beck | Blackridge Investments | Aegis / Blackridge Investments - HIPAA… 21 Apr 2026 | |
| Typical initial configuration time for Aegis Comply | “a few days to maybe a week” | Effort?An estimate of work required, in time, points, or other units. | Lisa Park | Blackridge Investments | Aegis / Blackridge Investments - HIPAA… 21 Apr 2026 | |
| Duration of the March Detect event-processing incident | “six-hour window” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Lisa Park | Blackridge Investments | Aegis / Blackridge Investments - HIPAA… 21 Apr 2026 | |
| Uptime SLA availability target | “99.9%” | Uptime?The percentage of time a system is available, often as an SLA. | Nina Kowalski | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Duration of monitoring visibility loss in the March outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Ravi Gupta | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Number of enterprise prospects requiring SOC 2 Type II for procurement | “three” | Account Count?The number of customer accounts or organizations. | Diana Reeves | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Number of existing customers with SOC 2 Type II in renewal terms | “two” | Account Count?The number of customer accounts or organizations. | Diana Reeves | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Deadline for the SOC 2 Type II report | “end of May” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Diana Reeves | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Time previously spent pulling evidence packages together manually | “two weeks” | Effort?An estimate of work required, in time, points, or other units. | Tyler Washington | Internal | SOC 2 Type II - Final Review 20 Apr 2026 | |
| Workloads in scope for Protect deployment | “probably 40 to 50 workloads total” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Vanessa Cruz | Coastal Living | Aegis / Coastal Living Co - Protect Mod… 19 Apr 2026 | |
| Total data volume across environments | “somewhere around 80 to 100 terabytes” | Data Volume?The amount of data, measured in bytes, records, or similar units. | Vanessa Cruz | Coastal Living | Aegis / Coastal Living Co - Protect Mod… 19 Apr 2026 | |
| Maximum acceptable RPO for the customer data platform | “no more than an hour” | Recovery Time?Time-related targets for data recovery, including RPO and RTO. | Vanessa Cruz | Coastal Living | Aegis / Coastal Living Co - Protect Mod… 19 Apr 2026 | |
| Maximum acceptable RTO for the customer data platform | “ideally under four hours” | Recovery Time?Time-related targets for data recovery, including RPO and RTO. | Vanessa Cruz | Coastal Living | Aegis / Coastal Living Co - Protect Mod… 19 Apr 2026 | |
| Phase one onboarding duration | “about two to three weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kevin O'Brien | Coastal Living | Aegis / Coastal Living Co - Protect Mod… 19 Apr 2026 | |
| Monthly price differential between Comply v2 and standard tier | “$1,275 per month” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | David Kim | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Correct prorated charge for April (24 of 30 days) | “$1,020” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | David Kim | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Proration percentage for 24 of 30 days | “80 percent” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | David Kim | Silverline Brands | Support Case #7570 - Silverline Brands… 18 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 | |
| Proration period after upgrade | “24 days out of 30” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | David Kim | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Days charged before v2 activation | “6 days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Dominic Flores | Silverline Brands | Support Case #7570 - Silverline Brands… 18 Apr 2026 | |
| Audit log entries threshold triggering Comply report timeout | “around 50,000” | Threshold?A numeric limit or trigger value that initiates an action. | Sofia Petrov | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Duration of March outage without threat monitoring visibility | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Ryan Caldwell | Axiom Labs | Aegis / Axiom Labs - Multi-Year Renewal 17 Apr 2026 | |
| Expected headcount growth over next 18 months | “40%” | People Count?The number of people, including users, seats, and staff. | Ryan Caldwell | Axiom Labs | Aegis / Axiom Labs - Multi-Year Renewal 17 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 | |
| Latency spike magnitude on Detect ingestion | “200ms” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Ravi Gupta | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Time after outage for post-incident report publication | “five days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Mina Joshi | Axiom Labs | Aegis / Axiom Labs - Multi-Year Renewal 17 Apr 2026 | |
| Status page update frequency during incident | “every 20-30 minutes” | Throughput?A rate of data or operations, such as backup throughput, requests per day, or connections per second. | Ryan Caldwell | Axiom Labs | Aegis / Axiom Labs - Multi-Year Renewal 17 Apr 2026 | |
| Self-resolution time of latency spike | “four minutes” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ravi Gupta | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Proposed contract length | “three-year” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Aisha Johnson | Axiom Labs | Aegis / Axiom Labs - Multi-Year Renewal 17 Apr 2026 | |
| Time since Comply v2 launch | “ten days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Raj Kapoor | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Estimated workload for load testing suite | “two weeks” | Effort?An estimate of work required, in time, points, or other units. | Sofia Petrov | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Suggested health check timeout | “500ms” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Sofia Petrov | Internal | Weekly Engineering Standup 17 Apr 2026 | |
| Duration of March Detect outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Sandra Keating | Pinnacle Insurance | Aegis / Pinnacle Insurance - Detect Roa… 16 Apr 2026 | |
| Alert volume during March outage | “zero” | Event Count?The number of events, alerts, or incident notifications. | Sandra Keating | Pinnacle Insurance | Aegis / Pinnacle Insurance - Detect Roa… 16 Apr 2026 | |
| Delay of Aegis Detect alert notifications | “20 to 45 minutes” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Alicia Monroe | Summit Trust | Support Case #6147 - Summit Trust Detec… 15 Apr 2026 | |
| Backup job queue time during simulated 2x P95 load | “47 minutes” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Tyler Washington | Internal | Protect Performance - Scalability Conce… 15 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 | |
| Load level at which throughput degradation begins | “around the 60% load mark” | Threshold?A numeric limit or trigger value that initiates an action. | Tyler Washington | Internal | Protect Performance - Scalability Conce… 15 Apr 2026 | |
| Duration of reduced visibility during March Detect outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | David Kim | Summit Trust | Support Case #6147 - Summit Trust Detec… 15 Apr 2026 | |
| Scheduler refactor effort estimate | “six to eight minimum” | Effort?An estimate of work required, in time, points, or other units. | Sofia Petrov | Internal | Protect Performance - Scalability Conce… 15 Apr 2026 | |
| Estimated time to complete tenant rebalance migration | “two to four hours” | Effort?An estimate of work required, in time, points, or other units. | David Kim | Summit Trust | Support Case #6147 - Summit Trust Detec… 15 Apr 2026 | |
| Deduplication fix effort estimate | “one to two week effort” | Effort?An estimate of work required, in time, points, or other units. | Sofia Petrov | Internal | Protect Performance - Scalability Conce… 15 Apr 2026 | |
| Detect outage duration in March | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Chris Lee | Internal | Protect Performance - Scalability Conce… 15 Apr 2026 | |
| Expected brief pause in queue processing during migration | “10, 15 minutes” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | David Kim | Summit Trust | Support Case #6147 - Summit Trust Detec… 15 Apr 2026 | |
| Simulated load test scale | “roughly 2x our current P95 customer scale” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Tyler Washington | Internal | Protect Performance - Scalability Conce… 15 Apr 2026 | |
| Duration of March outage with no threat monitoring | “roughly six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Russell Tang | Ironworks Corp | Aegis / Ironworks Corp - Vendor Compari… 14 Apr 2026 | |
| Number of demos with Fortiguard Pro | “two” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Catherine Page | Ironworks Corp | Aegis / Ironworks Corp - Vendor Compari… 14 Apr 2026 | |
| Time since Fortiguard Pro reached out | “about six weeks ago” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Catherine Page | Ironworks Corp | Aegis / Ironworks Corp - Vendor Compari… 14 Apr 2026 | |
| Comply v2 general availability date | “April 7th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Maria Santos | Ironworks Corp | Aegis / Ironworks Corp - Vendor Compari… 14 Apr 2026 | |
| Period of stability since remediation | “three weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Russell Tang | Ironworks Corp | Aegis / Ironworks Corp - Vendor Compari… 14 Apr 2026 | |
| Estimated timeline for JIT provisioning and SCIM improvements | “four to five weeks” | Effort?An estimate of work required, in time, points, or other units. | Ananya Sharma | Internal | Identity Team - Q2 Roadmap 13 Apr 2026 | |
| Backup throughput before regression | “around 800 megabytes per second” | Throughput?A rate of data or operations, such as backup throughput, requests per day, or connections per second. | David Kim | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Backup throughput after regression | “around 180 to 220” | Throughput?A rate of data or operations, such as backup throughput, requests per day, or connections per second. | David Kim | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Average SQLPROD01 backup job duration over last ten days | “about eight hours over the last ten days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | David Kim | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Backup overrun into business hours | “four to five hours of overage” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Dominic Flores | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Duration issue has been occurring | “about two weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Dominic Flores | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Alert threshold for SQL backup job duration | “six hours” | Threshold?A numeric limit or trigger value that initiates an action. | David Kim | Silverline Brands | Support Case #9856 - Silverline Brands… 12 Apr 2026 | |
| Duration of Detect outage without threat monitoring visibility | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Lauren Bishop | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 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 | |
| Standard contract renewal escalator | “three percent” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Lisa Park | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Planned additional cloud workloads through Q3 | “about forty more” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Lauren Bishop | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Cloud workload split between CloudPrime and Azure | “about a 70/30 split” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Lauren Bishop | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Time until contract renewal | “eleven weeks out” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Lisa Park | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Proposal delivery turnaround | “two weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Lisa Park | Cobalt Software | Aegis / Cobalt Software - Q2 Planning 11 Apr 2026 | |
| Late-stage deals where SentinelShield appeared aggressively | “three” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | James Mitchell | Internal | Competitive Response Strategy 10 Apr 2026 | |
| Total overage charges on April invoice | “just over four thousand dollars” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Natalie Simmons | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Visibility loss during March outage | “roughly six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Tom Bradley | Internal | Competitive Response Strategy 10 Apr 2026 | |
| Comply overage amount | “three thousand two hundred and change” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Marcus Williams | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Detect overage amount | “eight hundred and forty dollars” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Ajay Mehta | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Time to generate compliance report in Comply v2 | “four clicks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Jordan Whitfield | Internal | Competitive Response Strategy 10 Apr 2026 | |
| Included on-demand compliance reports per billing cycle | “up to twenty” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Marcus Williams | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Number of configuration steps for CyberNova compliance report template | “three separate configuration steps” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Jordan Whitfield | Internal | Competitive Response Strategy 10 Apr 2026 | |
| On-demand compliance reports generated between April 7 and April 9 | “forty-seven” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Marcus Williams | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Outage visibility gap duration | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Natalie Simmons | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Customer tenure with Aegis | “three years” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Natalie Simmons | Clearwater Medical | Support Case #8179 - Clearwater Medical… 10 Apr 2026 | |
| Time to compile QSA evidence for a control | “two, three days” | Effort?An estimate of work required, in time, points, or other units. | Gerald Hutchins | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| QSA assessment scheduled date | “end of June” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Gerald Hutchins | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| Time remaining until QSA assessment | “two and a half months” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Gerald Hutchins | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| Initial integration and data ingestion time | “one to two weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ananya Sharma | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| Time to tune control mappings | “another week” | Effort?An estimate of work required, in time, points, or other units. | Ananya Sharma | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| Time to meaningful report output | “two to three weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ananya Sharma | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 Apr 2026 | |
| Comply v2 general availability date | “April 7th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Ananya Sharma | Forge Industries | Aegis / Forge Industries - PCI DSS Comp… 9 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 | |
| Time for initial connector setup | “a few hours” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Mike Romano | Clearwater Medical | Aegis / Clearwater Medical - Comply v2… 7 Apr 2026 | |
| Detect accounts affected by the outage | “forty-seven” | Account Count?The number of customer accounts or organizations. | Diana Reeves | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| HIPAA audit advance notice | “thirty days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ajay Mehta | Clearwater Medical | Aegis / Clearwater Medical - Comply v2… 7 Apr 2026 | |
| Formal support tickets filed during the outage | “eleven” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Diana Reeves | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| Accounts requesting executive briefings after the outage | “three” | Account Count?The number of customer accounts or organizations. | Diana Reeves | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| SOC 2 type 2 observation period | “six month observation period” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ajay Mehta | Clearwater Medical | Aegis / Clearwater Medical - Comply v2… 7 Apr 2026 | |
| Share of cloud environment on CloudPrime | “eighty percent” | Percentage?A proportion or rate expressed as a percent, such as adoption rate or coverage. | Natalie Simmons | Clearwater Medical | Aegis / Clearwater Medical - Comply v2… 7 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 | |
| Time to create IAM role with CloudFormation template | “about five minutes” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Mike Romano | Clearwater Medical | Aegis / Clearwater Medical - Comply v2… 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 | |
| Event telemetry dashboard work completion | “60% done” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Chris Lee | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| Deployment date of redundant ingestion nodes | “March 24th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Tyler Washington | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| Circuit breaker pattern production date | “March 29th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Tyler Washington | Internal | Detect Reliability - 30-Day Review 7 Apr 2026 | |
| Length of time Trailhead has run Protect and Detect | “about fourteen months now” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Isaac Brennan | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Duration of March Detect outage | “six hours” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Isaac Brennan | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Proposed renewal price uplift on Protect and Detect | “three percent” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Time until Comply v2 launch | “two days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Comply v2 launch date | “April seventh” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Number of weeks compliance team spends in spreadsheets during PCI audits | “like six weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Isaac Brennan | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Standard annual price for Comply add-on at Trailhead's environment size | “around twenty-two thousand annually” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Promotional annual price for Comply add-on for renewing customers | “eighteen five” | Money?A monetary amount, such as contract value, charges, overages, and revenue. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Proposed renewal contract term | “full two-year term” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Rachel Torres | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| Estimated start of next PCI audit cycle | “late July” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Isaac Brennan | Trailhead | Aegis / Trailhead Marketplace - Renewal… 5 Apr 2026 | |
| QA test configurations run for HIPAA reporting module validation | “forty” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Nina Kowalski | Internal | Comply v2 - Launch Day Checklist 4 Apr 2026 | |
| Time until Silverline's PCI DSS renewal audit | “six weeks” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Dominic Flores | Silverline Brands | Aegis / Silverline Brands - Comply v2 E… 3 Apr 2026 | |
| Comply v2 general availability date | “April 7th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Elena Vasquez | Forge Industries | Support Case #1993 - Forge Industries C… 3 Apr 2026 | |
| Comply v2 customer webinar date | “April 10th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | David Kim | Forge Industries | Support Case #1993 - Forge Industries C… 3 Apr 2026 | |
| Comply v2 report generation time | “eight, nine seconds” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kevin O'Brien | Silverline Brands | Aegis / Silverline Brands - Comply v2 E… 3 Apr 2026 | |
| Number of tools Silverline currently uses to cover compliance frameworks | “three” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Dominic Flores | Silverline Brands | Aegis / Silverline Brands - Comply v2 E… 3 Apr 2026 | |
| Length of time Forge has used Comply | “about eight months” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Dana Moretti | Forge Industries | Support Case #1993 - Forge Industries C… 3 Apr 2026 | |
| Expected report rendering time in Comply v2 | “a minute or two” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Elena Vasquez | Forge Industries | Support Case #1993 - Forge Industries C… 3 Apr 2026 | |
| Time to generate a SOC 2 Type II report in Comply v2 | “between, uh, ninety seconds and about four minutes” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kevin O'Brien | Nimbus Platform | Aegis / Nimbus Platform - Comply v2 Pre… 1 Apr 2026 | |
| GA deployment date | “April 7th” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Ananya Sharma | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| Time Nimbus spent pulling data for its last SOC 2 audit | “three days” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Keith Donovan | Nimbus Platform | Aegis / Nimbus Platform - Comply v2 Pre… 1 Apr 2026 | |
| Deploy window time | “around 10 PM Eastern” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ananya Sharma | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| Buffer before early morning traffic | “about a three hour buffer” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Ravi Gupta | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| Work saved by not having to build an internal compliance reporting tool | “three months” | Effort?An estimate of work required, in time, points, or other units. | Keith Donovan | Nimbus Platform | Aegis / Nimbus Platform - Comply v2 Pre… 1 Apr 2026 | |
| Comply v2 onboarding window for an account of Nimbus's size | “one to two week window” | Duration?A span of time not classified as an outage, response, retention, recovery, or effort, such as windows, tenures, and buffers. | Kevin O'Brien | Nimbus Platform | Aegis / Nimbus Platform - Comply v2 Pre… 1 Apr 2026 | |
| SOC 2 first-call latency | “like 8 seconds” | Response Time?The time between an event and a response, including latency, delay, and notification time. | Ravi Gupta | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| Concurrent requests in load test | “50 simultaneous requests” | Count?The number of discrete items not covered by a more specific count metric, such as instances, requests, or frameworks. | Nina Kowalski | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| Detect availability outage period in March | “March tenth through the eighteenth” | Outage Duration?The length of time a service, system, or monitoring capability was down or unavailable. | Kevin O'Brien | Nimbus Platform | Aegis / Nimbus Platform - Comply v2 Pre… 1 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 | |
| Tier one customer count | “a few hundred orgs” | Account Count?The number of customer accounts or organizations. | Ananya Sharma | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 | |
| v1 decommission timeline | “two weeks post-GA” | Date?A specific calendar date or clock time, including deadlines, launch dates, and target dates. | Ravi Gupta | Internal | Comply v2 - GA Deployment Plan 1 Apr 2026 |