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
05 Nov 2026 22:40 – 06 Nov 2026 01:39 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.411 ms
1.153 ms
1.407 ms
1.387 ms
1.163 ms
1.451 ms
1.157 ms
1.378 ms
1.122 ms
1.428 ms
1.433 ms
12.147 ms
1.422 ms
1.345 ms
1.497 ms
1.389 ms
1.353 ms
1.398 ms
1.137 ms
1.137 ms
1.185 ms
1.399 ms
1.150 ms
1.135 ms
1.167 ms
1.218 ms
1.421 ms
1.368 ms
1.171 ms
1.422 ms
1.115 ms
1.393 ms
1.146 ms
1.172 ms
1.398 ms
1.370 ms
1.168 ms
1.186 ms
1.365 ms
1.327 ms
1.362 ms
1.332 ms
1.247 ms
1.360 ms
1.379 ms
1.342 ms
1.156 ms
1.161 ms
1.417 ms
3.385 ms
1.371 ms
1.310 ms
1.715 ms
1.365 ms
1.138 ms
1.343 ms
1.165 ms
1.139 ms
1.365 ms
1.141 ms
1.375 ms
1.357 ms
1.402 ms
7.654 ms
1.409 ms
1.372 ms
1.306 ms
1.151 ms
1.141 ms
1.395 ms
1.331 ms
1.339 ms
1.146 ms
1.383 ms
1.450 ms
1.366 ms
1.151 ms
19.933 ms
1.358 ms
1.162 ms
1.349 ms
1.374 ms
1.137 ms
1.378 ms
1.414 ms
1.285 ms
1.429 ms
1.133 ms
1.139 ms
1.328 ms
1.365 ms
1.182 ms
1.139 ms
1.171 ms
1.147 ms
1.161 ms
1.574 ms
1.148 ms
1.365 ms
1.162 ms
1.146 ms
1.170 ms
1.362 ms
1.191 ms
1.132 ms
10.152 ms
1.131 ms
1.489 ms
1.459 ms
1.154 ms
1.438 ms
1.348 ms
1.394 ms
1.155 ms
1.416 ms
1.139 ms
1.143 ms
1.170 ms
1.329 ms
1.332 ms
1.137 ms
1.136 ms
1.346 ms
10.976 ms
1.137 ms
1.149 ms
1.480 ms
1.151 ms
1.368 ms
1.230 ms
1.369 ms
1.383 ms
1.361 ms
1.366 ms
1.187 ms
1.418 ms
1.424 ms
8.590 ms
1.155 ms
1.408 ms
1.158 ms
1.150 ms
1.406 ms
1.130 ms
7.236 ms
1.223 ms
1.400 ms
1.168 ms
1.308 ms
1.155 ms
1.370 ms
1.157 ms
1.145 ms
1.169 ms
1.147 ms
1.383 ms
1.183 ms
1.163 ms
1.249 ms
1.151 ms
1.372 ms
1.367 ms
1.166 ms
1.346 ms
1.360 ms
1.283 ms
1.206 ms
1.152 ms
1.485 ms
1.489 ms
15.982 ms
1.358 ms
1.147 ms
19.918 ms
1.157 ms
1.442 ms
1.206 ms
1.344 ms
1.166 ms
15.152 ms
1.147 ms
3.629 ms
2.290 ms
1.176 ms
1.419 ms
1.359 ms
1.667 ms
10.569 ms
1.176 ms
1.388 ms
1.429 ms
1.160 ms
1.370 ms
7.838 ms
1.335 ms
1.197 ms
1.186 ms
1.230 ms
1.361 ms
1.372 ms
1.132 ms
1.188 ms
1.382 ms
1.162 ms
1.293 ms
1.426 ms
1.338 ms
1.201 ms
5.271 ms
1.168 ms
1.148 ms
1.164 ms
1.428 ms
1.377 ms
1.566 ms
1.399 ms
1.145 ms
1.397 ms
1.153 ms
1.403 ms
1.157 ms
1.543 ms
1.157 ms
1.136 ms
1.383 ms
1.409 ms
1.588 ms
1.368 ms
1.335 ms
3.022 ms
1.328 ms
1.142 ms
1.369 ms
1.399 ms
1.340 ms
1.148 ms
1.206 ms
1.143 ms
1.347 ms
1.152 ms
1.125 ms
1.385 ms
1.388 ms
1.160 ms
1.181 ms
1.188 ms
1.154 ms
1.575 ms
1.181 ms
1.186 ms
1.186 ms
4.624 ms
1.384 ms
1.425 ms
1.440 ms
1.357 ms
1.169 ms
1.161 ms
1.190 ms
1.450 ms
1.182 ms
1.367 ms
1.132 ms
1.484 ms
1.164 ms
1.168 ms
1.185 ms
1.342 ms
1.414 ms
1.368 ms
1.397 ms
1.484 ms
1.165 ms
1.139 ms
1.149 ms
1.165 ms
1.335 ms
1.358 ms
1.319 ms
1.218 ms
1.160 ms
1.175 ms
1.181 ms
1.365 ms
1.897 ms
1.139 ms
1.148 ms
1.381 ms
1.422 ms
1.158 ms
1.168 ms
11.465 ms
1.147 ms
1.202 ms
1.137 ms
1.339 ms
1.318 ms
1.190 ms
1.285 ms
1.392 ms
1.499 ms
1.200 ms
2.854 ms
1.147 ms
1.393 ms
1.169 ms
1.327 ms
3.796 ms
1.382 ms
1.156 ms
1.156 ms
1.135 ms
1.419 ms
1.400 ms
1.698 ms
1.383 ms
1.424 ms
1.188 ms
1.301 ms
1.362 ms
1.369 ms
1.258 ms
1.331 ms
18.798 ms
1.372 ms
1.173 ms
1.368 ms
1.328 ms
1.359 ms
1.203 ms
1.357 ms
1.375 ms
1.462 ms
1.269 ms
1.162 ms
1.388 ms
1.139 ms
1.140 ms
1.350 ms
1.210 ms
1.165 ms
1.112 ms
1.146 ms
1.393 ms
1.388 ms
5.541 ms
1.367 ms
1.352 ms
1.376 ms
1.401 ms
1.600 ms
3.409 ms
1.365 ms
1.215 ms
1.371 ms
1.358 ms
1.159 ms
1.340 ms
Network path / recorded observations
Network path observations.
18 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.
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.124 msAS8002 · Stealth
0.206 msAS8002 · Stealth
Same responder
2
0.187 msAS8002 · Stealth
0.240 msAS8002 · Stealth
Same responder
3
34.090 ms
1.206 msAS13335 · Cloudflare
Same responder
4
5.049 msAS13335 · Cloudflare
Not recorded
Not established
5
2.943 msAS13335 · Cloudflare
Not recorded
Not established
6
1.239 msAS13335 · Cloudflare
Not recorded
Not established
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.131 msAS8002 · Stealth
0.119 msAS8002 · Stealth
Same responder
2
0.182 msAS8002 · Stealth
0.184 msAS8002 · Stealth
Same responder
3
1.111 ms
0.659 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.176 msAS8002 · Stealth
0.141 msAS8002 · Stealth
Same responder
2
0.177 msAS8002 · Stealth
0.188 msAS8002 · Stealth
Same responder
3
0.694 ms
1.521 ms
Same responder
4
No reply
No reply
Not established
5
6.754 msAS13335 · Cloudflare
2.105 msAS13335 · Cloudflare
Different responders
6
1.419 msAS13335 · Cloudflare
1.454 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.157 msAS8002 · Stealth
0.228 msAS8002 · Stealth
Same responder
2
0.178 msAS8002 · Stealth
0.186 msAS8002 · Stealth
Same responder
3
1.479 ms
1.935 msAS13335 · Cloudflare
Same responder
4
No reply
No reply
Not established
5
2.058 msAS13335 · Cloudflare
4.532 msAS13335 · Cloudflare
Different responders
6
1.172 msAS13335 · Cloudflare
1.406 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.
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.369 msUsual round trip before the event
Last recorded event RTT1.152 msLast successful event recording
Event p95 RTT7.875 ms95th percentile of successful recordings
Change from baseline-0.217 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.