Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-FFA688EFF870F3BF

OpenAI 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

29 Oct 2026 17:10 – 29 Oct 2026 19:44 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.469 ms
1.361 ms
1.675 ms
1.975 ms
1.497 ms
1.357 ms
1.377 ms
1.336 ms
1.366 ms
1.375 ms
3.009 ms
1.387 ms
1.411 ms
3.332 ms
3.638 ms
1.358 ms
1.347 ms
1.347 ms
1.332 ms
1.483 ms
1.787 ms
1.470 ms
1.425 ms
1.405 ms
1.628 ms
14.435 ms
1.475 ms
3.422 ms
1.400 ms
3.880 ms
1.341 ms
1.379 ms
1.372 ms
1.430 ms
1.368 ms
1.571 ms
1.436 ms
1.354 ms
1.355 ms
13.629 ms
1.363 ms
2.041 ms
1.415 ms
11.343 ms
16.250 ms
1.466 ms
1.335 ms
16.547 ms
1.363 ms
1.409 ms
1.419 ms
1.397 ms
1.465 ms
9.185 ms
4.046 ms
1.342 ms
1.586 ms
5.037 ms
1.393 ms
19.703 ms
17.231 ms
1.390 ms
1.351 ms
1.577 ms
1.369 ms
1.481 ms
1.384 ms
1.415 ms
5.860 ms
1.360 ms
1.343 ms
1.377 ms
18.408 ms
1.362 ms
1.367 ms
1.477 ms
1.393 ms
1.408 ms
1.427 ms
1.331 ms
1.362 ms
1.357 ms
1.319 ms
1.353 ms
1.394 ms
1.530 ms
1.351 ms
1.383 ms
1.518 ms
1.374 ms
1.408 ms
1.349 ms
1.581 ms
1.570 ms
1.382 ms
1.418 ms
1.336 ms
1.379 ms
1.393 ms
1.322 ms
1.407 ms
1.401 ms
1.361 ms
1.373 ms
1.358 ms
1.341 ms
1.364 ms
1.462 ms
1.395 ms
1.370 ms
1.403 ms
1.422 ms
1.491 ms
1.489 ms
1.531 ms
1.432 ms
1.521 ms
1.346 ms
1.369 ms
1.397 ms
1.367 ms
1.368 ms
1.378 ms
1.378 ms
1.385 ms
1.350 ms
1.393 ms
19.489 ms
1.390 ms
1.368 ms
1.374 ms
1.371 ms
1.394 ms
18.111 ms
20.917 ms
1.368 ms
1.394 ms
1.358 ms
18.223 ms
20.089 ms
6.338 ms
8.196 ms
1.380 ms
1.563 ms
1.369 ms
1.448 ms
1.372 ms
1.410 ms
1.363 ms
19.525 ms
1.375 ms
16.013 ms
1.373 ms
1.355 ms
1.547 ms
1.385 ms
1.444 ms
1.339 ms
1.366 ms
1.374 ms
1.347 ms
1.537 ms
1.421 ms
1.347 ms
1.379 ms
1.375 ms
1.343 ms
1.375 ms
1.364 ms
1.457 ms
1.372 ms
1.392 ms
1.492 ms
1.358 ms
1.337 ms
1.353 ms
1.361 ms
1.354 ms
1.378 ms
1.424 ms
1.396 ms
1.397 ms
1.396 ms
1.337 ms
1.363 ms
1.377 ms
1.445 ms
1.426 ms
1.369 ms
2.064 ms
7.984 ms
1.365 ms
1.410 ms
1.486 ms
1.454 ms
1.407 ms
1.462 ms
1.378 ms
18.851 ms
1.540 ms
2.568 ms
1.373 ms
1.368 ms
1.385 ms
1.345 ms
1.419 ms
1.647 ms
1.357 ms
1.407 ms
1.362 ms
1.405 ms
1.353 ms
1.346 ms
1.379 ms
1.346 ms
1.484 ms
1.361 ms
1.348 ms
1.390 ms
1.322 ms
1.509 ms
1.499 ms
1.368 ms
2.158 ms
1.349 ms
1.547 ms
1.364 ms
1.378 ms
1.748 ms
1.364 ms
20.160 ms
1.368 ms
1.374 ms
1.395 ms
1.413 ms
1.418 ms
1.344 ms
1.441 ms
1.364 ms
1.617 ms
1.342 ms
19.438 ms
1.427 ms
1.412 ms
2.217 ms
1.680 ms
1.402 ms
6.252 ms
1.355 ms
1.387 ms
8.983 ms
6.774 ms
19.695 ms
8.970 ms
1.375 ms
1.353 ms
1.413 ms
1.494 ms
10.172 ms
1.356 ms
1.451 ms
16.155 ms
16.502 ms
1.404 ms
2.096 ms
1.454 ms
1.443 ms
1.727 ms
9.907 ms
18.374 ms
17.683 ms
14.992 ms
15.959 ms
17.677 ms
9.188 ms
3.259 ms
7.698 ms
1.502 ms
1.388 ms
1.481 ms
1.353 ms
19.236 ms
13.637 ms
1.416 ms
1.490 ms
1.538 ms
6.531 ms
3.024 ms
4.642 ms
1.368 ms
1.382 ms
1.455 ms
1.476 ms
1.372 ms
1.356 ms
1.430 ms
1.348 ms
1.362 ms
1.480 ms
1.412 ms
1.338 ms
1.540 ms
1.448 ms
1.360 ms
5.219 ms
1.382 ms
1.398 ms
1.439 ms
Network path / recorded observations

Network path observations.

18 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.119 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.243 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.655 msReply RTT ASN unavailable
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.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.195 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.529 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.279 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.421 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.157 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.236 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.392 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.755 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.753 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.571 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop64.313 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.585 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop6.485 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination5.240 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.357 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.255 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop21.233 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.481 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.269 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination12.441 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.157 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.844 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.073 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.087 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.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.311 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 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.134 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.273 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.757 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.237 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.947 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.833 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.920 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.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.486 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.280 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.311 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination4.126 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.230 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.165 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 hop1.281 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.971 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.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop69.485 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.211 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.109 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.669 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.676 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.119 msAS8002 · Stealth0.125 msAS8002 · StealthSame responder
20.243 msAS8002 · Stealth0.197 msAS8002 · StealthSame responder
31.655 msNot 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.357 msAS8002 · Stealth0.237 msAS8002 · StealthSame responder
20.255 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
321.233 ms18.947 msAS13335 · CloudflareSame responder
41.481 msAS13335 · CloudflareNo replyNot established
52.269 msAS13335 · Cloudflare1.833 msAS13335 · CloudflareDifferent responders
612.441 msAS13335 · CloudflareNo replyNot established
7Not recorded1.920 msAS13335 · CloudflareNot established
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.157 msAS8002 · Stealth0.157 msAS8002 · StealthSame responder
20.236 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
36.392 msAS13335 · Cloudflare0.844 msSame responder
4No replyNo replyNot established
51.755 msAS13335 · Cloudflare1.073 msAS13335 · CloudflareDifferent responders
6No reply1.087 msAS13335 · CloudflareNot established
71.753 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.

Possible SLA event. 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.386 msUsual round trip before the event
Last recorded event RTT2.064 msLast successful event recording
Event p95 RTT18.919 ms95th percentile of successful recordings
Change from baseline+0.678 msLast event RTT compared with the baseline
Successful / expected recordings70 / 70Recorded 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