Start an order
Root cause analysis / Investigation

copilot.microsoft.com

Reference RCA-50F4A73665218B1A

Microsoft Chat website

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.

Use the recordings table below to view latency values.
Successful RTT recording Event interval

06 Nov 2026 13:35 – 06 Nov 2026 16:19 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.015 ms
1.349 ms
1.456 ms
0.976 ms
0.986 ms
1.191 ms
0.980 ms
1.382 ms
1.364 ms
1.391 ms
1.006 ms
1.406 ms
1.379 ms
1.397 ms
1.332 ms
1.351 ms
0.970 ms
3.019 ms
1.430 ms
1.378 ms
0.959 ms
1.019 ms
1.351 ms
1.337 ms
0.992 ms
0.936 ms
1.376 ms
1.440 ms
1.024 ms
1.417 ms
1.001 ms
1.003 ms
1.419 ms
1.379 ms
0.981 ms
1.375 ms
0.968 ms
1.436 ms
0.986 ms
1.377 ms
0.965 ms
1.082 ms
0.966 ms
15.963 ms
0.980 ms
1.009 ms
0.943 ms
1.348 ms
1.365 ms
1.391 ms
1.016 ms
1.356 ms
0.984 ms
1.391 ms
1.012 ms
1.394 ms
1.029 ms
1.445 ms
1.716 ms
0.990 ms
1.387 ms
1.388 ms
1.462 ms
1.039 ms
0.962 ms
1.060 ms
1.424 ms
1.025 ms
0.958 ms
1.336 ms
0.973 ms
0.972 ms
8.917 ms
1.351 ms
1.013 ms
0.936 ms
0.972 ms
0.998 ms
1.008 ms
1.110 ms
0.961 ms
0.992 ms
1.407 ms
1.043 ms
1.317 ms
0.944 ms
1.343 ms
1.440 ms
1.401 ms
1.404 ms
0.991 ms
0.970 ms
1.443 ms
1.332 ms
0.975 ms
1.381 ms
0.985 ms
1.418 ms
0.988 ms
1.133 ms
1.000 ms
0.983 ms
1.647 ms
1.384 ms
1.361 ms
0.930 ms
0.980 ms
1.349 ms
1.409 ms
0.940 ms
0.985 ms
0.960 ms
0.950 ms
1.370 ms
3.903 ms
1.433 ms
1.398 ms
1.377 ms
0.949 ms
1.021 ms
13.532 ms
1.415 ms
1.056 ms
1.333 ms
1.368 ms
5.208 ms
1.379 ms
1.392 ms
1.326 ms
0.991 ms
0.967 ms
1.038 ms
1.414 ms
0.959 ms
1.026 ms
1.359 ms
1.548 ms
1.478 ms
1.467 ms
16.974 ms
1.408 ms
0.955 ms
1.395 ms
1.415 ms
1.064 ms
1.385 ms
1.088 ms
0.958 ms
1.344 ms
17.955 ms
1.018 ms
1.030 ms
4.735 ms
0.953 ms
10.429 ms
0.964 ms
1.014 ms
0.982 ms
0.980 ms
17.528 ms
1.354 ms
1.509 ms
1.383 ms
1.397 ms
1.063 ms
1.354 ms
0.990 ms
0.995 ms
0.969 ms
1.366 ms
1.063 ms
0.973 ms
1.368 ms
14.231 ms
14.116 ms
1.400 ms
14.202 ms
0.947 ms
0.955 ms
0.974 ms
1.595 ms
1.005 ms
1.008 ms
1.032 ms
1.049 ms
0.960 ms
1.063 ms
1.367 ms
1.388 ms
1.351 ms
1.090 ms
1.372 ms
1.382 ms
1.361 ms
1.335 ms
1.367 ms
1.361 ms
1.365 ms
0.985 ms
0.965 ms
1.462 ms
1.355 ms
1.010 ms
1.583 ms
2.218 ms
1.007 ms
0.960 ms
1.414 ms
1.021 ms
3.502 ms
1.356 ms
1.062 ms
1.071 ms
1.363 ms
0.937 ms
1.037 ms
14.206 ms
1.395 ms
1.417 ms
0.996 ms
1.001 ms
1.403 ms
1.361 ms
7.578 ms
1.389 ms
1.052 ms
1.023 ms
1.380 ms
1.378 ms
0.963 ms
1.008 ms
1.031 ms
1.051 ms
0.981 ms
0.963 ms
1.007 ms
0.983 ms
1.366 ms
1.074 ms
1.414 ms
0.966 ms
1.378 ms
0.989 ms
0.963 ms
1.358 ms
1.363 ms
1.589 ms
1.381 ms
1.029 ms
1.376 ms
1.076 ms
1.618 ms
2.065 ms
1.400 ms
5.270 ms
1.368 ms
1.094 ms
1.366 ms
1.371 ms
1.356 ms
1.432 ms
1.387 ms
1.024 ms
1.028 ms
1.258 ms
0.991 ms
1.031 ms
2.853 ms
0.971 ms
0.968 ms
0.992 ms
1.398 ms
1.076 ms
1.386 ms
5.519 ms
0.988 ms
1.605 ms
1.356 ms
1.367 ms
1.367 ms
11.662 ms
1.377 ms
0.966 ms
1.032 ms
1.007 ms
1.481 ms
1.013 ms
1.061 ms
1.026 ms
1.431 ms
1.081 ms
1.733 ms
1.034 ms
1.024 ms
1.301 ms
0.991 ms
0.986 ms
14.849 ms
1.409 ms
0.955 ms
1.395 ms
1.387 ms
1.375 ms
1.046 ms
0.991 ms
1.629 ms
1.452 ms
0.999 ms
1.054 ms
1.358 ms
1.364 ms
1.454 ms
13.771 ms
2.864 ms
1.351 ms
0.963 ms
1.057 ms
1.470 ms
1.029 ms
0.973 ms
0.996 ms
1.362 ms
1.406 ms
0.962 ms
1.171 ms
14.119 ms
1.069 ms
1.020 ms
1.102 ms
Network path / recorded observations

