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 17:50 – 04 Nov 2026 20: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.449 ms
6.395 ms
6.401 ms
6.432 ms
6.379 ms
6.410 ms
6.373 ms
6.406 ms
6.388 ms
6.381 ms
6.424 ms
6.400 ms
6.393 ms
6.401 ms
6.396 ms
6.387 ms
6.387 ms
6.423 ms
6.434 ms
6.427 ms
6.420 ms
6.400 ms
6.401 ms
6.437 ms
6.415 ms
6.464 ms
6.414 ms
6.425 ms
6.395 ms
6.465 ms
6.396 ms
6.445 ms
6.645 ms
6.666 ms
6.642 ms
6.679 ms
6.667 ms
6.688 ms
6.688 ms
6.656 ms
6.683 ms
6.654 ms
6.670 ms
6.670 ms
6.668 ms
6.656 ms
6.721 ms
6.674 ms
6.644 ms
6.669 ms
6.700 ms
6.656 ms
6.662 ms
6.669 ms
6.687 ms
6.667 ms
6.730 ms
6.646 ms
6.714 ms
6.661 ms
6.661 ms
6.669 ms
6.644 ms
6.666 ms
6.671 ms
6.682 ms
6.687 ms
6.657 ms
6.651 ms
6.694 ms
6.664 ms
6.680 ms
6.682 ms
6.678 ms
6.648 ms
6.677 ms
6.653 ms
6.660 ms
6.655 ms
6.753 ms
6.655 ms
6.665 ms
6.691 ms
6.662 ms
6.705 ms
6.675 ms
6.711 ms
6.663 ms
6.961 ms
6.683 ms
6.660 ms
6.695 ms
6.704 ms
6.661 ms
6.673 ms
6.686 ms
6.651 ms
6.642 ms
6.689 ms
6.727 ms
6.683 ms
6.663 ms
6.707 ms
6.688 ms
6.673 ms
6.711 ms
6.702 ms
6.387 ms
6.388 ms
6.388 ms
6.370 ms
6.388 ms
6.410 ms
6.373 ms
6.405 ms
6.395 ms
6.395 ms
6.454 ms
6.399 ms
6.393 ms
6.405 ms
6.422 ms
6.451 ms
6.401 ms
6.447 ms
6.410 ms
6.410 ms
6.384 ms
6.258 ms
22.824 ms
22.816 ms
22.877 ms
22.916 ms
22.843 ms
22.841 ms
22.875 ms
22.918 ms
22.877 ms
22.829 ms
22.866 ms
22.878 ms
22.837 ms
22.854 ms
22.861 ms
23.081 ms
22.915 ms
22.852 ms
22.882 ms
23.653 ms
22.879 ms
22.862 ms
22.843 ms
22.795 ms
22.845 ms
22.901 ms
22.836 ms
22.840 ms
22.798 ms
22.870 ms
22.850 ms
22.844 ms
22.834 ms
22.885 ms
22.853 ms
6.261 ms
6.269 ms
6.307 ms
6.260 ms
6.284 ms
6.317 ms
6.334 ms
6.292 ms
6.255 ms
6.273 ms
6.282 ms
6.276 ms
6.286 ms
6.305 ms
6.274 ms
6.281 ms
6.263 ms
6.254 ms
6.278 ms
6.290 ms
6.295 ms
6.291 ms
6.264 ms
6.260 ms
6.303 ms
6.691 ms
6.315 ms
6.260 ms
6.295 ms
6.246 ms
6.332 ms
6.358 ms
6.272 ms
6.271 ms
6.269 ms
6.268 ms
6.242 ms
6.245 ms
6.245 ms
6.278 ms
6.266 ms
6.262 ms
6.261 ms
6.275 ms
6.274 ms
6.307 ms
6.267 ms
6.284 ms
6.252 ms
6.265 ms
6.291 ms
6.250 ms
6.250 ms
6.341 ms
6.373 ms
6.281 ms
6.355 ms
6.268 ms
6.277 ms
6.281 ms
6.262 ms
6.283 ms
6.248 ms
6.275 ms
6.282 ms
6.254 ms
6.270 ms
6.260 ms
6.266 ms
6.263 ms
6.245 ms
6.310 ms
6.278 ms
18.110 ms
18.001 ms
17.978 ms
18.038 ms
18.019 ms
17.601 ms
17.590 ms
17.573 ms
17.604 ms
17.606 ms
17.569 ms
17.591 ms
17.710 ms
17.582 ms
17.591 ms
17.676 ms
17.667 ms
17.572 ms
17.591 ms
17.591 ms
17.608 ms
17.554 ms
17.599 ms
17.566 ms
6.722 ms
6.727 ms
6.727 ms
6.767 ms
6.718 ms
22.845 ms
22.855 ms
22.869 ms
22.907 ms
22.885 ms
22.797 ms
22.841 ms
22.834 ms
22.844 ms
22.843 ms
22.856 ms
22.848 ms
22.857 ms
22.830 ms
22.833 ms
22.908 ms
22.825 ms
22.852 ms
22.864 ms
22.827 ms
22.823 ms
22.813 ms
22.842 ms
22.826 ms
22.826 ms
22.895 ms
22.800 ms
22.823 ms
22.864 ms
22.843 ms
22.869 ms
22.838 ms
22.879 ms
22.931 ms
22.885 ms
22.856 ms
22.877 ms
22.858 ms
22.838 ms
22.842 ms
22.882 ms
22.815 ms
22.868 ms
22.911 ms
22.832 ms
22.849 ms
22.810 ms
22.913 ms
22.851 ms
22.833 ms
22.826 ms
22.875 ms
22.873 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 4
Recorded trace · destination not reached by this trace
TTL 13Destination22.953 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.
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.719 msUsual round trip before the event
Last recorded event RTT6.268 msLast successful event recording
Event p95 RTT22.915 ms95th percentile of successful recordings
Change from baseline-0.450 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.