Start an order
Root cause analysis / Investigation

api.perplexity.ai

Reference RCA-BB493A74CA71BAAC

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

03 Nov 2026 21:40 – 04 Nov 2026 03:49 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.403 ms
3.127 ms
3.059 ms
1.342 ms
3.176 ms
3.117 ms
3.103 ms
3.107 ms
1.310 ms
1.429 ms
1.459 ms
1.400 ms
3.169 ms
5.454 ms
1.322 ms
3.153 ms
3.062 ms
3.101 ms
1.296 ms
1.357 ms
3.091 ms
3.123 ms
1.312 ms
1.345 ms
1.292 ms
1.303 ms
1.403 ms
1.283 ms
1.392 ms
1.372 ms
1.279 ms
3.119 ms
3.130 ms
5.618 ms
1.423 ms
1.343 ms
3.203 ms
3.148 ms
1.361 ms
5.581 ms
1.300 ms
3.205 ms
3.193 ms
1.301 ms
3.188 ms
1.311 ms
1.372 ms
3.181 ms
1.306 ms
3.176 ms
1.411 ms
1.302 ms
1.280 ms
3.158 ms
1.564 ms
1.318 ms
1.427 ms
3.177 ms
1.350 ms
1.308 ms
3.217 ms
1.329 ms
3.245 ms
1.390 ms
3.192 ms
1.352 ms
3.241 ms
1.423 ms
3.198 ms
1.309 ms
1.317 ms
3.181 ms
3.275 ms
1.443 ms
3.396 ms
1.428 ms
3.216 ms
1.376 ms
1.436 ms
1.377 ms
3.200 ms
3.185 ms
1.297 ms
3.212 ms
1.293 ms
1.283 ms
3.207 ms
1.259 ms
3.206 ms
1.415 ms
1.355 ms
1.307 ms
3.231 ms
3.247 ms
1.288 ms
1.298 ms
3.215 ms
1.316 ms
1.305 ms
3.239 ms
3.216 ms
1.550 ms
3.252 ms
1.328 ms
1.343 ms
3.240 ms
1.319 ms
3.260 ms
1.446 ms
3.218 ms
3.229 ms
1.292 ms
1.324 ms
1.318 ms
1.350 ms
3.287 ms
1.312 ms
1.388 ms
1.384 ms
3.306 ms
1.487 ms
3.252 ms
1.318 ms
1.302 ms
1.325 ms
1.341 ms
3.313 ms
3.289 ms
3.316 ms
3.320 ms
1.345 ms
3.312 ms
1.414 ms
3.397 ms
3.325 ms
3.338 ms
3.355 ms
1.302 ms
1.382 ms
3.374 ms
3.361 ms
1.327 ms
3.355 ms
1.294 ms
1.326 ms
3.274 ms
1.291 ms
1.461 ms
1.314 ms
1.447 ms
3.361 ms
1.331 ms
3.384 ms
1.405 ms
1.375 ms
1.373 ms
3.365 ms
3.335 ms
1.293 ms
1.270 ms
3.369 ms
3.338 ms
1.284 ms
1.340 ms
1.311 ms
3.353 ms
1.308 ms
3.312 ms
1.381 ms
1.415 ms
3.326 ms
1.285 ms
1.285 ms
3.392 ms
3.333 ms
3.325 ms
1.424 ms
1.388 ms
1.554 ms
1.387 ms
1.289 ms
3.317 ms
1.301 ms
3.332 ms
3.429 ms
1.298 ms
1.362 ms
3.322 ms
3.459 ms
3.303 ms
1.401 ms
3.338 ms
3.367 ms
1.442 ms
1.356 ms
3.377 ms
3.381 ms
1.297 ms
1.418 ms
1.294 ms
1.387 ms
3.334 ms
2.062 ms
1.323 ms
1.451 ms
1.293 ms
1.333 ms
3.325 ms
3.173 ms
3.267 ms
1.301 ms
1.290 ms
3.187 ms
1.322 ms
1.298 ms
3.261 ms
3.197 ms
1.350 ms
1.280 ms
3.449 ms
1.294 ms
3.280 ms
1.315 ms
1.504 ms
3.202 ms
1.304 ms
3.172 ms
1.371 ms
1.283 ms
3.167 ms
1.320 ms
3.168 ms
3.231 ms
1.322 ms
1.404 ms
3.223 ms
1.284 ms
3.195 ms
1.314 ms
1.456 ms
2.755 ms
1.423 ms
1.281 ms
3.236 ms
3.187 ms
3.161 ms
1.290 ms
1.366 ms
3.189 ms
1.377 ms
3.153 ms
1.358 ms
3.275 ms
1.341 ms
1.312 ms
1.314 ms
5.527 ms
1.338 ms
3.409 ms
1.336 ms
1.722 ms
1.293 ms
0.806 ms
0.807 ms
0.822 ms
0.818 ms
0.812 ms
1.395 ms
1.358 ms
1.431 ms
1.372 ms
1.329 ms
1.294 ms
1.289 ms
1.340 ms
0.801 ms
0.786 ms
1.284 ms
1.408 ms
1.325 ms
0.846 ms
1.401 ms
1.306 ms
0.819 ms
0.818 ms
1.309 ms
0.897 ms
0.803 ms
1.334 ms
1.352 ms
1.307 ms
0.840 ms
1.304 ms
0.799 ms
1.314 ms
0.839 ms
1.290 ms
1.333 ms
0.845 ms
0.871 ms
1.870 ms
1.374 ms
1.693 ms
0.799 ms
1.283 ms
1.390 ms
1.285 ms
1.290 ms
0.829 ms
0.906 ms
1.283 ms
0.855 ms
1.442 ms
1.304 ms
0.799 ms
1.416 ms
1.306 ms
0.817 ms
1.366 ms
1.291 ms
1.296 ms
1.328 ms
0.815 ms
1.285 ms
0.872 ms
0.820 ms
1.306 ms
1.376 ms
1.504 ms
1.296 ms
0.793 ms
0.810 ms
0.822 ms
0.810 ms
1.314 ms
1.362 ms
1.362 ms
1.270 ms
1.345 ms
1.277 ms
0.880 ms
0.877 ms
0.797 ms
0.834 ms
Network path / recorded observations