Network path observations.

25 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


to UTC

  1. TTL 1 Probe hop0.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.641 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.241 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.345 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.410 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 17 traces


to UTC

  1. TTL 1 Stealth associated hop0.132 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.178 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop4.151 msMedian reply RTT13/17 replies · 76.5%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP/443 traceroute · Destination 2

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.191 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.200 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.506 msMedian reply RTT12/15 replies · 80.0%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.296 msMedian reply RTT13/15 replies · 86.7%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 13 traces


to UTC

  1. TTL 1 Stealth associated hop0.132 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.665 msMedian reply RTT6/13 replies · 46.2%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP/443 traceroute · Destination 4

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.186 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.199 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop13.104 msMedian reply RTT8/15 replies · 53.3%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.320 msMedian reply RTT13/15 replies · 86.7%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.283 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.243 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.347 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.370 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.447 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.380 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.099 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.644 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.507 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.901 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.109 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.891 msReply RTT ASN unavailable
  4. TTL 4 Probe hop15.851 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.400 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.368 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.130 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.183 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.650 msMedian reply RTT13/16 replies · 81.3%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 2

Comparison window · median of 19 traces


to UTC

  1. TTL 1 Stealth associated hop0.165 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.187 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop8.068 msMedian reply RTT12/19 replies · 63.2%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.400 msMedian reply RTT14/19 replies · 73.7%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.135 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop2.040 msMedian reply RTT9/14 replies · 64.3%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 4

Comparison window · median of 11 traces


to UTC

  1. TTL 1 Stealth associated hop0.158 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.464 msMedian reply RTT9/11 replies · 81.8%ASN unavailable
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.490 msMedian reply RTT10/11 replies · 90.9%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.762 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.645 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.520 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.218 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.676 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.175 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.469 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.375 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.173 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.486 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.512 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.919 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.083 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.240 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.618 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.914 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop27.398 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.507 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop30.771 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.646 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.331 msReply RTT AS13335 · Cloudflare

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 1

Before: UTC · During: UTC

Same destination address and probe method. A matching TTL does not establish the same forwarding path.
TTLBefore RTTDuring RTTResponding address
10.148 msAS8002 · Stealth0.134 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.176 msAS8002 · StealthSame responder
37.447 ms1.175 msSame responder
4No replyNo replyNot established
51.380 msAS13335 · Cloudflare4.469 msAS13335 · CloudflareDifferent responders
61.099 msAS13335 · Cloudflare1.375 msAS13335 · CloudflareSame 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

Stealth replies stable; external replies varied.

Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.

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.096 msUsual round trip before the event
Last recorded event RTT3.502 msLast successful event recording
Event p95 RTT14.164 ms95th percentile of successful recordings
Change from baseline+2.406 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.

References: ICMP reply handling / RFC 1812 · Round trip measurements / RFC 2681 · Full methodology