Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-E81DC6C5F31854FB

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

03 Nov 2026 14:30 – 03 Nov 2026 18:19 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.360 ms
1.371 ms
15.976 ms
1.334 ms
7.939 ms
1.405 ms
1.531 ms
17.154 ms
1.396 ms
1.341 ms
1.349 ms
1.449 ms
1.348 ms
1.531 ms
1.471 ms
1.433 ms
1.398 ms
1.380 ms
1.418 ms
1.386 ms
1.403 ms
1.376 ms
1.317 ms
13.855 ms
1.430 ms
1.327 ms
1.340 ms
1.315 ms
1.395 ms
1.358 ms
1.370 ms
1.430 ms
1.670 ms
1.426 ms
1.361 ms
1.348 ms
1.334 ms
1.456 ms
1.331 ms
1.338 ms
1.398 ms
1.396 ms
1.359 ms
1.648 ms
3.035 ms
1.465 ms
1.347 ms
20.559 ms
1.334 ms
1.434 ms
1.342 ms
1.506 ms
1.424 ms
1.397 ms
1.363 ms
1.399 ms
1.563 ms
1.474 ms
1.340 ms
1.341 ms
3.146 ms
1.359 ms
1.317 ms
10.539 ms
1.620 ms
1.465 ms
15.795 ms
1.396 ms
1.413 ms
8.197 ms
1.353 ms
1.474 ms
1.335 ms
1.336 ms
1.349 ms
1.331 ms
1.388 ms
3.168 ms
1.626 ms
1.338 ms
1.420 ms
1.351 ms
1.371 ms
1.373 ms
1.359 ms
1.470 ms
1.332 ms
1.450 ms
1.666 ms
1.378 ms
1.326 ms
16.809 ms
1.327 ms
1.325 ms
1.483 ms
1.351 ms
1.340 ms
1.373 ms
1.337 ms
1.352 ms
1.360 ms
1.484 ms
18.640 ms
1.392 ms
1.339 ms
1.376 ms
1.347 ms
1.333 ms
1.383 ms
1.404 ms
1.391 ms
1.325 ms
1.449 ms
1.364 ms
1.405 ms
1.376 ms
1.406 ms
2.220 ms
1.385 ms
1.335 ms
1.386 ms
6.638 ms
1.565 ms
1.446 ms
1.335 ms
1.451 ms
6.163 ms
1.360 ms
1.374 ms
1.559 ms
1.333 ms
1.429 ms
1.436 ms
1.345 ms
1.397 ms
10.622 ms
1.411 ms
1.437 ms
1.373 ms
14.542 ms
1.365 ms
1.444 ms
1.328 ms
1.450 ms
1.386 ms
1.404 ms
1.342 ms
1.358 ms
2.473 ms
1.366 ms
1.382 ms
1.354 ms
1.370 ms
2.518 ms
1.488 ms
1.456 ms
2.711 ms
1.368 ms
3.033 ms
1.487 ms
5.855 ms
1.360 ms
1.369 ms
1.376 ms
1.348 ms
3.777 ms
1.401 ms
1.352 ms
1.325 ms
1.388 ms
1.335 ms
1.523 ms
2.319 ms
20.499 ms
1.377 ms
1.410 ms
1.440 ms
1.362 ms
18.070 ms
1.330 ms
15.920 ms
20.085 ms
1.413 ms
7.379 ms
1.330 ms
1.331 ms
19.947 ms
1.357 ms
13.445 ms
1.375 ms
1.593 ms
1.418 ms
1.441 ms
1.346 ms
1.414 ms
3.879 ms
1.479 ms
1.444 ms
1.386 ms
1.370 ms
1.324 ms
6.457 ms
1.413 ms
1.330 ms
1.469 ms
1.353 ms
1.352 ms
1.385 ms
1.347 ms
1.337 ms
1.344 ms
1.467 ms
1.411 ms
1.387 ms
1.345 ms
1.406 ms
1.389 ms
1.394 ms
12.102 ms
1.408 ms
17.606 ms
1.299 ms
1.406 ms
1.727 ms
1.386 ms
1.354 ms
1.406 ms
1.418 ms
1.388 ms
1.504 ms
1.384 ms
1.356 ms
1.364 ms
1.350 ms
1.334 ms
1.397 ms
1.387 ms
1.335 ms
1.398 ms
1.603 ms
1.427 ms
1.364 ms
1.357 ms
1.343 ms
1.355 ms
1.470 ms
1.426 ms
13.466 ms
1.452 ms
1.340 ms
16.083 ms
1.356 ms
16.178 ms
1.333 ms
2.484 ms
8.060 ms
13.947 ms
1.348 ms
2.923 ms
1.339 ms
1.350 ms
1.551 ms
15.216 ms
1.371 ms
4.773 ms
1.342 ms
1.600 ms
1.354 ms
18.308 ms
1.441 ms
1.329 ms
5.032 ms
1.416 ms
1.362 ms
1.343 ms
1.323 ms
6.797 ms
1.336 ms
1.395 ms
1.482 ms
1.393 ms
1.386 ms
19.508 ms
1.456 ms
1.404 ms
1.355 ms
20.360 ms
20.456 ms
1.996 ms
1.352 ms
1.353 ms
1.387 ms
1.355 ms
3.495 ms
13.688 ms
1.357 ms
1.414 ms
1.317 ms
1.391 ms
1.378 ms
1.382 ms
1.391 ms
1.340 ms
1.381 ms
1.333 ms
1.366 ms
1.389 ms
12.375 ms
1.385 ms
1.358 ms
1.411 ms
1.490 ms
1.374 ms
1.355 ms
1.423 ms
1.431 ms
1.374 ms
1.370 ms
2.564 ms
1.333 ms
1.387 ms
1.508 ms
2.984 ms
1.452 ms
4.406 ms
7.755 ms
14.946 ms
1.390 ms
1.429 ms
1.389 ms
1.374 ms
11.968 ms
6.603 ms
17.947 ms
1.467 ms
1.349 ms
1.502 ms
1.392 ms
1.576 ms
1.356 ms
1.341 ms
1.448 ms
1.377 ms
1.419 ms
1.432 ms
17.969 ms
1.348 ms
1.356 ms
1.379 ms
1.322 ms
1.339 ms
1.361 ms
1.336 ms
1.753 ms
1.485 ms
1.361 ms
1.576 ms
1.343 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.155 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 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 hop7.829 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.388 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop21.468 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.248 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop57.311 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.730 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination4.128 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.606 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.485 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.481 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.966 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.899 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.317 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.048 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.400 msReply RTT ASN unavailable
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.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.095 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop27.454 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.022 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.004 msReply RTT AS13335 · Cloudflare
During

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.294 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.974 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.616 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.741 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.175 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.139 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 hop2.691 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.097 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.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.386 msReply RTT ASN unavailable
After

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.286 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.886 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop10.171 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.051 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.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.642 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop60.468 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop16.626 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.393 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.155 msAS8002 · Stealth0.130 msAS8002 · StealthSame responder
20.188 msAS8002 · Stealth0.190 msAS8002 · StealthSame responder
3Not recorded16.004 msAS13335 · CloudflareNot established
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.121 msAS8002 · Stealth0.117 msAS8002 · StealthSame responder
20.182 msAS8002 · Stealth0.181 msAS8002 · StealthSame responder
321.468 msAS13335 · Cloudflare3.966 msSame 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.144 msAS8002 · Stealth0.141 msAS8002 · StealthSame responder
20.184 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
31.606 ms10.899 msSame responder
4No replyNo replyNot established
51.485 msAS13335 · Cloudflare2.317 msAS13335 · CloudflareDifferent responders
61.481 msAS13335 · Cloudflare1.048 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.398 msLast successful event recording
Event p95 RTT17.621 ms95th percentile of successful recordings
Change from baseline+0.031 msLast event RTT compared with the baseline
Successful / expected recordings219 / 220Recorded 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