Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-12CC6E6040F73F88

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

30 Oct 2026 17:25 – 30 Oct 2026 19:54 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.535 ms
1.394 ms
1.410 ms
1.480 ms
1.379 ms
1.421 ms
1.417 ms
1.414 ms
1.549 ms
1.465 ms
1.396 ms
1.335 ms
1.475 ms
1.405 ms
1.407 ms
1.427 ms
1.361 ms
1.452 ms
1.365 ms
1.411 ms
1.400 ms
1.477 ms
1.531 ms
1.452 ms
1.373 ms
1.376 ms
1.429 ms
1.436 ms
1.374 ms
1.354 ms
1.473 ms
1.368 ms
1.398 ms
1.439 ms
1.341 ms
12.998 ms
1.366 ms
1.441 ms
1.427 ms
1.350 ms
2.204 ms
1.384 ms
1.468 ms
1.386 ms
1.383 ms
1.388 ms
1.370 ms
1.415 ms
1.355 ms
1.373 ms
1.389 ms
1.384 ms
1.305 ms
1.368 ms
1.368 ms
1.371 ms
1.436 ms
1.368 ms
1.375 ms
1.412 ms
1.416 ms
1.343 ms
1.490 ms
1.336 ms
1.451 ms
1.382 ms
1.543 ms
1.404 ms
1.362 ms
1.368 ms
2.312 ms
1.429 ms
15.121 ms
1.385 ms
2.076 ms
1.392 ms
1.534 ms
1.546 ms
1.689 ms
1.397 ms
1.364 ms
1.356 ms
1.334 ms
1.341 ms
1.338 ms
1.372 ms
1.434 ms
1.368 ms
1.352 ms
1.481 ms
1.476 ms
1.496 ms
1.491 ms
1.434 ms
1.406 ms
1.362 ms
1.373 ms
1.397 ms
1.360 ms
1.335 ms
1.402 ms
1.373 ms
3.029 ms
1.524 ms
1.383 ms
1.385 ms
18.251 ms
1.434 ms
1.353 ms
1.345 ms
1.441 ms
1.517 ms
1.386 ms
1.460 ms
1.356 ms
1.420 ms
1.356 ms
1.460 ms
1.492 ms
1.406 ms
1.362 ms
1.391 ms
1.445 ms
1.341 ms
1.352 ms
1.396 ms
2.617 ms
4.382 ms
19.435 ms
2.888 ms
16.986 ms
1.469 ms
19.550 ms
3.113 ms
1.382 ms
19.985 ms
8.330 ms
2.885 ms
1.397 ms
11.189 ms
1.397 ms
1.388 ms
1.370 ms
1.340 ms
2.162 ms
1.384 ms
1.431 ms
1.368 ms
1.391 ms
1.356 ms
1.395 ms
1.369 ms
1.407 ms
1.376 ms
1.514 ms
1.352 ms
2.070 ms
1.431 ms
1.370 ms
1.362 ms
1.361 ms
1.382 ms
1.364 ms
1.846 ms
1.410 ms
1.347 ms
1.412 ms
1.389 ms
1.361 ms
1.457 ms
1.372 ms
1.332 ms
1.485 ms
1.337 ms
1.342 ms
1.823 ms
1.404 ms
1.482 ms
1.744 ms
1.438 ms
20.084 ms
4.294 ms
1.511 ms
1.354 ms
1.642 ms
15.336 ms
1.443 ms
1.321 ms
1.439 ms
1.361 ms
1.350 ms
1.360 ms
1.478 ms
1.384 ms
1.370 ms
1.360 ms
1.400 ms
1.386 ms
1.362 ms
1.365 ms
1.378 ms
1.335 ms
1.409 ms
1.365 ms
1.364 ms
1.445 ms
1.339 ms
1.438 ms
14.658 ms
1.480 ms
1.370 ms
1.391 ms
1.627 ms
1.385 ms
1.371 ms
1.375 ms
1.371 ms
1.391 ms
1.579 ms
18.191 ms
1.365 ms
1.429 ms
1.406 ms
1.440 ms
1.340 ms
1.349 ms
1.369 ms
1.343 ms
1.373 ms
1.353 ms
1.354 ms
1.353 ms
1.372 ms
1.348 ms
1.422 ms
1.484 ms
1.562 ms
1.422 ms
1.358 ms
1.361 ms
1.364 ms
1.378 ms
1.557 ms
1.356 ms
1.399 ms
1.371 ms
1.395 ms
1.344 ms
1.349 ms
1.371 ms
1.369 ms
1.428 ms
1.346 ms
1.411 ms
1.362 ms
1.441 ms
1.475 ms
1.352 ms
1.344 ms
1.423 ms
1.376 ms
1.384 ms
1.645 ms
1.458 ms
1.337 ms
1.431 ms
1.363 ms
1.423 ms
1.343 ms
1.352 ms
1.400 ms
1.501 ms
1.353 ms
1.343 ms
1.379 ms
1.504 ms
1.498 ms
1.350 ms
1.364 ms
3.264 ms
1.368 ms
1.364 ms
1.448 ms
1.406 ms
1.578 ms
1.317 ms
1.479 ms
1.390 ms
1.383 ms
1.393 ms
1.433 ms
1.393 ms
1.351 ms
1.394 ms
1.407 ms
1.338 ms
1.429 ms
1.360 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.164 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
Before

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.203 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.517 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.281 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.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.212 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.350 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.187 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.816 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.098 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.299 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.195 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.219 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 hop4.072 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.985 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.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 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 hop4.374 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.594 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.172 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.988 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.220 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.174 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop10.379 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.250 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.238 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 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.040 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.491 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.802 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.178 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 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 hop16.125 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.079 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.123 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.056 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.249 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.300 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.942 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.468 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.512 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.103 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.484 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.262 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.843 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.694 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.152 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.164 msAS8002 · Stealth0.138 msAS8002 · StealthSame responder
20.189 msAS8002 · Stealth0.177 msAS8002 · StealthSame 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.150 msAS8002 · Stealth0.238 msAS8002 · StealthSame responder
20.212 msAS8002 · Stealth0.179 msAS8002 · StealthSame responder
31.350 msAS13335 · CloudflareNot 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.195 msAS8002 · Stealth0.154 msAS8002 · StealthSame responder
20.219 msAS8002 · Stealth0.176 msAS8002 · StealthSame responder
3No replyNo replyNot established
4No replyNo replyNot established
54.072 msAS13335 · Cloudflare4.374 msAS13335 · CloudflareDifferent responders
60.985 msAS13335 · Cloudflare1.594 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.378 msUsual round trip before the event
Last recorded event RTT1.744 msLast successful event recording
Event p95 RTT17.109 ms95th percentile of successful recordings
Change from baseline+0.366 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