Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-2107DB9874897DFE

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

28 Oct 2026 17:30 – 28 Oct 2026 21:04 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.478 ms
1.417 ms
6.490 ms
1.332 ms
8.049 ms
1.364 ms
10.238 ms
7.836 ms
3.751 ms
1.397 ms
1.427 ms
1.352 ms
7.896 ms
1.465 ms
1.351 ms
1.339 ms
1.386 ms
2.800 ms
1.384 ms
1.386 ms
1.381 ms
1.370 ms
1.443 ms
1.562 ms
1.384 ms
4.944 ms
1.346 ms
1.460 ms
1.382 ms
1.360 ms
1.394 ms
5.237 ms
1.362 ms
1.417 ms
15.062 ms
9.211 ms
1.357 ms
8.422 ms
1.488 ms
11.561 ms
1.334 ms
1.432 ms
1.451 ms
1.384 ms
1.375 ms
1.363 ms
1.392 ms
1.357 ms
1.384 ms
1.367 ms
1.398 ms
14.397 ms
13.232 ms
10.247 ms
1.376 ms
1.477 ms
1.445 ms
1.570 ms
1.384 ms
1.392 ms
1.392 ms
1.429 ms
1.506 ms
1.360 ms
1.433 ms
1.416 ms
1.440 ms
11.914 ms
1.358 ms
1.364 ms
1.378 ms
1.377 ms
1.449 ms
1.372 ms
1.459 ms
1.381 ms
1.339 ms
1.540 ms
1.440 ms
1.348 ms
1.448 ms
1.403 ms
1.349 ms
1.453 ms
1.359 ms
1.339 ms
1.409 ms
1.448 ms
1.322 ms
1.338 ms
1.544 ms
1.411 ms
1.374 ms
1.326 ms
1.421 ms
1.376 ms
1.437 ms
1.358 ms
1.384 ms
1.404 ms
1.342 ms
1.426 ms
15.837 ms
1.451 ms
1.354 ms
1.407 ms
1.486 ms
1.544 ms
1.360 ms
1.346 ms
1.463 ms
1.424 ms
1.360 ms
1.384 ms
1.388 ms
1.412 ms
1.358 ms
1.401 ms
1.343 ms
1.457 ms
1.356 ms
1.378 ms
1.382 ms
1.310 ms
1.356 ms
15.188 ms
1.433 ms
1.397 ms
1.387 ms
1.396 ms
8.384 ms
17.011 ms
12.398 ms
1.491 ms
1.477 ms
2.686 ms
1.419 ms
6.993 ms
1.478 ms
1.367 ms
1.375 ms
1.409 ms
1.352 ms
1.444 ms
1.351 ms
1.481 ms
1.445 ms
1.376 ms
1.441 ms
1.381 ms
1.432 ms
1.362 ms
1.413 ms
1.500 ms
19.860 ms
1.483 ms
1.337 ms
1.361 ms
15.915 ms
17.493 ms
1.436 ms
1.519 ms
1.354 ms
1.476 ms
1.357 ms
6.371 ms
1.422 ms
1.448 ms
2.789 ms
1.440 ms
1.618 ms
1.380 ms
1.377 ms
1.336 ms
1.398 ms
1.385 ms
1.347 ms
12.621 ms
1.345 ms
1.501 ms
1.510 ms
1.358 ms
1.356 ms
1.442 ms
1.360 ms
1.389 ms
1.477 ms
1.447 ms
1.403 ms
19.396 ms
1.433 ms
1.523 ms
1.456 ms
1.418 ms
1.369 ms
1.365 ms
1.387 ms
1.386 ms
1.360 ms
1.375 ms
18.531 ms
1.364 ms
1.349 ms
1.395 ms
9.699 ms
1.399 ms
1.453 ms
1.393 ms
1.399 ms
1.439 ms
1.353 ms
1.411 ms
1.337 ms
1.354 ms
1.626 ms
1.505 ms
1.396 ms
1.430 ms
1.411 ms
1.422 ms
1.371 ms
1.461 ms
1.467 ms
1.394 ms
1.374 ms
1.373 ms
1.579 ms
1.445 ms
1.492 ms
1.388 ms
1.414 ms
2.160 ms
1.404 ms
1.481 ms
1.410 ms
1.416 ms
1.441 ms
1.430 ms
1.383 ms
1.407 ms
1.391 ms
1.497 ms
1.494 ms
4.215 ms
1.406 ms
1.477 ms
1.391 ms
1.418 ms
1.426 ms
14.044 ms
1.349 ms
1.477 ms
1.346 ms
1.364 ms
1.377 ms
1.384 ms
1.436 ms
1.423 ms
1.477 ms
1.460 ms
1.360 ms
1.397 ms
12.473 ms
12.095 ms
19.146 ms
10.173 ms
1.497 ms
1.871 ms
1.466 ms
1.369 ms
1.497 ms
1.337 ms
1.398 ms
1.531 ms
1.380 ms
1.371 ms
1.357 ms
1.367 ms
1.397 ms
1.343 ms
1.348 ms
1.528 ms
1.487 ms
1.469 ms
1.371 ms
1.581 ms
1.423 ms
1.555 ms
1.389 ms
16.945 ms
1.466 ms
1.377 ms
1.450 ms
2.493 ms
1.381 ms
1.351 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.271 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.227 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.916 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop6.243 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.923 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.113 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.254 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.895 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.918 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 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.154 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.426 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.657 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop49.522 msReply RTT ASN unavailable
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.203 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.056 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.713 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.123 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.112 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.453 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.386 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.403 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.377 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.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.819 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.172 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.749 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.190 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.295 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.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.798 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.180 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.221 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.137 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.186 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop3.793 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.314 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.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 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.278 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.775 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.172 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 hop22.436 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.388 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.202 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.229 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.399 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.318 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.135 msAS8002 · Stealth0.117 msAS8002 · StealthSame responder
20.174 msAS8002 · Stealth0.657 msAS8002 · StealthSame responder
31.271 ms49.522 msSame 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.113 msAS8002 · Stealth0.112 msAS8002 · StealthSame responder
20.175 msAS8002 · Stealth0.175 msAS8002 · StealthSame responder
3Not recorded18.453 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.227 msAS8002 · Stealth0.137 msAS8002 · StealthSame responder
20.200 msAS8002 · Stealth0.203 msAS8002 · StealthSame responder
30.916 ms8.056 msSame responder
4No replyNo replyNot established
56.243 msAS13335 · Cloudflare1.713 msAS13335 · CloudflareDifferent responders
6No replyNo replyNot established
71.923 msAS13335 · Cloudflare2.123 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.388 msUsual round trip before the event
Last recorded event RTT1.407 msLast successful event recording
Event p95 RTT12.566 ms95th percentile of successful recordings
Change from baseline+0.019 msLast event RTT compared with the baseline
Successful / expected recordings189 / 190Recorded 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