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 14:30 – 04 Nov 2026 17:29 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
1.358 ms
1.304 ms
1.302 ms
1.356 ms
1.410 ms
1.356 ms
1.343 ms
1.294 ms
1.470 ms
1.340 ms
1.361 ms
1.380 ms
1.336 ms
1.336 ms
1.348 ms
1.477 ms
1.385 ms
1.313 ms
1.343 ms
1.341 ms
1.371 ms
1.406 ms
1.311 ms
1.322 ms
1.396 ms
1.309 ms
1.340 ms
1.390 ms
1.395 ms
1.320 ms
1.333 ms
1.308 ms
1.369 ms
1.411 ms
1.366 ms
1.349 ms
1.330 ms
1.330 ms
1.364 ms
1.375 ms
1.371 ms
1.330 ms
1.344 ms
1.351 ms
1.290 ms
1.408 ms
1.326 ms
1.449 ms
1.316 ms
1.448 ms
1.447 ms
1.365 ms
1.324 ms
1.316 ms
1.532 ms
1.328 ms
1.351 ms
1.478 ms
1.325 ms
1.421 ms
1.323 ms
1.535 ms
1.417 ms
1.338 ms
1.319 ms
1.341 ms
1.335 ms
3.601 ms
1.338 ms
1.394 ms
1.367 ms
1.341 ms
1.416 ms
1.325 ms
9.994 ms
1.300 ms
1.441 ms
1.397 ms
1.402 ms
1.831 ms
1.321 ms
1.356 ms
1.408 ms
1.475 ms
1.331 ms
1.426 ms
1.399 ms
1.354 ms
1.393 ms
1.480 ms
1.329 ms
1.365 ms
1.363 ms
1.385 ms
1.395 ms
1.363 ms
1.371 ms
3.832 ms
1.348 ms
7.887 ms
1.429 ms
1.344 ms
1.379 ms
1.381 ms
1.339 ms
1.371 ms
1.395 ms
1.336 ms
1.478 ms
1.442 ms
1.449 ms
1.313 ms
1.495 ms
1.504 ms
1.392 ms
1.331 ms
1.380 ms
1.368 ms
2.209 ms
1.355 ms
1.345 ms
10.160 ms
1.455 ms
1.405 ms
1.471 ms
1.322 ms
1.409 ms
2.271 ms
1.333 ms
1.381 ms
3.132 ms
7.640 ms
1.375 ms
1.410 ms
1.353 ms
1.444 ms
1.358 ms
1.371 ms
1.954 ms
1.429 ms
1.359 ms
4.200 ms
10.153 ms
1.395 ms
1.361 ms
1.373 ms
1.327 ms
1.340 ms
1.378 ms
2.129 ms
1.435 ms
1.594 ms
1.410 ms
1.344 ms
1.341 ms
1.894 ms
4.707 ms
1.381 ms
5.928 ms
1.508 ms
9.012 ms
2.519 ms
1.322 ms
1.376 ms
1.408 ms
1.401 ms
1.300 ms
1.343 ms
1.378 ms
1.320 ms
1.333 ms
1.401 ms
1.296 ms
1.383 ms
1.350 ms
1.324 ms
1.392 ms
8.141 ms
2.960 ms
1.401 ms
1.321 ms
1.725 ms
2.304 ms
1.353 ms
1.331 ms
1.368 ms
1.403 ms
1.515 ms
1.338 ms
8.827 ms
1.326 ms
1.368 ms
1.329 ms
1.349 ms
6.659 ms
2.762 ms
1.320 ms
1.349 ms
1.435 ms
1.401 ms
1.661 ms
1.333 ms
1.460 ms
1.341 ms
1.427 ms
1.485 ms
1.344 ms
1.506 ms
1.341 ms
8.533 ms
1.338 ms
2.406 ms
1.314 ms
1.364 ms
1.573 ms
1.432 ms
1.400 ms
1.471 ms
1.395 ms
1.453 ms
1.462 ms
1.365 ms
1.409 ms
1.338 ms
1.410 ms
1.364 ms
1.359 ms
1.347 ms
1.499 ms
1.319 ms
1.464 ms
1.661 ms
1.331 ms
1.329 ms
1.314 ms
1.463 ms
1.373 ms
1.599 ms
1.399 ms
1.414 ms
1.406 ms
1.322 ms
1.358 ms
1.395 ms
1.515 ms
1.355 ms
1.373 ms
1.653 ms
1.362 ms
1.424 ms
1.445 ms
4.415 ms
1.399 ms
2.171 ms
1.402 ms
10.753 ms
1.330 ms
1.504 ms
1.324 ms
1.374 ms
1.427 ms
1.315 ms
1.459 ms
11.894 ms
1.398 ms
1.304 ms
1.333 ms
1.349 ms
1.351 ms
1.348 ms
1.416 ms
1.392 ms
1.911 ms
2.352 ms
1.556 ms
1.374 ms
1.430 ms
1.358 ms
1.458 ms
1.485 ms
1.359 ms
1.374 ms
1.422 ms
1.427 ms
1.320 ms
1.359 ms
1.411 ms
11.817 ms
1.503 ms
1.325 ms
3.805 ms
1.372 ms
1.316 ms
1.331 ms
1.443 ms
1.372 ms
1.351 ms
1.429 ms
1.347 ms
1.388 ms
5.854 ms
8.570 ms
1.401 ms
1.463 ms
1.379 ms
10.327 ms
1.313 ms
1.370 ms
1.378 ms
1.414 ms
1.365 ms
1.385 ms
1.361 ms
1.404 ms
6.383 ms
1.596 ms
1.333 ms
1.461 ms
1.386 ms
9.763 ms
1.377 ms
1.339 ms
1.331 ms
1.394 ms
1.327 ms
1.544 ms
1.344 ms
1.559 ms
1.338 ms
1.338 ms
1.328 ms
1.522 ms
1.343 ms
1.387 ms
1.339 ms
1.354 ms
1.557 ms
1.317 ms
1.327 ms
1.348 ms
1.333 ms
1.362 ms
1.299 ms
1.367 ms
1.355 ms
1.354 ms
1.428 ms
1.305 ms
1.369 ms
1.465 ms
1.318 ms
1.312 ms
3.297 ms
1.330 ms
1.458 ms
1.378 ms
1.341 ms
1.405 ms
1.328 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 1
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.131 msAS8002 · Stealth
0.121 msAS8002 · Stealth
Same responder
2
0.180 msAS8002 · Stealth
0.178 msAS8002 · Stealth
Same responder
3
0.943 ms
26.952 ms
Same responder
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.167 msAS8002 · Stealth
0.280 msAS8002 · Stealth
Same responder
2
0.180 msAS8002 · Stealth
0.199 msAS8002 · Stealth
Same responder
3
1.184 ms
63.562 ms
Same responder
4
No reply
1.594 msAS13335 · Cloudflare
Not established
5
1.514 msAS13335 · Cloudflare
No reply
Not established
6
3.734 msAS13335 · Cloudflare
No reply
Not established
7
Not recorded
No reply
Not established
8
Not recorded
No reply
Not established
9
Not recorded
No reply
Not established
10
Not recorded
No reply
Not established
11
Not recorded
No reply
Not established
12
Not recorded
No reply
Not established
13
Not recorded
No reply
Not established
14
Not recorded
No reply
Not established
15
Not recorded
No reply
Not established
16
Not recorded
No reply
Not established
17
Not recorded
No reply
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.211 msAS8002 · Stealth
0.166 msAS8002 · Stealth
Same responder
2
0.254 msAS8002 · Stealth
0.185 msAS8002 · Stealth
Same responder
3
No reply
19.286 msAS13335 · Cloudflare
Not established
4
No reply
No reply
Not established
5
4.291 msAS13335 · Cloudflare
1.457 msAS13335 · Cloudflare
Different responders
6
1.290 msAS13335 · Cloudflare
No reply
Not established
7
Not recorded
No reply
Not established
8
Not recorded
No reply
Not established
9
Not recorded
No reply
Not established
10
Not recorded
No reply
Not established
11
Not recorded
No reply
Not established
12
Not recorded
No reply
Not established
13
Not recorded
No reply
Not established
14
Not recorded
No reply
Not established
15
Not recorded
No reply
Not established
16
Not recorded
No reply
Not established
17
Not recorded
No reply
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.
Latency anomaly. 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.355 msUsual round trip before the event
Last recorded event RTT1.414 msLast successful event recording
Event p95 RTT7.665 ms95th percentile of successful recordings
Change from baseline+0.059 msLast event RTT compared with the baseline
Successful / expected recordings120 / 120Recorded 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.