Start an order
Root cause analysis / Investigation

copilot.microsoft.com

Reference RCA-B37022E9D0930E0A

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 19:35 – 06 Nov 2026 22:04 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
0.976 ms
1.558 ms
1.007 ms
1.405 ms
1.085 ms
1.405 ms
1.419 ms
1.378 ms
1.380 ms
7.406 ms
1.367 ms
1.409 ms
4.376 ms
1.425 ms
1.029 ms
1.004 ms
14.567 ms
1.364 ms
1.457 ms
0.963 ms
5.491 ms
0.954 ms
1.048 ms
2.410 ms
18.396 ms
1.018 ms
1.364 ms
1.380 ms
0.976 ms
0.983 ms
14.318 ms
1.531 ms
1.020 ms
1.422 ms
0.938 ms
1.380 ms
0.963 ms
1.381 ms
1.444 ms
1.713 ms
0.972 ms
1.399 ms
1.357 ms
1.432 ms
1.387 ms
1.063 ms
2.349 ms
1.369 ms
8.630 ms
1.090 ms
1.351 ms
1.005 ms
1.022 ms
1.468 ms
0.989 ms
0.980 ms
1.000 ms
1.368 ms
1.476 ms
1.389 ms
1.352 ms
0.987 ms
1.393 ms
1.444 ms
0.988 ms
1.071 ms
1.312 ms
1.030 ms
1.077 ms
1.399 ms
4.127 ms
1.009 ms
1.477 ms
0.960 ms
1.040 ms
1.158 ms
1.395 ms
0.977 ms
1.053 ms
1.359 ms
1.379 ms
1.536 ms
1.389 ms
1.362 ms
1.362 ms
1.036 ms
1.413 ms
1.386 ms
1.365 ms
1.368 ms
1.354 ms
1.427 ms
0.996 ms
1.502 ms
1.374 ms
1.052 ms
0.966 ms
1.007 ms
14.730 ms
1.478 ms
1.017 ms
1.422 ms
1.023 ms
1.000 ms
0.977 ms
1.392 ms
1.102 ms
1.404 ms
1.027 ms
0.987 ms
0.961 ms
1.411 ms
1.355 ms
1.006 ms
1.548 ms
1.029 ms
0.964 ms
1.008 ms
1.044 ms
1.410 ms
9.508 ms
0.964 ms
1.078 ms
1.463 ms
0.976 ms
0.999 ms
1.046 ms
1.387 ms
1.361 ms
1.414 ms
1.407 ms
1.374 ms
1.029 ms
1.003 ms
2.836 ms
3.535 ms
20.032 ms
1.012 ms
20.466 ms
1.004 ms
1.125 ms
0.985 ms
1.423 ms
0.994 ms
1.029 ms
1.069 ms
1.117 ms
1.419 ms
13.680 ms
1.103 ms
0.999 ms
1.382 ms
1.055 ms
1.424 ms
0.976 ms
0.960 ms
1.026 ms
1.376 ms
1.095 ms
0.999 ms
1.424 ms
1.414 ms
1.382 ms
0.992 ms
1.018 ms
1.008 ms
1.353 ms
0.992 ms
1.003 ms
0.999 ms
1.036 ms
1.422 ms
1.393 ms
1.374 ms
0.976 ms
1.399 ms
1.048 ms
1.044 ms
1.022 ms
1.055 ms
1.229 ms
0.957 ms
1.461 ms
1.338 ms
1.372 ms
1.490 ms
14.306 ms
1.029 ms
1.004 ms
1.374 ms
17.100 ms
1.009 ms
2.377 ms
1.382 ms
1.378 ms
1.046 ms
3.337 ms
1.232 ms
1.030 ms
1.345 ms
1.390 ms
1.364 ms
0.939 ms
1.422 ms
1.432 ms
1.399 ms
0.959 ms
1.022 ms
1.023 ms
1.036 ms
1.033 ms
1.341 ms
1.387 ms
0.997 ms
1.332 ms
1.367 ms
1.012 ms
1.127 ms
1.419 ms
1.498 ms
1.005 ms
1.363 ms
1.013 ms
1.013 ms
0.988 ms
1.001 ms
1.334 ms
1.021 ms
1.030 ms
1.011 ms
1.009 ms
1.634 ms
0.973 ms
0.984 ms
1.387 ms
1.025 ms
1.110 ms
1.388 ms
1.380 ms
0.976 ms
1.000 ms
1.011 ms
1.428 ms
1.389 ms
1.380 ms
1.867 ms
1.403 ms
1.371 ms
1.365 ms
1.364 ms
1.446 ms
1.030 ms
1.362 ms
0.978 ms
0.943 ms
1.013 ms
1.028 ms
1.400 ms
1.389 ms
1.368 ms
1.034 ms
1.458 ms
0.960 ms
1.420 ms
1.405 ms
1.422 ms
0.992 ms
0.948 ms
1.362 ms
1.343 ms
0.935 ms
1.351 ms
1.359 ms
1.372 ms
15.927 ms
1.385 ms
1.383 ms
1.416 ms
1.385 ms
0.947 ms
1.382 ms
1.417 ms
1.402 ms
1.064 ms
1.001 ms
0.970 ms
1.075 ms
0.935 ms
1.425 ms
0.964 ms
3.079 ms
1.000 ms
1.464 ms
1.357 ms
0.992 ms
1.507 ms
1.033 ms
1.058 ms
1.073 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 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.317 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop31.112 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.601 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.839 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.133 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.185 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.270 msMedian reply RTT12/14 replies · 85.7%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 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.179 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.189 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.597 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 Destination reply1.260 msMedian reply RTT12/16 replies · 75.0%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.129 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 hop4.560 msMedian reply RTT12/16 replies · 75.0%AS13335 · Cloudflare
Before

