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
03 Nov 2026 22:50 – 04 Nov 2026 01:29 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
6.733 ms
6.699 ms
6.684 ms
6.736 ms
6.719 ms
6.721 ms
6.741 ms
6.770 ms
22.882 ms
22.835 ms
22.846 ms
22.830 ms
22.874 ms
22.871 ms
22.902 ms
22.852 ms
6.402 ms
6.383 ms
6.404 ms
6.379 ms
6.434 ms
6.404 ms
6.413 ms
6.433 ms
6.421 ms
6.414 ms
6.416 ms
6.415 ms
6.431 ms
6.485 ms
6.372 ms
6.396 ms
6.382 ms
6.388 ms
6.391 ms
17.365 ms
17.398 ms
17.402 ms
17.387 ms
17.420 ms
17.378 ms
17.402 ms
17.394 ms
17.431 ms
17.420 ms
17.360 ms
17.420 ms
17.389 ms
17.405 ms
17.398 ms
6.268 ms
6.280 ms
6.306 ms
6.247 ms
6.248 ms
6.316 ms
6.302 ms
6.313 ms
6.252 ms
6.306 ms
6.321 ms
6.251 ms
6.276 ms
6.277 ms
22.907 ms
22.814 ms
22.872 ms
22.847 ms
22.844 ms
22.884 ms
22.806 ms
22.857 ms
22.848 ms
22.806 ms
22.819 ms
22.805 ms
22.851 ms
6.525 ms
6.552 ms
6.727 ms
6.663 ms
6.653 ms
6.668 ms
6.671 ms
6.675 ms
6.551 ms
6.576 ms
6.584 ms
6.536 ms
6.536 ms
6.529 ms
6.667 ms
6.657 ms
6.674 ms
6.691 ms
6.725 ms
6.671 ms
6.534 ms
6.539 ms
6.544 ms
6.542 ms
6.559 ms
6.552 ms
6.555 ms
6.552 ms
6.554 ms
6.549 ms
6.528 ms
6.542 ms
6.537 ms
6.554 ms
6.574 ms
6.554 ms
6.662 ms
6.540 ms
6.609 ms
6.530 ms
6.567 ms
6.537 ms
6.544 ms
6.528 ms
6.544 ms
6.549 ms
6.580 ms
6.562 ms
6.546 ms
6.529 ms
6.537 ms
22.861 ms
22.837 ms
22.798 ms
22.907 ms
22.820 ms
22.867 ms
22.866 ms
22.386 ms
22.429 ms
22.370 ms
22.420 ms
22.411 ms
22.393 ms
22.385 ms
22.353 ms
22.339 ms
22.425 ms
22.406 ms
22.389 ms
21.945 ms
21.920 ms
21.964 ms
21.944 ms
21.886 ms
21.929 ms
21.899 ms
21.988 ms
22.000 ms
21.910 ms
21.934 ms
21.985 ms
21.926 ms
22.882 ms
22.799 ms
22.811 ms
22.922 ms
22.853 ms
22.880 ms
6.523 ms
6.657 ms
6.647 ms
6.675 ms
6.667 ms
6.723 ms
6.665 ms
6.516 ms
6.527 ms
6.554 ms
6.519 ms
6.541 ms
6.534 ms
6.531 ms
6.511 ms
6.551 ms
6.511 ms
6.515 ms
6.505 ms
6.525 ms
6.561 ms
6.509 ms
6.492 ms
6.621 ms
6.538 ms
6.531 ms
6.522 ms
6.531 ms
6.547 ms
6.529 ms
6.528 ms
6.522 ms
6.567 ms
6.502 ms
6.522 ms
6.507 ms
6.526 ms
6.497 ms
6.641 ms
6.634 ms
6.637 ms
6.639 ms
6.656 ms
6.660 ms
6.675 ms
6.519 ms
6.822 ms
6.533 ms
6.516 ms
6.516 ms
6.607 ms
6.592 ms
6.510 ms
6.550 ms
6.547 ms
6.506 ms
6.495 ms
6.519 ms
6.561 ms
6.510 ms
6.533 ms
6.513 ms
6.508 ms
6.527 ms
6.557 ms
6.519 ms
6.531 ms
6.537 ms
6.515 ms
6.279 ms
6.257 ms
6.267 ms
6.257 ms
6.271 ms
6.257 ms
6.281 ms
6.263 ms
6.265 ms
6.243 ms
6.331 ms
6.251 ms
6.266 ms
6.292 ms
6.260 ms
6.253 ms
6.257 ms
6.259 ms
6.264 ms
6.265 ms
6.275 ms
6.258 ms
6.241 ms
6.326 ms
6.281 ms
6.252 ms
6.269 ms
6.279 ms
6.259 ms
6.266 ms
6.263 ms
6.257 ms
6.254 ms
6.255 ms
6.291 ms
6.261 ms
6.324 ms
6.278 ms
6.276 ms
6.323 ms
6.267 ms
6.296 ms
6.278 ms
6.290 ms
6.270 ms
6.282 ms
6.274 ms
6.267 ms
6.264 ms
6.315 ms
6.281 ms
6.280 ms
6.258 ms
6.257 ms
6.360 ms
6.275 ms
6.298 ms
6.272 ms
6.247 ms
6.259 ms
6.253 ms
6.289 ms
6.273 ms
6.278 ms
6.251 ms
6.257 ms
6.738 ms
6.713 ms
6.746 ms
6.735 ms
6.736 ms
6.724 ms
6.739 ms
6.713 ms
6.735 ms
6.756 ms
6.735 ms
6.732 ms
6.721 ms
6.771 ms
6.731 ms
6.726 ms
6.799 ms
6.745 ms
Network path / recorded observations
Network path observations.
16 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 6
Recorded trace · destination not reached by this trace
to UTC
TTL 1Probe hop0.129 msReply RTTAS8002 · Stealth
TTL 2Probe hop0.944 msReply RTTAS8075 · Microsoft
Before
TCP traceroute / 443 · Recorded address 6
Recorded trace · destination replied
to UTC
TTL 1Probe hop0.137 msReply RTTAS8002 · Stealth
TTL 2Probe hop2.693 msReply RTTAS8075 · Microsoft
TTL 3Probe hop45.653 msReply RTTAS8075 · Microsoft
TTL 12Destination6.675 msReply RTTAS8075 · Microsoft
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.
No same-address, same-method pair is available among the selected replay samples. This does not mean no other matching traces were recorded.
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.
The measured destination address changed across the comparison period.
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 RTT6.715 msUsual round trip before the event
Last recorded event RTT6.502 msLast successful event recording
Event p95 RTT22.868 ms95th percentile of successful recordings
Change from baseline-0.214 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.
