Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-C817EB7A5089E908

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

30 Oct 2026 11:55 – 30 Oct 2026 14:59 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.449 ms
1.331 ms
1.326 ms
1.373 ms
1.426 ms
1.347 ms
1.396 ms
1.461 ms
1.475 ms
1.339 ms
1.361 ms
1.336 ms
1.358 ms
1.333 ms
1.363 ms
1.349 ms
1.375 ms
1.353 ms
1.370 ms
1.631 ms
1.366 ms
1.511 ms
1.381 ms
1.410 ms
1.333 ms
1.506 ms
1.334 ms
1.334 ms
1.357 ms
1.344 ms
1.338 ms
1.418 ms
1.382 ms
1.374 ms
1.409 ms
1.352 ms
1.339 ms
1.340 ms
1.357 ms
1.400 ms
1.353 ms
1.340 ms
1.406 ms
1.392 ms
1.372 ms
1.365 ms
1.328 ms
1.462 ms
1.347 ms
1.389 ms
1.556 ms
1.586 ms
1.371 ms
1.407 ms
1.386 ms
1.328 ms
1.352 ms
1.378 ms
1.381 ms
1.384 ms
1.363 ms
1.364 ms
1.367 ms
1.423 ms
1.396 ms
1.351 ms
1.410 ms
1.423 ms
1.443 ms
1.447 ms
1.418 ms
1.398 ms
1.412 ms
1.356 ms
1.414 ms
1.383 ms
1.417 ms
1.435 ms
1.341 ms
1.395 ms
1.385 ms
1.312 ms
1.330 ms
1.370 ms
1.420 ms
1.398 ms
1.356 ms
1.472 ms
1.386 ms
1.362 ms
1.458 ms
1.349 ms
1.410 ms
1.394 ms
1.377 ms
1.361 ms
1.348 ms
1.427 ms
1.578 ms
1.339 ms
1.381 ms
1.404 ms
1.487 ms
1.365 ms
1.408 ms
1.424 ms
1.345 ms
1.343 ms
1.380 ms
1.385 ms
1.365 ms
1.387 ms
1.351 ms
1.684 ms
1.403 ms
1.400 ms
1.353 ms
1.379 ms
1.345 ms
1.356 ms
9.877 ms
1.517 ms
1.388 ms
1.373 ms
1.473 ms
1.566 ms
1.349 ms
1.343 ms
1.325 ms
1.375 ms
1.335 ms
1.644 ms
1.451 ms
1.584 ms
11.899 ms
1.346 ms
1.335 ms
1.355 ms
1.365 ms
1.332 ms
1.339 ms
1.345 ms
1.353 ms
12.782 ms
1.362 ms
1.423 ms
1.427 ms
1.389 ms
1.366 ms
1.340 ms
1.335 ms
1.357 ms
1.375 ms
1.335 ms
1.374 ms
1.382 ms
1.398 ms
1.363 ms
1.357 ms
19.066 ms
1.360 ms
1.383 ms
1.373 ms
1.411 ms
1.405 ms
1.393 ms
1.368 ms
1.323 ms
1.383 ms
1.376 ms
1.474 ms
1.499 ms
1.379 ms
1.329 ms
1.352 ms
18.337 ms
1.434 ms
1.484 ms
1.411 ms
7.918 ms
1.341 ms
1.370 ms
13.887 ms
1.417 ms
1.359 ms
1.379 ms
1.373 ms
4.404 ms
6.153 ms
1.355 ms
1.366 ms
1.367 ms
1.382 ms
1.371 ms
1.404 ms
1.474 ms
1.374 ms
1.367 ms
1.392 ms
1.408 ms
1.359 ms
1.497 ms
1.588 ms
1.356 ms
1.388 ms
1.347 ms
1.528 ms
1.403 ms
15.567 ms
1.360 ms
1.410 ms
1.420 ms
1.433 ms
1.509 ms
1.448 ms
1.455 ms
4.742 ms
1.335 ms
1.379 ms
1.355 ms
1.423 ms
1.398 ms
1.356 ms
1.611 ms
1.436 ms
1.363 ms
1.358 ms
1.367 ms
1.346 ms
1.416 ms
1.368 ms
1.350 ms
1.344 ms
1.389 ms
1.370 ms
1.360 ms
1.401 ms
1.356 ms
1.431 ms
1.347 ms
1.607 ms
1.405 ms
1.368 ms
1.440 ms
1.320 ms
1.486 ms
13.434 ms
1.361 ms
1.372 ms
1.390 ms
1.372 ms
1.336 ms
1.347 ms
1.529 ms
1.411 ms
1.384 ms
1.419 ms
16.409 ms
1.373 ms
1.686 ms
1.482 ms
1.326 ms
1.362 ms
1.466 ms
1.357 ms
1.401 ms
1.443 ms
1.354 ms
1.425 ms
1.571 ms
1.424 ms
1.461 ms
1.367 ms
1.394 ms
1.389 ms
1.414 ms
1.359 ms
1.422 ms
1.506 ms
1.356 ms
1.337 ms
1.342 ms
17.426 ms
1.486 ms
1.403 ms
1.409 ms
15.607 ms
1.530 ms
1.378 ms
1.445 ms
1.367 ms
1.347 ms
1.463 ms
1.400 ms
1.411 ms
1.351 ms
1.345 ms
1.613 ms
1.375 ms
1.420 ms
1.337 ms
1.724 ms
8.694 ms
1.407 ms
1.375 ms
1.366 ms
1.360 ms
1.357 ms
1.464 ms
1.442 ms
1.394 ms
1.357 ms
1.428 ms
1.346 ms
1.425 ms
1.368 ms
1.434 ms
1.441 ms
1.413 ms
1.417 ms
1.370 ms
2.250 ms
1.368 ms
1.736 ms
1.406 ms
1.373 ms
1.465 ms
1.498 ms
1.420 ms
1.371 ms
1.347 ms
1.450 ms
1.375 ms
1.384 ms
1.366 ms
1.440 ms
1.371 ms
1.393 ms
1.462 ms
1.378 ms
1.362 ms
1.359 ms
1.512 ms
1.396 ms
1.363 ms
1.490 ms
1.437 ms
1.333 ms
1.370 ms
1.502 ms
1.392 ms
1.362 ms
1.558 ms
1.694 ms
1.351 ms
1.453 ms
1.342 ms
1.352 ms
1.364 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.123 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.218 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.525 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.636 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.120 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.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
Before

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.188 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.373 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.358 msReply RTT AS13335 · Cloudflare
Before

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.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.883 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop19.933 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.613 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.175 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.168 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.269 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.991 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.010 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.454 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.210 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.188 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.265 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop38.959 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop6.053 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.406 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.707 msReply RTT ASN unavailable
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.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.038 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop15.718 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.888 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.359 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.347 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.220 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop1.980 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.371 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.345 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.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.441 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.831 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.271 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.014 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.522 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.537 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.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
After

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.175 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.527 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination8.297 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.147 msAS8002 · Stealth0.175 msAS8002 · StealthSame responder
20.174 msAS8002 · Stealth0.168 msAS8002 · StealthSame responder
3Not recorded5.269 msNot 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.154 msAS8002 · Stealth0.141 msAS8002 · StealthSame responder
20.204 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
35.883 ms16.991 msSame responder
4No replyNo replyNot established
519.933 msAS13335 · Cloudflare4.010 msAS13335 · CloudflareDifferent responders
61.613 msAS13335 · Cloudflare1.454 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.218 msAS8002 · Stealth0.169 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
31.525 msAS13335 · Cloudflare22.038 msSame responder
4No replyNo replyNot established
51.636 msAS13335 · Cloudflare15.718 msAS13335 · CloudflareDifferent responders
61.120 msAS13335 · Cloudflare0.888 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.380 msUsual round trip before the event
Last recorded event RTT1.347 msLast successful event recording
Event p95 RTT9.699 ms95th percentile of successful recordings
Change from baseline-0.033 msLast event RTT compared with the baseline
Successful / expected recordings129 / 130Recorded 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