Start an order
Root cause analysis / Investigation

api.x.ai

Reference RCA-2A5BEC9280BB9C1D

xAI 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

03 Nov 2026 15:05 – 03 Nov 2026 17: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.
Recorded at (UTC)RTT
1.310 ms
1.565 ms
1.375 ms
1.377 ms
1.307 ms
1.459 ms
1.422 ms
1.382 ms
1.316 ms
1.373 ms
1.377 ms
1.403 ms
1.343 ms
1.396 ms
1.356 ms
1.338 ms
1.371 ms
1.383 ms
1.359 ms
1.333 ms
2.821 ms
1.559 ms
1.446 ms
1.345 ms
1.302 ms
1.336 ms
1.379 ms
1.439 ms
1.392 ms
1.313 ms
1.321 ms
1.363 ms
1.352 ms
1.357 ms
1.364 ms
1.371 ms
1.353 ms
1.344 ms
1.337 ms
1.328 ms
1.331 ms
1.303 ms
1.325 ms
1.869 ms
1.325 ms
1.487 ms
1.338 ms
1.393 ms
1.404 ms
1.361 ms
1.387 ms
1.330 ms
1.361 ms
1.338 ms
1.367 ms
1.456 ms
1.507 ms
1.445 ms
1.345 ms
1.436 ms
1.402 ms
1.381 ms
1.347 ms
1.491 ms
1.384 ms
1.312 ms
1.338 ms
1.340 ms
1.327 ms
1.406 ms
1.349 ms
1.298 ms
1.408 ms
1.406 ms
1.342 ms
1.352 ms
1.420 ms
1.490 ms
1.355 ms
1.372 ms
4.885 ms
1.435 ms
1.407 ms
1.426 ms
1.408 ms
10.258 ms
1.406 ms
1.469 ms
4.002 ms
1.439 ms
1.368 ms
1.386 ms
1.379 ms
4.034 ms
1.444 ms
1.357 ms
1.349 ms
1.332 ms
1.340 ms
1.435 ms
1.421 ms
1.411 ms
1.327 ms
1.471 ms
1.482 ms
1.336 ms
1.338 ms
1.361 ms
1.368 ms
1.457 ms
1.330 ms
1.481 ms
1.371 ms
1.394 ms
1.407 ms
1.318 ms
1.408 ms
1.342 ms
1.370 ms
1.423 ms
1.415 ms
1.340 ms
2.955 ms
1.402 ms
1.412 ms
1.353 ms
3.777 ms
1.477 ms
1.558 ms
1.312 ms
4.036 ms
7.310 ms
1.445 ms
1.429 ms
1.489 ms
1.361 ms
1.340 ms
1.455 ms
1.341 ms
1.369 ms
1.482 ms
1.501 ms
1.298 ms
1.537 ms
1.330 ms
1.318 ms
1.358 ms
10.233 ms
1.386 ms
1.386 ms
1.349 ms
1.345 ms
1.362 ms
1.371 ms
1.400 ms
1.521 ms
1.412 ms
2.443 ms
1.296 ms
1.313 ms
1.354 ms
1.347 ms
1.452 ms
1.450 ms
1.416 ms
1.337 ms
1.374 ms
1.366 ms
1.368 ms
7.064 ms
1.365 ms
1.385 ms
5.661 ms
1.488 ms
1.434 ms
5.471 ms
1.475 ms
1.418 ms
1.386 ms
1.371 ms
1.357 ms
1.350 ms
1.345 ms
1.341 ms
1.383 ms
1.715 ms
1.570 ms
1.323 ms
1.354 ms
1.367 ms
1.409 ms
1.391 ms
1.330 ms
1.312 ms
1.403 ms
1.394 ms
1.385 ms
1.485 ms
1.508 ms
1.370 ms
1.334 ms
1.375 ms
1.335 ms
1.342 ms
1.411 ms
1.383 ms
1.326 ms
1.590 ms
1.344 ms
1.347 ms
1.326 ms
1.371 ms
1.328 ms
1.351 ms
1.407 ms
1.453 ms
1.439 ms
1.445 ms
1.390 ms
1.331 ms
1.357 ms
1.420 ms
1.348 ms
1.350 ms
1.478 ms
1.330 ms
1.442 ms
1.359 ms
1.304 ms
1.393 ms
1.401 ms
1.413 ms
1.351 ms
1.395 ms
1.379 ms
1.380 ms
1.360 ms
1.334 ms
1.386 ms
1.393 ms
1.368 ms
1.433 ms
1.357 ms
1.567 ms
1.410 ms
1.357 ms
1.375 ms
1.357 ms
1.371 ms
1.356 ms
1.457 ms
1.388 ms
1.384 ms
1.360 ms
1.387 ms
1.601 ms
1.329 ms
1.411 ms
1.322 ms
1.431 ms
1.336 ms
1.417 ms
1.309 ms
1.305 ms
1.351 ms
6.328 ms
1.343 ms
1.469 ms
1.352 ms
1.336 ms
1.602 ms
1.359 ms
1.314 ms
1.341 ms
1.359 ms
1.364 ms
1.356 ms
1.329 ms
1.401 ms
1.914 ms
1.328 ms
1.347 ms
1.447 ms
1.468 ms
1.391 ms
1.388 ms
1.358 ms
2.084 ms
1.303 ms
1.403 ms
1.383 ms
1.339 ms
1.303 ms
1.519 ms
1.300 ms
1.323 ms
1.353 ms
1.349 ms
1.322 ms
1.339 ms
1.336 ms
1.365 ms
1.365 ms
1.306 ms
1.337 ms
1.353 ms
1.394 ms
1.375 ms
1.344 ms
1.384 ms
1.367 ms
1.394 ms
1.305 ms
1.353 ms
4.132 ms
1.519 ms
1.390 ms
1.328 ms
1.467 ms
1.348 ms
1.412 ms
1.548 ms
1.338 ms
1.331 ms
1.357 ms
1.385 ms
1.341 ms
1.606 ms
1.456 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 2

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.194 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.751 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.173 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.011 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.893 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.275 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 2

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.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.683 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.233 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.722 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.865 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.247 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.165 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.948 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.896 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 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.255 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.681 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.395 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.116 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop20.340 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop32.955 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.512 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.242 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.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.759 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.590 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.661 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.233 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.194 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.537 msReply RTT ASN unavailable
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.194 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.328 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.621 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.022 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.115 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
After

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.227 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.574 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.375 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.474 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.829 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.770 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.389 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.133 msAS8002 · Stealth0.126 msAS8002 · StealthSame responder
20.182 msAS8002 · Stealth0.181 msAS8002 · StealthSame responder
30.683 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.165 msAS8002 · Stealth0.143 msAS8002 · StealthSame responder
20.186 msAS8002 · Stealth0.255 msAS8002 · StealthSame responder
3No replyNo replyNot established
4No replyNo replyNot established
52.948 msAS13335 · Cloudflare1.681 msAS13335 · CloudflareDifferent responders
60.896 msAS13335 · CloudflareNo replyNot established
7Not recorded1.395 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

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.353 msUsual round trip before the event
Last recorded event RTT1.347 msLast successful event recording
Event p95 RTT4.826 ms95th percentile of successful recordings
Change from baseline-0.006 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