Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-5317A835DBB75261

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 00:25 – 29 Oct 2026 03:14 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
2.131 ms
1.352 ms
1.377 ms
1.502 ms
1.409 ms
1.504 ms
1.405 ms
1.503 ms
1.382 ms
1.373 ms
1.382 ms
1.338 ms
1.415 ms
2.357 ms
1.388 ms
2.084 ms
1.359 ms
1.548 ms
1.387 ms
1.365 ms
1.383 ms
1.393 ms
14.330 ms
1.359 ms
1.352 ms
1.435 ms
1.352 ms
1.381 ms
1.453 ms
1.366 ms
1.392 ms
1.438 ms
1.455 ms
1.428 ms
1.355 ms
5.725 ms
1.958 ms
2.642 ms
1.423 ms
1.454 ms
1.474 ms
1.368 ms
1.403 ms
1.499 ms
1.381 ms
1.400 ms
1.352 ms
1.353 ms
1.520 ms
1.329 ms
1.394 ms
2.546 ms
1.347 ms
1.398 ms
1.487 ms
1.552 ms
2.269 ms
1.350 ms
1.509 ms
1.438 ms
1.395 ms
1.373 ms
1.380 ms
1.445 ms
1.404 ms
1.443 ms
5.564 ms
1.344 ms
1.490 ms
1.346 ms
1.360 ms
1.333 ms
1.389 ms
1.438 ms
1.450 ms
1.364 ms
1.419 ms
1.404 ms
1.347 ms
1.395 ms
1.343 ms
1.378 ms
1.397 ms
1.351 ms
1.627 ms
11.759 ms
9.951 ms
5.271 ms
1.380 ms
1.387 ms
1.333 ms
1.423 ms
1.462 ms
1.436 ms
1.365 ms
1.977 ms
1.545 ms
1.376 ms
1.394 ms
1.399 ms
1.402 ms
1.360 ms
1.412 ms
1.419 ms
1.362 ms
1.426 ms
1.374 ms
1.354 ms
1.372 ms
1.370 ms
1.420 ms
1.407 ms
1.474 ms
1.352 ms
1.396 ms
1.456 ms
1.364 ms
1.420 ms
1.351 ms
1.380 ms
1.379 ms
5.461 ms
6.008 ms
1.468 ms
1.345 ms
1.356 ms
1.424 ms
1.406 ms
1.431 ms
1.401 ms
1.327 ms
1.369 ms
1.347 ms
1.462 ms
1.453 ms
1.344 ms
1.443 ms
8.662 ms
1.364 ms
1.446 ms
18.575 ms
1.516 ms
1.391 ms
1.408 ms
1.470 ms
1.375 ms
1.380 ms
1.424 ms
1.334 ms
1.364 ms
1.386 ms
1.534 ms
1.365 ms
1.539 ms
1.471 ms
1.432 ms
1.424 ms
1.385 ms
1.373 ms
1.483 ms
1.432 ms
1.425 ms
1.342 ms
1.378 ms
1.381 ms
1.445 ms
1.346 ms
6.329 ms
1.341 ms
1.370 ms
1.385 ms
15.725 ms
1.584 ms
1.379 ms
1.357 ms
16.697 ms
1.403 ms
1.433 ms
1.397 ms
1.413 ms
1.869 ms
6.242 ms
1.404 ms
1.381 ms
4.280 ms
1.397 ms
1.566 ms
1.414 ms
1.416 ms
1.375 ms
1.352 ms
1.375 ms
1.456 ms
1.481 ms
1.386 ms
1.482 ms
1.374 ms
1.390 ms
1.451 ms
1.361 ms
1.360 ms
1.370 ms
1.364 ms
1.367 ms
1.411 ms
1.373 ms
1.431 ms
1.357 ms
1.414 ms
1.420 ms
1.428 ms
1.387 ms
1.385 ms
1.477 ms
1.344 ms
1.463 ms
1.390 ms
1.352 ms
1.368 ms
1.660 ms
1.367 ms
1.327 ms
1.424 ms
1.464 ms
1.367 ms
1.476 ms
1.447 ms
1.453 ms
1.427 ms
1.348 ms
1.350 ms
1.629 ms
1.790 ms
1.391 ms
1.390 ms
1.555 ms
1.478 ms
1.350 ms
1.447 ms
1.377 ms
1.433 ms
1.410 ms
1.427 ms
1.341 ms
1.379 ms
1.346 ms
1.375 ms
1.478 ms
1.410 ms
1.462 ms
1.376 ms
1.378 ms
1.417 ms
1.413 ms
2.488 ms
1.394 ms
1.390 ms
1.362 ms
1.372 ms
1.369 ms
1.348 ms
1.384 ms
1.532 ms
1.412 ms
1.345 ms
1.426 ms
1.774 ms
1.473 ms
1.417 ms
1.389 ms
1.462 ms
1.466 ms
1.451 ms
1.356 ms
1.332 ms
1.393 ms
1.492 ms
1.355 ms
5.875 ms
1.354 ms
1.346 ms
1.346 ms
1.400 ms
1.332 ms
1.341 ms
1.381 ms
1.362 ms
1.365 ms
1.338 ms
1.351 ms
1.375 ms
1.350 ms
1.334 ms
1.335 ms
1.569 ms
1.397 ms
1.364 ms
1.383 ms
1.411 ms
1.377 ms
1.416 ms
1.398 ms
1.453 ms
1.321 ms
1.665 ms
1.418 ms
1.352 ms
8.444 ms
1.506 ms
1.469 ms
1.388 ms
1.394 ms
1.402 ms
8.923 ms
17.286 ms
1.350 ms
1.347 ms
1.362 ms
1.375 ms
1.495 ms
1.400 ms
1.494 ms
1.471 ms
1.392 ms
1.383 ms
1.501 ms
1.389 ms
1.398 ms
1.359 ms
1.364 ms
1.351 ms
1.474 ms
1.453 ms
1.373 ms
1.465 ms
1.348 ms
1.615 ms
1.370 ms
1.343 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.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.533 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.672 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.066 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.090 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.119 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
Before

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.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.335 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.862 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.496 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.245 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.527 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.674 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.058 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.209 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.683 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop20.053 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop6.135 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.610 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.427 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.177 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.735 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.759 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.115 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop38.529 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.198 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.194 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop46.742 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop11.151 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.407 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.226 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.928 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.185 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.240 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.690 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.449 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.591 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.911 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.210 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.295 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.969 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.585 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.424 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.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.921 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.181 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.252 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.929 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.819 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.108 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.127 msAS8002 · StealthSame responder
20.183 msAS8002 · Stealth0.209 msAS8002 · StealthSame responder
3Not recorded1.683 msNot established
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.119 msAS8002 · Stealth0.130 msAS8002 · StealthSame responder
20.176 msAS8002 · Stealth0.427 msAS8002 · StealthSame responder
31.533 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.245 msAS8002 · Stealth0.161 msAS8002 · StealthSame responder
20.183 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
31.527 ms22.177 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
55.674 msAS13335 · Cloudflare1.735 msAS13335 · CloudflareDifferent responders
61.058 msAS13335 · Cloudflare1.759 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.387 msUsual round trip before the event
Last recorded event RTT1.660 msLast successful event recording
Event p95 RTT6.246 ms95th percentile of successful recordings
Change from baseline+0.274 msLast event RTT compared with the baseline
Successful / expected recordings100 / 100Recorded 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