Network observations.
Evidence in context.
A rolling 14-day record of sustained latency investigations from Stealth NYC to public AI service endpoints. Findings distinguish measured observations, supported assessments and unresolved conditions.
The record.
And its limits.
Collection health is shown alongside the findings. Missing evidence remains unknown.
Public snapshot published UTC · 671 seconds ago. Collection began UTC. Reload this page to retrieve the latest published record. Page load time is not a measurement timestamp.
What was observed.
What remains open.
Sustained anomalies and possible SLA events are tracked separately. Each destination is assessed on its own evidence.
No investigations
published yet.
Collection and evidence verification are shown above. An empty record does not establish that no latency event occurred.
An observation.
Then an assessment.
Findings are bounded by what the measurements can establish. Uncertainty remains visible.
- 01EndpointThe address actually measured
- 02ForwardingThe route observed at that time
- 03InterfacesState, traffic and counter changes
- 04OpticsReadings and reported thresholds
- 05AssessmentCorroboration, gaps and limits
What the evidence describes
Measurements originate from Stealth’s monitoring server at 32 Avenue of the Americas in New York City. Public AI hostnames may resolve to CDN edges or other shared service endpoints. ICMP RTT measures a network round trip to the responding address; it does not measure model inference or application response time.
A route snapshot describes the selected forwarding information at its observation time. Traces record responding hops along a candidate path. Load balancing, silent routers and return-path differences can leave parts of the path unresolved.
Interface error and discard changes, congestion indicators and optical readings can corroborate an investigation when they are available, fresh and mapped to the relevant path. Normal optical levels or unchanged physical error counters alone cannot rule out congestion.
What a finding means
An anomaly is a sustained change from an endpoint’s normal measured latency. A possible SLA event is a separate measurement flag for investigation. Neither label establishes a Stealth-attributable breach, customer eligibility or an application outage.
ICMP non-response alone does not establish an application outage. Intermediate-hop non-response is not treated as packet loss at the destination. A clear outbound Stealth path does not establish the return path or locate the remaining round trip delay.
Public summaries cover the latest 14 days. Detailed routes, router identifiers and technical evidence remain private under the 365-day retention policy. The signed agreement governs SLA eligibility, attribution and remedies.
Read the AI connectivity SLAMeasurement references: IETF round trip delay and path asymmetry · Measurement uncertainty and error. These references explain measurement limits; they do not certify this implementation.
A concern
about your connection?
Contact Stealth support with your circuit details, the destination and the time observed. The public investigation record does not replace a support notification.
Contact Stealth support