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. Points are sampled from the retained history.
Enter time range
Times use the selected timezone; choices include recorded samples and intervals across the available chart.
Successful RTT recording Event interval
05 Nov 2026 13:00 – 05 Nov 2026 22:14 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; displayed points are a sample of the retained records.
Recorded at (UTC)
RTT
1.325 ms
1.369 ms
1.668 ms
1.334 ms
1.322 ms
1.450 ms
1.322 ms
1.345 ms
1.321 ms
1.433 ms
1.347 ms
1.338 ms
1.374 ms
1.332 ms
1.366 ms
1.359 ms
1.348 ms
1.328 ms
1.314 ms
1.314 ms
1.459 ms
1.363 ms
1.341 ms
1.325 ms
1.396 ms
1.415 ms
1.329 ms
1.382 ms
1.312 ms
1.326 ms
1.339 ms
1.337 ms
1.322 ms
1.345 ms
1.327 ms
1.322 ms
1.397 ms
1.346 ms
1.340 ms
1.340 ms
1.349 ms
1.321 ms
1.336 ms
1.331 ms
1.403 ms
1.392 ms
1.395 ms
1.389 ms
1.365 ms
1.326 ms
1.375 ms
1.331 ms
1.346 ms
13.957 ms
1.348 ms
1.371 ms
1.363 ms
1.344 ms
1.319 ms
1.339 ms
1.352 ms
1.342 ms
1.368 ms
1.330 ms
1.336 ms
1.328 ms
14.710 ms
19.194 ms
1.401 ms
1.326 ms
3.460 ms
1.358 ms
1.338 ms
1.436 ms
1.329 ms
1.382 ms
1.321 ms
1.523 ms
1.693 ms
1.352 ms
1.360 ms
1.365 ms
1.400 ms
1.312 ms
1.387 ms
1.466 ms
1.491 ms
1.330 ms
1.332 ms
1.415 ms
1.351 ms
1.387 ms
1.355 ms
1.344 ms
1.309 ms
1.325 ms
1.350 ms
1.334 ms
1.355 ms
1.352 ms
1.343 ms
11.297 ms
1.408 ms
1.374 ms
1.323 ms
1.407 ms
1.344 ms
6.579 ms
1.356 ms
1.357 ms
1.364 ms
1.320 ms
1.342 ms
1.362 ms
1.472 ms
1.385 ms
1.444 ms
4.211 ms
1.332 ms
1.357 ms
1.472 ms
1.483 ms
1.385 ms
1.378 ms
13.924 ms
1.337 ms
11.080 ms
1.369 ms
1.313 ms
1.332 ms
1.352 ms
1.340 ms
1.477 ms
5.730 ms
1.528 ms
1.327 ms
13.710 ms
1.388 ms
1.356 ms
14.308 ms
12.262 ms
1.343 ms
1.374 ms
1.633 ms
1.447 ms
1.329 ms
1.968 ms
1.304 ms
1.340 ms
1.931 ms
1.333 ms
1.400 ms
2.363 ms
1.406 ms
13.736 ms
1.343 ms
13.920 ms
1.347 ms
3.219 ms
9.925 ms
17.023 ms
16.318 ms
4.128 ms
19.883 ms
5.355 ms
15.845 ms
2.823 ms
15.485 ms
17.345 ms
1.337 ms
1.342 ms
16.327 ms
16.712 ms
19.976 ms
18.631 ms
10.358 ms
17.097 ms
1.351 ms
1.456 ms
1.395 ms
1.452 ms
1.498 ms
1.454 ms
19.782 ms
15.701 ms
19.001 ms
16.997 ms
16.241 ms
16.648 ms
1.326 ms
11.326 ms
1.331 ms
18.327 ms
1.338 ms
1.348 ms
1.436 ms
1.576 ms
19.315 ms
17.508 ms
1.340 ms
1.357 ms
16.526 ms
16.057 ms
1.362 ms
1.331 ms
1.921 ms
1.424 ms
16.359 ms
1.529 ms
1.319 ms
15.332 ms
1.437 ms
7.505 ms
6.440 ms
1.426 ms
1.346 ms
1.345 ms
1.323 ms
1.454 ms
1.362 ms
1.606 ms
1.477 ms
1.358 ms
1.340 ms
6.679 ms
1.473 ms
1.429 ms
1.334 ms
1.459 ms
1.349 ms
1.492 ms
1.381 ms
1.380 ms
1.353 ms
1.425 ms
1.335 ms
4.609 ms
1.334 ms
1.503 ms
1.358 ms
1.382 ms
1.397 ms
1.486 ms
1.332 ms
1.473 ms
1.349 ms
1.403 ms
1.357 ms
1.485 ms
1.329 ms
1.400 ms
1.347 ms
1.392 ms
1.508 ms
1.343 ms
1.356 ms
1.333 ms
1.340 ms
1.410 ms
1.379 ms
1.359 ms
1.411 ms
1.413 ms
11.320 ms
4.479 ms
3.950 ms
1.346 ms
1.423 ms
1.447 ms
1.332 ms
1.374 ms
1.381 ms
1.455 ms
1.354 ms
1.428 ms
1.497 ms
1.371 ms
1.383 ms
1.482 ms
1.395 ms
1.383 ms
1.350 ms
13.051 ms
1.329 ms
1.393 ms
1.423 ms
1.331 ms
1.365 ms
1.483 ms
1.373 ms
1.314 ms
1.321 ms
1.498 ms
1.539 ms
1.411 ms
1.374 ms
1.371 ms
1.396 ms
17.920 ms
17.623 ms
1.488 ms
1.434 ms
1.434 ms
1.350 ms
1.331 ms
1.369 ms
1.352 ms
1.370 ms
1.325 ms
1.345 ms
1.343 ms
1.379 ms
1.336 ms
1.361 ms
1.359 ms
1.352 ms
1.341 ms
1.371 ms
1.362 ms
1.411 ms
1.469 ms
1.605 ms
1.354 ms
5.111 ms
1.365 ms
1.375 ms
1.344 ms
1.450 ms
1.363 ms
1.317 ms
8.330 ms
1.345 ms
1.331 ms
1.316 ms
1.477 ms
1.406 ms
1.317 ms
1.370 ms
1.405 ms
1.369 ms
1.369 ms
1.348 ms
1.451 ms
1.370 ms
1.362 ms
1.374 ms
1.455 ms
1.482 ms
1.424 ms
1.369 ms
1.354 ms
1.422 ms
1.368 ms
1.314 ms
1.327 ms
1.348 ms
1.387 ms
1.337 ms
1.416 ms
Network path / recorded observations
Network path observations.
17 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
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 1
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.144 msAS8002 · Stealth
0.138 msAS8002 · Stealth
Same responder
2
0.187 msAS8002 · Stealth
0.206 msAS8002 · Stealth
Same responder
ICMP traceroute · Recorded address 2
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.157 msAS8002 · Stealth
0.143 msAS8002 · Stealth
Same responder
2
0.261 msAS8002 · Stealth
0.216 msAS8002 · Stealth
Same responder
3
Not recorded
54.919 ms
Not established
TCP traceroute / 443 · Recorded address 2
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.160 msAS8002 · Stealth
0.155 msAS8002 · Stealth
Same responder
2
0.199 msAS8002 · Stealth
0.391 msAS8002 · Stealth
Same responder
3
No reply
35.309 ms
Not established
4
No reply
No reply
Not established
5
2.625 msAS13335 · Cloudflare
2.185 msAS13335 · Cloudflare
Different responders
6
17.994 msAS13335 · Cloudflare
1.098 msAS13335 · Cloudflare
Same responder
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.
Stored traces were compared using matching source and destination addresses.
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 RTT1.374 msUsual round trip before the event
Last recorded event RTT1.358 msLast successful event recording
Event p95 RTT18.231 ms95th percentile of successful recordings
Change from baseline-0.016 msLast event RTT compared with the baseline
Successful / expected recordings860 / 870Recorded 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.