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
06 Nov 2026 18:35 – 06 Nov 2026 21: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.
Recorded at (UTC)
RTT
15.950 ms
1.405 ms
3.092 ms
0.990 ms
0.975 ms
1.384 ms
0.939 ms
1.079 ms
0.992 ms
0.978 ms
0.977 ms
1.415 ms
19.946 ms
0.946 ms
0.932 ms
0.958 ms
0.970 ms
1.165 ms
0.983 ms
1.434 ms
13.859 ms
13.948 ms
19.235 ms
0.999 ms
1.000 ms
1.414 ms
17.816 ms
8.442 ms
9.159 ms
10.173 ms
0.987 ms
1.005 ms
2.084 ms
21.354 ms
1.044 ms
1.387 ms
0.976 ms
1.431 ms
15.605 ms
1.425 ms
1.497 ms
14.835 ms
1.067 ms
0.950 ms
1.366 ms
1.413 ms
1.359 ms
0.982 ms
1.558 ms
7.029 ms
6.109 ms
1.443 ms
1.511 ms
0.966 ms
1.037 ms
15.184 ms
1.088 ms
2.666 ms
1.406 ms
1.834 ms
1.413 ms
1.112 ms
8.830 ms
2.265 ms
2.194 ms
0.988 ms
9.216 ms
1.384 ms
0.988 ms
1.439 ms
1.014 ms
9.121 ms
1.015 ms
1.054 ms
1.419 ms
0.953 ms
0.944 ms
10.469 ms
0.999 ms
0.954 ms
1.391 ms
1.160 ms
1.050 ms
1.028 ms
1.038 ms
16.965 ms
20.246 ms
1.007 ms
1.004 ms
1.120 ms
0.962 ms
1.028 ms
1.430 ms
1.387 ms
0.967 ms
1.415 ms
1.027 ms
1.366 ms
1.463 ms
1.432 ms
0.998 ms
1.364 ms
1.032 ms
1.018 ms
1.386 ms
1.382 ms
1.052 ms
1.024 ms
1.122 ms
1.022 ms
1.081 ms
0.986 ms
1.366 ms
1.427 ms
0.935 ms
1.400 ms
1.434 ms
1.374 ms
0.976 ms
1.558 ms
1.007 ms
1.405 ms
1.085 ms
1.405 ms
1.419 ms
1.378 ms
1.380 ms
7.406 ms
1.367 ms
1.409 ms
4.376 ms
1.425 ms
1.029 ms
1.004 ms
14.567 ms
1.364 ms
1.457 ms
0.963 ms
5.491 ms
0.954 ms
1.048 ms
2.410 ms
18.396 ms
1.018 ms
1.364 ms
1.380 ms
0.976 ms
0.983 ms
14.318 ms
1.531 ms
1.020 ms
1.422 ms
0.938 ms
1.380 ms
0.963 ms
1.381 ms
1.444 ms
1.713 ms
0.972 ms
1.399 ms
1.357 ms
1.432 ms
1.387 ms
1.063 ms
2.349 ms
1.369 ms
8.630 ms
1.090 ms
1.351 ms
1.005 ms
1.022 ms
1.468 ms
0.989 ms
0.980 ms
1.000 ms
1.368 ms
1.476 ms
1.389 ms
1.352 ms
0.987 ms
1.393 ms
1.444 ms
0.988 ms
1.071 ms
1.312 ms
1.030 ms
1.077 ms
1.399 ms
4.127 ms
1.009 ms
1.477 ms
0.960 ms
1.040 ms
1.158 ms
1.395 ms
0.977 ms
1.053 ms
1.359 ms
1.379 ms
1.536 ms
1.389 ms
1.362 ms
1.362 ms
1.036 ms
1.413 ms
1.386 ms
1.365 ms
1.368 ms
1.354 ms
1.427 ms
0.996 ms
1.502 ms
1.374 ms
1.052 ms
0.966 ms
1.007 ms
14.730 ms
1.478 ms
1.017 ms
1.422 ms
1.023 ms
1.000 ms
0.977 ms
1.392 ms
1.102 ms
1.404 ms
1.027 ms
0.987 ms
0.961 ms
1.411 ms
1.355 ms
1.006 ms
1.548 ms
1.029 ms
0.964 ms
1.008 ms
1.044 ms
1.410 ms
9.508 ms
0.964 ms
1.078 ms
1.463 ms
0.976 ms
0.999 ms
1.046 ms
1.387 ms
1.361 ms
1.414 ms
1.407 ms
1.374 ms
1.029 ms
1.003 ms
2.836 ms
3.535 ms
20.032 ms
1.012 ms
20.466 ms
1.004 ms
1.125 ms
0.985 ms
1.423 ms
0.994 ms
1.029 ms
1.069 ms
1.117 ms
1.419 ms
13.680 ms
1.103 ms
0.999 ms
1.382 ms
1.055 ms
1.424 ms
0.976 ms
0.960 ms
1.026 ms
1.376 ms
1.095 ms
0.999 ms
1.424 ms
1.414 ms
1.382 ms
0.992 ms
1.018 ms
1.008 ms
1.353 ms
0.992 ms
1.003 ms
0.999 ms
1.036 ms
1.422 ms
1.393 ms
1.374 ms
0.976 ms
1.399 ms
1.048 ms
1.044 ms
1.022 ms
1.055 ms
1.229 ms
0.957 ms
1.461 ms
1.338 ms
1.372 ms
1.490 ms
14.306 ms
1.029 ms
1.004 ms
1.374 ms
17.100 ms
1.009 ms
2.377 ms
1.382 ms
1.378 ms
1.046 ms
3.337 ms
1.232 ms
1.030 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 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 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.143 msAS8002 · Stealth
0.169 msAS8002 · Stealth
Same responder
2
0.897 msAS8002 · Stealth
0.181 msAS8002 · Stealth
Same responder
3
12.617 msAS13335 · Cloudflare
31.112 msAS13335 · Cloudflare
Same responder
4
No reply
No reply
Not established
5
2.278 msAS13335 · Cloudflare
1.601 msAS13335 · Cloudflare
Different responders
6
1.254 msAS13335 · Cloudflare
No reply
Not established
7
Not recorded
1.839 msAS13335 · Cloudflare
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.165 msUsual round trip before the event
Last recorded event RTT1.359 msLast successful event recording
Event p95 RTT7.467 ms95th percentile of successful recordings
Change from baseline+0.194 msLast event RTT compared with the baseline
Successful / expected recordings80 / 80Recorded 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.