Network path observations.

17 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.194 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.209 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.242 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.187 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.506 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 1

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.226 msReply RTT AS8002 · Stealth
Before

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.186 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.998 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.643 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.155 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.052 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.619 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.220 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.272 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.204 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.046 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.377 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.599 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.653 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.239 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.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.296 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.915 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.586 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.615 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.023 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.414 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.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.905 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.380 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.451 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.643 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop11.843 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.053 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination3.238 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.203 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.192 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.670 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.987 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.191 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.472 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.210 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop21.479 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop27.026 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.040 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.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.633 msReply RTT ASN unavailable
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.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.092 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.514 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.677 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.118 msAS8002 · Stealth0.143 msAS8002 · StealthSame responder
20.226 msAS8002 · Stealth0.184 msAS8002 · StealthSame responder
3Not recorded1.296 msNot 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.209 msAS8002 · Stealth0.144 msAS8002 · StealthSame responder
20.242 msAS8002 · Stealth0.198 msAS8002 · StealthSame responder
3No reply0.905 msAS13335 · CloudflareNot established
4No replyNo replyNot established
54.187 msAS13335 · Cloudflare2.380 msAS13335 · CloudflareDifferent responders
61.506 msAS13335 · Cloudflare1.451 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.155 msAS8002 · Stealth0.377 msAS8002 · StealthSame responder
20.177 msAS8002 · Stealth0.187 msAS8002 · StealthSame responder
318.052 ms6.599 msSame responder
41.619 msAS13335 · CloudflareNo replyNot established
52.220 msAS13335 · Cloudflare1.653 msAS13335 · CloudflareDifferent responders
6No reply1.239 msAS13335 · CloudflareNot established
71.272 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

Elevated latency observed.

Endpoint round-trip time was elevated during part of the event. The available path observations do not identify where the increase occurred.

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.278 msUsual round trip before the event
Last recorded event RTT1.283 msLast successful event recording
Event p95 RTT3.392 ms95th percentile of successful recordings
Change from baseline+0.006 msLast event RTT compared with the baseline
Successful / expected recordings474 / 500Recorded 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