Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-099B6D2033C198F8

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

04 Nov 2026 14:15 – 04 Nov 2026 22: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.355 ms
1.536 ms
1.472 ms
1.454 ms
1.396 ms
1.382 ms
1.347 ms
1.379 ms
1.396 ms
1.443 ms
1.350 ms
1.350 ms
1.415 ms
1.350 ms
1.392 ms
1.427 ms
1.403 ms
1.313 ms
1.379 ms
1.350 ms
1.394 ms
1.334 ms
1.326 ms
1.370 ms
1.448 ms
1.409 ms
1.464 ms
1.442 ms
1.396 ms
1.324 ms
1.421 ms
1.351 ms
1.328 ms
5.903 ms
6.983 ms
1.332 ms
1.429 ms
1.358 ms
1.342 ms
1.448 ms
1.374 ms
1.377 ms
1.326 ms
1.398 ms
1.360 ms
1.760 ms
1.353 ms
16.387 ms
1.336 ms
1.340 ms
1.471 ms
1.348 ms
1.351 ms
1.353 ms
1.368 ms
1.363 ms
1.352 ms
1.348 ms
1.314 ms
1.390 ms
1.479 ms
1.348 ms
1.405 ms
1.351 ms
1.474 ms
1.365 ms
7.114 ms
1.412 ms
1.336 ms
1.370 ms
1.350 ms
1.393 ms
1.345 ms
1.393 ms
1.423 ms
1.396 ms
1.409 ms
1.432 ms
1.460 ms
1.365 ms
1.471 ms
2.097 ms
1.422 ms
1.387 ms
1.343 ms
1.320 ms
1.368 ms
1.366 ms
1.353 ms
1.415 ms
1.325 ms
1.336 ms
1.429 ms
1.400 ms
1.322 ms
1.489 ms
1.307 ms
1.331 ms
1.374 ms
1.345 ms
1.396 ms
1.340 ms
1.399 ms
1.456 ms
14.053 ms
1.644 ms
1.526 ms
1.417 ms
5.520 ms
1.328 ms
1.444 ms
1.423 ms
1.365 ms
1.399 ms
1.337 ms
1.341 ms
1.324 ms
1.381 ms
1.342 ms
1.370 ms
1.411 ms
1.349 ms
13.593 ms
1.336 ms
12.675 ms
1.420 ms
3.575 ms
10.045 ms
10.122 ms
3.124 ms
3.180 ms
18.304 ms
19.883 ms
1.406 ms
20.106 ms
17.584 ms
18.286 ms
1.446 ms
17.099 ms
1.359 ms
1.342 ms
1.345 ms
1.449 ms
2.298 ms
1.361 ms
11.663 ms
1.448 ms
1.356 ms
16.812 ms
16.635 ms
20.229 ms
1.326 ms
1.429 ms
3.017 ms
20.360 ms
13.889 ms
5.980 ms
1.405 ms
9.622 ms
1.422 ms
1.390 ms
1.370 ms
1.403 ms
1.326 ms
1.357 ms
1.511 ms
1.352 ms
11.836 ms
8.392 ms
1.339 ms
1.358 ms
17.894 ms
18.536 ms
1.352 ms
15.913 ms
16.308 ms
1.356 ms
1.499 ms
1.373 ms
16.740 ms
18.403 ms
19.566 ms
1.327 ms
19.946 ms
1.327 ms
1.430 ms
1.332 ms
1.473 ms
2.416 ms
1.389 ms
19.257 ms
1.330 ms
1.498 ms
3.071 ms
19.813 ms
17.727 ms
11.340 ms
1.354 ms
1.375 ms
1.400 ms
1.530 ms
1.352 ms
1.364 ms
1.408 ms
1.394 ms
1.373 ms
1.452 ms
1.386 ms
15.347 ms
1.367 ms
1.458 ms
1.977 ms
18.663 ms
1.410 ms
1.547 ms
1.338 ms
16.297 ms
11.561 ms
2.368 ms
2.072 ms
1.396 ms
1.342 ms
1.372 ms
1.345 ms
1.331 ms
1.428 ms
1.386 ms
1.332 ms
1.333 ms
1.445 ms
1.395 ms
1.610 ms
11.134 ms
1.445 ms
4.933 ms
1.360 ms
1.371 ms
1.404 ms
1.403 ms
1.339 ms
17.393 ms
1.437 ms
1.353 ms
1.329 ms
1.331 ms
13.380 ms
1.346 ms
1.336 ms
1.467 ms
1.463 ms
1.325 ms
1.483 ms
1.386 ms
1.377 ms
1.355 ms
1.327 ms
1.361 ms
1.426 ms
1.337 ms
1.458 ms
1.377 ms
1.341 ms
1.339 ms
1.355 ms
1.364 ms
1.511 ms
1.355 ms
1.347 ms
1.353 ms
1.474 ms
1.396 ms
1.419 ms
1.391 ms
1.378 ms
1.448 ms
1.378 ms
1.376 ms
1.458 ms
1.348 ms
1.355 ms
1.462 ms
1.388 ms
1.335 ms
1.379 ms
1.321 ms
1.334 ms
1.408 ms
1.344 ms
1.389 ms
1.380 ms
1.380 ms
1.424 ms
1.350 ms
1.540 ms
1.352 ms
1.373 ms
1.432 ms
1.499 ms
1.359 ms
1.372 ms
1.324 ms
1.691 ms
1.458 ms
1.487 ms
1.353 ms
1.338 ms
3.838 ms
1.381 ms
1.396 ms
1.417 ms
1.374 ms
1.326 ms
1.369 ms
1.399 ms
1.345 ms
1.404 ms
1.305 ms
1.345 ms
1.355 ms
1.375 ms
1.419 ms
1.508 ms
1.377 ms
1.335 ms
1.450 ms
1.415 ms
1.381 ms
1.406 ms
1.394 ms
1.400 ms
1.415 ms
1.339 ms
1.405 ms
1.509 ms
1.486 ms
1.357 ms
1.413 ms
1.512 ms
1.317 ms
1.330 ms
1.367 ms
1.431 ms
1.350 ms
1.354 ms
1.338 ms
1.366 ms
1.358 ms
1.357 ms
1.344 ms
1.415 ms
1.372 ms
1.390 ms
1.370 ms
1.329 ms
1.461 ms
1.363 ms
1.353 ms
1.349 ms
1.438 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 replied


