Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-AFF763EB38C8C936

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. 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

29 Oct 2026 13:45 – 29 Oct 2026 17:29 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.370 ms
1.476 ms
1.422 ms
1.423 ms
1.490 ms
1.410 ms
1.367 ms
1.422 ms
7.557 ms
1.373 ms
1.351 ms
1.409 ms
1.402 ms
1.526 ms
1.474 ms
3.084 ms
1.353 ms
1.358 ms
1.369 ms
1.486 ms
6.116 ms
6.842 ms
1.572 ms
1.381 ms
1.387 ms
1.416 ms
1.939 ms
1.530 ms
1.990 ms
1.523 ms
1.435 ms
1.381 ms
1.415 ms
1.373 ms
1.405 ms
1.385 ms
1.374 ms
1.954 ms
1.494 ms
1.367 ms
1.359 ms
1.388 ms
3.111 ms
2.222 ms
1.345 ms
1.521 ms
1.549 ms
11.589 ms
1.411 ms
9.274 ms
1.434 ms
18.984 ms
1.337 ms
1.463 ms
1.383 ms
6.249 ms
17.174 ms
1.456 ms
1.392 ms
1.352 ms
1.408 ms
2.490 ms
1.363 ms
1.490 ms
1.360 ms
1.367 ms
1.365 ms
1.350 ms
1.510 ms
1.545 ms
1.391 ms
1.405 ms
1.327 ms
1.351 ms
1.429 ms
1.382 ms
1.334 ms
1.392 ms
1.361 ms
1.386 ms
1.484 ms
1.357 ms
1.493 ms
1.343 ms
1.392 ms
1.374 ms
1.415 ms
1.391 ms
1.459 ms
1.370 ms
1.386 ms
1.376 ms
1.433 ms
1.489 ms
1.338 ms
1.331 ms
4.502 ms
1.377 ms
7.063 ms
1.439 ms
11.755 ms
1.375 ms
1.347 ms
1.406 ms
1.418 ms
1.567 ms
1.395 ms
17.288 ms
13.229 ms
1.419 ms
1.454 ms
1.386 ms
1.386 ms
1.363 ms
1.514 ms
1.467 ms
1.472 ms
1.371 ms
1.444 ms
1.363 ms
1.475 ms
1.374 ms
7.551 ms
1.345 ms
1.406 ms
1.666 ms
1.373 ms
8.100 ms
1.387 ms
1.388 ms
1.373 ms
1.529 ms
1.349 ms
1.363 ms
1.535 ms
1.335 ms
17.265 ms
1.552 ms
1.472 ms
1.382 ms
1.522 ms
1.353 ms
1.369 ms
1.379 ms
1.382 ms
1.517 ms
1.430 ms
1.364 ms
1.475 ms
1.361 ms
1.383 ms
1.444 ms
2.382 ms
1.564 ms
1.359 ms
1.405 ms
1.369 ms
1.385 ms
1.514 ms
1.364 ms
18.601 ms
1.420 ms
1.340 ms
1.365 ms
1.393 ms
12.213 ms
1.405 ms
1.388 ms
17.228 ms
1.402 ms
17.099 ms
4.521 ms
16.554 ms
1.437 ms
1.396 ms
1.335 ms
1.369 ms
1.405 ms
1.424 ms
1.375 ms
1.331 ms
1.459 ms
1.580 ms
1.374 ms
1.392 ms
1.401 ms
1.370 ms
1.383 ms
1.374 ms
1.509 ms
1.340 ms
1.344 ms
1.341 ms
5.154 ms
1.399 ms
1.407 ms
1.365 ms
1.420 ms
1.424 ms
1.443 ms
1.385 ms
18.930 ms
1.404 ms
1.479 ms
1.372 ms
1.429 ms
1.380 ms
1.357 ms
1.401 ms
1.444 ms
1.370 ms
1.349 ms
1.341 ms
1.389 ms
1.440 ms
1.360 ms
7.377 ms
1.484 ms
1.371 ms
1.381 ms
1.372 ms
1.340 ms
1.401 ms
1.353 ms
1.441 ms
1.353 ms
1.362 ms
1.414 ms
1.411 ms
1.516 ms
1.341 ms
1.383 ms
1.505 ms
1.333 ms
1.395 ms
1.352 ms
1.362 ms
1.343 ms
1.336 ms
1.509 ms
1.315 ms
1.383 ms
1.360 ms
1.340 ms
1.352 ms
1.445 ms
1.508 ms
1.388 ms
1.353 ms
1.371 ms
1.427 ms
1.347 ms
1.374 ms
1.428 ms
1.370 ms
1.349 ms
1.363 ms
1.384 ms
1.715 ms
1.432 ms
12.851 ms
1.370 ms
1.396 ms
13.241 ms
1.401 ms
1.394 ms
1.372 ms
1.339 ms
1.409 ms
1.393 ms
1.414 ms
1.446 ms
1.422 ms
1.443 ms
1.497 ms
8.717 ms
1.397 ms
1.409 ms
1.394 ms
1.349 ms
1.407 ms
1.348 ms
1.461 ms
1.450 ms
1.340 ms
1.411 ms
1.354 ms
1.382 ms
10.862 ms
1.375 ms
1.531 ms
1.382 ms
1.402 ms
3.235 ms
2.625 ms
1.471 ms
18.613 ms
1.367 ms
2.047 ms
1.588 ms
1.423 ms
5.220 ms
1.394 ms
1.444 ms
1.328 ms
1.333 ms
1.493 ms
1.321 ms
1.402 ms
1.351 ms
1.422 ms
1.505 ms
1.416 ms
1.408 ms
1.419 ms
1.351 ms
1.335 ms
1.378 ms
1.386 ms
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
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.119 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.173 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.499 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.234 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop71.577 msReply 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.777 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.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop44.726 msReply RTT AS13335 · Cloudflare
Before

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.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.486 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.364 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.762 msReply RTT AS13335 · Cloudflare
Before

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.180 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.468 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.382 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.119 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.811 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.393 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 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 hop6.250 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.640 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.209 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.390 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop24.017 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.750 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.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.184 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 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 hop15.447 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.264 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.366 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.477 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.512 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.013 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 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.181 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination10.802 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.113 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.878 msReply RTT AS13335 · Cloudflare
After

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.261 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.789 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop31.075 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.967 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.149 msAS8002 · Stealth0.142 msAS8002 · StealthSame responder
20.176 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
344.726 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.137 msAS8002 · Stealth0.393 msAS8002 · StealthSame responder
20.180 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
3No replyNo replyNot established
4No replyNo replyNot established
51.468 msAS13335 · Cloudflare6.250 msAS13335 · CloudflareDifferent responders
61.382 msAS13335 · Cloudflare1.640 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.234 msAS8002 · Stealth0.209 msAS8002 · StealthSame responder
20.188 msAS8002 · Stealth0.184 msAS8002 · StealthSame responder
371.577 ms16.390 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.574 msAS13335 · Cloudflare24.017 msAS13335 · CloudflareDifferent responders
61.777 msAS13335 · Cloudflare1.750 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.

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.389 msUsual round trip before the event
Last recorded event RTT1.336 msLast successful event recording
Event p95 RTT15.664 ms95th percentile of successful recordings
Change from baseline-0.052 msLast event RTT compared with the baseline
Successful / expected recordings210 / 210Recorded 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