Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-C84309AB6977AD64

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

05 Nov 2026 02:05 – 05 Nov 2026 05: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.337 ms
1.649 ms
1.359 ms
1.353 ms
1.346 ms
1.359 ms
1.381 ms
1.344 ms
1.318 ms
1.396 ms
1.421 ms
1.396 ms
1.378 ms
1.389 ms
1.329 ms
1.337 ms
1.340 ms
1.338 ms
1.363 ms
1.342 ms
1.433 ms
1.356 ms
1.336 ms
1.485 ms
1.345 ms
1.419 ms
1.336 ms
1.323 ms
1.444 ms
1.434 ms
1.320 ms
1.318 ms
1.319 ms
1.338 ms
1.334 ms
1.479 ms
1.413 ms
1.450 ms
1.342 ms
5.820 ms
1.349 ms
1.364 ms
1.450 ms
1.432 ms
1.478 ms
1.354 ms
1.464 ms
1.347 ms
1.384 ms
1.386 ms
1.379 ms
1.378 ms
1.330 ms
1.588 ms
1.337 ms
1.395 ms
1.401 ms
1.443 ms
1.469 ms
1.326 ms
1.375 ms
1.343 ms
1.337 ms
9.002 ms
1.374 ms
1.318 ms
1.387 ms
1.336 ms
1.336 ms
1.347 ms
1.356 ms
1.326 ms
1.340 ms
1.346 ms
1.345 ms
1.421 ms
1.316 ms
1.408 ms
7.528 ms
1.347 ms
1.415 ms
1.436 ms
1.355 ms
1.337 ms
1.356 ms
1.349 ms
1.355 ms
1.369 ms
1.450 ms
1.350 ms
1.350 ms
1.330 ms
1.436 ms
1.667 ms
1.348 ms
1.349 ms
1.339 ms
1.327 ms
1.310 ms
1.356 ms
1.426 ms
1.338 ms
1.435 ms
1.345 ms
1.372 ms
1.313 ms
1.385 ms
1.411 ms
1.369 ms
1.358 ms
1.358 ms
1.373 ms
4.044 ms
1.336 ms
1.300 ms
1.397 ms
1.408 ms
1.374 ms
1.512 ms
1.338 ms
1.355 ms
19.144 ms
2.056 ms
2.450 ms
20.513 ms
1.440 ms
20.237 ms
2.689 ms
18.357 ms
13.808 ms
20.469 ms
1.382 ms
1.354 ms
4.609 ms
10.046 ms
10.279 ms
19.090 ms
9.424 ms
1.373 ms
1.341 ms
18.016 ms
1.348 ms
1.346 ms
17.874 ms
1.382 ms
1.390 ms
1.366 ms
17.245 ms
1.817 ms
1.358 ms
4.949 ms
1.324 ms
7.827 ms
14.394 ms
1.813 ms
1.411 ms
19.960 ms
3.332 ms
3.973 ms
19.891 ms
8.846 ms
1.367 ms
5.003 ms
11.058 ms
1.380 ms
4.624 ms
4.693 ms
20.008 ms
7.051 ms
1.352 ms
1.383 ms
1.394 ms
16.945 ms
1.455 ms
11.881 ms
19.729 ms
1.373 ms
1.820 ms
5.096 ms
1.419 ms
12.969 ms
1.336 ms
6.142 ms
1.353 ms
6.355 ms
4.035 ms
1.392 ms
1.395 ms
19.192 ms
1.361 ms
13.109 ms
1.373 ms
4.185 ms
1.337 ms
15.133 ms
1.318 ms
1.376 ms
19.025 ms
1.466 ms
1.321 ms
1.384 ms
1.320 ms
1.402 ms
1.990 ms
3.230 ms
1.340 ms
1.318 ms
8.506 ms
16.046 ms
14.871 ms
15.401 ms
1.397 ms
5.447 ms
1.310 ms
1.362 ms
1.354 ms
1.434 ms
1.344 ms
1.312 ms
1.337 ms
1.441 ms
1.646 ms
1.568 ms
1.343 ms
1.424 ms
1.372 ms
1.350 ms
1.432 ms
1.432 ms
1.372 ms
1.588 ms
2.888 ms
1.378 ms
1.429 ms
1.316 ms
1.345 ms
1.381 ms
1.302 ms
1.488 ms
1.349 ms
1.357 ms
1.332 ms
1.387 ms
1.356 ms
3.225 ms
1.350 ms
1.417 ms
1.359 ms
1.344 ms
1.365 ms
1.343 ms
1.328 ms
1.431 ms
1.405 ms
1.444 ms
1.352 ms
1.406 ms
1.377 ms
17.973 ms
1.379 ms
3.922 ms
1.365 ms
1.319 ms
1.353 ms
1.347 ms
1.349 ms
1.316 ms
1.386 ms
2.170 ms
1.376 ms
1.372 ms
1.349 ms
10.463 ms
1.478 ms
1.402 ms
1.387 ms
1.347 ms
1.437 ms
1.364 ms
1.700 ms
1.372 ms
1.479 ms
1.985 ms
1.299 ms
1.348 ms
1.338 ms
1.502 ms
1.335 ms
1.333 ms
1.322 ms
1.334 ms
1.335 ms
1.329 ms
1.318 ms
1.361 ms
1.400 ms
1.320 ms
1.329 ms
1.327 ms
1.349 ms
1.369 ms
1.321 ms
1.316 ms
1.349 ms
1.341 ms
1.339 ms
1.380 ms
1.339 ms
7.036 ms
1.388 ms
1.323 ms
1.373 ms
1.361 ms
1.333 ms
1.338 ms
1.396 ms
1.412 ms
1.529 ms
1.366 ms
1.419 ms
1.333 ms
1.391 ms
1.397 ms
1.326 ms
1.465 ms
1.389 ms
4.669 ms
1.332 ms
1.322 ms
1.423 ms
1.428 ms
1.359 ms
1.392 ms
1.350 ms
1.365 ms
1.332 ms
1.359 ms
1.386 ms
1.349 ms
1.418 ms
1.299 ms
1.333 ms
1.320 ms
1.350 ms
1.347 ms
1.334 ms
1.355 ms
1.398 ms
1.374 ms
1.502 ms
1.327 ms
1.308 ms
1.422 ms
1.330 ms
1.337 ms
1.331 ms
1.434 ms
1.339 ms
1.317 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.281 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.158 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.817 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.621 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.794 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.164 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.194 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.335 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.234 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.276 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.323 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.174 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.562 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.194 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop57.684 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop13.620 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.388 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.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.952 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.267 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.796 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.524 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination9.964 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.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.215 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.924 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.157 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.868 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.929 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.219 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.115 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.356 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.125 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.175 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.567 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.203 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.766 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.556 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.162 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.373 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.206 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.271 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.846 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.442 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.523 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.195 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.548 msReply RTT ASN unavailable
After

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.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.934 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop56.937 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.080 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.183 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.855 msReply RTT ASN unavailable
After

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.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.879 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.806 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.778 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.517 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.124 msAS8002 · Stealth0.115 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.190 msAS8002 · StealthSame responder
31.281 msAS13335 · Cloudflare1.356 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.164 msAS8002 · Stealth0.127 msAS8002 · StealthSame responder
20.194 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
318.335 ms19.952 msSame responder
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.194 msAS8002 · Stealth0.137 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.267 msAS8002 · StealthSame responder
357.684 ms19.796 msSame responder
4No replyNo replyNot established
513.620 msAS13335 · Cloudflare7.524 msAS13335 · CloudflareDifferent responders
61.388 msAS13335 · CloudflareNo replyNot established
7Not recorded9.964 msAS13335 · CloudflareNot established
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.234 msAS8002 · Stealth0.170 msAS8002 · StealthSame responder
20.276 msAS8002 · Stealth0.178 msAS8002 · StealthSame responder
32.323 ms1.125 msSame responder
4No replyNo replyNot established
52.174 msAS13335 · Cloudflare2.175 msAS13335 · CloudflareDifferent responders
61.562 msAS13335 · Cloudflare1.567 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.370 msUsual round trip before the event
Last recorded event RTT1.349 msLast successful event recording
Event p95 RTT19.818 ms95th percentile of successful recordings
Change from baseline-0.020 msLast event RTT compared with the baseline
Successful / expected recordings130 / 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