to UTC

  1. TTL 1 Probe hop0.217 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.429 msReply RTT ASN unavailable
  4. TTL 4 Probe hop5.942 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop14.350 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.379 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.311 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.231 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.825 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.089 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.264 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.918 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.583 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.348 msReply RTT AS13335 · Cloudflare
Before

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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.622 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.184 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.236 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.529 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.751 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.219 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.279 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.381 msReply RTT AS13335 · Cloudflare
During

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.246 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.169 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop13.924 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination2.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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop44.571 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.735 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop23.784 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.880 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.401 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.169 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.972 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.775 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.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.301 msReply RTT AS13335 · Cloudflare
After

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.256 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.698 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.435 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.298 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.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.867 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.828 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.255 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.387 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.727 msReply RTT AS13335 · Cloudflare
After

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.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.287 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop8.602 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.860 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.124 msAS8002 · Stealth0.148 msAS8002 · StealthSame responder
20.188 msAS8002 · Stealth0.529 msAS8002 · StealthSame responder
311.089 ms0.751 msAS13335 · CloudflareSame responder
4Not recorded2.219 msAS13335 · CloudflareNot established
5Not recorded2.279 msAS13335 · CloudflareNot established
6Not recorded1.381 msAS13335 · CloudflareNot 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.150 msAS8002 · Stealth0.137 msAS8002 · StealthSame responder
20.264 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
30.918 ms19.169 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.583 msAS13335 · Cloudflare1.972 msAS13335 · CloudflareDifferent responders
61.348 msAS13335 · Cloudflare1.775 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.142 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
20.178 msAS8002 · Stealth0.246 msAS8002 · StealthSame responder
310.622 msAS13335 · Cloudflare1.169 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.184 msAS13335 · Cloudflare13.924 msAS13335 · CloudflareDifferent responders
61.236 msAS13335 · Cloudflare2.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.

Possible SLA event. 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.367 msUsual round trip before the event
Last recorded event RTT1.339 msLast successful event recording
Event p95 RTT19.539 ms95th percentile of successful recordings
Change from baseline-0.028 msLast event RTT compared with the baseline
Successful / expected recordings748 / 760Recorded 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