Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-F24220332B46CE09

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

05 Nov 2026 00:35 – 05 Nov 2026 03:04 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.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
1.396 ms
1.421 ms
1.396 ms
1.378 ms
1.389 ms
1.329 ms
1.337 ms
1.340 ms
1.338 ms
1.363 ms
1.342 ms
1.433 ms
1.356 ms
1.336 ms
1.485 ms
1.345 ms
1.419 ms
1.336 ms
1.323 ms
1.444 ms
1.434 ms
1.320 ms
1.318 ms
1.319 ms
1.338 ms
1.334 ms
1.479 ms
1.413 ms
1.450 ms
1.342 ms
5.820 ms
1.349 ms
1.364 ms
1.450 ms
1.432 ms
1.478 ms
1.354 ms
1.464 ms
1.347 ms
1.384 ms
1.386 ms
1.379 ms
1.378 ms
1.330 ms
1.588 ms
1.337 ms
1.395 ms
1.401 ms
1.443 ms
1.469 ms
1.326 ms
1.375 ms
1.343 ms
1.337 ms
9.002 ms
1.374 ms
1.318 ms
1.387 ms
1.336 ms
1.336 ms
1.347 ms
1.356 ms
1.326 ms
1.340 ms
1.346 ms
1.345 ms
1.421 ms
1.316 ms
1.408 ms
7.528 ms
1.347 ms
1.415 ms
1.436 ms
1.355 ms
1.337 ms
1.356 ms
1.349 ms
1.355 ms
1.369 ms
1.450 ms
1.350 ms
1.350 ms
1.330 ms
1.436 ms
1.667 ms
1.348 ms
1.349 ms
1.339 ms
1.327 ms
1.310 ms
1.356 ms
1.426 ms
1.338 ms
1.435 ms
1.345 ms
1.372 ms
1.313 ms
1.385 ms
1.411 ms
1.369 ms
1.358 ms
1.358 ms
1.373 ms
4.044 ms
1.336 ms
1.300 ms
1.397 ms
1.408 ms
1.374 ms
1.512 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.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.173 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.312 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.451 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 hop2.134 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.452 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.114 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.222 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.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.796 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.805 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.163 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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.615 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.828 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.462 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.157 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.593 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.252 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.252 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.066 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.082 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.777 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.211 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop26.531 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.874 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.927 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.022 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.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.379 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.259 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.785 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.823 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.497 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.663 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop6.799 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.774 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination3.287 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.485 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.107 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.273 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.171 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.267 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.172 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.631 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop25.387 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.610 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.232 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.595 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.220 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop13.314 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination19.280 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.143 msAS8002 · Stealth0.157 msAS8002 · StealthSame responder
20.173 msAS8002 · Stealth0.179 msAS8002 · StealthSame responder
37.312 msAS13335 · Cloudflare1.593 msSame 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.114 msAS8002 · Stealth0.167 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.193 msAS8002 · StealthSame responder
31.222 msAS13335 · Cloudflare1.379 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.141 msAS8002 · Stealth0.252 msAS8002 · StealthSame responder
20.178 msAS8002 · Stealth0.252 msAS8002 · StealthSame responder
31.615 ms1.066 msSame responder
4No replyNo replyNot established
51.828 msAS13335 · Cloudflare2.082 msAS13335 · CloudflareDifferent responders
61.462 msAS13335 · CloudflareNo replyNot established
7Not recorded1.777 msAS13335 · CloudflareNot 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.

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.371 msUsual round trip before the event
Last recorded event RTT1.459 msLast successful event recording
Event p95 RTT5.477 ms95th percentile of successful recordings
Change from baseline+0.089 msLast event RTT compared with the baseline
Successful / expected recordings60 / 60Recorded 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