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
09 Nov 2026 13:30 – 09 Nov 2026 15:59 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
0.988 ms
1.436 ms
0.999 ms
0.990 ms
1.023 ms
1.191 ms
1.415 ms
0.990 ms
0.984 ms
1.410 ms
1.390 ms
1.028 ms
1.368 ms
1.070 ms
0.981 ms
1.375 ms
0.964 ms
1.029 ms
1.415 ms
1.405 ms
0.994 ms
1.339 ms
0.963 ms
1.054 ms
1.009 ms
0.974 ms
0.976 ms
1.432 ms
1.385 ms
1.202 ms
0.974 ms
1.375 ms
0.989 ms
1.066 ms
2.622 ms
1.509 ms
1.183 ms
1.031 ms
0.958 ms
0.987 ms
1.351 ms
1.089 ms
1.002 ms
0.996 ms
0.984 ms
1.376 ms
1.348 ms
0.954 ms
1.353 ms
1.010 ms
1.380 ms
1.365 ms
1.021 ms
1.028 ms
1.412 ms
2.643 ms
1.359 ms
0.926 ms
0.968 ms
0.986 ms
0.974 ms
1.026 ms
1.369 ms
1.438 ms
1.038 ms
1.388 ms
0.986 ms
1.002 ms
1.013 ms
1.044 ms
1.423 ms
1.013 ms
0.980 ms
1.431 ms
0.990 ms
1.375 ms
0.980 ms
1.020 ms
1.482 ms
1.365 ms
0.964 ms
0.966 ms
1.034 ms
1.008 ms
1.059 ms
0.950 ms
1.002 ms
1.047 ms
18.629 ms
1.396 ms
1.358 ms
0.947 ms
0.998 ms
0.990 ms
1.335 ms
1.339 ms
1.490 ms
1.424 ms
0.971 ms
0.963 ms
1.594 ms
1.443 ms
1.426 ms
1.010 ms
0.995 ms
1.012 ms
1.460 ms
6.159 ms
1.350 ms
1.009 ms
1.022 ms
1.044 ms
1.093 ms
1.079 ms
1.366 ms
0.980 ms
1.124 ms
1.397 ms
1.097 ms
1.017 ms
0.989 ms
1.815 ms
1.390 ms
1.003 ms
1.046 ms
0.980 ms
1.406 ms
14.427 ms
1.413 ms
1.037 ms
1.402 ms
0.943 ms
13.743 ms
0.962 ms
6.090 ms
18.779 ms
1.455 ms
1.014 ms
1.378 ms
1.381 ms
1.355 ms
11.103 ms
7.471 ms
1.368 ms
0.978 ms
1.020 ms
1.373 ms
17.426 ms
1.381 ms
1.445 ms
1.430 ms
2.857 ms
1.412 ms
1.412 ms
1.389 ms
1.386 ms
1.446 ms
0.989 ms
1.028 ms
1.452 ms
0.984 ms
0.974 ms
1.447 ms
1.406 ms
0.969 ms
0.992 ms
1.391 ms
1.326 ms
1.364 ms
1.558 ms
1.005 ms
1.379 ms
0.996 ms
1.090 ms
0.994 ms
1.483 ms
0.987 ms
1.392 ms
1.408 ms
1.540 ms
1.010 ms
1.393 ms
9.496 ms
2.447 ms
1.058 ms
1.066 ms
1.041 ms
1.059 ms
1.969 ms
1.438 ms
1.593 ms
1.391 ms
1.017 ms
1.408 ms
1.002 ms
1.425 ms
0.990 ms
1.500 ms
1.021 ms
1.078 ms
18.430 ms
0.984 ms
0.994 ms
0.997 ms
11.541 ms
1.235 ms
1.385 ms
1.004 ms
1.404 ms
1.003 ms
1.035 ms
1.440 ms
0.991 ms
1.758 ms
0.995 ms
1.003 ms
1.069 ms
15.034 ms
1.387 ms
13.835 ms
1.029 ms
1.060 ms
1.050 ms
1.126 ms
0.960 ms
0.952 ms
1.390 ms
1.044 ms
1.374 ms
1.394 ms
1.263 ms
1.382 ms
0.994 ms
1.423 ms
1.426 ms
1.420 ms
1.426 ms
14.455 ms
1.474 ms
1.500 ms
0.994 ms
18.646 ms
13.723 ms
1.001 ms
1.025 ms
0.982 ms
0.968 ms
4.231 ms
1.380 ms
16.715 ms
1.470 ms
1.011 ms
11.063 ms
16.451 ms
1.408 ms
1.020 ms
5.320 ms
0.986 ms
0.977 ms
3.128 ms
1.422 ms
17.812 ms
1.002 ms
1.362 ms
19.391 ms
1.388 ms
1.365 ms
1.063 ms
15.853 ms
13.746 ms
0.957 ms
1.042 ms
1.010 ms
1.404 ms
1.367 ms
1.015 ms
13.635 ms
0.988 ms
11.114 ms
11.144 ms
1.453 ms
1.416 ms
1.013 ms
1.036 ms
1.487 ms
11.998 ms
9.749 ms
0.953 ms
1.423 ms
1.063 ms
15.410 ms
1.008 ms
8.988 ms
1.052 ms
1.143 ms
1.505 ms
1.361 ms
1.007 ms
1.424 ms
Network path / recorded observations
Network path observations.
25 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 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.113 msAS8002 · Stealth
0.132 msAS8002 · Stealth
Same responder
2
0.198 msAS8002 · Stealth
0.209 msAS8002 · Stealth
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.141 msAS8002 · Stealth
0.142 msAS8002 · Stealth
Same responder
2
0.188 msAS8002 · Stealth
0.201 msAS8002 · Stealth
Same responder
3
4.201 msAS13335 · Cloudflare
No reply
Not established
4
6.770 msAS13335 · Cloudflare
No reply
Not established
5
1.807 msAS13335 · Cloudflare
2.859 msAS13335 · Cloudflare
Different responders
6
1.332 msAS13335 · Cloudflare
1.373 msAS13335 · Cloudflare
Same responder
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.165 msAS8002 · Stealth
0.168 msAS8002 · Stealth
Same responder
2
0.182 msAS8002 · Stealth
0.179 msAS8002 · Stealth
Same responder
3
No reply
0.617 msAS13335 · Cloudflare
Not established
4
13.342 msAS13335 · Cloudflare
No reply
Not established
5
2.002 msAS13335 · Cloudflare
2.341 msAS13335 · Cloudflare
Different responders
6
No reply
1.321 msAS13335 · Cloudflare
Not established
7
1.663 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.
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
Stealth replies stable; external replies varied.
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
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.071 msUsual round trip before the event
Last recorded event RTT1.540 msLast successful event recording
Event p95 RTT13.777 ms95th percentile of successful recordings
Change from baseline+0.469 msLast event RTT compared with the baseline
Successful / expected recordings60 / 60Recorded 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.