Start an order
Root cause analysis / Investigation

api.openai.com

Reference RCA-9877851923AE07E0

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

27 Oct 2026 23:55 – 28 Oct 2026 03:39 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.465 ms
1.380 ms
1.443 ms
1.375 ms
1.356 ms
1.390 ms
1.450 ms
1.461 ms
1.458 ms
1.369 ms
1.381 ms
1.348 ms
1.391 ms
1.405 ms
1.410 ms
1.401 ms
1.485 ms
1.332 ms
1.456 ms
1.366 ms
1.452 ms
1.372 ms
1.409 ms
1.501 ms
1.402 ms
1.350 ms
1.654 ms
1.347 ms
1.894 ms
1.376 ms
1.401 ms
1.338 ms
1.315 ms
1.422 ms
1.428 ms
1.345 ms
5.057 ms
1.330 ms
10.126 ms
1.426 ms
1.339 ms
1.471 ms
1.356 ms
1.323 ms
1.375 ms
1.399 ms
1.418 ms
1.431 ms
1.348 ms
1.359 ms
1.407 ms
1.353 ms
1.714 ms
1.390 ms
1.530 ms
1.345 ms
1.371 ms
1.405 ms
1.407 ms
1.355 ms
1.447 ms
1.439 ms
1.368 ms
1.389 ms
2.798 ms
1.329 ms
1.549 ms
1.339 ms
1.376 ms
1.484 ms
1.381 ms
1.365 ms
1.410 ms
1.376 ms
1.396 ms
1.336 ms
1.372 ms
1.398 ms
1.486 ms
1.393 ms
1.483 ms
1.581 ms
1.383 ms
16.990 ms
1.347 ms
1.359 ms
1.484 ms
1.529 ms
1.362 ms
1.439 ms
1.476 ms
1.371 ms
1.564 ms
1.420 ms
2.186 ms
1.336 ms
1.331 ms
1.419 ms
1.370 ms
1.440 ms
1.354 ms
1.380 ms
1.419 ms
1.513 ms
1.385 ms
1.396 ms
1.461 ms
1.381 ms
1.397 ms
1.612 ms
1.380 ms
1.636 ms
1.495 ms
1.434 ms
1.331 ms
3.051 ms
1.377 ms
1.345 ms
1.541 ms
1.392 ms
1.546 ms
1.368 ms
1.360 ms
2.787 ms
1.437 ms
1.457 ms
1.476 ms
1.596 ms
1.339 ms
1.358 ms
1.342 ms
1.402 ms
1.414 ms
7.199 ms
5.877 ms
1.386 ms
1.333 ms
1.420 ms
1.342 ms
1.431 ms
1.465 ms
1.339 ms
1.359 ms
1.427 ms
1.363 ms
1.463 ms
1.534 ms
1.349 ms
1.522 ms
1.413 ms
1.420 ms
17.345 ms
1.531 ms
1.377 ms
2.035 ms
1.385 ms
1.421 ms
1.606 ms
1.471 ms
1.454 ms
1.388 ms
1.339 ms
1.374 ms
1.443 ms
1.395 ms
1.393 ms
1.409 ms
1.362 ms
1.357 ms
1.411 ms
1.362 ms
1.338 ms
1.347 ms
1.351 ms
1.421 ms
1.380 ms
1.405 ms
18.487 ms
1.353 ms
1.367 ms
1.426 ms
1.383 ms
1.382 ms
1.348 ms
1.360 ms
1.339 ms
4.112 ms
1.369 ms
1.400 ms
1.359 ms
1.351 ms
1.402 ms
1.455 ms
1.370 ms
1.344 ms
1.410 ms
1.362 ms
1.548 ms
1.474 ms
11.099 ms
1.325 ms
1.514 ms
1.339 ms
1.473 ms
1.352 ms
1.374 ms
1.380 ms
1.347 ms
1.435 ms
1.395 ms
1.438 ms
1.359 ms
1.360 ms
1.364 ms
1.405 ms
1.361 ms
1.335 ms
10.604 ms
1.367 ms
1.533 ms
1.365 ms
1.361 ms
1.332 ms
1.461 ms
1.472 ms
1.443 ms
1.503 ms
1.355 ms
1.461 ms
1.380 ms
1.400 ms
1.417 ms
1.393 ms
1.338 ms
1.382 ms
1.374 ms
1.427 ms
1.373 ms
1.330 ms
1.499 ms
1.414 ms
1.363 ms
1.334 ms
1.336 ms
1.341 ms
1.469 ms
1.516 ms
1.322 ms
1.433 ms
1.411 ms
2.859 ms
1.399 ms
1.371 ms
1.343 ms
1.338 ms
1.411 ms
1.407 ms
1.481 ms
1.396 ms
1.509 ms
1.414 ms
1.373 ms
1.380 ms
1.415 ms
1.346 ms
1.434 ms
1.394 ms
1.430 ms
1.361 ms
1.366 ms
1.353 ms
1.410 ms
1.333 ms
1.348 ms
1.344 ms
1.361 ms
1.354 ms
1.378 ms
6.452 ms
1.389 ms
1.387 ms
1.377 ms
1.381 ms
1.448 ms
1.423 ms
1.386 ms
1.357 ms
1.737 ms
1.359 ms
1.345 ms
1.364 ms
1.429 ms
1.406 ms
1.862 ms
1.419 ms
1.418 ms
1.364 ms
1.366 ms
1.359 ms
1.513 ms
1.385 ms
1.413 ms
1.379 ms
1.361 ms
1.361 ms
1.393 ms
1.346 ms
1.374 ms
1.344 ms
1.345 ms
1.390 ms
1.342 ms
1.376 ms
1.390 ms
1.398 ms
1.355 ms
1.409 ms
1.365 ms
1.419 ms
1.424 ms
1.398 ms
1.450 ms
1.420 ms
1.444 ms
1.432 ms
1.526 ms
1.387 ms
1.433 ms
1.347 ms
1.413 ms
1.346 ms
1.392 ms
1.399 ms
1.364 ms
1.333 ms
1.403 ms
1.383 ms
1.398 ms
1.466 ms
1.597 ms
1.331 ms
1.341 ms
1.351 ms
1.377 ms
1.414 ms
1.338 ms
7.637 ms
1.466 ms
1.430 ms
1.477 ms
1.377 ms
1.381 ms
1.355 ms
1.361 ms
1.350 ms
1.320 ms
1.342 ms
1.373 ms
1.359 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.879 msReply RTT AS13335 · Cloudflare
Before

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.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 hop62.187 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.286 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.172 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.237 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.969 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.450 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.836 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.420 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.164 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.292 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.586 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.276 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.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.669 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.166 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 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.057 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.295 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.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.023 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.245 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.077 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.689 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.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.120 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.163 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop35.234 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop6.220 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.055 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.211 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.683 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.165 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.429 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop13.719 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.386 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.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
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.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.170 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.739 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.215 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.043 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.398 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.509 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.429 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.210 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.778 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.616 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.376 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.125 msAS8002 · Stealth0.151 msAS8002 · StealthSame responder
20.176 msAS8002 · Stealth0.174 msAS8002 · StealthSame responder
31.879 msAS13335 · Cloudflare13.120 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.117 msAS8002 · Stealth0.138 msAS8002 · StealthSame responder
20.172 msAS8002 · Stealth0.174 msAS8002 · StealthSame responder
322.237 ms6.669 msAS13335 · CloudflareSame 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.160 msAS8002 · Stealth0.160 msAS8002 · StealthSame responder
20.180 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
30.969 ms2.245 msAS13335 · CloudflareSame responder
41.450 msAS13335 · CloudflareNo replyNot established
51.836 msAS13335 · Cloudflare2.077 msAS13335 · CloudflareDifferent responders
61.420 msAS13335 · CloudflareNo replyNot established
7Not recorded1.689 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.164 msAS8002 · Stealth0.166 msAS8002 · StealthSame responder
20.188 msAS8002 · Stealth0.176 msAS8002 · StealthSame responder
31.292 msAS13335 · CloudflareNo replyNot established
4No replyNo replyNot established
51.586 msAS13335 · Cloudflare2.057 msAS13335 · CloudflareSame responder
61.276 msAS13335 · CloudflareNo replyNot established
7Not recorded1.295 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.

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.384 msUsual round trip before the event
Last recorded event RTT1.499 msLast successful event recording
Event p95 RTT8.678 ms95th percentile of successful recordings
Change from baseline+0.115 msLast event RTT compared with the baseline
Successful / expected recordings210 / 210Recorded 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