Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-A96CF264CC56AAC9

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

30 Oct 2026 15:35 – 30 Oct 2026 18: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.395 ms
1.331 ms
1.372 ms
1.495 ms
1.367 ms
1.362 ms
1.356 ms
1.479 ms
10.463 ms
1.375 ms
1.459 ms
1.476 ms
1.397 ms
1.380 ms
1.367 ms
1.411 ms
1.545 ms
1.499 ms
1.631 ms
1.363 ms
1.405 ms
19.606 ms
1.341 ms
2.361 ms
1.457 ms
1.467 ms
1.460 ms
4.668 ms
1.449 ms
1.369 ms
1.405 ms
1.357 ms
1.370 ms
1.352 ms
1.348 ms
1.422 ms
1.387 ms
1.388 ms
1.355 ms
1.429 ms
1.358 ms
1.440 ms
1.382 ms
1.370 ms
12.545 ms
1.382 ms
2.194 ms
1.374 ms
1.360 ms
1.485 ms
1.348 ms
1.438 ms
1.784 ms
1.480 ms
1.490 ms
1.381 ms
1.357 ms
1.372 ms
1.354 ms
1.380 ms
1.377 ms
1.371 ms
1.408 ms
1.356 ms
1.404 ms
1.367 ms
5.229 ms
1.587 ms
1.451 ms
5.301 ms
1.457 ms
1.430 ms
1.464 ms
1.398 ms
1.360 ms
1.338 ms
1.398 ms
1.368 ms
1.440 ms
1.437 ms
1.375 ms
1.560 ms
1.320 ms
1.401 ms
1.360 ms
1.354 ms
1.446 ms
1.379 ms
1.433 ms
1.362 ms
1.387 ms
1.434 ms
1.375 ms
1.411 ms
1.367 ms
1.416 ms
1.414 ms
1.465 ms
1.396 ms
5.650 ms
1.351 ms
1.339 ms
1.360 ms
1.341 ms
1.393 ms
1.384 ms
7.571 ms
1.366 ms
1.337 ms
1.368 ms
1.338 ms
1.351 ms
1.431 ms
1.418 ms
2.236 ms
1.439 ms
1.326 ms
1.455 ms
1.399 ms
1.382 ms
1.352 ms
17.353 ms
1.449 ms
1.362 ms
1.491 ms
1.327 ms
1.422 ms
1.381 ms
1.341 ms
1.332 ms
8.114 ms
1.401 ms
1.378 ms
1.406 ms
1.361 ms
1.424 ms
1.361 ms
1.357 ms
1.343 ms
2.355 ms
1.452 ms
1.366 ms
1.349 ms
1.424 ms
1.370 ms
1.373 ms
1.384 ms
11.131 ms
1.449 ms
1.334 ms
1.408 ms
1.369 ms
1.406 ms
1.429 ms
1.364 ms
1.406 ms
6.561 ms
10.073 ms
1.451 ms
1.426 ms
4.864 ms
1.383 ms
1.429 ms
1.384 ms
1.352 ms
1.371 ms
1.503 ms
16.103 ms
1.386 ms
1.474 ms
1.461 ms
1.331 ms
1.438 ms
5.036 ms
7.574 ms
1.549 ms
1.370 ms
1.483 ms
16.523 ms
1.472 ms
1.354 ms
1.396 ms
2.453 ms
1.460 ms
1.475 ms
7.658 ms
1.351 ms
2.648 ms
1.400 ms
1.427 ms
1.434 ms
1.397 ms
8.446 ms
1.473 ms
1.377 ms
1.460 ms
1.344 ms
19.075 ms
1.462 ms
1.336 ms
1.785 ms
1.399 ms
1.397 ms
18.778 ms
1.419 ms
11.544 ms
1.383 ms
1.403 ms
1.431 ms
1.386 ms
1.457 ms
1.359 ms
1.327 ms
1.535 ms
1.394 ms
1.410 ms
1.379 ms
1.421 ms
1.417 ms
1.414 ms
1.549 ms
1.465 ms
1.396 ms
1.335 ms
1.475 ms
1.405 ms
1.407 ms
1.427 ms
1.452 ms
1.365 ms
1.411 ms
1.400 ms
1.477 ms
1.531 ms
1.452 ms
1.373 ms
1.376 ms
1.429 ms
1.436 ms
1.354 ms
1.473 ms
1.368 ms
1.398 ms
1.439 ms
1.341 ms
12.998 ms
1.366 ms
1.441 ms
1.427 ms
1.350 ms
2.204 ms
1.384 ms
1.468 ms
1.386 ms
1.383 ms
1.388 ms
1.370 ms
1.415 ms
1.355 ms
1.373 ms
1.389 ms
1.384 ms
1.305 ms
1.368 ms
1.368 ms
1.371 ms
1.436 ms
1.368 ms
1.375 ms
1.412 ms
1.416 ms
1.343 ms
1.490 ms
1.336 ms
1.451 ms
1.382 ms
1.543 ms
1.404 ms
1.362 ms
1.368 ms
2.312 ms
1.429 ms
15.121 ms
1.385 ms
2.076 ms
1.392 ms
1.534 ms
1.546 ms
1.689 ms
1.397 ms
1.364 ms
1.356 ms
1.334 ms
1.341 ms
1.338 ms
1.372 ms
1.434 ms
1.368 ms
1.352 ms
1.481 ms
1.476 ms
1.496 ms
1.491 ms
1.434 ms
1.406 ms
1.362 ms
1.373 ms
1.397 ms
1.360 ms
1.335 ms
1.402 ms
1.373 ms
3.029 ms
1.524 ms
1.383 ms
1.385 ms
18.251 ms
1.434 ms
1.353 ms
1.345 ms
1.441 ms
1.517 ms
1.386 ms
1.460 ms
1.356 ms
1.420 ms
1.356 ms
1.460 ms
1.492 ms
1.406 ms
1.362 ms
1.391 ms
1.445 ms
1.341 ms
1.352 ms
1.396 ms
2.617 ms
4.382 ms
19.435 ms
2.888 ms
16.986 ms
1.469 ms
19.550 ms
3.113 ms
1.382 ms
19.985 ms
8.330 ms
2.885 ms
1.397 ms
11.189 ms
1.397 ms
1.388 ms
1.370 ms
1.340 ms
2.162 ms
1.384 ms
1.431 ms
1.368 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.476 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.183 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.726 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.116 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.355 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.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.209 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 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.361 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.272 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.454 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 hop9.697 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.836 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.123 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.110 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 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.246 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.141 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.665 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 hop7.037 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.561 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.579 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.703 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.514 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.250 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.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
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.216 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 hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Destination1.194 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.240 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.242 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.741 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.850 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.646 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.180 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.180 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.823 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.404 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.449 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.130 msAS8002 · Stealth0.123 msAS8002 · StealthSame responder
20.205 msAS8002 · Stealth0.189 msAS8002 · StealthSame responder
325.476 msAS13335 · Cloudflare16.110 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.147 msAS8002 · Stealth0.122 msAS8002 · StealthSame responder
20.209 msAS8002 · Stealth0.179 msAS8002 · StealthSame 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.141 msAS8002 · Stealth0.146 msAS8002 · StealthSame responder
20.454 msAS8002 · Stealth0.199 msAS8002 · StealthSame responder
3No replyNo replyNot established
4No replyNo replyNot established
59.697 msAS13335 · Cloudflare1.246 msAS13335 · CloudflareSame responder
61.836 msAS13335 · Cloudflare1.141 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

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.378 msUsual round trip before the event
Last recorded event RTT1.354 msLast successful event recording
Event p95 RTT10.942 ms95th percentile of successful recordings
Change from baseline-0.024 msLast event RTT compared with the baseline
Successful / expected recordings130 / 130Recorded 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