Start an order
Root cause analysis / Investigation

api.perplexity.ai

Reference RCA-3B62E0BEC4C4F4D5

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 18:40 – 06 Nov 2026 21:24 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.164 ms
2.481 ms
19.401 ms
4.527 ms
1.351 ms
10.115 ms
1.324 ms
1.296 ms
1.310 ms
1.285 ms
3.867 ms
2.285 ms
1.349 ms
9.725 ms
11.878 ms
1.290 ms
11.269 ms
1.162 ms
1.333 ms
19.334 ms
14.136 ms
1.132 ms
4.332 ms
19.896 ms
1.398 ms
1.289 ms
1.306 ms
1.371 ms
4.165 ms
1.070 ms
1.293 ms
1.127 ms
1.274 ms
1.194 ms
19.542 ms
1.298 ms
1.399 ms
1.102 ms
1.318 ms
1.384 ms
1.280 ms
2.185 ms
1.325 ms
1.100 ms
1.136 ms
1.285 ms
1.383 ms
1.128 ms
1.115 ms
10.757 ms
1.339 ms
1.058 ms
3.000 ms
1.353 ms
1.187 ms
1.132 ms
1.330 ms
1.167 ms
1.338 ms
1.066 ms
1.211 ms
1.317 ms
1.065 ms
1.309 ms
6.557 ms
1.122 ms
1.094 ms
1.300 ms
2.389 ms
1.331 ms
1.447 ms
1.306 ms
17.137 ms
1.112 ms
1.062 ms
1.349 ms
16.985 ms
1.276 ms
2.460 ms
1.303 ms
18.813 ms
1.314 ms
1.336 ms
1.109 ms
4.345 ms
1.072 ms
1.322 ms
1.292 ms
1.125 ms
1.304 ms
1.312 ms
1.468 ms
1.148 ms
1.412 ms
1.413 ms
1.283 ms
1.331 ms
1.127 ms
1.336 ms
1.085 ms
1.130 ms
1.359 ms
1.199 ms
1.056 ms
3.072 ms
1.332 ms
1.325 ms
1.306 ms
1.082 ms
1.311 ms
1.297 ms
1.275 ms
1.090 ms
1.316 ms
1.087 ms
1.385 ms
1.069 ms
1.394 ms
1.329 ms
1.291 ms
1.441 ms
1.521 ms
1.463 ms
1.107 ms
1.170 ms
1.087 ms
1.282 ms
14.970 ms
1.087 ms
1.078 ms
1.067 ms
4.932 ms
19.174 ms
6.644 ms
1.287 ms
1.075 ms
18.590 ms
1.528 ms
1.313 ms
1.288 ms
1.362 ms
1.099 ms
1.324 ms
1.077 ms
1.154 ms
4.897 ms
1.106 ms
1.087 ms
1.370 ms
1.149 ms
1.351 ms
1.200 ms
1.085 ms
1.083 ms
3.993 ms
1.105 ms
1.117 ms
1.283 ms
1.040 ms
1.317 ms
1.349 ms
12.081 ms
1.128 ms
1.054 ms
1.104 ms
9.897 ms
1.339 ms
1.333 ms
1.319 ms
1.337 ms
1.180 ms
1.339 ms
1.109 ms
1.095 ms
1.307 ms
1.132 ms
1.323 ms
7.412 ms
1.300 ms
1.139 ms
1.081 ms
1.097 ms
1.376 ms
1.335 ms
1.113 ms
1.081 ms
1.062 ms
1.075 ms
1.273 ms
1.399 ms
1.457 ms
1.389 ms
1.289 ms
1.053 ms
1.150 ms
1.332 ms
1.125 ms
1.305 ms
1.298 ms
1.347 ms
1.104 ms
1.210 ms
1.430 ms
1.344 ms
1.148 ms
1.075 ms
1.299 ms
1.099 ms
1.165 ms
1.062 ms
1.181 ms
1.053 ms
1.438 ms
1.139 ms
1.400 ms
1.364 ms
1.126 ms
1.130 ms
1.064 ms
1.292 ms
1.141 ms
1.169 ms
1.302 ms
11.214 ms
1.337 ms
1.154 ms
1.299 ms
2.875 ms
1.189 ms
1.331 ms
1.163 ms
1.269 ms
1.392 ms
1.315 ms
1.306 ms
1.358 ms
1.342 ms
1.141 ms
1.329 ms
1.363 ms
1.073 ms
1.051 ms
1.088 ms
1.342 ms
1.094 ms
1.279 ms
1.371 ms
19.257 ms
1.323 ms
1.361 ms
1.329 ms
1.059 ms
1.271 ms
3.877 ms
1.084 ms
1.111 ms
1.302 ms
16.070 ms
1.117 ms
1.071 ms
1.117 ms
1.083 ms
1.111 ms
1.138 ms
1.280 ms
1.082 ms
1.163 ms
1.294 ms
1.295 ms
1.053 ms
1.160 ms
1.372 ms
1.338 ms
1.322 ms
2.147 ms
1.272 ms
1.266 ms
1.310 ms
1.083 ms
1.071 ms
1.104 ms
1.244 ms
1.363 ms
1.285 ms
1.290 ms
1.290 ms
1.304 ms
1.498 ms
1.063 ms
1.110 ms
1.103 ms
1.106 ms
1.147 ms
1.075 ms
1.059 ms
6.077 ms
1.085 ms
1.318 ms
1.381 ms
1.326 ms
1.082 ms
1.090 ms
1.395 ms
1.404 ms
1.326 ms
1.113 ms
1.103 ms
1.287 ms
1.295 ms
1.345 ms
1.402 ms
1.287 ms
1.322 ms
1.070 ms
1.322 ms
1.172 ms
1.323 ms
1.108 ms
1.101 ms
1.103 ms
1.155 ms
1.098 ms
1.352 ms
1.320 ms
1.090 ms
1.348 ms
1.061 ms
1.080 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.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.415 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.114 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.229 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 8 traces


