Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-EC2BB5F62A4A1CBE

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

03 Nov 2026 19:30 – 03 Nov 2026 23: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
11.558 ms
1.343 ms
1.354 ms
1.358 ms
6.338 ms
1.402 ms
5.380 ms
1.371 ms
6.165 ms
1.339 ms
8.445 ms
16.431 ms
1.342 ms
1.332 ms
1.402 ms
1.441 ms
1.382 ms
1.370 ms
1.371 ms
16.649 ms
1.399 ms
1.339 ms
1.336 ms
1.313 ms
13.912 ms
1.357 ms
1.377 ms
1.350 ms
7.554 ms
1.462 ms
1.629 ms
1.379 ms
1.388 ms
12.739 ms
1.639 ms
1.373 ms
1.332 ms
1.479 ms
1.513 ms
1.449 ms
1.365 ms
2.636 ms
1.479 ms
1.338 ms
1.378 ms
1.393 ms
1.316 ms
6.998 ms
1.368 ms
1.377 ms
1.343 ms
1.377 ms
1.661 ms
1.321 ms
12.040 ms
1.350 ms
1.435 ms
1.456 ms
7.393 ms
19.667 ms
1.339 ms
1.374 ms
1.347 ms
1.363 ms
1.368 ms
1.392 ms
1.382 ms
1.349 ms
1.335 ms
1.386 ms
1.354 ms
1.450 ms
1.315 ms
1.383 ms
1.353 ms
1.365 ms
1.335 ms
1.349 ms
1.403 ms
5.825 ms
1.365 ms
1.379 ms
1.407 ms
1.332 ms
1.338 ms
1.439 ms
1.389 ms
1.400 ms
1.452 ms
1.509 ms
1.374 ms
1.328 ms
1.429 ms
1.321 ms
1.367 ms
1.347 ms
1.343 ms
1.403 ms
1.370 ms
1.436 ms
1.377 ms
1.399 ms
1.391 ms
1.359 ms
1.394 ms
1.444 ms
1.338 ms
1.378 ms
1.336 ms
1.333 ms
1.351 ms
3.848 ms
1.361 ms
1.520 ms
1.359 ms
1.483 ms
1.422 ms
1.359 ms
1.351 ms
1.366 ms
1.411 ms
1.457 ms
1.357 ms
1.422 ms
4.073 ms
1.364 ms
1.458 ms
1.367 ms
4.865 ms
1.437 ms
17.268 ms
1.372 ms
4.723 ms
1.355 ms
1.383 ms
9.484 ms
1.328 ms
1.321 ms
20.034 ms
1.390 ms
1.336 ms
4.406 ms
2.149 ms
1.400 ms
19.275 ms
1.425 ms
1.362 ms
1.476 ms
1.402 ms
1.373 ms
6.347 ms
1.392 ms
1.354 ms
1.341 ms
1.392 ms
5.735 ms
19.010 ms
1.395 ms
1.445 ms
1.336 ms
1.353 ms
1.529 ms
1.407 ms
1.349 ms
1.411 ms
1.735 ms
8.992 ms
5.444 ms
1.360 ms
1.415 ms
1.359 ms
1.356 ms
1.348 ms
16.974 ms
1.396 ms
1.330 ms
1.336 ms
1.337 ms
1.395 ms
1.382 ms
1.349 ms
1.329 ms
1.371 ms
6.471 ms
1.414 ms
1.395 ms
1.343 ms
1.353 ms
1.349 ms
1.495 ms
1.384 ms
1.374 ms
1.398 ms
1.413 ms
1.405 ms
1.460 ms
1.455 ms
1.344 ms
1.346 ms
1.347 ms
1.495 ms
1.333 ms
1.365 ms
1.386 ms
12.479 ms
1.325 ms
1.355 ms
1.338 ms
11.578 ms
1.335 ms
1.451 ms
1.330 ms
1.427 ms
1.409 ms
1.460 ms
1.344 ms
4.666 ms
1.366 ms
1.352 ms
1.594 ms
8.358 ms
1.347 ms
1.375 ms
1.507 ms
1.528 ms
1.358 ms
1.336 ms
1.374 ms
1.359 ms
1.447 ms
1.331 ms
1.338 ms
1.422 ms
1.363 ms
1.364 ms
1.308 ms
1.358 ms
1.393 ms
1.400 ms
1.411 ms
1.329 ms
1.514 ms
1.389 ms
1.344 ms
1.394 ms
1.369 ms
1.351 ms
1.367 ms
1.385 ms
1.325 ms
1.349 ms
1.434 ms
1.319 ms
1.335 ms
1.325 ms
1.337 ms
1.376 ms
1.389 ms
1.365 ms
1.365 ms
1.339 ms
1.391 ms
1.517 ms
1.322 ms
1.342 ms
1.388 ms
1.343 ms
1.364 ms
1.363 ms
1.388 ms
1.331 ms
1.395 ms
1.327 ms
1.368 ms
1.388 ms
1.337 ms
1.401 ms
1.404 ms
1.487 ms
1.334 ms
1.443 ms
1.345 ms
1.441 ms
4.078 ms
1.422 ms
1.431 ms
1.387 ms
1.338 ms
1.434 ms
1.373 ms
1.326 ms
16.329 ms
1.335 ms
1.319 ms
1.372 ms
1.362 ms
1.344 ms
1.389 ms
1.359 ms
1.356 ms
1.486 ms
1.333 ms
1.681 ms
1.324 ms
1.357 ms
1.356 ms
1.403 ms
1.404 ms
1.404 ms
1.405 ms
1.470 ms
1.486 ms
1.335 ms
1.413 ms
1.372 ms
1.369 ms
1.432 ms
1.379 ms
4.458 ms
1.376 ms
1.316 ms
1.331 ms
1.361 ms
1.480 ms
1.376 ms
1.458 ms
1.353 ms
1.446 ms
1.402 ms
1.476 ms
1.787 ms
2.591 ms
1.384 ms
1.329 ms
1.374 ms
1.358 ms
1.338 ms
1.341 ms
1.377 ms
1.329 ms
1.495 ms
1.395 ms
1.479 ms
1.418 ms
1.367 ms
1.345 ms
1.398 ms
1.382 ms
1.340 ms
9.573 ms
1.344 ms
1.360 ms
1.401 ms
1.395 ms
1.383 ms
1.332 ms
1.378 ms
1.350 ms
1.451 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.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.437 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.165 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.551 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.814 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.470 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.183 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.412 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.213 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 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.376 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.188 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 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.837 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.885 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.114 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.206 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.018 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.032 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop16.247 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.381 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.489 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.403 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.260 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination4.764 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.171 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.465 msReply RTT ASN unavailable
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.228 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.314 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.108 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.347 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.301 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.238 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.250 msReply RTT ASN unavailable
  4. TTL 4 Probe hop4.450 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.678 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.416 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.249 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.783 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.167 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Destination6.236 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.158 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.221 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop39.853 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.227 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.675 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.716 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Destination7.533 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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.920 msReply RTT AS13335 · Cloudflare
