Start an order
Root cause analysis / Investigation

api.perplexity.ai

Reference RCA-1619C72C29714DDF

Perplexity API endpoint

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 16:00 – 06 Nov 2026 18:34 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.257 ms
1.161 ms
1.088 ms
1.837 ms
1.068 ms
1.455 ms
1.314 ms
4.320 ms
1.144 ms
1.291 ms
1.066 ms
1.543 ms
1.083 ms
1.316 ms
1.066 ms
1.296 ms
1.323 ms
1.352 ms
3.941 ms
1.217 ms
1.098 ms
1.056 ms
1.272 ms
1.381 ms
1.327 ms
9.614 ms
15.520 ms
1.286 ms
1.060 ms
6.045 ms
1.082 ms
1.286 ms
1.135 ms
1.369 ms
1.508 ms
1.287 ms
1.159 ms
1.346 ms
1.110 ms
1.438 ms
1.395 ms
1.359 ms
1.326 ms
1.289 ms
1.112 ms
1.044 ms
8.302 ms
1.320 ms
1.278 ms
1.362 ms
1.335 ms
1.309 ms
1.295 ms
1.112 ms
1.147 ms
1.338 ms
1.331 ms
1.319 ms
1.301 ms
14.166 ms
1.107 ms
1.373 ms
1.275 ms
1.335 ms
4.054 ms
1.070 ms
1.295 ms
16.331 ms
1.378 ms
1.375 ms
1.322 ms
9.222 ms
1.076 ms
16.786 ms
1.355 ms
1.096 ms
1.282 ms
1.090 ms
14.634 ms
1.427 ms
1.346 ms
1.303 ms
1.405 ms
1.096 ms
1.277 ms
1.157 ms
1.070 ms
1.369 ms
1.105 ms
1.243 ms
1.064 ms
1.127 ms
1.392 ms
1.287 ms
1.462 ms
1.323 ms
1.303 ms
1.306 ms
1.393 ms
1.315 ms
1.149 ms
1.146 ms
1.091 ms
1.273 ms
1.093 ms
1.073 ms
1.096 ms
1.307 ms
1.328 ms
1.345 ms
1.299 ms
1.368 ms
1.336 ms
1.072 ms
1.281 ms
2.443 ms
1.399 ms
1.303 ms
1.313 ms
1.333 ms
1.122 ms
14.018 ms
14.147 ms
1.445 ms
11.946 ms
16.538 ms
1.271 ms
1.313 ms
13.045 ms
1.089 ms
1.489 ms
3.408 ms
1.285 ms
1.308 ms
8.978 ms
1.367 ms
1.067 ms
16.696 ms
19.978 ms
16.364 ms
1.325 ms
11.708 ms
1.301 ms
1.333 ms
5.905 ms
1.096 ms
1.315 ms
1.307 ms
1.291 ms
1.147 ms
2.327 ms
1.124 ms
1.071 ms
1.315 ms
17.680 ms
1.372 ms
1.198 ms
1.429 ms
1.295 ms
1.316 ms
1.333 ms
1.115 ms
1.414 ms
1.404 ms
1.299 ms
1.329 ms
1.388 ms
1.353 ms
1.346 ms
1.311 ms
1.318 ms
1.286 ms
1.157 ms
1.065 ms
1.177 ms
1.070 ms
1.306 ms
1.290 ms
1.066 ms
1.419 ms
1.293 ms
1.110 ms
1.281 ms
1.381 ms
1.058 ms
1.369 ms
1.282 ms
1.354 ms
1.124 ms
1.345 ms
1.087 ms
1.336 ms
1.287 ms
17.665 ms
1.301 ms
1.346 ms
16.562 ms
1.397 ms
1.060 ms
1.318 ms
1.316 ms
1.292 ms
1.166 ms
1.346 ms
1.297 ms
19.851 ms
1.782 ms
6.899 ms
1.297 ms
1.094 ms
1.087 ms
1.315 ms
1.166 ms
1.161 ms
1.113 ms
1.394 ms
1.328 ms
1.355 ms
1.123 ms
1.283 ms
1.230 ms
1.080 ms
17.028 ms
1.329 ms
6.722 ms
1.130 ms
9.118 ms
1.497 ms
1.282 ms
1.145 ms
1.395 ms
1.090 ms
1.342 ms
1.519 ms
1.287 ms
1.053 ms
10.487 ms
1.275 ms
1.104 ms
1.364 ms
1.206 ms
1.177 ms
3.885 ms
1.481 ms
1.337 ms
5.037 ms
17.629 ms
18.466 ms
1.125 ms
1.350 ms
1.053 ms
1.054 ms
1.351 ms
1.445 ms
1.363 ms
1.241 ms
2.727 ms
1.312 ms
17.374 ms
1.050 ms
5.196 ms
1.297 ms
5.271 ms
1.362 ms
1.299 ms
1.435 ms
1.399 ms
18.284 ms
1.280 ms
13.943 ms
14.698 ms
1.304 ms
16.113 ms
12.349 ms
11.476 ms
4.784 ms
1.121 ms
1.358 ms
1.305 ms
1.319 ms
1.257 ms
1.259 ms
1.324 ms
1.288 ms
1.377 ms
1.377 ms
19.791 ms
9.148 ms
13.666 ms
1.360 ms
12.673 ms
1.552 ms
19.141 ms
6.566 ms
14.080 ms
1.362 ms
18.435 ms
18.931 ms
15.973 ms
17.251 ms
20.187 ms
19.724 ms
1.298 ms
1.346 ms
19.658 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop29.401 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.442 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.756 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop11.716 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.020 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.134 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.182 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop3.181 msMedian reply RTT12/16 replies · 75.0%AS13335 · Cloudflare
Before

