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 23:20 – 05 Nov 2026 02: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
1.162 ms
1.330 ms
1.395 ms
1.203 ms
1.191 ms
1.434 ms
1.164 ms
1.499 ms
1.149 ms
1.117 ms
1.437 ms
1.315 ms
1.479 ms
1.134 ms
1.181 ms
1.390 ms
1.377 ms
1.357 ms
1.376 ms
1.442 ms
1.361 ms
1.342 ms
10.979 ms
1.398 ms
1.362 ms
1.152 ms
1.379 ms
1.408 ms
1.405 ms
1.127 ms
1.159 ms
1.150 ms
1.367 ms
1.369 ms
1.166 ms
1.168 ms
1.393 ms
1.481 ms
1.163 ms
5.768 ms
1.350 ms
1.139 ms
1.388 ms
1.388 ms
1.158 ms
1.169 ms
1.402 ms
1.217 ms
1.191 ms
1.417 ms
1.358 ms
1.373 ms
1.505 ms
1.145 ms
7.318 ms
1.332 ms
1.243 ms
1.241 ms
1.360 ms
1.911 ms
1.175 ms
1.127 ms
1.378 ms
1.144 ms
2.130 ms
1.402 ms
1.408 ms
1.358 ms
1.421 ms
1.350 ms
1.176 ms
1.352 ms
1.207 ms
1.141 ms
1.145 ms
1.175 ms
1.163 ms
1.370 ms
1.159 ms
1.160 ms
2.781 ms
1.232 ms
1.174 ms
1.168 ms
1.385 ms
1.382 ms
1.372 ms
1.375 ms
1.185 ms
1.167 ms
1.384 ms
1.236 ms
1.643 ms
1.203 ms
1.405 ms
1.420 ms
1.141 ms
1.345 ms
1.189 ms
1.374 ms
16.890 ms
1.392 ms
1.126 ms
1.168 ms
1.156 ms
1.371 ms
1.139 ms
1.409 ms
1.151 ms
1.141 ms
1.348 ms
1.174 ms
1.159 ms
1.382 ms
1.360 ms
1.186 ms
1.363 ms
1.805 ms
1.189 ms
4.278 ms
1.201 ms
3.147 ms
2.453 ms
18.987 ms
18.296 ms
19.153 ms
7.546 ms
19.718 ms
19.520 ms
1.338 ms
18.931 ms
11.529 ms
1.366 ms
1.362 ms
1.417 ms
1.137 ms
6.214 ms
1.321 ms
5.474 ms
1.199 ms
6.865 ms
5.320 ms
1.209 ms
1.322 ms
12.866 ms
1.392 ms
9.709 ms
7.054 ms
6.592 ms
12.713 ms
14.289 ms
16.825 ms
3.640 ms
7.651 ms
6.591 ms
16.774 ms
13.083 ms
2.085 ms
2.167 ms
6.057 ms
1.140 ms
1.370 ms
1.364 ms
1.998 ms
8.769 ms
19.746 ms
1.395 ms
1.142 ms
1.156 ms
1.192 ms
1.201 ms
16.780 ms
7.874 ms
17.592 ms
17.710 ms
1.433 ms
1.375 ms
1.351 ms
1.193 ms
1.396 ms
1.394 ms
3.397 ms
1.159 ms
1.450 ms
1.369 ms
1.140 ms
1.155 ms
12.537 ms
1.210 ms
7.552 ms
18.768 ms
2.490 ms
1.358 ms
1.141 ms
1.923 ms
1.178 ms
1.349 ms
1.158 ms
1.394 ms
1.159 ms
1.972 ms
1.165 ms
1.464 ms
1.363 ms
1.158 ms
1.185 ms
1.360 ms
1.187 ms
1.401 ms
1.159 ms
1.398 ms
1.391 ms
1.175 ms
1.423 ms
1.147 ms
1.360 ms
1.151 ms
2.230 ms
1.149 ms
1.475 ms
1.491 ms
1.351 ms
1.350 ms
1.183 ms
1.164 ms
1.146 ms
1.368 ms
1.165 ms
1.175 ms
1.163 ms
1.182 ms
1.177 ms
1.686 ms
1.367 ms
1.158 ms
1.376 ms
1.351 ms
1.378 ms
1.331 ms
1.354 ms
1.382 ms
1.178 ms
1.161 ms
1.505 ms
1.197 ms
1.191 ms
1.397 ms
1.357 ms
1.143 ms
1.402 ms
1.190 ms
1.164 ms
1.387 ms
1.369 ms
1.540 ms
1.243 ms
1.157 ms
1.139 ms
1.330 ms
1.135 ms
1.381 ms
1.458 ms
1.155 ms
1.169 ms
2.635 ms
1.201 ms
1.140 ms
1.357 ms
1.394 ms
1.599 ms
1.172 ms
1.256 ms
16.206 ms
3.763 ms
1.178 ms
1.161 ms
1.155 ms
1.142 ms
1.152 ms
1.375 ms
1.181 ms
1.160 ms
1.173 ms
1.153 ms
1.396 ms
1.144 ms
1.390 ms
1.155 ms
1.364 ms
1.408 ms
20.245 ms
1.381 ms
1.148 ms
1.359 ms
1.353 ms
1.394 ms
1.394 ms
1.394 ms
1.154 ms
1.346 ms
1.155 ms
1.385 ms
1.142 ms
1.362 ms
1.352 ms
1.354 ms
1.352 ms
1.382 ms
1.148 ms
1.179 ms
1.361 ms
1.149 ms
1.358 ms
1.137 ms
1.161 ms
1.400 ms
1.124 ms
15.203 ms
1.187 ms
1.483 ms
1.402 ms
1.382 ms
1.152 ms
1.370 ms
1.362 ms
1.148 ms
1.151 ms
1.365 ms
1.167 ms
1.342 ms
1.164 ms
19.532 ms
11.255 ms
2.922 ms
1.461 ms
1.215 ms
1.404 ms
1.180 ms
1.160 ms
1.220 ms
1.133 ms
1.228 ms
1.397 ms
1.376 ms
1.389 ms
1.254 ms
1.222 ms
1.161 ms
1.121 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.138 msAS8002 · Stealth
0.132 msAS8002 · Stealth
Same responder
2
0.197 msAS8002 · Stealth
0.180 msAS8002 · Stealth
Same responder
3
3.702 msAS13335 · Cloudflare
1.101 msAS13335 · Cloudflare
Same responder
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.119 msAS8002 · Stealth
0.112 msAS8002 · Stealth
Same responder
2
0.176 msAS8002 · Stealth
0.178 msAS8002 · Stealth
Same responder
3
4.061 ms
37.342 ms
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.201 msAS8002 · Stealth
0.161 msAS8002 · Stealth
Same responder
2
0.199 msAS8002 · Stealth
0.178 msAS8002 · Stealth
Same responder
3
18.579 ms
24.862 ms
Same responder
4
No reply
No reply
Not established
5
3.689 msAS13335 · Cloudflare
4.971 msAS13335 · Cloudflare
Different responders
6
No reply
1.615 msAS13335 · Cloudflare
Not established
7
1.898 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.356 msUsual round trip before the event
Last recorded event RTT1.163 msLast successful event recording
Event p95 RTT18.858 ms95th percentile of successful recordings
Change from baseline-0.192 msLast event RTT compared with the baseline
Successful / expected recordings110 / 110Recorded 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.