Root cause analysis / Investigation

api.perplexity.ai

Reference RCA-3EE249A45D0997C0

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. Points are sampled from the retained history.

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 14:00 – 06 Nov 2026 17:54 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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.293 ms
1.300 ms
1.090 ms
1.442 ms
1.402 ms
1.327 ms
1.315 ms
1.289 ms
1.142 ms
1.108 ms
1.106 ms
1.068 ms
1.267 ms
1.293 ms
1.292 ms
1.300 ms
1.076 ms
1.107 ms
16.854 ms
5.801 ms
1.347 ms
1.074 ms
1.089 ms
2.080 ms
14.087 ms
1.344 ms
1.292 ms
1.118 ms
1.273 ms
1.285 ms
1.384 ms
1.087 ms
1.403 ms
1.063 ms
1.334 ms
1.326 ms
1.053 ms
1.245 ms
1.094 ms
1.099 ms
1.298 ms
1.062 ms
1.310 ms
1.091 ms
1.384 ms
18.794 ms
13.685 ms
1.278 ms
1.311 ms
1.311 ms
1.130 ms
1.094 ms
1.284 ms
1.109 ms
1.291 ms
1.086 ms
1.071 ms
1.432 ms
1.095 ms
1.318 ms
1.081 ms
1.118 ms
1.286 ms
1.062 ms
1.274 ms
1.295 ms
1.313 ms
1.080 ms
1.286 ms
1.266 ms
1.280 ms
1.312 ms
1.423 ms
1.162 ms
1.085 ms
1.425 ms
1.318 ms
1.281 ms
1.178 ms
1.317 ms
1.373 ms
1.327 ms
1.318 ms
1.345 ms
1.062 ms
1.056 ms
1.293 ms
1.082 ms
1.278 ms
1.100 ms
1.056 ms
10.477 ms
19.360 ms
14.708 ms
3.774 ms
1.045 ms
1.285 ms
5.757 ms
1.275 ms
1.290 ms
1.280 ms
1.312 ms
1.290 ms
1.389 ms
1.277 ms
1.343 ms
1.283 ms
1.309 ms
8.013 ms
18.820 ms
1.069 ms
1.071 ms
1.286 ms
1.081 ms
3.529 ms
1.293 ms
1.321 ms
1.092 ms
1.128 ms
1.068 ms
1.194 ms
1.074 ms
18.507 ms
10.651 ms
16.278 ms
1.069 ms
1.302 ms
13.828 ms
1.084 ms
1.410 ms
1.066 ms
1.383 ms
1.342 ms
1.319 ms
1.348 ms
19.084 ms
1.149 ms
6.945 ms
1.138 ms
1.076 ms
9.285 ms
1.112 ms
1.320 ms
1.397 ms
1.094 ms
1.289 ms
1.057 ms
4.287 ms
11.454 ms
2.363 ms
1.386 ms
1.362 ms
1.304 ms
1.295 ms
1.336 ms
1.317 ms
1.291 ms
1.303 ms
1.269 ms
1.311 ms
1.068 ms
1.212 ms
5.429 ms
1.128 ms
1.944 ms
1.292 ms
1.298 ms
1.075 ms
1.135 ms
1.135 ms
1.319 ms
1.404 ms
1.433 ms
1.180 ms
1.107 ms
6.543 ms
1.606 ms
1.366 ms
1.567 ms
1.125 ms
1.337 ms
1.311 ms
1.413 ms
1.257 ms
1.088 ms
1.068 ms
1.314 ms
1.144 ms
1.066 ms
1.083 ms
1.066 ms
1.323 ms
1.352 ms
1.217 ms
1.056 ms
1.381 ms
9.614 ms
1.286 ms
6.045 ms
1.286 ms
1.369 ms
1.287 ms
1.346 ms
1.438 ms
1.395 ms
1.326 ms
1.112 ms
8.302 ms
1.278 ms
1.335 ms
1.295 ms
1.147 ms
1.331 ms
1.301 ms
1.107 ms
1.275 ms
1.335 ms
1.070 ms
16.331 ms
1.375 ms
9.222 ms
16.786 ms
1.096 ms
1.090 ms
1.427 ms
1.303 ms
1.096 ms
1.157 ms
1.070 ms
1.105 ms
1.064 ms
1.392 ms
1.462 ms
1.303 ms
1.393 ms
1.149 ms
1.091 ms
1.093 ms
1.096 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
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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.259 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.251 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.142 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.595 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.621 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 11 traces


to UTC

  1. TTL 1 Stealth associated hop0.129 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.183 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.350 msMedian reply RTT11/11 replies · 100.0%AS13335 · Cloudflare
Before

TCP/443 traceroute · Destination 2

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.168 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.205 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.617 msMedian reply RTT9/16 replies · 56.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.275 msMedian reply RTT13/16 replies · 81.3%ASN unavailable
  7. TTL 7 Destination reply1.866 msMedian reply RTT3/16 replies · 18.8%ASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 19 traces


to UTC

  1. TTL 1 Stealth associated hop0.147 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.182 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.650 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 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.181 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.190 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.107 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 Destination reply1.370 msMedian reply RTT10/14 replies · 71.4%ASN unavailable
  7. TTL 7 Destination reply1.981 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.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.813 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.096 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.935 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.093 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.839 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.725 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination5.539 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.256 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.767 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.763 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.233 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.286 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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.750 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.571 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.942 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.070 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.136 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 hop1.332 msMedian reply RTT10/14 replies · 71.4%AS13335 · Cloudflare
During

TCP/443 traceroute · Destination 2

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.166 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.193 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop5.735 msMedian reply RTT12/18 replies · 66.7%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.374 msMedian reply RTT12/18 replies · 66.7%ASN unavailable
  7. TTL 7 Destination reply2.198 msMedian reply RTT6/18 replies · 33.3%ASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.133 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.489 msMedian reply RTT15/16 replies · 93.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 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 4

Comparison window · median of 12 traces


to UTC

  1. TTL 1 Stealth associated hop0.171 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.187 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.650 msMedian reply RTT9/12 replies · 75.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.380 msMedian reply RTT9/12 replies · 75.0%ASN unavailable
  7. TTL 7 Destination reply1.693 msMedian reply RTT3/12 replies · 25.0%ASN unavailable
During

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.025 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.197 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.265 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.617 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop12.162 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.384 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.717 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.743 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.484 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.333 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.241 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.508 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.671 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.155 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.262 msReply RTT AS8002 · Stealth
After

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.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.770 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.552 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.005 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.335 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.511 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.374 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.852 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.184 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.097 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 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.126 msAS8002 · Stealth0.126 msAS8002 · StealthSame responder
20.175 msAS8002 · Stealth0.256 msAS8002 · StealthSame responder
316.813 msAS13335 · Cloudflare8.767 msSame responder
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.149 msAS8002 · Stealth0.139 msAS8002 · StealthSame responder
20.197 msAS8002 · Stealth0.185 msAS8002 · StealthSame responder
33.096 msAS13335 · Cloudflare0.763 msSame responder
4No replyNo replyNot established
54.935 msAS13335 · Cloudflare3.233 msAS13335 · CloudflareSame responder
61.093 msAS13335 · Cloudflare1.286 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.

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

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.272 msUsual round trip before the event
Last recorded event RTT1.328 msLast successful event recording
Event p95 RTT11.207 ms95th percentile of successful recordings
Change from baseline+0.056 msLast event RTT compared with the baseline
Successful / expected recordings229 / 230Recorded 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