After

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.207 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.126 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.241 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.116 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.719 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.509 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.621 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.215 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.511 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.183 msAS8002 · Stealth0.114 msAS8002 · StealthSame responder
20.190 msAS8002 · Stealth0.206 msAS8002 · StealthSame responder
31.412 ms1.018 msAS13335 · CloudflareSame responder
4Not recorded2.032 msAS13335 · CloudflareNot established
5Not recorded16.247 msAS13335 · CloudflareNot established
6Not recorded1.381 msAS13335 · CloudflareNot 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.138 msAS8002 · Stealth0.171 msAS8002 · StealthSame responder
20.202 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
31.437 msAS13335 · Cloudflare1.465 msSame 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.143 msAS8002 · Stealth0.489 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.184 msAS8002 · StealthSame responder
3No reply1.403 msAS13335 · CloudflareNot established
4No replyNo replyNot established
57.837 msAS13335 · Cloudflare1.260 msAS13335 · CloudflareDifferent responders
6No reply4.764 msAS13335 · CloudflareNot established
71.885 msAS13335 · CloudflareNot recordedNot 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.366 msUsual round trip before the event
Last recorded event RTT1.411 msLast successful event recording
Event p95 RTT9.002 ms95th percentile of successful recordings
Change from baseline+0.045 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