AI connectivity.
In writing.

This addendum covers network latency and reachability from the Stealth NYC measurement point named in the service order to the listed public AI endpoints. The initial measurement point is Stealth’s monitoring location at 32 Avenue of the Americas, New York City.

A qualifying incident must be directly attributable to Stealth and affect the covered circuit’s connectivity through the relevant Stealth network path. Stealth investigates attribution using network telemetry, probe health, routing information and available corroborating evidence. Customers do not need access to Stealth’s internal systems to report an incident.

Public endpoints may resolve to CDN edges. This commitment does not measure model inference, API response generation or customer premises latency. TCP port 443 checks assess network reachability; they do not establish application availability.

The existing Dedicated Internet SLA continues to apply. This addendum adds the specific remedies below when included in your agreement.

Latency

Latency is assessed in fixed, nonoverlapping 5 minute intervals aligned to UTC. Each interval uses p95 from the underlying successful ICMP RTT recordings collected every 30 seconds. It requires at least 9 of the ten expected successful recordings. The calculation and any fixed calibration are recorded in the signed measurement schedule and remain fixed for that agreement.

A latency breach requires 3 consecutive qualifying intervals above the destination’s target, totaling 15 minutes, with the cause directly attributable to Stealth. The breach starts at the beginning of the first interval in that sequence, subject to the customer notice requirement below.

Reachability

A reachability breach requires 15 continuous minutes of unsuccessful TCP port 443 checks, with healthy collection and corroborating evidence that a Stealth network fault affects the covered circuit’s path to the destination. A failed ICMP response alone does not establish a reachability breach. General Internet connectivity need not be completely unavailable for an AI connectivity breach to qualify.

Missing measurements and recovery

Failed probes, missing recordings and unhealthy collection are assessed separately. Missing data is unconfirmed and is never counted as successful service or a zero RTT. An incomplete interval cannot establish latency compliance or recovery; available network and incident evidence is reviewed to determine the affected period.

The public graph shows five minute averages, and its summary statistics cover the available five day history. Those displays are observations, rather than an automatic determination of SLA eligibility. The contractual p95 uses underlying recordings for the intervals defined here.

1. Report the service issue to support.

   Before seeking a credit or cancellation under this addendum, email support@stealth.net. Include your company, account or circuit identifier, service address, affected endpoint, symptoms, when the issue began and a callback number. Stealth support is available 24/7.

2. Send the remedy request to billing.

   For a billing credit or cancellation, email billing@stealth.net. Reference the support case or original support email, identify the affected circuit and dates, and state whether you are requesting a credit or cancellation.

For this addendum, eligible degradation is counted from the time Stealth receives the customer’s initial support email about the issue, while the qualifying condition is present. Earlier periods do not count toward these additional remedies. Recurrences of the same reported issue can be linked to that case; keep support informed of the affected times. Website monitoring and a phone call do not replace the required email notice.

Stealth reviews the measurements and incident record and explains the outcome of the request. Support investigates the fault; billing handles the credit or disconnection request.

One or more verified qualifying breaches in a calendar month entitle the customer to a 10% credit against the affected circuit’s monthly recurring service fee, after the required support notification and billing request.

The AI connectivity credit is limited to 10% per circuit per calendar month. Multiple affected endpoints or incidents do not multiply that credit. If the same incident also qualifies for a Dedicated Internet SLA credit, the larger applicable credit applies; the same incident is not credited twice. Existing remedies for separate incidents remain subject to the applicable agreement.

Email the credit request to billing@stealth.net within 30 calendar days after the end of the affected month, referencing the earlier support notification. Installation charges and other nonrecurring charges are excluded from the credit calculation.

If Stealth directly causes qualifying degradation on the same covered circuit on 5 affected business days within any rolling 30 calendar day period, after the required support notification, the customer may cancel that circuit without an early termination charge or liability for the remaining minimum service term.

An affected business day has at least 60 cumulative minutes of verified qualifying degradation under this addendum. A business day is Monday through Friday, from midnight to midnight in America/New_York, excluding observed US federal holidays. Overlapping incidents count only once toward affected minutes; each business day counts once. Separate covered destinations may contribute qualifying time on the same circuit. Weekend and holiday incidents can still qualify for credits.

Email the cancellation request to billing@stealth.net within 30 calendar days after the fifth affected business day, referencing the original support notice and affected dates. The customer can request an effective disconnection date within 30 calendar days of that email. Once this threshold has been met, later recovery does not remove the earned cancellation right during that request period.

No additional cure period applies after qualification. Stealth will not recapture previously waived installation charges because of an eligible cancellation. Charges for service provided through the effective disconnection date remain payable, subject to applicable credits. Other circuits remain under their existing agreements.

Provider application failures, inference delays, authentication errors, usage limits, customer equipment or LAN faults, and faults outside Stealth’s responsibility do not qualify as Stealth network breaches. An exclusion requires attribution evidence; a provider name or an unanswered ICMP probe alone does not establish the cause. Planned maintenance and other excused events apply only as already defined in the customer’s governing agreement.

The signed order records the covered circuit, endpoint schedule, NYC measurement point, measurement method and addendum version. Changes to contractual destinations, targets or measurement methods require written agreement. The initial deployment uses one NYC monitoring location; this addendum does not represent it as multiple independent probes.

These terms add to the existing Dedicated Internet agreement and do not remove its existing termination rights or other remedies. No separate AI application uptime percentage, inference performance, packet loss or jitter guarantee is created by this addendum. The signed agreement governs service eligibility and remedies.