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
06 Nov 2026 19:45 – 06 Nov 2026 22: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.754 ms
6.745 ms
6.736 ms
6.753 ms
6.747 ms
6.774 ms
6.735 ms
6.755 ms
6.775 ms
6.793 ms
6.753 ms
6.763 ms
6.755 ms
6.786 ms
6.736 ms
6.759 ms
6.722 ms
6.725 ms
6.736 ms
6.741 ms
6.752 ms
6.740 ms
6.733 ms
6.720 ms
6.733 ms
6.742 ms
6.752 ms
6.768 ms
6.748 ms
6.755 ms
6.759 ms
6.810 ms
6.750 ms
6.829 ms
6.740 ms
6.729 ms
6.765 ms
6.816 ms
6.744 ms
6.727 ms
6.755 ms
6.729 ms
6.785 ms
6.728 ms
6.778 ms
6.784 ms
6.773 ms
6.788 ms
6.761 ms
6.746 ms
6.762 ms
6.770 ms
6.743 ms
6.600 ms
6.629 ms
6.626 ms
6.605 ms
6.640 ms
6.602 ms
6.622 ms
6.592 ms
6.600 ms
6.599 ms
6.602 ms
6.618 ms
6.583 ms
6.596 ms
6.665 ms
6.593 ms
6.600 ms
6.685 ms
6.607 ms
6.610 ms
6.618 ms
6.609 ms
6.641 ms
6.593 ms
6.613 ms
6.585 ms
6.612 ms
6.602 ms
6.617 ms
6.594 ms
6.625 ms
6.592 ms
6.616 ms
6.592 ms
6.619 ms
6.606 ms
6.583 ms
6.656 ms
6.623 ms
6.610 ms
6.585 ms
6.603 ms
6.585 ms
6.619 ms
6.699 ms
6.633 ms
6.610 ms
6.637 ms
6.618 ms
6.589 ms
6.647 ms
6.608 ms
6.597 ms
6.601 ms
6.578 ms
6.601 ms
6.637 ms
6.617 ms
6.640 ms
6.641 ms
6.637 ms
6.610 ms
6.611 ms
6.608 ms
6.587 ms
6.590 ms
6.594 ms
6.611 ms
6.583 ms
6.587 ms
6.575 ms
6.625 ms
17.663 ms
17.661 ms
17.692 ms
17.739 ms
17.711 ms
17.680 ms
17.691 ms
17.697 ms
17.701 ms
17.717 ms
17.681 ms
17.745 ms
17.705 ms
17.653 ms
17.746 ms
17.683 ms
17.693 ms
17.715 ms
17.713 ms
17.669 ms
17.715 ms
17.698 ms
17.677 ms
17.716 ms
17.683 ms
17.680 ms
17.791 ms
17.700 ms
17.658 ms
17.705 ms
17.676 ms
17.680 ms
17.665 ms
17.698 ms
17.723 ms
17.699 ms
17.689 ms
17.718 ms
17.723 ms
17.722 ms
17.697 ms
17.720 ms
17.669 ms
17.663 ms
17.694 ms
17.695 ms
17.747 ms
17.697 ms
17.680 ms
17.683 ms
17.668 ms
17.715 ms
17.692 ms
17.683 ms
17.778 ms
6.410 ms
6.420 ms
6.419 ms
6.384 ms
6.399 ms
6.400 ms
6.391 ms
6.398 ms
6.412 ms
6.398 ms
6.385 ms
6.384 ms
6.371 ms
6.390 ms
6.395 ms
6.423 ms
6.429 ms
6.379 ms
6.402 ms
6.367 ms
6.398 ms
6.384 ms
6.427 ms
6.370 ms
6.383 ms
6.419 ms
6.390 ms
6.412 ms
6.398 ms
6.421 ms
6.400 ms
6.392 ms
6.393 ms
6.377 ms
6.403 ms
6.385 ms
6.421 ms
6.440 ms
6.388 ms
6.387 ms
6.404 ms
6.371 ms
6.416 ms
6.383 ms
6.396 ms
6.415 ms
6.392 ms
6.392 ms
6.410 ms
6.364 ms
6.385 ms
6.374 ms
6.369 ms
6.422 ms
6.439 ms
6.385 ms
6.440 ms
6.374 ms
6.399 ms
6.383 ms
6.370 ms
6.374 ms
6.382 ms
6.375 ms
6.435 ms
6.412 ms
6.387 ms
6.413 ms
6.445 ms
6.496 ms
6.382 ms
6.395 ms
6.415 ms
6.413 ms
6.362 ms
6.402 ms
6.387 ms
6.425 ms
6.427 ms
6.421 ms
6.407 ms
6.444 ms
6.424 ms
6.374 ms
6.390 ms
6.423 ms
6.413 ms
6.387 ms
6.389 ms
6.391 ms
6.430 ms
6.386 ms
22.799 ms
22.814 ms
22.817 ms
22.839 ms
22.868 ms
22.849 ms
22.860 ms
22.930 ms
22.822 ms
22.847 ms
22.876 ms
22.810 ms
22.841 ms
22.818 ms
22.842 ms
22.814 ms
22.888 ms
22.875 ms
22.824 ms
22.844 ms
22.839 ms
22.799 ms
22.862 ms
22.811 ms
22.819 ms
22.812 ms
22.883 ms
22.816 ms
22.828 ms
22.848 ms
22.867 ms
22.841 ms
22.871 ms
22.843 ms
22.890 ms
22.823 ms
22.774 ms
22.870 ms
22.839 ms
22.857 ms
22.784 ms
22.889 ms
22.855 ms
22.862 ms
22.853 ms
22.893 ms
22.828 ms
22.892 ms
22.826 ms
22.776 ms
22.859 ms
22.859 ms
22.866 ms
22.823 ms
22.881 ms
22.941 ms
22.817 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 2
Recorded trace · destination not reached by this trace
TTL 13Destination22.890 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.
ICMP traceroute · Recorded address 3
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.130 msAS8002 · Stealth
0.127 msAS8002 · Stealth
Same responder
2
Not recorded
0.998 msAS8075 · Microsoft
Not established
TCP traceroute / 443 · Recorded address 3
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.149 msAS8002 · Stealth
Same responder
2
0.859 msAS8075 · Microsoft
No reply
Not established
3
0.929 msAS8075 · Microsoft
1.463 msAS8075 · Microsoft
Same responder
4
6.839 msAS8075 · Microsoft
7.212 msAS8075 · Microsoft
Same responder
5
No reply
No reply
Not established
6
6.854 msAS8075 · Microsoft
7.748 msAS8075 · Microsoft
Different responders
7
No reply
8.003 msAS8075 · Microsoft
Not established
8
No reply
No reply
Not established
9
No reply
No reply
Not established
10
No reply
No reply
Not established
11
6.957 msAS8075 · Microsoft
No reply
Not established
12
Not recorded
6.968 msAS8075 · Microsoft
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.
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.738 msUsual round trip before the event
Last recorded event RTT6.421 msLast successful event recording
Event p95 RTT17.743 ms95th percentile of successful recordings
Change from baseline-0.318 msLast event RTT compared with the baseline
Successful / expected recordings90 / 90Recorded 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.