TCP/443 traceroute · Destination 2

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.197 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.537 msMedian reply RTT11/16 replies · 68.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.402 msMedian reply RTT9/16 replies · 56.3%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

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.181 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.489 msMedian reply RTT13/14 replies · 92.9%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 4

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.168 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.671 msMedian reply RTT11/14 replies · 78.6%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.408 msMedian reply RTT10/14 replies · 71.4%ASN unavailable
  7. TTL 7 Destination reply1.674 msMedian reply RTT4/14 replies · 28.6%ASN unavailable
Before

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.154 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.224 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.247 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.634 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.493 msReply RTT AS13335 · Cloudflare
Before

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.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.031 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.295 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.115 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.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.260 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 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.255 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination13.854 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 12 traces


to UTC

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

TCP/443 traceroute · Destination 2

Comparison window · median of 5 traces


to UTC

  1. TTL 1 Stealth associated hop0.207 msMedian reply RTT5/5 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.210 msMedian reply RTT5/5 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.995 msMedian reply RTT3/5 replies · 60.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.445 msMedian reply RTT4/5 replies · 80.0%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.144 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.189 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop3.695 msMedian reply RTT13/18 replies · 72.2%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 4

Comparison window · median of 25 traces


to UTC

  1. TTL 1 Stealth associated hop0.173 msMedian reply RTT25/25 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.198 msMedian reply RTT25/25 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.899 msMedian reply RTT20/25 replies · 80.0%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.390 msMedian reply RTT19/25 replies · 76.0%ASN unavailable
  7. TTL 7 Destination reply1.574 msMedian reply RTT6/25 replies · 24.0%ASN unavailable
During

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.668 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.285 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 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.827 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.437 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.158 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.441 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop1.625 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop4.932 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.575 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.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.213 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.245 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.059 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.802 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.409 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.328 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.335 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.666 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.252 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.989 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.538 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination3.562 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.230 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.288 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 hop4.527 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.380 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.129 msAS8002 · Stealth0.140 msAS8002 · StealthSame responder
20.183 msAS8002 · Stealth0.260 msAS8002 · StealthSame responder
329.401 msAS13335 · CloudflareNot recordedNot established
ICMP traceroute · 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.128 msAS8002 · Stealth0.129 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.668 msAS8002 · StealthSame responder
313.154 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.224 msAS8002 · Stealth0.146 msAS8002 · StealthSame responder
20.247 msAS8002 · Stealth0.190 msAS8002 · StealthSame responder
3No replyNo replyNot established
4No replyNo replyNot established
51.634 msAS13335 · Cloudflare2.255 msAS13335 · CloudflareDifferent responders
61.493 msAS13335 · CloudflareNo replyNot established
7Not recorded13.854 msAS13335 · CloudflareNot established
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.154 msAS8002 · Stealth0.158 msAS8002 · StealthSame responder
20.187 msAS8002 · Stealth0.441 msAS8002 · StealthSame responder
316.031 msNo replyNot established
4No reply1.625 msAS13335 · CloudflareNot established
53.295 msAS13335 · Cloudflare4.932 msAS13335 · CloudflareDifferent responders
61.115 msAS13335 · CloudflareNo replyNot established
7Not recorded1.575 msAS13335 · CloudflareNot 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

Findings differ by destination.

Findings differ between destination comparisons. The evidence does not point to one location for the whole event.

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.276 msUsual round trip before the event
Last recorded event RTT1.124 msLast successful event recording
Event p95 RTT16.460 ms95th percentile of successful recordings
Change from baseline-0.152 msLast event RTT compared with the baseline
Successful / expected recordings70 / 70Recorded 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