Contract analysis

I. Executive Summary The purpose of this memorandum is to analyze and compare the uptime telemetry data provided by Sentinel Uptime Services Inc. ("Sentinel"), Lumos Analytics Inc.'s ("Lumos") independent third-party infrastructure monitoring vendor, against the outage durations claimed by Pinnacle Financial Holdings LLC ("Pinnacle") in its May 1, 2023 demand letter and accompanying supporting documentation. This ana

II. Background A. The Master Services Agreement and SLA Framework Lumos Analytics Inc. and Pinnacle Financial Holdings LLC entered into a Master Services Agreement dated January 15, 2021, bearing the internal reference number MSA-PFH-2021-0015 (the "MSA"). Under the MSA, Lumos provides Pinnacle with access to its proprietary data analytics platform, including real-time financial data processing, portfolio risk modeli

III. Methodology A. Sentinel Monitoring Architecture A clear understanding of Sentinel's monitoring architecture is essential to evaluating the reliability of its data and the nature of the discrepancies with Pinnacle's claimed durations. Sentinel monitors Lumos's production SaaS environment through two complementary mechanisms: Synthetic Transaction Checks. Sentinel deploys automated synthetic transactions that simu

1. US-East — Northern Virginia, United States

2. US-West — Oregon, United States

3. US-Central — Iowa, United States

6. APAC-South — Sydney, Australia This geographic distribution ensures that Sentinel's monitoring captures availability from a diverse set of network paths and access points, reducing the risk that localized network issues, ISP outages, or routing anomalies at any single location could distort the overall availability picture. Outage Definition. Under Sentinel's standard monitoring protocol, an "outage minute" is rec

1. Sentinel's recorded full-outage duration — the total minutes during which Sentinel recorded a full outage (all six monitoring nodes reporting unavailability) during the incident window;

2. Pinnacle's claimed duration — the outage duration stated in Pinnacle's demand letter and supporting exhibits;

3. The resulting uptime percentage under each party's figures — calculated using total minutes in the relevant calendar month as the denominator; and

4. The corresponding SLA credit tier — determined by reference to the tiered credit structure in Exhibit C, Section 3.2. Uptime percentages are calculated using the following denominators for each relevant calendar month: • October 2022: 31 days × 24 hours × 60 minutes = 44,640 total minutes • November 2022: 30 days × 24 hours × 60 minutes = 43,200 total minutes • January 2023: 31 days × 24 hours × 60 minutes = 44,64

IV. Incident-by-Incident Analysis A. Incident INC-4471 (October 12–13, 2022)

1. Pinnacle's Claimed Data. Pinnacle's demand letter asserts that Incident INC-4471 caused a service outage lasting 7 hours and 42 minutes (462 minutes), beginning at approximately 11:18 PM EDT on October 12, 2022 and concluding at approximately 7:00 AM EDT on October 13, 2022. Based on this claimed duration, Pinnacle calculates the October 2022 monthly uptime as follows: Uptime = (44,640 − 462) / 44,640 × 100 = 98.9

2. Sentinel's Recorded Data. Sentinel's telemetry data for October 2022 records the INC-4471 incident as a full outage lasting 4 hours and 11 minutes (251 minutes). Sentinel's incident log shows the full outage commencing at 11:18 PM EDT on October 12, 2022 — consistent with Pinnacle's reported start time — and full service restoration occurring at 3:29 AM EDT on October 13, 2022. All six Sentinel monitoring nodes co

3. Discrepancy Analysis. The discrepancy between Pinnacle's claimed duration and Sentinel's recorded duration for INC-4471 is 3 hours and 31 minutes (211 minutes). This is a significant discrepancy that materially affects the applicable credit tier, moving the October 2022 uptime from below 99.00% (Pinnacle's calculation) to the 99.00%–99.49% range (Sentinel's calculation) and reducing the credit from $36,000 to $24,

