Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-A22BC0ECBE93A8BD

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 12:10 – 03 Nov 2026 14:59 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.143 ms
1.368 ms
1.351 ms
1.160 ms
1.111 ms
1.129 ms
1.363 ms
1.138 ms
1.150 ms
1.130 ms
1.388 ms
1.150 ms
1.202 ms
1.378 ms
1.119 ms
1.341 ms
1.394 ms
1.356 ms
1.293 ms
1.384 ms
1.157 ms
1.351 ms
1.370 ms
1.372 ms
1.333 ms
1.175 ms
1.338 ms
1.322 ms
1.144 ms
1.124 ms
1.146 ms
1.126 ms
1.362 ms
1.141 ms
1.357 ms
1.135 ms
1.344 ms
1.143 ms
1.377 ms
1.346 ms
1.147 ms
1.170 ms
1.174 ms
1.367 ms
1.130 ms
1.135 ms
1.366 ms
1.355 ms
1.114 ms
1.448 ms
1.345 ms
1.123 ms
1.352 ms
1.134 ms
1.412 ms
1.408 ms
1.361 ms
1.170 ms
1.335 ms
1.351 ms
1.366 ms
1.130 ms
1.325 ms
1.189 ms
1.268 ms
1.157 ms
1.483 ms
1.144 ms
1.148 ms
1.339 ms
1.361 ms
9.076 ms
1.115 ms
1.372 ms
1.661 ms
1.330 ms
1.379 ms
1.368 ms
1.361 ms
1.133 ms
1.420 ms
1.224 ms
1.219 ms
1.359 ms
1.133 ms
1.428 ms
1.258 ms
1.371 ms
1.327 ms
1.161 ms
1.175 ms
1.352 ms
1.348 ms
1.378 ms
1.364 ms
1.105 ms
1.226 ms
1.370 ms
1.211 ms
1.158 ms
1.180 ms
1.383 ms
1.317 ms
1.361 ms
1.460 ms
2.187 ms
1.375 ms
1.125 ms
1.163 ms
1.346 ms
3.386 ms
1.440 ms
1.397 ms
1.372 ms
1.154 ms
1.134 ms
1.317 ms
1.323 ms
1.338 ms
1.374 ms
1.133 ms
1.430 ms
1.322 ms
20.239 ms
1.413 ms
1.340 ms
1.128 ms
1.523 ms
1.367 ms
1.385 ms
1.141 ms
1.397 ms
1.180 ms
1.455 ms
1.378 ms
1.376 ms
1.341 ms
1.384 ms
11.839 ms
3.893 ms
16.668 ms
1.379 ms
1.537 ms
1.393 ms
1.361 ms
1.191 ms
1.500 ms
1.205 ms
1.355 ms
1.315 ms
1.184 ms
5.234 ms
1.187 ms
1.348 ms
1.388 ms
1.160 ms
1.656 ms
1.368 ms
1.318 ms
1.159 ms
1.362 ms
1.345 ms
1.329 ms
1.134 ms
1.363 ms
1.152 ms
1.450 ms
1.252 ms
12.129 ms
1.201 ms
1.314 ms
1.151 ms
1.354 ms
1.346 ms
1.287 ms
1.358 ms
1.339 ms
1.144 ms
1.153 ms
1.360 ms
1.161 ms
6.822 ms
1.179 ms
1.153 ms
1.369 ms
3.753 ms
1.163 ms
1.356 ms
1.383 ms
1.138 ms
1.349 ms
1.237 ms
1.450 ms
1.230 ms
1.314 ms
1.396 ms
1.311 ms
1.223 ms
1.427 ms
1.273 ms
1.376 ms
1.122 ms
1.378 ms
1.154 ms
1.134 ms
1.352 ms
1.325 ms
1.218 ms
1.171 ms
1.388 ms
1.382 ms
1.331 ms
1.389 ms
1.246 ms
1.154 ms
1.391 ms
1.318 ms
1.457 ms
1.128 ms
1.488 ms
1.148 ms
1.144 ms
1.363 ms
1.386 ms
1.141 ms
1.174 ms
7.206 ms
6.203 ms
1.413 ms
1.389 ms
1.344 ms
1.155 ms
1.163 ms
7.843 ms
1.183 ms
1.449 ms
1.357 ms
1.398 ms
1.348 ms
1.495 ms
1.167 ms
1.207 ms
16.223 ms
1.158 ms
1.201 ms
1.163 ms
5.808 ms
1.459 ms
1.201 ms
1.154 ms
1.424 ms
1.185 ms
1.424 ms
1.739 ms
3.549 ms
1.379 ms
1.418 ms
1.214 ms
1.155 ms
1.390 ms
1.427 ms
1.137 ms
1.401 ms
1.183 ms
1.163 ms
1.230 ms
1.392 ms
3.219 ms
1.385 ms
1.393 ms
1.365 ms
1.358 ms
8.880 ms
5.856 ms
9.961 ms
1.389 ms
20.122 ms
1.433 ms
5.573 ms
1.175 ms
1.194 ms
1.185 ms
1.195 ms
1.206 ms
1.177 ms
1.365 ms
1.359 ms
1.226 ms
1.149 ms
1.401 ms
1.382 ms
12.251 ms
1.263 ms
1.261 ms
1.356 ms
19.053 ms
1.336 ms
1.419 ms
1.160 ms
1.207 ms
1.349 ms
2.570 ms
1.347 ms
1.362 ms
1.247 ms
1.328 ms
1.374 ms
1.347 ms
1.486 ms
1.151 ms
2.243 ms
1.396 ms
1.726 ms
1.544 ms
1.403 ms
1.177 ms
1.182 ms
1.186 ms
1.151 ms
1.693 ms
1.373 ms
1.169 ms
15.816 ms
1.194 ms
1.162 ms
16.751 ms
1.381 ms
1.388 ms
1.347 ms
1.375 ms
1.352 ms
1.338 ms
1.366 ms
1.365 ms
3.714 ms
1.390 ms
1.384 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 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.778 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.223 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.270 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.785 msReply RTT ASN unavailable
  4. TTL 4 Probe hop2.275 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop4.202 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.024 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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.450 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.287 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.255 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.555 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.995 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.017 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.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.480 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.163 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop61.111 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.600 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination8.451 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.618 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.232 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.870 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.944 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.296 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.542 msReply RTT AS13335 · Cloudflare
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.270 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.594 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.330 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.351 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.528 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.547 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop3.147 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.222 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.887 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.623 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.375 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.181 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.230 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.887 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.189 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.137 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination3.315 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.113 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
After

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.250 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.363 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.629 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.141 msAS8002 · Stealth0.160 msAS8002 · StealthSame responder
20.196 msAS8002 · Stealth0.199 msAS8002 · StealthSame responder
3Not recorded1.480 msAS13335 · CloudflareNot 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.140 msAS8002 · Stealth0.163 msAS8002 · StealthSame responder
20.186 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
324.555 msAS13335 · Cloudflare61.111 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.995 msAS13335 · Cloudflare1.600 msAS13335 · CloudflareDifferent responders
61.017 msAS13335 · Cloudflare8.451 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.143 msAS8002 · Stealth0.232 msAS8002 · StealthSame responder
20.183 msAS8002 · Stealth0.195 msAS8002 · StealthSame responder
317.450 msAS13335 · Cloudflare6.870 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
54.287 msAS13335 · Cloudflare1.944 msAS13335 · CloudflareDifferent responders
61.255 msAS13335 · Cloudflare1.296 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.

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.348 msUsual round trip before the event
Last recorded event RTT1.457 msLast successful event recording
Event p95 RTT5.393 ms95th percentile of successful recordings
Change from baseline+0.110 msLast event RTT compared with the baseline
Successful / expected recordings99 / 100Recorded 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