to UTC

  1. TTL 1 Stealth associated hop0.132 msMedian reply RTT8/8 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.187 msMedian reply RTT8/8 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop3.834 msMedian reply RTT7/8 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 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.193 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.203 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop11.211 msMedian reply RTT12/15 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.454 msMedian reply RTT12/15 replies · 80.0%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 22 traces


to UTC

  1. TTL 1 Stealth associated hop0.131 msMedian reply RTT22/22 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.183 msMedian reply RTT22/22 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.762 msMedian reply RTT18/22 replies · 81.8%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 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.184 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop6.494 msMedian reply RTT14/15 replies · 93.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.417 msMedian reply RTT10/15 replies · 66.7%ASN unavailable
  7. TTL 7 Destination reply2.158 msMedian reply RTT5/15 replies · 33.3%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.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.633 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.219 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.796 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.752 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.431 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.222 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.769 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.065 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.516 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.118 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.626 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.211 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.512 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.301 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.497 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.130 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.188 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.414 msMedian reply RTT16/18 replies · 88.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
During

TCP/443 traceroute · Destination 2

Comparison window · median of 17 traces


to UTC

  1. TTL 1 Stealth associated hop0.163 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.197 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.388 msMedian reply RTT14/17 replies · 82.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.340 msMedian reply RTT16/17 replies · 94.1%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.151 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 hop8.774 msMedian reply RTT11/12 replies · 91.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 4

Comparison window · median of 13 traces


to UTC

  1. TTL 1 Stealth associated hop0.194 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.196 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.364 msMedian reply RTT9/13 replies · 69.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 Destination reply1.377 msMedian reply RTT9/13 replies · 69.2%ASN unavailable
  7. TTL 7 Destination reply1.796 msMedian reply RTT4/13 replies · 30.8%ASN unavailable
During

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.169 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.405 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.166 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.802 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.503 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.521 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.231 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 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.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.664 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.186 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.833 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.231 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.777 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.628 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop9.475 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.899 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.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.664 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.157 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.782 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.146 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.056 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.856 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.515 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.430 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.646 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.071 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.131 msAS8002 · Stealth0.130 msAS8002 · StealthSame responder
20.178 msAS8002 · Stealth0.169 msAS8002 · StealthSame responder
3Not recorded1.405 msAS13335 · CloudflareNot 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.126 msAS8002 · Stealth0.118 msAS8002 · StealthSame responder
20.186 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
31.633 msAS13335 · Cloudflare22.626 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.222 msAS8002 · Stealth0.146 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.201 msAS8002 · StealthSame responder
322.769 msNo replyNot established
4No replyNo replyNot established
52.065 msAS13335 · Cloudflare1.664 msAS13335 · CloudflareDifferent responders
61.516 msAS13335 · Cloudflare1.186 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.170 msAS8002 · Stealth0.211 msAS8002 · StealthSame responder
20.219 msAS8002 · Stealth0.190 msAS8002 · StealthSame responder
37.796 msAS13335 · Cloudflare2.512 msSame responder
4No replyNo replyNot established
52.752 msAS13335 · Cloudflare1.301 msAS13335 · CloudflareDifferent responders
61.431 msAS13335 · CloudflareNo replyNot established
7Not recorded1.497 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.

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.282 msUsual round trip before the event
Last recorded event RTT1.165 msLast successful event recording
Event p95 RTT8.779 ms95th percentile of successful recordings
Change from baseline-0.117 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