TCP/443 traceroute · Destination 4

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.183 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.185 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop6.118 msMedian reply RTT12/14 replies · 85.7%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 Destination reply1.364 msMedian reply RTT10/14 replies · 71.4%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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.168 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 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 hop2.122 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.869 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.135 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.182 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop8.861 msMedian reply RTT12/18 replies · 66.7%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 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.169 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.189 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop10.430 msMedian reply RTT10/14 replies · 71.4%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 Destination reply1.337 msMedian reply RTT13/14 replies · 92.9%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 12 traces


to UTC

  1. TTL 1 Stealth associated hop0.127 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.191 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop6.304 msMedian reply RTT10/12 replies · 83.3%AS13335 · Cloudflare
During

TCP/443 traceroute · Destination 4

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.166 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.187 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop8.042 msMedian reply RTT14/16 replies · 87.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 Destination reply1.368 msMedian reply RTT15/16 replies · 93.8%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.172 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop36.359 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.749 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.037 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.226 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.189 msReply RTT ASN unavailable
  4. TTL 4 Probe hop3.112 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop3.593 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.298 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.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.022 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.162 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.905 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.456 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.115 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.320 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop30.663 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.571 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.371 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.363 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.898 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.444 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop6.339 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.023 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.257 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.659 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop28.163 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.155 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.357 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.079 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.552 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.156 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.160 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.210 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.447 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.598 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.374 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.175 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.218 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.504 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.239 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.242 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.883 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.516 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.

ICMP traceroute · 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.125 msAS8002 · Stealth0.133 msAS8002 · StealthSame responder
20.192 msAS8002 · Stealth0.186 msAS8002 · StealthSame responder
317.317 msAS13335 · CloudflareNot recordedNot established
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.172 msAS8002 · Stealth0.226 msAS8002 · StealthSame responder
20.182 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
336.359 ms1.189 msSame responder
4No reply3.112 msAS13335 · CloudflareNot established
51.749 msAS13335 · Cloudflare3.593 msAS13335 · CloudflareDifferent responders
61.037 msAS13335 · Cloudflare1.298 msAS13335 · CloudflareSame responder
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.
TTLBefore RTTDuring RTTResponding address
10.169 msAS8002 · Stealth0.147 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
331.112 msAS13335 · Cloudflare30.663 msAS13335 · CloudflareSame responder
4No reply1.571 msAS13335 · CloudflareNot established
51.601 msAS13335 · Cloudflare1.371 msAS13335 · CloudflareDifferent responders
6No reply1.363 msAS13335 · CloudflareNot established
71.839 msAS13335 · CloudflareNot recordedNot 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.

Latency anomaly. 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.227 msUsual round trip before the event
Last recorded event RTT1.055 msLast successful event recording
Event p95 RTT9.717 ms95th percentile of successful recordings
Change from baseline-0.172 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.

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