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
29 Oct 2026 15:40 – 29 Oct 2026 19:04 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.580 ms
1.393 ms
1.374 ms
1.382 ms
1.392 ms
1.401 ms
1.386 ms
1.370 ms
1.364 ms
1.383 ms
1.382 ms
1.374 ms
1.509 ms
1.357 ms
1.340 ms
1.351 ms
1.344 ms
1.374 ms
1.341 ms
5.154 ms
1.372 ms
1.399 ms
1.409 ms
1.407 ms
1.451 ms
1.365 ms
1.420 ms
1.381 ms
1.424 ms
1.365 ms
1.443 ms
1.351 ms
1.385 ms
1.363 ms
18.930 ms
1.404 ms
1.416 ms
1.479 ms
1.416 ms
1.372 ms
1.371 ms
1.429 ms
1.380 ms
1.416 ms
1.357 ms
1.455 ms
1.401 ms
1.408 ms
1.444 ms
1.370 ms
1.405 ms
1.349 ms
1.381 ms
1.341 ms
1.354 ms
1.389 ms
1.440 ms
6.187 ms
1.360 ms
1.359 ms
7.377 ms
1.436 ms
1.484 ms
1.371 ms
1.435 ms
1.381 ms
18.998 ms
1.372 ms
1.351 ms
1.340 ms
1.401 ms
1.384 ms
1.353 ms
1.410 ms
1.441 ms
1.402 ms
1.353 ms
1.362 ms
1.368 ms
1.414 ms
1.389 ms
1.411 ms
1.364 ms
1.516 ms
1.341 ms
1.418 ms
1.383 ms
1.431 ms
1.505 ms
1.357 ms
1.333 ms
1.395 ms
1.400 ms
1.352 ms
1.395 ms
1.362 ms
1.429 ms
1.343 ms
1.418 ms
1.336 ms
1.509 ms
1.315 ms
1.383 ms
1.360 ms
1.340 ms
1.352 ms
1.445 ms
1.508 ms
1.388 ms
1.353 ms
1.371 ms
1.427 ms
1.347 ms
1.374 ms
1.428 ms
1.370 ms
1.349 ms
1.363 ms
1.384 ms
1.715 ms
1.432 ms
12.851 ms
1.370 ms
13.241 ms
1.401 ms
1.372 ms
1.339 ms
1.409 ms
1.414 ms
1.446 ms
1.443 ms
1.497 ms
1.397 ms
1.409 ms
1.394 ms
1.407 ms
1.348 ms
1.450 ms
1.340 ms
1.411 ms
1.382 ms
10.862 ms
1.531 ms
1.382 ms
3.235 ms
2.625 ms
1.471 ms
1.367 ms
2.047 ms
1.423 ms
5.220 ms
1.444 ms
1.328 ms
1.333 ms
1.321 ms
1.402 ms
1.422 ms
1.505 ms
1.416 ms
1.419 ms
1.351 ms
1.378 ms
1.386 ms
1.361 ms
1.675 ms
1.975 ms
1.357 ms
1.377 ms
1.366 ms
1.375 ms
1.387 ms
1.411 ms
3.332 ms
1.358 ms
1.347 ms
1.332 ms
1.483 ms
1.787 ms
1.425 ms
1.405 ms
14.435 ms
1.475 ms
1.400 ms
3.880 ms
1.341 ms
1.372 ms
1.430 ms
1.571 ms
1.436 ms
1.354 ms
13.629 ms
1.363 ms
1.415 ms
11.343 ms
1.466 ms
1.335 ms
16.547 ms
1.409 ms
1.419 ms
1.465 ms
9.185 ms
1.342 ms
1.586 ms
5.037 ms
19.703 ms
17.231 ms
1.351 ms
1.577 ms
1.369 ms
1.384 ms
1.415 ms
1.360 ms
1.343 ms
18.408 ms
1.362 ms
1.367 ms
1.393 ms
1.408 ms
1.331 ms
1.362 ms
1.319 ms
1.353 ms
1.394 ms
1.351 ms
1.383 ms
1.374 ms
1.408 ms
1.349 ms
1.570 ms
1.382 ms
1.336 ms
1.379 ms
1.322 ms
1.407 ms
1.401 ms
1.373 ms
1.358 ms
1.364 ms
1.462 ms
1.370 ms
1.403 ms
1.422 ms
1.491 ms
1.489 ms
1.531 ms
1.432 ms
1.521 ms
1.346 ms
1.369 ms
1.397 ms
1.367 ms
1.368 ms
1.378 ms
1.378 ms
1.385 ms
1.350 ms
1.393 ms
19.489 ms
1.390 ms
1.368 ms
1.374 ms
1.371 ms
1.394 ms
18.111 ms
20.917 ms
1.368 ms
1.394 ms
1.358 ms
18.223 ms
20.089 ms
6.338 ms
8.196 ms
1.380 ms
1.563 ms
1.369 ms
1.448 ms
1.372 ms
1.410 ms
1.363 ms
19.525 ms
1.375 ms
16.013 ms
1.373 ms
1.355 ms
1.547 ms
1.385 ms
1.444 ms
1.339 ms
1.366 ms
1.374 ms
1.347 ms
1.537 ms
1.421 ms
1.347 ms
1.379 ms
1.375 ms
1.343 ms
1.375 ms
1.364 ms
1.457 ms
1.372 ms
1.392 ms
1.492 ms
1.358 ms
1.337 ms
1.353 ms
1.361 ms
1.354 ms
1.378 ms
1.424 ms
1.396 ms
1.397 ms
1.396 ms
1.337 ms
1.363 ms
1.377 ms
1.445 ms
1.426 ms
1.369 ms
2.064 ms
7.984 ms
1.365 ms
1.410 ms
1.486 ms
1.454 ms
1.407 ms
1.462 ms
1.378 ms
18.851 ms
1.540 ms
2.568 ms
1.373 ms
1.368 ms
1.385 ms
1.345 ms
1.419 ms
1.647 ms
1.357 ms
1.407 ms
1.362 ms
1.405 ms
1.353 ms
1.346 ms
1.379 ms
1.346 ms
1.484 ms
1.361 ms
1.348 ms
1.390 ms
1.322 ms
1.509 ms
1.499 ms
1.368 ms
2.158 ms
1.349 ms
1.547 ms
1.364 ms
1.378 ms
1.748 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.
TCP traceroute / 443 · 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.171 msAS8002 · Stealth
0.161 msAS8002 · Stealth
Same responder
2
0.259 msAS8002 · Stealth
0.198 msAS8002 · Stealth
Same responder
3
17.796 msAS13335 · Cloudflare
No reply
Not established
4
No reply
No reply
Not established
5
2.077 msAS13335 · Cloudflare
2.036 msAS13335 · Cloudflare
Different responders
6
No reply
1.806 msAS13335 · Cloudflare
Not established
7
1.569 msAS13335 · Cloudflare
Not recorded
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.328 msAS8002 · Stealth
0.139 msAS8002 · Stealth
Same responder
2
0.182 msAS8002 · Stealth
0.187 msAS8002 · Stealth
Same responder
3
5.151 msAS13335 · Cloudflare
2.469 ms
Same responder
4
No reply
No reply
Not established
5
4.019 msAS13335 · Cloudflare
3.753 msAS13335 · Cloudflare
Different responders
6
No reply
1.349 msAS13335 · Cloudflare
Not established
7
1.513 msAS13335 · Cloudflare
Not recorded
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.
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.387 msUsual round trip before the event
Last recorded event RTT1.370 msLast successful event recording
Event p95 RTT13.065 ms95th percentile of successful recordings
Change from baseline-0.017 msLast event RTT compared with the baseline
Successful / expected recordings170 / 170Recorded 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.