Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-C6E4970CAE98A615

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

29 Oct 2026 18:05 – 29 Oct 2026 22:29 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.403 ms
1.422 ms
1.491 ms
1.489 ms
1.531 ms
1.432 ms
1.521 ms
1.346 ms
1.369 ms
1.397 ms
1.367 ms
1.368 ms
1.378 ms
1.378 ms
1.385 ms
1.350 ms
1.393 ms
19.489 ms
1.390 ms
1.368 ms
1.374 ms
1.371 ms
1.394 ms
18.111 ms
20.917 ms
1.368 ms
1.394 ms
1.358 ms
18.223 ms
20.089 ms
6.338 ms
8.196 ms
1.380 ms
1.563 ms
1.369 ms
1.448 ms
1.372 ms
1.410 ms
1.363 ms
19.525 ms
1.375 ms
16.013 ms
1.373 ms
1.355 ms
1.547 ms
1.385 ms
1.444 ms
1.339 ms
1.366 ms
1.374 ms
1.347 ms
1.537 ms
1.421 ms
1.347 ms
1.379 ms
1.375 ms
1.343 ms
1.375 ms
1.364 ms
1.457 ms
1.372 ms
1.392 ms
1.492 ms
1.358 ms
1.337 ms
1.353 ms
1.361 ms
1.354 ms
1.378 ms
1.424 ms
1.396 ms
1.397 ms
1.396 ms
1.337 ms
1.363 ms
1.377 ms
1.445 ms
1.426 ms
1.369 ms
2.064 ms
7.984 ms
1.365 ms
1.410 ms
1.486 ms
1.454 ms
1.407 ms
1.462 ms
1.378 ms
18.851 ms
1.540 ms
2.568 ms
1.373 ms
1.368 ms
1.385 ms
1.345 ms
1.419 ms
1.647 ms
1.357 ms
1.407 ms
1.362 ms
1.405 ms
1.353 ms
1.346 ms
1.379 ms
1.346 ms
1.484 ms
1.361 ms
1.348 ms
1.390 ms
1.322 ms
1.509 ms
1.499 ms
1.368 ms
2.158 ms
1.349 ms
1.547 ms
1.364 ms
1.378 ms
1.748 ms
1.364 ms
20.160 ms
1.374 ms
1.413 ms
1.441 ms
1.617 ms
1.427 ms
2.217 ms
1.402 ms
1.387 ms
6.774 ms
1.375 ms
1.413 ms
1.356 ms
16.155 ms
1.404 ms
1.443 ms
9.907 ms
14.992 ms
17.677 ms
3.259 ms
1.388 ms
1.353 ms
1.416 ms
1.538 ms
4.642 ms
1.382 ms
1.476 ms
1.430 ms
1.362 ms
1.338 ms
1.448 ms
1.382 ms
1.439 ms
1.400 ms
1.420 ms
1.414 ms
1.452 ms
1.449 ms
4.741 ms
1.369 ms
1.403 ms
1.367 ms
1.438 ms
1.371 ms
1.640 ms
1.445 ms
1.549 ms
1.458 ms
2.221 ms
1.470 ms
1.496 ms
1.357 ms
1.367 ms
1.383 ms
7.718 ms
1.376 ms
1.329 ms
1.529 ms
14.461 ms
10.404 ms
1.407 ms
1.870 ms
1.455 ms
1.465 ms
1.371 ms
1.328 ms
1.391 ms
1.422 ms
1.382 ms
1.379 ms
1.369 ms
1.368 ms
9.747 ms
1.371 ms
2.557 ms
1.458 ms
1.364 ms
1.392 ms
1.348 ms
1.342 ms
1.401 ms
1.350 ms
1.396 ms
6.443 ms
1.377 ms
1.423 ms
1.766 ms
1.901 ms
1.483 ms
1.363 ms
1.384 ms
1.359 ms
1.339 ms
1.527 ms
1.376 ms
1.405 ms
1.334 ms
5.996 ms
1.353 ms
1.457 ms
2.868 ms
1.342 ms
1.347 ms
1.362 ms
1.323 ms
1.358 ms
8.201 ms
1.429 ms
1.375 ms
1.436 ms
1.398 ms
1.417 ms
1.426 ms
1.470 ms
1.425 ms
1.354 ms
1.390 ms
1.322 ms
1.380 ms
1.433 ms
1.484 ms
1.424 ms
1.597 ms
1.363 ms
1.401 ms
1.530 ms
1.369 ms
1.373 ms
1.431 ms
1.389 ms
1.412 ms
1.370 ms
1.379 ms
1.369 ms
1.412 ms
1.407 ms
1.359 ms
1.387 ms
1.331 ms
1.412 ms
1.376 ms
1.353 ms
1.438 ms
1.391 ms
1.670 ms
1.368 ms
1.403 ms
1.408 ms
1.369 ms
1.362 ms
1.353 ms
1.364 ms
1.417 ms
1.474 ms
1.351 ms
1.445 ms
1.368 ms
1.371 ms
1.448 ms
1.407 ms
1.341 ms
1.537 ms
1.409 ms
1.385 ms
1.394 ms
1.356 ms
1.357 ms
1.363 ms
1.415 ms
1.445 ms
1.352 ms
1.469 ms
1.375 ms
1.350 ms
1.461 ms
1.420 ms
1.449 ms
1.485 ms
1.345 ms
4.227 ms
1.407 ms
1.435 ms
1.344 ms
1.413 ms
1.379 ms
1.413 ms
1.438 ms
1.369 ms
1.374 ms
1.357 ms
1.367 ms
1.383 ms
1.363 ms
1.370 ms
1.350 ms
1.403 ms
1.377 ms
1.454 ms
1.355 ms
1.393 ms
1.470 ms
1.354 ms
1.427 ms
1.359 ms
1.351 ms
1.444 ms
1.351 ms
1.361 ms
1.340 ms
1.439 ms
1.684 ms
7.861 ms
1.331 ms
1.373 ms
1.410 ms
1.345 ms
1.394 ms
1.458 ms
1.362 ms
1.361 ms
1.389 ms
1.449 ms
1.421 ms
1.493 ms
1.552 ms
1.403 ms
1.373 ms
1.465 ms
1.415 ms
2.043 ms
1.420 ms
1.407 ms
1.443 ms
1.346 ms
1.405 ms
1.345 ms
1.335 ms
1.345 ms
1.401 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.178 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop52.081 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.181 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.403 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.126 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.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 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.159 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.009 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.158 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.173 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop39.261 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.132 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.243 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 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 hop3.208 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.288 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.118 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.171 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.543 msReply RTT AS13335 · Cloudflare
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.239 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.231 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.618 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.460 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.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.247 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.685 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.049 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.377 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.841 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.293 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.021 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.485 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.550 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.904 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.144 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.550 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.692 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.822 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.175 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.208 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.694 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.683 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.332 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.126 msAS8002 · Stealth0.243 msAS8002 · StealthSame responder
20.178 msAS8002 · Stealth0.180 msAS8002 · StealthSame 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.158 msAS8002 · Stealth0.151 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.186 msAS8002 · StealthSame responder
319.173 msAS13335 · CloudflareNo replyNot established
4No replyNo replyNot established
539.261 msAS13335 · Cloudflare3.208 msAS13335 · CloudflareDifferent responders
61.132 msAS13335 · Cloudflare1.288 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.385 msUsual round trip before the event
Last recorded event RTT1.433 msLast successful event recording
Event p95 RTT14.156 ms95th percentile of successful recordings
Change from baseline+0.048 msLast event RTT compared with the baseline
Successful / expected recordings289 / 290Recorded 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