Measurement point: Stealth NYC, 32 Avenue of the Americas.
Published investigation. Updates run automatically.
01 / Network path
Network path.
Endpoint measurements / ICMP IPv4
Latency over time.
Successful endpoint RTT recordings from up to one hour before and after the event.
Enter time range
Times use the selected timezone; choices include recorded samples and intervals across the available chart.
Successful RTT recording Event interval
04 Nov 2026 00:50 – 04 Nov 2026 03:24 UTC. Hover or tap to inspect; drag across the chart to zoom. On touchscreens, first choose Select time range. Escape or Reset zoom restores the full range. Missing recordings are gaps; this is not an application availability or packet-loss chart.
Select a recording to explore nearby path observations.
View recorded values
Successful ICMP IPv4 RTT recordings.
Recorded at (UTC)
RTT
6.257 ms
6.281 ms
6.263 ms
6.265 ms
6.243 ms
6.331 ms
6.251 ms
6.266 ms
6.292 ms
6.260 ms
6.253 ms
6.257 ms
6.259 ms
6.264 ms
6.265 ms
6.275 ms
6.258 ms
6.241 ms
6.326 ms
6.281 ms
6.252 ms
6.269 ms
6.279 ms
6.259 ms
6.266 ms
6.263 ms
6.257 ms
6.254 ms
6.255 ms
6.291 ms
6.261 ms
6.324 ms
6.278 ms
6.276 ms
6.323 ms
6.267 ms
6.296 ms
6.278 ms
6.290 ms
6.270 ms
6.282 ms
6.274 ms
6.267 ms
6.264 ms
6.315 ms
6.281 ms
6.280 ms
6.258 ms
6.257 ms
6.360 ms
6.275 ms
6.298 ms
6.272 ms
6.247 ms
6.259 ms
6.253 ms
6.289 ms
6.273 ms
6.278 ms
6.251 ms
6.257 ms
6.738 ms
6.713 ms
6.746 ms
6.735 ms
6.736 ms
6.724 ms
6.739 ms
6.713 ms
6.735 ms
6.756 ms
6.735 ms
6.732 ms
6.721 ms
6.771 ms
6.731 ms
6.726 ms
6.799 ms
6.745 ms
6.736 ms
6.747 ms
6.710 ms
6.716 ms
6.727 ms
6.724 ms
6.728 ms
6.771 ms
6.733 ms
6.718 ms
6.751 ms
6.737 ms
6.733 ms
6.744 ms
6.739 ms
6.727 ms
6.711 ms
6.733 ms
6.722 ms
6.801 ms
6.701 ms
6.727 ms
6.727 ms
6.736 ms
6.731 ms
6.765 ms
6.726 ms
6.763 ms
6.747 ms
6.749 ms
6.719 ms
6.714 ms
6.717 ms
6.725 ms
6.763 ms
6.734 ms
6.758 ms
6.738 ms
6.714 ms
6.725 ms
6.761 ms
6.751 ms
6.721 ms
6.717 ms
6.740 ms
6.734 ms
22.808 ms
22.871 ms
22.809 ms
22.828 ms
22.818 ms
22.854 ms
22.856 ms
22.781 ms
22.903 ms
22.818 ms
22.818 ms
22.821 ms
22.838 ms
22.858 ms
22.807 ms
22.809 ms
22.887 ms
22.835 ms
22.845 ms
23.055 ms
22.863 ms
22.840 ms
22.789 ms
22.867 ms
22.441 ms
22.346 ms
22.403 ms
22.406 ms
22.371 ms
22.398 ms
6.253 ms
6.308 ms
6.237 ms
6.326 ms
6.270 ms
6.284 ms
6.268 ms
6.274 ms
6.277 ms
6.267 ms
6.254 ms
6.273 ms
6.317 ms
6.125 ms
6.149 ms
6.131 ms
6.131 ms
6.124 ms
6.144 ms
6.336 ms
6.282 ms
6.285 ms
6.258 ms
6.302 ms
6.265 ms
6.296 ms
6.245 ms
6.269 ms
6.273 ms
6.267 ms
6.302 ms
6.115 ms
6.147 ms
6.139 ms
6.120 ms
6.144 ms
6.210 ms
6.251 ms
6.802 ms
6.266 ms
6.328 ms
6.319 ms
6.290 ms
6.261 ms
6.198 ms
6.141 ms
6.134 ms
6.119 ms
6.173 ms
6.141 ms
6.187 ms
6.161 ms
6.137 ms
6.149 ms
6.176 ms
6.164 ms
6.155 ms
6.144 ms
6.184 ms
6.153 ms
6.120 ms
6.149 ms
6.177 ms
6.140 ms
6.152 ms
6.239 ms
6.174 ms
6.172 ms
6.132 ms
6.126 ms
6.124 ms
6.123 ms
6.132 ms
6.572 ms
6.545 ms
6.522 ms
6.539 ms
6.548 ms
6.525 ms
6.567 ms
6.663 ms
6.551 ms
6.541 ms
6.540 ms
6.569 ms
6.582 ms
6.737 ms
6.724 ms
6.749 ms
6.722 ms
6.729 ms
6.729 ms
6.760 ms
6.735 ms
6.735 ms
22.821 ms
22.894 ms
22.867 ms
22.892 ms
22.842 ms
22.842 ms
22.894 ms
22.799 ms
22.799 ms
22.866 ms
22.832 ms
22.807 ms
22.955 ms
22.864 ms
22.797 ms
22.805 ms
22.848 ms
22.880 ms
22.831 ms
22.813 ms
22.837 ms
22.816 ms
22.820 ms
22.850 ms
22.846 ms
22.891 ms
22.853 ms
22.457 ms
22.452 ms
22.388 ms
22.401 ms
22.373 ms
22.377 ms
22.842 ms
22.817 ms
22.811 ms
22.828 ms
22.850 ms
22.850 ms
22.965 ms
22.810 ms
22.863 ms
22.845 ms
22.907 ms
22.815 ms
22.814 ms
22.853 ms
22.866 ms
22.836 ms
22.895 ms
22.830 ms
22.831 ms
22.847 ms
22.834 ms
22.881 ms
22.862 ms
22.863 ms
22.860 ms
Network path / recorded observations
Network path observations.
16 observations
Choose a measurement type to see the closest of the available sampled observations to the selected chart point. Each probe is separate and may follow a different path.
Before
ICMP traceroute · Recorded address 2
Recorded trace · destination not reached by this trace
to UTC
TTL 1Probe hop0.130 msReply RTTAS8002 · Stealth
Before
TCP traceroute / 443 · Recorded address 2
Recorded trace · destination replied
to UTC
TTL 1Probe hop0.199 msReply RTTAS8002 · Stealth
TTL 2Probe hop13.738 msReply RTTAS8075 · Microsoft
TTL 13Destination22.993 msReply RTTAS8075 · Microsoft
RTT is the round trip to each responding hop, not the delay of the preceding link. TTL order may omit routers and does not prove direct links. A missing reply is not proof of packet loss. ASN labels are dated address associations; they do not establish the forwarding path or the operator at the event time. Up to three recorded traces per method and period are selected across the archive. Where no individual trace is available, a comparison may summarize a window; MTR observations aggregate multiple probes. Address aliases are independent across measurement types.
Same method / same recorded address
Compare the traces.
Compare one selected trace from before the event with one during it. Values are individual replies, not a statistical comparison.
ICMP traceroute · Recorded address 3
Before: UTC · During: UTC
Same destination address and probe method. A matching TTL does not establish the same forwarding path.
TTL
Before RTT
During RTT
Responding address
1
0.109 msAS8002 · Stealth
0.121 msAS8002 · Stealth
Same responder
2
1.068 ms
0.868 ms
Same responder
3
1.063 msAS8075 · Microsoft
Not recorded
Not established
4
6.991 msAS8075 · Microsoft
Not recorded
Not established
TCP traceroute / 443 · Recorded address 3
Before: UTC · During: UTC
Same destination address and probe method. A matching TTL does not establish the same forwarding path.
TTL
Before RTT
During RTT
Responding address
1
0.205 msAS8002 · Stealth
0.142 msAS8002 · Stealth
Same responder
2
No reply
2.479 ms
Not established
3
1.012 msAS8075 · Microsoft
No reply
Not established
4
6.898 msAS8075 · Microsoft
7.432 msAS8075 · Microsoft
Different responders
5
No reply
8.888 msAS8075 · Microsoft
Not established
6
No reply
8.192 msAS8075 · Microsoft
Not established
7
No reply
8.064 msAS8075 · Microsoft
Not established
8
No reply
No reply
Not established
9
No reply
No reply
Not established
10
No reply
No reply
Not established
11
6.795 msAS8075 · Microsoft
No reply
Not established
12
Not recorded
6.465 msAS8075 · Microsoft
Not established
RTTs include the return path. Different responders, missing replies and independent probe flows limit what a change can localize. MTR snapshots remain separate in the replay.
Event timeline.
Possible SLA event. Times shown are UTC.
Event opened
UTC
Last event observation
UTC
Recovery observed
UTC
Recorded recovery describes this event, not current reachability.
02 / Assessment
Assessment.
Investigation stateRecovered
Path assessment
Elevated latency observed.
Endpoint round-trip time was elevated during part of the event. The available path observations do not identify where the increase occurred.
What we observed
A sustained increase in measured round trip time was observed.
The measured destination address changed across the comparison period.
Recording counts describe collected measurements, not application availability or packet loss. Exact packet paths and the return path remain unverified.
Measurements at a glance.
Baseline RTT6.696 msUsual round trip before the event
Last recorded event RTT6.139 msLast successful event recording
Event p95 RTT22.870 ms95th percentile of successful recordings
Change from baseline-0.557 msLast event RTT compared with the baseline
Successful / expected recordings69 / 70Recorded endpoint samples during the event
RTT is round trip time; p95 describes the upper range of successful recordings. Endpoint measurements differ from individual trace replies and are not an uptime percentage.
Record sources and timestamps
Analysis updated
UTC
Public snapshot published
UTC
Public observation window
– UTC
Event and source timestamps are UTC. The latency chart uses its selected timezone. Page refresh times are separate from measurement timestamps.
03 / Method and limits
Method and limits.
How to interpret the sampled path and its limits
Corroborating the path.
Comparisons use matching destinations before and during the event. ICMP traces use echo probes. TCP/443 traces send SYN probes to port 443 only; they do not complete a TCP handshake or perform a TLS or HTTP exchange.
The Stealth gNMI interface verifies the active route-table choice and maps its primary next hop to the Stealth logical interface, configured attachment and, where applicable, the known LAG member set at each snapshot. Stable Stealth replies, together with mapped interface evidence showing no corresponding errors or sustained capacity pressure, reduce the likelihood of a Stealth forwarding issue. An 80% load warning warrants investigation; it does not prove congestion. Lower interval averages can conceal bursts or queue pressure. Optical readings assess the physical link, not congestion.
What remains unseen.
Probe reply handling can differ from packet forwarding. A slow intermediate reply that disappears at later hops does not locate a forwarding problem. A destination that does not respond to a trace is not thereby shown to be unavailable.
Stealth does not use ECMP in this monitored scope. The route snapshot does not identify which physical LAG member carried a particular independent probe, attest line-card forwarding at that packet instant, prove the exact application packet flow or observe the return path. RTT includes the return path, which may differ. No remote reverse traceroute is available. Tunnels and silent routers may hide parts of the path. Address registration alone does not establish the forwarding operator or responsibility.