Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-BC6A359E02F8AC89

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

04 Nov 2026 23:20 – 05 Nov 2026 02:09 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.397 ms
1.352 ms
1.375 ms
1.420 ms
1.376 ms
1.335 ms
1.414 ms
1.341 ms
1.432 ms
1.323 ms
1.444 ms
1.347 ms
1.441 ms
1.339 ms
1.340 ms
1.347 ms
1.342 ms
1.673 ms
1.341 ms
1.338 ms
1.343 ms
1.320 ms
1.398 ms
1.344 ms
1.521 ms
1.336 ms
1.340 ms
1.352 ms
1.509 ms
1.348 ms
1.396 ms
1.365 ms
1.352 ms
1.348 ms
1.335 ms
1.480 ms
1.417 ms
1.486 ms
1.471 ms
4.761 ms
1.421 ms
1.310 ms
1.366 ms
1.341 ms
1.445 ms
1.316 ms
1.382 ms
1.328 ms
1.383 ms
1.400 ms
1.346 ms
1.340 ms
1.398 ms
1.417 ms
14.087 ms
1.329 ms
1.374 ms
1.314 ms
1.394 ms
1.426 ms
1.411 ms
1.355 ms
1.429 ms
1.339 ms
1.414 ms
1.440 ms
1.406 ms
1.383 ms
1.366 ms
1.327 ms
1.436 ms
1.342 ms
1.336 ms
1.325 ms
1.593 ms
1.338 ms
1.378 ms
1.422 ms
1.387 ms
1.338 ms
3.984 ms
1.368 ms
1.383 ms
1.341 ms
1.466 ms
1.350 ms
1.355 ms
1.350 ms
1.343 ms
1.437 ms
1.342 ms
1.313 ms
1.395 ms
1.369 ms
1.350 ms
1.381 ms
1.370 ms
1.368 ms
1.368 ms
1.384 ms
1.338 ms
1.318 ms
1.351 ms
1.460 ms
3.090 ms
1.329 ms
1.318 ms
1.410 ms
1.354 ms
1.389 ms
1.303 ms
1.342 ms
1.366 ms
1.374 ms
1.369 ms
1.368 ms
1.337 ms
1.374 ms
1.343 ms
1.353 ms
1.456 ms
1.347 ms
1.459 ms
3.796 ms
12.871 ms
15.921 ms
11.111 ms
1.390 ms
16.933 ms
1.334 ms
4.576 ms
8.221 ms
1.381 ms
4.706 ms
6.589 ms
1.347 ms
1.313 ms
2.350 ms
1.355 ms
8.865 ms
10.903 ms
10.156 ms
13.808 ms
1.568 ms
1.362 ms
1.342 ms
1.443 ms
1.399 ms
11.979 ms
1.377 ms
1.449 ms
1.769 ms
19.353 ms
3.615 ms
1.457 ms
1.341 ms
19.487 ms
1.318 ms
1.381 ms
1.355 ms
1.333 ms
1.332 ms
2.712 ms
4.301 ms
1.644 ms
1.321 ms
1.361 ms
1.361 ms
1.445 ms
1.394 ms
1.361 ms
17.315 ms
1.340 ms
10.797 ms
1.415 ms
1.458 ms
1.682 ms
1.423 ms
1.365 ms
1.470 ms
1.788 ms
1.386 ms
1.371 ms
1.349 ms
1.556 ms
1.411 ms
1.353 ms
9.417 ms
1.355 ms
1.378 ms
1.340 ms
1.430 ms
1.402 ms
1.387 ms
1.319 ms
1.317 ms
1.385 ms
1.428 ms
1.373 ms
1.574 ms
1.338 ms
1.408 ms
1.380 ms
1.336 ms
1.336 ms
1.400 ms
1.336 ms
1.317 ms
1.386 ms
1.332 ms
1.424 ms
1.314 ms
1.373 ms
1.389 ms
1.332 ms
1.335 ms
1.373 ms
1.359 ms
1.385 ms
1.470 ms
1.336 ms
1.348 ms
1.355 ms
1.393 ms
1.847 ms
1.401 ms
10.609 ms
1.348 ms
1.403 ms
1.657 ms
1.414 ms
1.327 ms
1.366 ms
1.375 ms
1.433 ms
1.351 ms
1.339 ms
1.342 ms
1.360 ms
1.359 ms
1.409 ms
1.357 ms
1.429 ms
1.400 ms
1.464 ms
1.333 ms
1.433 ms
1.320 ms
1.328 ms
1.499 ms
1.392 ms
1.339 ms
1.336 ms
1.445 ms
1.327 ms
1.436 ms
1.345 ms
1.326 ms
1.368 ms
1.405 ms
1.472 ms
1.445 ms
1.367 ms
1.382 ms
1.350 ms
1.430 ms
1.365 ms
1.373 ms
1.334 ms
1.383 ms
1.306 ms
1.385 ms
5.410 ms
1.333 ms
1.379 ms
1.344 ms
1.338 ms
1.319 ms
1.390 ms
1.326 ms
6.762 ms
1.378 ms
1.314 ms
7.641 ms
1.515 ms
1.408 ms
1.357 ms
1.410 ms
1.360 ms
1.350 ms
19.975 ms
1.320 ms
1.397 ms
1.311 ms
1.356 ms
1.345 ms
1.474 ms
1.337 ms
1.440 ms
1.427 ms
1.310 ms
1.380 ms
1.411 ms
1.344 ms
1.373 ms
1.334 ms
1.411 ms
1.432 ms
1.322 ms
1.365 ms
1.401 ms
1.477 ms
1.328 ms
1.649 ms
1.346 ms
1.338 ms
1.437 ms
1.369 ms
1.332 ms
1.342 ms
1.425 ms
1.342 ms
1.340 ms
3.647 ms
1.340 ms
1.328 ms
1.354 ms
1.348 ms
1.322 ms
1.459 ms
1.337 ms
1.649 ms
1.359 ms
1.353 ms
1.346 ms
1.359 ms
1.381 ms
1.344 ms
1.318 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.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.691 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.217 msReply RTT ASN unavailable
Before

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.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.254 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.969 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.358 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.521 msReply RTT ASN unavailable
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.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.596 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.275 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.252 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.166 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.574 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.466 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.300 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.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.221 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop37.392 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop26.759 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.884 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.044 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.245 msReply RTT AS13335 · Cloudflare
During

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.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.304 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.725 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.299 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.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.998 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.352 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.790 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.303 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.165 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop20.335 msReply RTT AS13335 · Cloudflare
After

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.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.998 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.491 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination7.898 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.113 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.645 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.906 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.146 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.442 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.221 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.234 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop41.194 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.462 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.296 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.269 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.720 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Destination1.267 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.150 msAS8002 · Stealth0.121 msAS8002 · StealthSame responder
20.691 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
31.217 ms1.245 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.135 msAS8002 · Stealth0.131 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.221 msAS8002 · StealthSame responder
33.521 ms37.392 msAS13335 · CloudflareSame 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.166 msAS8002 · Stealth0.138 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.172 msAS8002 · StealthSame responder
312.574 msAS13335 · Cloudflare1.304 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
53.466 msAS13335 · Cloudflare1.725 msAS13335 · CloudflareDifferent responders
61.300 msAS13335 · Cloudflare1.299 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.157 msAS8002 · Stealth0.149 msAS8002 · StealthSame responder
20.186 msAS8002 · Stealth0.182 msAS8002 · StealthSame responder
31.596 ms26.759 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.275 msAS13335 · Cloudflare5.884 msAS13335 · CloudflareDifferent responders
61.252 msAS13335 · Cloudflare1.044 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.370 msUsual round trip before the event
Last recorded event RTT1.470 msLast successful event recording
Event p95 RTT13.914 ms95th percentile of successful recordings
Change from baseline+0.100 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