Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-1F3B283BA2CAF855

OpenAI Chat website

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.

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 23:55 – 04 Nov 2026 02:24 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.
Recorded at (UTC)RTT
1.411 ms
1.393 ms
14.251 ms
1.216 ms
1.422 ms
1.128 ms
4.339 ms
1.350 ms
1.374 ms
1.307 ms
1.465 ms
1.456 ms
1.153 ms
1.179 ms
1.239 ms
1.199 ms
10.178 ms
1.433 ms
1.253 ms
1.347 ms
1.377 ms
1.152 ms
1.173 ms
1.361 ms
1.329 ms
1.129 ms
1.388 ms
1.393 ms
1.356 ms
1.177 ms
1.426 ms
1.158 ms
1.158 ms
1.197 ms
1.194 ms
1.153 ms
1.207 ms
1.179 ms
1.189 ms
1.220 ms
1.401 ms
17.621 ms
1.168 ms
1.180 ms
1.224 ms
2.160 ms
1.339 ms
1.472 ms
1.136 ms
1.361 ms
1.151 ms
1.345 ms
1.150 ms
1.363 ms
1.172 ms
1.358 ms
1.234 ms
1.472 ms
1.451 ms
1.206 ms
1.531 ms
1.363 ms
1.150 ms
1.190 ms
1.373 ms
1.406 ms
1.363 ms
1.358 ms
1.353 ms
1.178 ms
1.142 ms
10.550 ms
1.305 ms
1.374 ms
1.400 ms
1.204 ms
1.145 ms
1.397 ms
1.371 ms
1.128 ms
1.241 ms
1.370 ms
1.405 ms
1.377 ms
1.331 ms
1.409 ms
1.139 ms
1.499 ms
1.389 ms
4.831 ms
1.155 ms
1.165 ms
5.212 ms
1.183 ms
1.340 ms
1.132 ms
1.350 ms
1.404 ms
1.354 ms
1.342 ms
1.353 ms
1.446 ms
14.826 ms
1.203 ms
1.366 ms
1.214 ms
1.360 ms
1.194 ms
1.164 ms
1.144 ms
1.197 ms
1.454 ms
1.347 ms
1.137 ms
1.365 ms
1.207 ms
1.347 ms
1.151 ms
1.357 ms
1.201 ms
11.299 ms
1.344 ms
1.134 ms
1.381 ms
1.160 ms
1.150 ms
1.150 ms
1.138 ms
1.398 ms
1.133 ms
1.130 ms
1.249 ms
1.214 ms
1.203 ms
1.410 ms
9.219 ms
1.196 ms
1.140 ms
1.508 ms
1.181 ms
1.202 ms
1.355 ms
1.377 ms
1.352 ms
1.166 ms
5.973 ms
1.368 ms
1.377 ms
1.344 ms
1.123 ms
1.136 ms
1.154 ms
1.456 ms
1.379 ms
1.145 ms
1.383 ms
1.206 ms
1.422 ms
1.230 ms
1.396 ms
1.390 ms
1.402 ms
1.150 ms
1.414 ms
1.371 ms
1.405 ms
1.414 ms
1.175 ms
1.177 ms
1.159 ms
1.362 ms
1.381 ms
1.145 ms
1.183 ms
1.161 ms
1.382 ms
2.968 ms
1.195 ms
1.170 ms
1.414 ms
1.384 ms
1.197 ms
1.205 ms
1.184 ms
1.184 ms
1.809 ms
1.369 ms
1.444 ms
1.159 ms
1.333 ms
1.388 ms
1.386 ms
1.155 ms
1.324 ms
1.388 ms
1.438 ms
1.151 ms
1.380 ms
1.349 ms
1.301 ms
13.598 ms
1.291 ms
1.394 ms
1.129 ms
1.365 ms
1.378 ms
1.366 ms
1.183 ms
1.197 ms
1.379 ms
1.751 ms
1.470 ms
1.401 ms
1.134 ms
1.152 ms
1.391 ms
1.131 ms
1.541 ms
1.359 ms
1.153 ms
1.168 ms
1.214 ms
1.352 ms
1.369 ms
1.429 ms
3.505 ms
11.406 ms
1.468 ms
1.445 ms
1.316 ms
8.097 ms
1.143 ms
1.341 ms
15.967 ms
1.340 ms
1.174 ms
1.139 ms
1.141 ms
1.370 ms
1.365 ms
1.197 ms
1.184 ms
1.188 ms
1.379 ms
1.126 ms
1.374 ms
1.346 ms
1.176 ms
1.398 ms
1.146 ms
1.184 ms
1.155 ms
1.161 ms
1.424 ms
1.183 ms
1.149 ms
1.376 ms
1.417 ms
1.377 ms
1.373 ms
1.338 ms
1.399 ms
1.145 ms
1.340 ms
1.368 ms
1.211 ms
1.341 ms
1.403 ms
1.436 ms
1.153 ms
1.334 ms
4.488 ms
1.290 ms
1.254 ms
1.367 ms
1.148 ms
1.324 ms
1.352 ms
1.322 ms
1.369 ms
1.421 ms
1.196 ms
1.150 ms
1.134 ms
1.425 ms
1.163 ms
6.562 ms
1.392 ms
1.230 ms
1.381 ms
1.169 ms
1.148 ms
1.724 ms
1.417 ms
1.381 ms
1.415 ms
1.327 ms
1.338 ms
1.360 ms
Network path / recorded observations

Network path observations.

18 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.809 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.215 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.039 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.699 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.283 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.112 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.217 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.650 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.171 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.695 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop15.634 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.671 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.901 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.920 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop8.831 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.193 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.201 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.247 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.889 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.499 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.824 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.324 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.684 msReply RTT ASN unavailable
During

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.180 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 hop1.901 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.329 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.409 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.986 msReply RTT AS13335 · Cloudflare
During

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.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.432 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.422 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.526 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.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.215 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.390 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.246 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.799 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.015 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.227 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.123 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.075 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.203 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.638 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.778 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.398 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.111 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.209 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.605 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.201 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.662 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.717 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.496 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.440 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.723 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.278 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.408 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.197 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.472 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.120 msAS8002 · Stealth0.124 msAS8002 · StealthSame responder
20.177 msAS8002 · Stealth0.324 msAS8002 · StealthSame responder
30.901 ms0.684 msSame responder
41.920 msAS13335 · CloudflareNot recordedNot established
58.831 msAS13335 · CloudflareNot recordedNot established
61.193 msAS13335 · CloudflareNot recordedNot established
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.201 msAS8002 · Stealth0.150 msAS8002 · StealthSame responder
20.247 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
30.889 ms0.934 msSame responder
4No replyNo replyNot established
55.499 msAS13335 · Cloudflare1.901 msAS13335 · CloudflareSame responder
6No reply1.329 msAS13335 · CloudflareNot established
71.824 msAS13335 · CloudflareNot recordedNot 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.346 msUsual round trip before the event
Last recorded event RTT1.414 msLast successful event recording
Event p95 RTT3.119 ms95th percentile of successful recordings
Change from baseline+0.068 msLast event RTT compared with the baseline
Successful / expected recordings60 / 60Recorded 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