Start an order
Root cause analysis / Investigation

api.perplexity.ai

Reference RCA-AF9DC7FC88E54DA3

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 12:40 – 06 Nov 2026 15:39 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.201 ms
1.493 ms
1.089 ms
1.297 ms
1.585 ms
1.131 ms
1.299 ms
1.279 ms
1.406 ms
1.288 ms
1.442 ms
1.084 ms
1.268 ms
2.364 ms
1.043 ms
1.080 ms
2.216 ms
1.370 ms
1.321 ms
1.326 ms
1.058 ms
1.071 ms
1.316 ms
1.384 ms
1.144 ms
1.120 ms
1.298 ms
1.359 ms
1.274 ms
1.299 ms
1.305 ms
1.086 ms
1.289 ms
1.375 ms
1.110 ms
1.081 ms
1.051 ms
1.092 ms
1.099 ms
1.058 ms
1.292 ms
1.290 ms
1.330 ms
1.102 ms
1.044 ms
1.078 ms
1.077 ms
1.520 ms
1.111 ms
1.322 ms
1.066 ms
1.127 ms
1.181 ms
1.377 ms
1.291 ms
1.294 ms
1.064 ms
1.299 ms
1.275 ms
1.039 ms
1.065 ms
1.054 ms
1.289 ms
1.082 ms
1.287 ms
1.312 ms
1.070 ms
1.291 ms
1.377 ms
1.160 ms
1.115 ms
1.344 ms
1.088 ms
1.271 ms
1.330 ms
1.289 ms
1.313 ms
1.102 ms
1.104 ms
1.079 ms
1.282 ms
1.154 ms
1.080 ms
1.131 ms
1.069 ms
1.295 ms
1.331 ms
1.269 ms
1.053 ms
1.067 ms
1.111 ms
1.073 ms
1.099 ms
1.068 ms
1.278 ms
1.107 ms
1.078 ms
1.295 ms
1.366 ms
1.325 ms
1.302 ms
1.053 ms
1.294 ms
1.183 ms
1.362 ms
1.080 ms
1.822 ms
1.070 ms
1.286 ms
1.328 ms
1.278 ms
1.446 ms
1.152 ms
1.326 ms
1.260 ms
1.328 ms
1.305 ms
1.302 ms
1.287 ms
1.085 ms
1.340 ms
1.329 ms
1.397 ms
1.134 ms
1.077 ms
1.094 ms
19.103 ms
4.484 ms
1.118 ms
1.314 ms
1.080 ms
1.361 ms
1.442 ms
1.483 ms
1.415 ms
16.989 ms
1.080 ms
1.276 ms
1.298 ms
1.340 ms
1.392 ms
1.312 ms
1.345 ms
1.311 ms
13.240 ms
1.069 ms
2.020 ms
1.214 ms
1.097 ms
1.320 ms
1.331 ms
1.341 ms
1.067 ms
1.310 ms
1.176 ms
1.324 ms
1.292 ms
1.087 ms
1.326 ms
1.076 ms
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
1.311 ms
18.507 ms
1.324 ms
10.651 ms
1.380 ms
16.278 ms
1.071 ms
1.069 ms
1.099 ms
1.302 ms
1.435 ms
13.828 ms
1.291 ms
1.084 ms
1.067 ms
1.410 ms
1.048 ms
1.066 ms
1.081 ms
1.383 ms
1.342 ms
1.044 ms
1.319 ms
1.407 ms
1.348 ms
1.071 ms
19.084 ms
1.330 ms
1.149 ms
1.363 ms
6.945 ms
1.317 ms
1.138 ms
1.315 ms
1.076 ms
10.837 ms
9.285 ms
1.133 ms
1.112 ms
1.373 ms
1.320 ms
1.381 ms
1.397 ms
1.094 ms
1.275 ms
1.289 ms
1.184 ms
1.057 ms
1.315 ms
4.287 ms
1.303 ms
11.454 ms
1.135 ms
2.363 ms
1.330 ms
1.386 ms
1.323 ms
1.362 ms
1.349 ms
1.304 ms
1.048 ms
1.295 ms
1.098 ms
1.336 ms
1.281 ms
1.317 ms
1.291 ms
1.636 ms
1.303 ms
1.148 ms
1.269 ms
1.313 ms
1.311 ms
1.392 ms
1.068 ms
1.095 ms
1.212 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.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.382 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.601 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.207 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.015 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.902 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.116 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.129 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.184 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.613 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 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.164 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.191 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.465 msMedian reply RTT13/16 replies · 81.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.400 msMedian reply RTT12/16 replies · 75.0%ASN unavailable
  7. TTL 7 Destination reply1.663 msMedian reply RTT4/16 replies · 25.0%ASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.126 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.180 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.474 msMedian reply RTT14/16 replies · 87.5%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.206 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.194 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.354 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.330 msMedian reply RTT10/14 replies · 71.4%ASN unavailable
  7. TTL 7 Destination reply1.796 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.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.441 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.179 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.033 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.261 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.263 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.833 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.097 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.928 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.292 msReply RTT ASN unavailable
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.312 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.615 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.390 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.352 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 11 traces


to UTC

  1. TTL 1 Stealth associated hop0.132 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.182 msMedian reply RTT11/11 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.350 msMedian reply RTT9/11 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
During

TCP/443 traceroute · Destination 2

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.206 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop3.096 msMedian reply RTT7/14 replies · 50.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.275 msMedian reply RTT11/14 replies · 78.6%ASN unavailable
  7. TTL 7 Destination reply1.866 msMedian reply RTT3/14 replies · 21.4%ASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 19 traces


to UTC

  1. TTL 1 Stealth associated hop0.131 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.188 msMedian reply RTT19/19 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop14.767 msMedian reply RTT10/19 replies · 52.6%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 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.162 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.194 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop8.899 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.248 msMedian reply RTT12/16 replies · 75.0%ASN unavailable
  7. TTL 7 Destination reply1.992 msMedian reply RTT4/16 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.896 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.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.806 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.259 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.414 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.950 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.642 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.208 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.612 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.957 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.275 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.782 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.270 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop34.612 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.748 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.057 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.430 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.180 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.125 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.004 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.922 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.068 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.227 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.004 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.638 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination14.714 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.167 msAS8002 · Stealth0.115 msAS8002 · StealthSame responder
20.382 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
31.601 ms0.642 msAS13335 · CloudflareSame responder
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.148 msAS8002 · Stealth0.124 msAS8002 · StealthSame responder
20.186 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
31.441 msAS13335 · Cloudflare1.292 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.263 msAS8002 · Stealth0.285 msAS8002 · StealthSame responder
20.191 msAS8002 · Stealth0.312 msAS8002 · StealthSame responder
30.833 ms1.615 msSame responder
4No replyNo replyNot established
53.097 msAS13335 · Cloudflare4.390 msAS13335 · CloudflareDifferent responders
60.928 msAS13335 · Cloudflare1.352 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.166 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.193 msAS8002 · StealthSame responder
3No reply16.806 msAS13335 · CloudflareNot established
4No reply2.259 msAS13335 · CloudflareNot established
52.033 msAS13335 · Cloudflare2.414 msAS13335 · CloudflareDifferent responders
61.261 msAS13335 · Cloudflare0.950 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

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.267 msUsual round trip before the event
Last recorded event RTT1.317 msLast successful event recording
Event p95 RTT13.262 ms95th percentile of successful recordings
Change from baseline+0.050 msLast event RTT compared with the baseline
Successful / expected recordings120 / 120Recorded 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