Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-4D3B6AA54200DC1F

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

28 Oct 2026 11:50 – 28 Oct 2026 14:34 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.341 ms
1.376 ms
1.378 ms
1.449 ms
1.357 ms
1.504 ms
1.365 ms
1.368 ms
1.325 ms
1.369 ms
1.611 ms
1.338 ms
1.400 ms
1.354 ms
1.416 ms
1.416 ms
1.454 ms
1.452 ms
1.357 ms
1.403 ms
1.459 ms
1.369 ms
1.497 ms
1.391 ms
1.449 ms
1.511 ms
1.348 ms
1.392 ms
1.455 ms
1.377 ms
1.314 ms
1.462 ms
1.342 ms
1.378 ms
1.492 ms
1.319 ms
1.367 ms
1.329 ms
1.361 ms
1.351 ms
1.513 ms
5.811 ms
1.334 ms
1.421 ms
1.371 ms
1.372 ms
1.336 ms
1.374 ms
1.374 ms
1.391 ms
1.383 ms
1.339 ms
1.357 ms
1.434 ms
1.347 ms
1.409 ms
1.459 ms
1.388 ms
1.404 ms
1.412 ms
1.349 ms
1.374 ms
1.411 ms
1.416 ms
1.358 ms
1.406 ms
1.348 ms
1.405 ms
1.367 ms
1.374 ms
1.351 ms
1.390 ms
1.391 ms
1.343 ms
1.370 ms
1.375 ms
3.931 ms
1.354 ms
1.441 ms
1.347 ms
1.348 ms
1.435 ms
1.408 ms
1.334 ms
1.368 ms
1.363 ms
1.381 ms
1.361 ms
1.361 ms
1.426 ms
1.365 ms
1.431 ms
1.391 ms
1.355 ms
1.487 ms
1.452 ms
1.440 ms
1.454 ms
1.376 ms
1.421 ms
1.397 ms
1.338 ms
1.366 ms
1.390 ms
1.375 ms
1.352 ms
1.406 ms
1.384 ms
1.351 ms
1.334 ms
1.434 ms
1.396 ms
1.346 ms
1.413 ms
1.496 ms
1.454 ms
1.465 ms
1.350 ms
1.390 ms
1.353 ms
1.352 ms
1.427 ms
1.375 ms
1.379 ms
12.445 ms
1.331 ms
1.347 ms
1.406 ms
1.452 ms
1.398 ms
1.363 ms
1.352 ms
1.403 ms
1.526 ms
1.424 ms
1.525 ms
7.970 ms
1.456 ms
1.350 ms
1.430 ms
1.408 ms
1.414 ms
1.485 ms
1.354 ms
6.765 ms
1.383 ms
4.636 ms
15.957 ms
3.667 ms
19.787 ms
1.420 ms
1.699 ms
1.420 ms
1.407 ms
1.489 ms
1.393 ms
1.418 ms
1.351 ms
1.339 ms
1.389 ms
1.339 ms
1.366 ms
1.388 ms
1.377 ms
1.404 ms
1.400 ms
1.331 ms
1.370 ms
1.512 ms
1.408 ms
1.378 ms
1.338 ms
1.350 ms
1.470 ms
1.371 ms
5.260 ms
1.434 ms
1.379 ms
1.358 ms
1.408 ms
1.360 ms
1.374 ms
1.436 ms
1.372 ms
1.428 ms
1.341 ms
1.383 ms
1.423 ms
1.374 ms
1.368 ms
1.380 ms
1.376 ms
1.416 ms
1.427 ms
1.529 ms
1.377 ms
1.377 ms
1.325 ms
1.394 ms
1.409 ms
1.396 ms
1.353 ms
1.380 ms
1.501 ms
1.360 ms
1.349 ms
1.394 ms
1.354 ms
1.365 ms
1.564 ms
2.555 ms
1.350 ms
10.879 ms
3.075 ms
15.341 ms
1.405 ms
1.392 ms
1.355 ms
1.465 ms
1.454 ms
1.360 ms
1.352 ms
1.362 ms
1.456 ms
1.408 ms
1.341 ms
1.380 ms
1.369 ms
1.692 ms
1.362 ms
13.473 ms
1.371 ms
1.373 ms
1.357 ms
19.170 ms
1.371 ms
1.858 ms
1.433 ms
1.406 ms
6.545 ms
1.358 ms
3.109 ms
1.365 ms
1.428 ms
1.355 ms
1.384 ms
4.423 ms
17.911 ms
1.369 ms
1.355 ms
1.419 ms
1.361 ms
1.479 ms
1.416 ms
1.353 ms
1.409 ms
1.364 ms
1.404 ms
1.389 ms
1.384 ms
3.550 ms
1.414 ms
1.406 ms
1.384 ms
1.422 ms
1.367 ms
1.356 ms
1.327 ms
2.815 ms
1.378 ms
1.378 ms
2.151 ms
2.564 ms
1.413 ms
1.517 ms
1.359 ms
18.496 ms
1.450 ms
14.826 ms
1.371 ms
1.370 ms
1.360 ms
1.654 ms
7.419 ms
1.357 ms
1.399 ms
1.310 ms
1.397 ms
1.377 ms
1.335 ms
1.401 ms
1.417 ms
1.383 ms
1.415 ms
1.337 ms
14.806 ms
1.374 ms
1.382 ms
1.502 ms
1.347 ms
1.413 ms
1.350 ms
3.173 ms
1.358 ms
1.516 ms
15.879 ms
1.374 ms
1.443 ms
5.135 ms
1.469 ms
1.351 ms
1.442 ms
1.328 ms
6.038 ms
20.380 ms
15.189 ms
1.354 ms
1.335 ms
1.411 ms
1.462 ms
1.440 ms
5.564 ms
1.338 ms
1.370 ms
1.927 ms
1.510 ms
1.416 ms
1.372 ms
1.361 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.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.605 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.219 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.314 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.707 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.223 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.493 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.171 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.606 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.229 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop38.476 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.584 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.287 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.207 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.874 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.947 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.745 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.090 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.468 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.311 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.178 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.069 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.994 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.431 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.549 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.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.214 msReply RTT AS8002 · Stealth
During

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.248 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.420 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.664 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.214 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.437 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.600 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.943 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.833 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.251 msReply RTT ASN unavailable
  4. TTL 4 Probe hop21.960 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.968 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination2.173 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.193 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.208 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.894 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.236 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.148 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.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.171 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.174 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.279 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.879 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination11.978 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 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.117 msAS8002 · Stealth0.125 msAS8002 · StealthSame responder
20.171 msAS8002 · Stealth0.175 msAS8002 · StealthSame responder
31.606 msAS13335 · Cloudflare0.745 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.229 msAS8002 · Stealth0.148 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
338.476 msAS13335 · Cloudflare1.069 msAS13335 · CloudflareSame responder
4No reply1.994 msAS13335 · CloudflareNot established
51.584 msAS13335 · Cloudflare1.431 msAS13335 · CloudflareDifferent responders
61.287 msAS13335 · Cloudflare1.549 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.207 msAS8002 · Stealth0.152 msAS8002 · StealthSame responder
20.177 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
3No reply1.090 msNot established
4No replyNo replyNot established
51.874 msAS13335 · Cloudflare4.468 msAS13335 · CloudflareDifferent responders
60.947 msAS13335 · Cloudflare1.311 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.387 msUsual round trip before the event
Last recorded event RTT1.564 msLast successful event recording
Event p95 RTT6.088 ms95th percentile of successful recordings
Change from baseline+0.177 msLast event RTT compared with the baseline
Successful / expected recordings90 / 90Recorded 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