4. Conclusion. Based on Sentinel's independently recorded telemetry data, the correct SLA credit for Incident INC-4471 is $24,000 (20% of the monthly fee), assuming the credit request is deemed timely — a proposition that Lumos disputes. This represents a $12,000 reduction from Pinnacle's claimed credit of $36,000. If the timeliness defense succeeds, the credit for this incident would be $0. B. Incident INC-4602 (Nov

1. Pinnacle's Claimed Data. Pinnacle's demand letter asserts that Incident INC-4602 caused a service outage lasting 3 hours and 18 minutes (198 minutes) on November 28, 2022. Based on this claimed duration, Pinnacle calculates the November 2022 monthly uptime as follows: Uptime = (43,200 − 198) / 43,200 × 100 = 99.54% Pinnacle places November 2022 uptime within the 99.50%–99.89% credit tier and claims a credit of 10%

2. Sentinel's Recorded Data. Sentinel's telemetry data for November 2022 records the INC-4602 incident as a full outage lasting 1 hour and 47 minutes (107 minutes). Sentinel's incident log shows the full outage commencing at 2:14 PM EST on November 28, 2022 and full service restoration occurring at 4:01 PM EST on the same day. All six monitoring nodes confirmed platform availability by 4:01 PM EST. Based on Sentinel'

3. Discrepancy Analysis. The discrepancy between Pinnacle's claimed duration and Sentinel's recorded duration for INC-4602 is 1 hour and 31 minutes (91 minutes). While this is the smallest discrepancy in absolute terms among the four incidents, it is proportionally significant — Pinnacle's claimed duration is approximately 85% longer than the actual full-outage duration recorded by Sentinel. The pattern here mirrors

4. Conclusion. Based on Sentinel's independently recorded telemetry data, the correct SLA credit for Incident INC-4602 is $6,000 (5% of the monthly fee). This represents a $6,000 reduction from Pinnacle's claimed credit of $12,000. C. Incident INC-4815 (January 9–10, 2023)

1. Pinnacle's Claimed Data. Pinnacle's demand letter asserts that Incident INC-4815 caused a service outage lasting 11 hours and 5 minutes (665 minutes), beginning on the evening of January 9, 2023 and extending into January 10, 2023. Based on this claimed duration, Pinnacle calculates the January 2023 monthly uptime as follows: Uptime = (44,640 − 665) / 44,640 × 100 = 98.51% Pinnacle's demand letter states a claimed

2. Sentinel's Recorded Data. Sentinel's telemetry data for January 2023 records the INC-4815 incident as a full outage lasting 6 hours and 22 minutes (382 minutes). Sentinel's data reveals that the incident comprised two distinct outage windows: • Primary Outage Window: Commencing at 9:47 PM EST on January 9, 2023 and ending at 3:22 AM EST on January 10, 2023 (approximately 5 hours and 35 minutes). • Secondary Disrup

3. Discrepancy Analysis. The discrepancy between Pinnacle's claimed duration and Sentinel's recorded duration for INC-4815 is 4 hours and 43 minutes (283 minutes). This substantial discrepancy moves the January 2023 uptime from below 99.00% (Pinnacle's calculation) to the 99.00%–99.49% range (Sentinel's calculation), resulting in a one-tier reduction in the applicable credit. Sentinel's detailed telemetry data indica

4. Conclusion. Based on Sentinel's independently recorded telemetry data, the correct SLA credit for Incident INC-4815 is $24,000 (20% of the monthly fee). This represents a $12,000 reduction from Pinnacle's claimed credit of $36,000. D. Incident INC-5033 (March 3–5, 2023)

1. Pinnacle's Claimed Data. Pinnacle's demand letter asserts that Incident INC-5033 caused a service outage lasting 26 hours and 31 minutes (1,591 minutes), beginning on March 3, 2023 and extending through March 5, 2023. This is by far the longest and most consequential of the four claimed incidents, and it forms the foundation of Pinnacle's most significant consequential damages claims. Based on this claimed duratio

2. Sentinel's Recorded Data. Sentinel's telemetry data for March 2023 records the INC-5033 incident as a full outage lasting 14 hours and 8 minutes (848 minutes). This is substantially less than Pinnacle's claimed 26 hours and 31 minutes, representing a discrepancy of more than 12 hours. Sentinel's incident log shows the full outage commencing at 1:36 AM EST on March 3, 2023 and total service restoration occurring at

3. Discrepancy Analysis. The discrepancy between Pinnacle's claimed duration and Sentinel's recorded duration for INC-5033 is 12 hours and 23 minutes (743 minutes) — by far the largest discrepancy among the four incidents, both in absolute terms and as a proportion of the claimed duration. Pinnacle's claimed duration is approximately 88% longer than the full-outage duration recorded by Sentinel. This discrepancy has

4. Conclusion. Based on Sentinel's independently recorded telemetry data, the correct SLA credit for Incident INC-5033 is $36,000 (30% of the monthly fee). Both parties' calculations fall within the same credit tier (below 99.00%), so the credit amount is identical regardless of which party's figures are used. However, the dramatic discrepancy in uptime percentages (Pinnacle's 96.32% vs. Sentinel's 98.04%) is highly

V. Summary Comparison Table The following table summarizes the incident-by-incident comparison between Pinnacle's claimed outage data and Sentinel's independently recorded telemetry: Net Difference in SLA Credits: $120,000 (Pinnacle's claim) − $90,000 (Lumos's calculation) = $30,000 overstatement by Pinnacle. The $90,000 figure calculated using Sentinel's data represents a maximum figure that does not account for two

VI. Key Observations on Measurement Methodology Differences The systematic nature of the discrepancies between Pinnacle's claimed durations and Sentinel's recorded durations warrants several overarching observations regarding the parties' respective measurement methodologies. These observations are relevant not only to the SLA credit dispute but also to the broader credibility of Pinnacle's damages claims. A. Definit

VII. Impact on Lumos's Overall Exposure Analysis This uptime data analysis has significant implications for Lumos's overall exposure in the pending dispute with Pinnacle. Pinnacle's total demand, as set forth in its May 1, 2023 demand letter, is $2,870,000, comprising the following components: SLA Credit Component. As demonstrated in this memorandum, the SLA credit component of Pinnacle's demand is overstated by at l

VIII. Recommendations Based on the foregoing analysis, I recommend the following action items for the engagement team's consideration:

1. Preserve All Sentinel Data. Ensure that all raw telemetry exports, incident logs, availability reports, and associated metadata from Sentinel Uptime Services Inc. for the period September 2022 through April 2023 are fully preserved under the litigation hold issued on May 15, 2023. The litigation hold was communicated to Adriana Voss (General Counsel, Lumos), Thomas Kwan (VP of Engineering / SRE, Lumos), and Rachel

2. Obtain a Declaration or Certification from Brenda Hale. Contact Brenda Hale, Director of Client Engineering at Sentinel Uptime Services Inc., and arrange for the preparation of a sworn declaration or formal certification confirming: (a) Sentinel's monitoring methodology, including polling frequency, node distribution, outage-detection criteria, and status classification definitions; (b) the integrity and authentic

3. Request Pinnacle's Monitoring Data. In any discovery exchange, mediation information request, or pre-litigation correspondence, demand that Pinnacle produce: (a) the raw monitoring data and system logs underlying its claimed outage durations for all four incidents; (b) documentation of the monitoring tools, measurement protocols, and methodologies used by Pinnacle to determine outage start and end times; (c) all i

4. Request Brindoval Cloud Infrastructure LLC Records. Obtain or, if necessary, subpoena Brindoval Cloud Infrastructure LLC's change management logs, incident reports, network configuration change records, and customer notifications for the March 3–5, 2023 period. These records are essential to substantiating the third-party causation defense for INC-5033. Brindoval's own documentation of the BGP routing change that