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
28 Oct 2026 22:15 – 29 Oct 2026 01: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.
Recorded at (UTC)
RTT
1.225 ms
1.358 ms
1.161 ms
1.154 ms
1.380 ms
8.217 ms
1.213 ms
4.769 ms
1.511 ms
15.978 ms
1.237 ms
1.394 ms
1.384 ms
1.386 ms
1.400 ms
1.421 ms
1.385 ms
1.224 ms
1.374 ms
1.475 ms
1.250 ms
1.414 ms
1.171 ms
1.187 ms
1.175 ms
1.239 ms
1.485 ms
1.225 ms
1.188 ms
1.238 ms
1.480 ms
1.171 ms
1.166 ms
1.239 ms
1.198 ms
1.462 ms
1.391 ms
1.373 ms
1.355 ms
1.458 ms
1.167 ms
1.316 ms
1.464 ms
1.177 ms
1.398 ms
1.260 ms
1.266 ms
1.444 ms
5.447 ms
1.172 ms
1.245 ms
1.253 ms
1.395 ms
1.628 ms
1.405 ms
1.235 ms
1.413 ms
1.419 ms
1.405 ms
1.430 ms
1.166 ms
1.466 ms
1.184 ms
1.193 ms
1.191 ms
1.391 ms
1.214 ms
1.420 ms
1.495 ms
1.409 ms
1.429 ms
1.222 ms
1.396 ms
1.337 ms
1.403 ms
1.374 ms
1.159 ms
1.410 ms
1.232 ms
1.465 ms
1.196 ms
1.201 ms
1.219 ms
1.406 ms
1.221 ms
1.443 ms
1.422 ms
1.183 ms
1.180 ms
1.222 ms
1.196 ms
1.427 ms
1.192 ms
1.433 ms
1.163 ms
1.200 ms
1.190 ms
1.239 ms
1.179 ms
1.234 ms
1.263 ms
1.181 ms
1.189 ms
2.444 ms
1.181 ms
1.198 ms
2.774 ms
1.428 ms
1.548 ms
1.417 ms
1.440 ms
1.387 ms
1.537 ms
1.498 ms
1.680 ms
1.523 ms
2.719 ms
1.444 ms
1.396 ms
1.250 ms
1.235 ms
5.967 ms
1.192 ms
16.428 ms
1.191 ms
1.415 ms
1.200 ms
8.531 ms
1.550 ms
1.207 ms
1.411 ms
3.793 ms
8.498 ms
1.424 ms
15.390 ms
1.218 ms
1.235 ms
1.197 ms
14.726 ms
1.166 ms
1.189 ms
1.200 ms
1.513 ms
1.385 ms
17.932 ms
1.415 ms
1.416 ms
1.448 ms
1.192 ms
1.183 ms
1.439 ms
1.401 ms
16.190 ms
1.208 ms
1.458 ms
1.398 ms
1.176 ms
1.450 ms
1.354 ms
1.400 ms
15.677 ms
8.666 ms
1.216 ms
1.166 ms
1.233 ms
1.185 ms
1.242 ms
1.368 ms
1.404 ms
2.809 ms
4.045 ms
1.256 ms
1.211 ms
1.399 ms
1.236 ms
1.412 ms
1.164 ms
1.384 ms
1.439 ms
1.193 ms
1.220 ms
1.406 ms
1.202 ms
1.210 ms
7.068 ms
1.164 ms
1.258 ms
1.212 ms
1.260 ms
1.251 ms
1.261 ms
1.228 ms
1.428 ms
1.189 ms
1.442 ms
1.198 ms
1.437 ms
1.424 ms
3.360 ms
1.166 ms
1.417 ms
1.408 ms
1.909 ms
1.191 ms
1.399 ms
1.198 ms
1.367 ms
1.303 ms
1.469 ms
1.233 ms
1.624 ms
1.318 ms
1.423 ms
1.177 ms
1.175 ms
1.441 ms
1.467 ms
1.236 ms
1.210 ms
1.404 ms
1.400 ms
1.252 ms
1.214 ms
1.177 ms
1.396 ms
1.289 ms
1.215 ms
1.197 ms
1.357 ms
1.417 ms
1.444 ms
1.364 ms
1.422 ms
1.211 ms
1.465 ms
1.378 ms
1.503 ms
1.165 ms
1.381 ms
1.450 ms
1.205 ms
1.378 ms
1.213 ms
1.454 ms
1.214 ms
1.187 ms
1.415 ms
1.223 ms
1.254 ms
1.540 ms
1.430 ms
1.386 ms
1.244 ms
1.400 ms
1.386 ms
1.437 ms
1.202 ms
1.424 ms
1.429 ms
1.252 ms
16.885 ms
1.261 ms
1.239 ms
1.270 ms
1.203 ms
1.435 ms
1.415 ms
1.369 ms
1.243 ms
1.415 ms
1.444 ms
1.195 ms
1.213 ms
6.110 ms
1.422 ms
18.834 ms
1.546 ms
1.196 ms
1.458 ms
1.273 ms
1.410 ms
1.195 ms
18.628 ms
1.190 ms
1.391 ms
1.185 ms
1.187 ms
1.414 ms
1.251 ms
1.218 ms
1.205 ms
1.424 ms
1.387 ms
1.209 ms
1.411 ms
10.149 ms
1.444 ms
5.114 ms
1.485 ms
1.415 ms
1.243 ms
1.576 ms
1.148 ms
1.238 ms
1.225 ms
1.200 ms
1.609 ms
1.202 ms
1.198 ms
1.511 ms
1.403 ms
1.431 ms
1.179 ms
1.215 ms
1.400 ms
1.418 ms
1.409 ms
1.379 ms
1.190 ms
1.426 ms
1.200 ms
1.204 ms
1.228 ms
1.401 ms
1.164 ms
1.142 ms
6.355 ms
1.218 ms
1.367 ms
1.394 ms
1.384 ms
1.186 ms
1.250 ms
1.533 ms
1.261 ms
1.421 ms
1.456 ms
1.412 ms
1.263 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 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.148 msAS8002 · Stealth
0.134 msAS8002 · Stealth
Same responder
2
0.220 msAS8002 · Stealth
0.183 msAS8002 · Stealth
Same responder
3
Not recorded
35.519 ms
Not established
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.147 msAS8002 · Stealth
0.148 msAS8002 · Stealth
Same responder
2
0.189 msAS8002 · Stealth
0.265 msAS8002 · Stealth
Same responder
3
No reply
10.928 msAS13335 · Cloudflare
Not established
4
1.843 msAS13335 · Cloudflare
No reply
Not established
5
1.911 msAS13335 · Cloudflare
1.583 msAS13335 · Cloudflare
Different responders
6
No reply
1.686 msAS13335 · Cloudflare
Not established
7
1.597 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.375 msUsual round trip before the event
Last recorded event RTT1.404 msLast successful event recording
Event p95 RTT14.759 ms95th percentile of successful recordings
Change from baseline+0.029 msLast event RTT compared with the baseline
Successful / expected recordings100 / 100Recorded 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.