Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-D72E9A8DD4636684

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

03 Nov 2026 02:10 – 03 Nov 2026 04:49 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.375 ms
1.402 ms
1.334 ms
5.829 ms
1.361 ms
1.382 ms
1.326 ms
1.486 ms
1.343 ms
1.979 ms
1.415 ms
1.382 ms
1.384 ms
1.313 ms
1.323 ms
1.338 ms
1.320 ms
1.459 ms
1.384 ms
1.399 ms
1.423 ms
1.354 ms
1.378 ms
1.460 ms
1.365 ms
1.417 ms
1.464 ms
1.369 ms
1.395 ms
1.447 ms
2.401 ms
1.438 ms
1.372 ms
1.336 ms
1.437 ms
1.416 ms
1.331 ms
1.403 ms
1.399 ms
1.423 ms
1.354 ms
1.406 ms
1.333 ms
1.457 ms
1.367 ms
1.458 ms
1.362 ms
1.325 ms
1.336 ms
1.543 ms
1.360 ms
1.489 ms
1.333 ms
1.357 ms
1.319 ms
1.347 ms
1.338 ms
1.317 ms
1.393 ms
1.428 ms
1.322 ms
1.347 ms
1.377 ms
1.458 ms
1.417 ms
1.347 ms
3.939 ms
1.337 ms
1.566 ms
1.439 ms
1.343 ms
1.447 ms
1.333 ms
1.368 ms
1.408 ms
1.315 ms
5.908 ms
1.335 ms
1.358 ms
1.407 ms
10.132 ms
1.459 ms
1.371 ms
15.216 ms
1.381 ms
1.366 ms
1.348 ms
1.331 ms
1.372 ms
1.367 ms
1.469 ms
1.468 ms
1.417 ms
1.485 ms
2.186 ms
1.346 ms
1.343 ms
1.369 ms
1.388 ms
1.343 ms
1.381 ms
1.352 ms
1.327 ms
1.385 ms
1.448 ms
1.354 ms
1.431 ms
1.399 ms
1.361 ms
1.353 ms
1.367 ms
1.361 ms
1.400 ms
1.420 ms
1.349 ms
1.363 ms
1.397 ms
1.334 ms
1.424 ms
1.414 ms
1.327 ms
1.345 ms
6.638 ms
1.392 ms
1.511 ms
1.482 ms
1.369 ms
1.327 ms
1.360 ms
1.377 ms
1.357 ms
1.438 ms
1.327 ms
1.340 ms
1.366 ms
1.472 ms
1.344 ms
1.403 ms
11.671 ms
1.353 ms
11.920 ms
1.330 ms
1.352 ms
1.339 ms
1.350 ms
1.428 ms
1.390 ms
1.375 ms
1.347 ms
1.335 ms
1.344 ms
1.445 ms
1.328 ms
1.332 ms
1.519 ms
1.470 ms
1.351 ms
1.342 ms
1.375 ms
1.441 ms
4.874 ms
18.472 ms
1.330 ms
1.326 ms
1.337 ms
1.320 ms
1.340 ms
1.366 ms
1.486 ms
1.341 ms
1.332 ms
1.332 ms
1.374 ms
1.393 ms
1.370 ms
1.375 ms
1.377 ms
1.433 ms
1.327 ms
1.326 ms
1.355 ms
1.396 ms
1.459 ms
1.345 ms
1.422 ms
1.428 ms
1.326 ms
1.349 ms
1.354 ms
1.323 ms
1.352 ms
1.449 ms
1.354 ms
1.308 ms
1.334 ms
1.341 ms
1.466 ms
1.320 ms
1.353 ms
1.412 ms
1.349 ms
1.306 ms
1.307 ms
1.310 ms
1.323 ms
1.393 ms
1.330 ms
6.616 ms
1.419 ms
1.368 ms
1.382 ms
1.378 ms
1.323 ms
1.360 ms
1.382 ms
1.423 ms
1.453 ms
1.355 ms
1.400 ms
1.409 ms
1.436 ms
1.372 ms
1.351 ms
1.504 ms
1.405 ms
1.493 ms
1.451 ms
1.374 ms
1.353 ms
1.505 ms
1.333 ms
1.330 ms
1.416 ms
1.401 ms
1.344 ms
1.343 ms
1.545 ms
1.326 ms
1.350 ms
1.414 ms
1.329 ms
1.431 ms
1.376 ms
1.388 ms
1.304 ms
1.376 ms
1.335 ms
1.322 ms
1.339 ms
1.393 ms
1.610 ms
1.412 ms
1.408 ms
1.318 ms
1.338 ms
1.604 ms
1.551 ms
1.422 ms
1.327 ms
1.330 ms
1.346 ms
1.407 ms
1.358 ms
1.386 ms
1.381 ms
1.341 ms
1.376 ms
1.338 ms
1.372 ms
1.353 ms
2.157 ms
1.365 ms
1.344 ms
1.449 ms
1.371 ms
1.456 ms
1.367 ms
2.814 ms
1.441 ms
13.134 ms
1.507 ms
1.311 ms
1.384 ms
1.324 ms
1.336 ms
1.431 ms
1.320 ms
1.357 ms
1.317 ms
1.319 ms
1.438 ms
1.329 ms
9.528 ms
1.401 ms
1.428 ms
1.343 ms
1.333 ms
1.342 ms
1.863 ms
1.314 ms
1.327 ms
1.330 ms
1.476 ms
1.353 ms
1.329 ms
1.344 ms
1.366 ms
1.440 ms
1.322 ms
1.358 ms
1.311 ms
1.425 ms
1.346 ms
1.392 ms
1.294 ms
1.336 ms
1.362 ms
1.355 ms
1.412 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.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.992 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.745 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.538 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.384 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.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.732 msReply RTT AS13335 · Cloudflare
Before

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.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.257 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.194 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.378 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.249 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 hop3.866 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.276 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.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.364 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.258 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.673 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.500 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.212 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.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.805 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.221 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.281 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop27.219 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.559 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.184 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.438 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.882 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.075 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.317 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.238 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.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.441 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.953 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.171 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop21.946 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.493 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.439 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.226 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.414 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.689 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.211 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.710 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.183 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.028 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.202 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.231 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.336 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.366 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.396 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.145 msAS8002 · Stealth0.126 msAS8002 · StealthSame responder
20.178 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
313.992 ms1.364 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.183 msAS8002 · Stealth0.145 msAS8002 · StealthSame responder
20.249 msAS8002 · Stealth0.258 msAS8002 · StealthSame responder
3No reply0.673 msAS13335 · CloudflareNot established
4No replyNo replyNot established
53.866 msAS13335 · Cloudflare1.500 msAS13335 · CloudflareDifferent responders
61.276 msAS13335 · Cloudflare1.212 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.366 msUsual round trip before the event
Last recorded event RTT1.412 msLast successful event recording
Event p95 RTT4.962 ms95th percentile of successful recordings
Change from baseline+0.046 msLast event RTT compared with the baseline
Successful / expected recordings80 / 80Recorded 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