Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-FC15460789A9E5F3

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 01:00 – 03 Nov 2026 03:34 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.340 ms
1.389 ms
1.169 ms
1.313 ms
14.762 ms
1.360 ms
1.386 ms
1.341 ms
1.530 ms
1.128 ms
1.383 ms
1.349 ms
1.127 ms
1.177 ms
1.352 ms
1.329 ms
1.157 ms
1.195 ms
1.150 ms
1.169 ms
1.388 ms
1.163 ms
1.149 ms
1.141 ms
1.180 ms
1.453 ms
1.358 ms
1.116 ms
1.165 ms
1.173 ms
1.393 ms
2.514 ms
1.148 ms
1.150 ms
1.166 ms
1.129 ms
1.371 ms
1.167 ms
1.130 ms
1.370 ms
1.262 ms
1.172 ms
1.346 ms
1.160 ms
1.357 ms
1.379 ms
1.373 ms
1.127 ms
1.374 ms
1.360 ms
1.167 ms
1.531 ms
1.358 ms
1.913 ms
1.346 ms
1.338 ms
1.367 ms
1.365 ms
1.243 ms
1.152 ms
3.219 ms
10.039 ms
1.345 ms
1.343 ms
1.169 ms
13.404 ms
16.574 ms
1.381 ms
1.344 ms
1.287 ms
1.137 ms
1.354 ms
1.353 ms
1.345 ms
1.366 ms
1.157 ms
1.366 ms
1.186 ms
1.184 ms
1.378 ms
1.132 ms
1.359 ms
1.356 ms
1.359 ms
1.188 ms
1.227 ms
1.329 ms
1.118 ms
18.421 ms
1.167 ms
9.308 ms
1.194 ms
1.123 ms
1.365 ms
1.365 ms
1.488 ms
1.375 ms
1.369 ms
1.155 ms
1.182 ms
1.181 ms
1.343 ms
1.392 ms
1.168 ms
1.158 ms
1.448 ms
1.187 ms
1.359 ms
1.596 ms
1.363 ms
1.361 ms
2.123 ms
1.154 ms
1.415 ms
1.173 ms
1.161 ms
1.133 ms
1.145 ms
1.172 ms
1.402 ms
1.549 ms
18.829 ms
1.362 ms
1.148 ms
1.365 ms
1.131 ms
1.424 ms
1.172 ms
1.172 ms
1.390 ms
1.388 ms
1.369 ms
1.142 ms
7.406 ms
1.344 ms
1.423 ms
1.401 ms
1.237 ms
1.158 ms
7.262 ms
1.357 ms
1.143 ms
1.385 ms
16.555 ms
1.367 ms
1.381 ms
1.142 ms
1.399 ms
1.575 ms
8.511 ms
1.542 ms
1.360 ms
1.143 ms
1.243 ms
2.886 ms
1.356 ms
1.369 ms
11.032 ms
1.368 ms
1.182 ms
1.371 ms
1.368 ms
1.162 ms
1.385 ms
1.151 ms
1.173 ms
1.151 ms
1.129 ms
1.366 ms
1.240 ms
1.507 ms
1.343 ms
1.132 ms
1.149 ms
1.344 ms
1.474 ms
1.170 ms
1.148 ms
1.134 ms
1.330 ms
1.188 ms
1.353 ms
1.445 ms
1.347 ms
1.199 ms
1.389 ms
1.351 ms
1.325 ms
1.473 ms
1.355 ms
1.149 ms
1.146 ms
1.136 ms
1.368 ms
1.360 ms
1.782 ms
3.843 ms
1.382 ms
1.139 ms
1.360 ms
1.500 ms
1.356 ms
1.350 ms
18.220 ms
1.427 ms
1.170 ms
1.397 ms
1.200 ms
1.365 ms
1.146 ms
1.415 ms
1.157 ms
1.158 ms
1.382 ms
1.155 ms
1.345 ms
1.158 ms
1.388 ms
1.230 ms
1.130 ms
4.038 ms
1.342 ms
1.137 ms
12.606 ms
1.396 ms
1.151 ms
1.141 ms
2.251 ms
1.316 ms
1.469 ms
4.366 ms
19.275 ms
1.350 ms
1.379 ms
1.150 ms
1.338 ms
19.787 ms
1.369 ms
1.385 ms
1.412 ms
1.177 ms
1.358 ms
15.955 ms
1.186 ms
1.151 ms
1.368 ms
1.364 ms
3.456 ms
1.351 ms
1.220 ms
1.340 ms
1.293 ms
1.153 ms
1.409 ms
1.328 ms
1.349 ms
1.410 ms
1.385 ms
1.334 ms
1.397 ms
2.448 ms
1.147 ms
4.945 ms
1.349 ms
1.375 ms
1.185 ms
1.324 ms
1.243 ms
1.137 ms
1.241 ms
1.136 ms
1.423 ms
1.377 ms
1.135 ms
1.127 ms
1.170 ms
1.420 ms
1.371 ms
1.376 ms
1.120 ms
1.400 ms
1.459 ms
1.346 ms
1.243 ms
1.351 ms
1.341 ms
1.133 ms
1.164 ms
1.179 ms
1.146 ms
1.339 ms
1.368 ms
1.215 ms
1.122 ms
1.135 ms
1.335 ms
1.166 ms
6.372 ms
1.494 ms
1.379 ms
1.157 ms
1.178 ms
4.940 ms
1.142 ms
1.394 ms
1.168 ms
1.377 ms
1.166 ms
1.137 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.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.925 msReply RTT ASN unavailable
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.269 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.460 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.234 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.382 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.644 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.864 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

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 hop9.144 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.695 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop3.724 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.024 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.162 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.941 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.119 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.110 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.198 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.245 msReply RTT ASN unavailable
During

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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.049 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.497 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop11.097 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.446 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.165 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.206 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop20.187 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.207 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.239 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.019 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.565 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.481 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination11.374 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.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.662 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.196 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.390 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop11.191 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.432 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.706 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop36.950 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.210 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.242 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.344 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.735 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.251 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.517 msReply RTT ASN unavailable
  4. TTL 4 Probe hop12.416 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.902 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.706 msReply RTT AS13335 · Cloudflare
After

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.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.591 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.419 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.656 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.210 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.581 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.551 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.926 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.182 msReply RTT AS13335 · Cloudflare
After

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.236 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.220 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.343 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.960 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 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.128 msAS8002 · Stealth0.110 msAS8002 · StealthSame responder
20.644 msAS8002 · Stealth0.198 msAS8002 · StealthSame responder
30.864 msAS13335 · Cloudflare1.245 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.148 msAS8002 · Stealth0.196 msAS8002 · StealthSame responder
20.184 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
37.162 ms1.390 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.941 msAS13335 · Cloudflare11.191 msAS13335 · CloudflareDifferent responders
6No reply1.432 msAS13335 · CloudflareNot established
72.119 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.344 msUsual round trip before the event
Last recorded event RTT1.355 msLast successful event recording
Event p95 RTT8.014 ms95th percentile of successful recordings
Change from baseline+0.011 msLast event RTT compared with the baseline
Successful / expected recordings70 / 70Recorded 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