Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-CF7D9BF3BAF9C600

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

02 Nov 2026 14:10 – 02 Nov 2026 23:09 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.367 ms
1.342 ms
1.349 ms
1.346 ms
1.395 ms
1.336 ms
4.795 ms
1.374 ms
1.388 ms
1.391 ms
1.453 ms
1.317 ms
1.361 ms
19.581 ms
1.346 ms
1.345 ms
1.471 ms
1.356 ms
1.342 ms
1.410 ms
1.419 ms
1.357 ms
1.319 ms
1.351 ms
1.355 ms
1.369 ms
1.375 ms
1.495 ms
11.916 ms
1.327 ms
1.372 ms
1.430 ms
1.333 ms
1.323 ms
1.343 ms
1.384 ms
1.463 ms
1.360 ms
1.344 ms
1.307 ms
1.398 ms
1.374 ms
1.426 ms
1.637 ms
1.344 ms
1.335 ms
1.342 ms
1.411 ms
1.364 ms
1.429 ms
1.469 ms
1.387 ms
1.321 ms
1.381 ms
1.349 ms
1.399 ms
4.108 ms
1.348 ms
1.441 ms
1.332 ms
1.339 ms
1.425 ms
1.342 ms
1.458 ms
1.378 ms
1.360 ms
1.345 ms
1.490 ms
1.416 ms
1.335 ms
1.388 ms
1.332 ms
1.367 ms
1.351 ms
1.438 ms
1.747 ms
1.348 ms
1.333 ms
19.708 ms
20.635 ms
1.355 ms
12.726 ms
17.798 ms
1.616 ms
1.342 ms
1.311 ms
1.360 ms
1.429 ms
1.463 ms
1.402 ms
2.351 ms
1.440 ms
1.360 ms
1.370 ms
1.322 ms
1.378 ms
1.434 ms
1.366 ms
1.337 ms
1.368 ms
1.440 ms
10.093 ms
1.387 ms
1.361 ms
1.386 ms
2.082 ms
9.162 ms
1.371 ms
1.475 ms
1.371 ms
1.405 ms
1.429 ms
1.313 ms
1.310 ms
1.354 ms
1.379 ms
1.318 ms
1.541 ms
1.356 ms
1.400 ms
1.337 ms
1.342 ms
1.635 ms
1.533 ms
1.404 ms
1.390 ms
1.317 ms
17.986 ms
1.440 ms
1.382 ms
1.385 ms
1.374 ms
20.139 ms
1.451 ms
1.334 ms
1.399 ms
1.438 ms
18.052 ms
1.399 ms
19.811 ms
1.411 ms
8.017 ms
18.646 ms
2.992 ms
18.811 ms
14.641 ms
1.430 ms
1.342 ms
1.362 ms
1.351 ms
1.393 ms
18.714 ms
1.384 ms
19.358 ms
12.307 ms
1.343 ms
1.406 ms
19.201 ms
1.399 ms
1.374 ms
2.192 ms
1.756 ms
1.347 ms
1.356 ms
1.800 ms
1.364 ms
8.377 ms
17.012 ms
1.400 ms
1.351 ms
1.412 ms
1.332 ms
1.440 ms
1.409 ms
3.068 ms
1.336 ms
1.583 ms
1.361 ms
1.383 ms
17.205 ms
1.387 ms
1.393 ms
1.366 ms
1.337 ms
1.338 ms
16.919 ms
1.346 ms
1.334 ms
19.363 ms
1.381 ms
6.658 ms
1.439 ms
1.475 ms
20.153 ms
1.332 ms
1.438 ms
12.921 ms
1.306 ms
1.527 ms
13.292 ms
1.328 ms
1.403 ms
1.354 ms
1.359 ms
1.406 ms
1.490 ms
1.829 ms
13.263 ms
3.337 ms
1.351 ms
1.323 ms
1.331 ms
1.436 ms
1.466 ms
1.347 ms
2.495 ms
1.352 ms
1.342 ms
1.341 ms
1.379 ms
1.337 ms
5.937 ms
1.339 ms
1.373 ms
1.447 ms
1.423 ms
1.325 ms
1.488 ms
1.411 ms
1.323 ms
1.334 ms
1.350 ms
1.555 ms
1.400 ms
1.375 ms
1.477 ms
1.411 ms
1.439 ms
1.483 ms
1.315 ms
1.334 ms
1.373 ms
1.330 ms
1.395 ms
1.399 ms
1.332 ms
1.428 ms
1.411 ms
1.322 ms
1.312 ms
1.351 ms
1.336 ms
1.410 ms
1.354 ms
1.412 ms
1.330 ms
1.347 ms
1.339 ms
1.346 ms
1.363 ms
1.387 ms
1.336 ms
1.334 ms
1.364 ms
1.340 ms
1.372 ms
1.346 ms
1.308 ms
1.319 ms
1.312 ms
8.310 ms
6.998 ms
1.373 ms
1.330 ms
1.359 ms
1.332 ms
1.418 ms
1.356 ms
1.451 ms
1.364 ms
1.351 ms
1.323 ms
1.324 ms
1.399 ms
10.933 ms
2.416 ms
1.350 ms
1.365 ms
1.325 ms
1.315 ms
1.317 ms
1.350 ms
1.324 ms
1.367 ms
1.339 ms
1.359 ms
1.379 ms
1.415 ms
1.401 ms
1.332 ms
1.468 ms
1.425 ms
1.368 ms
1.350 ms
1.351 ms
1.368 ms
1.369 ms
1.353 ms
1.317 ms
1.306 ms
1.352 ms
1.380 ms
1.349 ms
1.340 ms
16.720 ms
1.307 ms
1.608 ms
1.361 ms
1.406 ms
1.346 ms
1.316 ms
1.374 ms
1.440 ms
1.377 ms
1.311 ms
1.399 ms
1.438 ms
1.335 ms
1.327 ms
1.471 ms
1.362 ms
1.344 ms
5.377 ms
1.340 ms
1.438 ms
1.328 ms
1.457 ms
1.365 ms
1.421 ms
1.349 ms
1.568 ms
1.360 ms
1.330 ms
1.435 ms
1.412 ms
1.372 ms
1.364 ms
1.358 ms
1.318 ms
1.418 ms
1.339 ms
1.363 ms
1.335 ms
1.343 ms
1.527 ms
1.420 ms
1.323 ms
1.370 ms
1.331 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.219 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 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.190 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.655 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.259 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.118 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.034 msReply RTT AS13335 · Cloudflare
Before

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.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop76.153 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop10.464 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.247 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.371 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.686 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.074 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.368 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.973 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.164 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.287 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.148 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.679 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.402 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.181 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.774 msReply RTT AS13335 · Cloudflare
During

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.210 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.981 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.479 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination16.281 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.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.298 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.931 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.038 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.412 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.866 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.150 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 hop1.387 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.065 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.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.175 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.262 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.285 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.303 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.224 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop72.021 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.513 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.700 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.327 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.

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.143 msAS8002 · Stealth0.164 msAS8002 · StealthSame responder
20.371 msAS8002 · Stealth0.287 msAS8002 · StealthSame responder
30.686 msAS13335 · Cloudflare1.148 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.074 msAS13335 · Cloudflare1.679 msAS13335 · CloudflareDifferent responders
61.368 msAS13335 · Cloudflare1.402 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.151 msAS8002 · Stealth0.144 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.210 msAS8002 · StealthSame responder
376.153 msAS13335 · Cloudflare14.981 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
510.464 msAS13335 · Cloudflare2.479 msAS13335 · CloudflareDifferent responders
61.247 msAS13335 · CloudflareNo replyNot established
7Not recorded16.281 msAS13335 · CloudflareNot established

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.358 msUsual round trip before the event
Last recorded event RTT1.315 msLast successful event recording
Event p95 RTT17.933 ms95th percentile of successful recordings
Change from baseline-0.043 msLast event RTT compared with the baseline
Successful / expected recordings834 / 840Recorded 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