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
02 Nov 2026 02:30 – 02 Nov 2026 04:59 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
22.822 ms
22.843 ms
22.855 ms
22.854 ms
22.880 ms
22.784 ms
22.852 ms
22.854 ms
22.883 ms
22.805 ms
22.856 ms
22.815 ms
22.818 ms
22.853 ms
22.829 ms
22.844 ms
22.985 ms
22.805 ms
22.870 ms
22.828 ms
22.825 ms
22.875 ms
22.846 ms
22.802 ms
22.939 ms
22.824 ms
22.810 ms
22.832 ms
22.813 ms
22.816 ms
22.826 ms
22.830 ms
22.887 ms
22.855 ms
22.822 ms
22.848 ms
23.035 ms
22.836 ms
22.871 ms
22.851 ms
22.814 ms
22.782 ms
22.840 ms
22.845 ms
22.916 ms
22.864 ms
22.879 ms
22.840 ms
23.091 ms
22.841 ms
22.789 ms
22.863 ms
22.831 ms
22.898 ms
22.871 ms
23.057 ms
23.021 ms
22.886 ms
22.921 ms
22.830 ms
22.793 ms
22.844 ms
21.878 ms
21.982 ms
21.919 ms
21.902 ms
21.914 ms
21.920 ms
22.905 ms
22.839 ms
22.837 ms
22.890 ms
22.828 ms
22.882 ms
22.847 ms
6.292 ms
6.318 ms
6.272 ms
6.271 ms
6.287 ms
6.279 ms
6.339 ms
6.264 ms
6.304 ms
6.281 ms
6.265 ms
6.309 ms
6.296 ms
6.253 ms
6.320 ms
6.276 ms
6.282 ms
6.278 ms
6.282 ms
6.267 ms
6.315 ms
6.320 ms
6.273 ms
6.260 ms
6.240 ms
6.271 ms
6.281 ms
6.262 ms
6.294 ms
6.270 ms
6.275 ms
6.327 ms
6.295 ms
6.259 ms
6.289 ms
6.269 ms
6.267 ms
6.290 ms
6.248 ms
6.260 ms
6.286 ms
6.278 ms
6.324 ms
6.286 ms
6.268 ms
6.288 ms
6.398 ms
6.461 ms
6.313 ms
6.326 ms
6.269 ms
6.262 ms
22.850 ms
22.820 ms
22.838 ms
22.918 ms
22.868 ms
22.906 ms
22.902 ms
22.827 ms
22.853 ms
22.856 ms
22.850 ms
22.805 ms
22.846 ms
22.834 ms
22.814 ms
22.866 ms
22.877 ms
22.889 ms
6.538 ms
6.544 ms
6.568 ms
6.533 ms
6.535 ms
6.556 ms
6.694 ms
6.654 ms
6.657 ms
6.658 ms
6.679 ms
6.648 ms
6.573 ms
6.595 ms
6.537 ms
6.532 ms
6.548 ms
6.554 ms
6.518 ms
6.535 ms
6.548 ms
6.566 ms
6.548 ms
6.578 ms
6.642 ms
6.551 ms
6.543 ms
6.539 ms
6.556 ms
6.533 ms
6.548 ms
6.539 ms
6.552 ms
6.534 ms
6.549 ms
6.555 ms
6.539 ms
6.544 ms
6.589 ms
6.546 ms
6.540 ms
6.534 ms
6.536 ms
6.550 ms
6.555 ms
6.533 ms
6.532 ms
6.537 ms
6.534 ms
6.604 ms
6.597 ms
6.531 ms
6.501 ms
6.513 ms
6.530 ms
6.522 ms
6.403 ms
6.385 ms
6.440 ms
6.396 ms
6.424 ms
6.387 ms
6.692 ms
6.711 ms
6.702 ms
6.700 ms
6.697 ms
6.742 ms
6.735 ms
6.596 ms
6.585 ms
6.578 ms
6.585 ms
6.622 ms
6.645 ms
6.745 ms
6.755 ms
6.703 ms
6.767 ms
6.738 ms
6.705 ms
6.733 ms
6.686 ms
6.753 ms
6.703 ms
6.786 ms
6.750 ms
6.767 ms
6.711 ms
6.722 ms
6.698 ms
6.703 ms
6.729 ms
6.773 ms
6.701 ms
6.729 ms
6.700 ms
6.726 ms
6.759 ms
6.721 ms
6.721 ms
6.730 ms
6.915 ms
6.752 ms
6.686 ms
6.698 ms
6.721 ms
6.691 ms
6.702 ms
6.727 ms
6.757 ms
6.718 ms
6.703 ms
6.771 ms
6.753 ms
6.686 ms
6.736 ms
6.731 ms
6.716 ms
6.776 ms
6.766 ms
6.702 ms
6.704 ms
6.716 ms
6.802 ms
6.779 ms
6.586 ms
6.584 ms
6.672 ms
22.883 ms
22.823 ms
22.839 ms
22.842 ms
22.851 ms
22.839 ms
22.822 ms
22.840 ms
22.875 ms
22.887 ms
22.816 ms
22.893 ms
22.800 ms
22.871 ms
22.833 ms
22.871 ms
22.830 ms
22.853 ms
22.835 ms
22.859 ms
22.848 ms
22.917 ms
22.860 ms
22.827 ms
22.860 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 3
Recorded trace · destination not reached by this trace
to UTC
TTL 1Probe hop0.126 msReply RTTAS8002 · Stealth
Before
TCP traceroute / 443 · Recorded address 3
Recorded trace · destination replied
to UTC
TTL 1Probe hop0.140 msReply RTTAS8002 · Stealth
TTL 2Probe hop43.732 msReply RTTASN unavailable
TTL 3Probe hop1.472 msReply RTTAS8075 · Microsoft
TTL 4Probe hop23.971 msReply RTTAS8075 · Microsoft
TTL 5Probe hop23.345 msReply RTTAS8075 · Microsoft
TTL 6Probe hop23.789 msReply RTTAS8075 · Microsoft
TTL 7Probe hop23.742 msReply RTTAS8075 · Microsoft
TTL 13Destination23.130 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.
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.138 msAS8002 · Stealth
0.140 msAS8002 · Stealth
Same responder
2
41.296 msAS8075 · Microsoft
1.188 msAS8075 · Microsoft
Same responder
3
1.087 msAS8075 · Microsoft
0.833 msAS8075 · Microsoft
Same responder
4
7.030 msAS8075 · Microsoft
7.182 msAS8075 · Microsoft
Different responders
5
7.096 msAS8075 · Microsoft
No reply
Not established
6
67.588 msAS8075 · Microsoft
54.675 msAS8075 · Microsoft
Different responders
7
6.710 msAS8075 · Microsoft
No reply
Not established
8
No reply
No reply
Not established
9
No reply
No reply
Not established
10
No reply
No reply
Not established
11
No reply
No reply
Not established
12
6.528 msAS8075 · Microsoft
6.150 msAS8075 · Microsoft
Same responder
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.532 msUsual round trip before the event
Last recorded event RTT6.549 msLast successful event recording
Event p95 RTT22.890 ms95th percentile of successful recordings
Change from baseline+0.017 msLast event RTT compared with the baseline
Successful / expected recordings60 / 60Recorded 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.
