Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-DE30BD4E1580D3FF

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

06 Nov 2026 00:50 – 06 Nov 2026 03:44 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.450 ms
1.182 ms
1.367 ms
1.132 ms
1.484 ms
1.164 ms
1.168 ms
1.185 ms
1.342 ms
1.414 ms
1.368 ms
1.397 ms
1.484 ms
1.165 ms
1.139 ms
1.149 ms
1.165 ms
1.335 ms
1.358 ms
1.319 ms
1.218 ms
1.160 ms
1.175 ms
1.181 ms
1.365 ms
1.897 ms
1.139 ms
1.148 ms
1.381 ms
1.422 ms
1.158 ms
1.168 ms
11.465 ms
1.147 ms
1.202 ms
1.137 ms
1.339 ms
1.318 ms
1.190 ms
1.285 ms
1.392 ms
1.499 ms
1.200 ms
2.854 ms
1.147 ms
1.393 ms
1.169 ms
1.327 ms
3.796 ms
1.382 ms
1.156 ms
1.156 ms
1.135 ms
1.419 ms
1.400 ms
1.698 ms
1.383 ms
1.424 ms
1.188 ms
1.301 ms
1.362 ms
1.369 ms
1.258 ms
1.331 ms
18.798 ms
1.372 ms
1.173 ms
1.368 ms
1.328 ms
1.359 ms
1.203 ms
1.357 ms
1.375 ms
1.462 ms
1.269 ms
1.162 ms
1.388 ms
1.139 ms
1.140 ms
1.350 ms
1.210 ms
1.165 ms
1.112 ms
1.146 ms
1.393 ms
1.388 ms
5.541 ms
1.367 ms
1.352 ms
1.376 ms
1.401 ms
1.600 ms
3.409 ms
1.365 ms
1.215 ms
1.371 ms
1.358 ms
1.159 ms
1.340 ms
1.260 ms
1.155 ms
1.150 ms
12.759 ms
1.509 ms
1.427 ms
1.363 ms
1.348 ms
1.151 ms
1.375 ms
1.163 ms
1.385 ms
1.169 ms
1.437 ms
1.198 ms
1.337 ms
1.173 ms
1.370 ms
1.361 ms
1.178 ms
1.157 ms
1.148 ms
1.405 ms
1.213 ms
1.359 ms
10.781 ms
1.364 ms
1.351 ms
1.153 ms
1.158 ms
1.149 ms
10.775 ms
1.191 ms
20.043 ms
1.363 ms
1.177 ms
1.154 ms
1.159 ms
1.352 ms
1.371 ms
2.049 ms
1.129 ms
6.961 ms
1.587 ms
1.168 ms
1.336 ms
1.386 ms
1.182 ms
1.296 ms
1.344 ms
15.130 ms
18.428 ms
1.205 ms
1.390 ms
1.368 ms
1.159 ms
1.156 ms
1.226 ms
3.334 ms
1.385 ms
21.254 ms
2.181 ms
1.340 ms
1.213 ms
1.380 ms
1.545 ms
1.375 ms
1.407 ms
1.892 ms
1.386 ms
1.160 ms
1.365 ms
2.114 ms
1.181 ms
2.318 ms
1.146 ms
1.168 ms
1.152 ms
17.728 ms
17.037 ms
1.931 ms
1.385 ms
1.135 ms
1.170 ms
1.350 ms
1.393 ms
1.136 ms
1.353 ms
1.155 ms
1.141 ms
17.491 ms
18.335 ms
1.200 ms
1.201 ms
1.366 ms
16.440 ms
1.381 ms
1.390 ms
4.065 ms
1.198 ms
1.361 ms
1.405 ms
1.178 ms
1.583 ms
1.148 ms
1.385 ms
1.389 ms
1.159 ms
1.341 ms
1.151 ms
1.130 ms
1.421 ms
1.139 ms
1.160 ms
1.151 ms
1.177 ms
1.149 ms
1.258 ms
1.354 ms
1.186 ms
1.508 ms
1.132 ms
1.389 ms
1.235 ms
1.182 ms
1.137 ms
1.376 ms
1.361 ms
1.165 ms
1.325 ms
1.181 ms
1.374 ms
1.424 ms
1.135 ms
1.420 ms
1.142 ms
1.379 ms
1.138 ms
1.130 ms
1.372 ms
1.364 ms
1.164 ms
1.155 ms
1.449 ms
1.354 ms
1.332 ms
3.866 ms
1.404 ms
1.332 ms
1.424 ms
1.321 ms
1.381 ms
1.201 ms
1.342 ms
1.177 ms
1.347 ms
1.380 ms
1.335 ms
1.342 ms
1.544 ms
1.164 ms
1.156 ms
1.159 ms
1.357 ms
1.356 ms
1.364 ms
1.406 ms
1.337 ms
1.168 ms
1.141 ms
1.140 ms
1.129 ms
1.344 ms
1.333 ms
1.151 ms
1.153 ms
1.123 ms
1.420 ms
1.388 ms
1.353 ms
1.375 ms
1.363 ms
1.124 ms
1.181 ms
1.367 ms
1.339 ms
1.116 ms
1.153 ms
1.234 ms
1.358 ms
1.358 ms
1.355 ms
1.136 ms
1.350 ms
5.097 ms
1.149 ms
1.376 ms
1.196 ms
1.340 ms
1.145 ms
1.188 ms
1.380 ms
1.339 ms
1.357 ms
1.155 ms
1.201 ms
1.189 ms
1.158 ms
1.462 ms
1.362 ms
1.526 ms
1.324 ms
1.120 ms
1.349 ms
1.527 ms
1.161 ms
1.419 ms
1.614 ms
1.145 ms
1.126 ms
1.135 ms
1.158 ms
1.153 ms
1.384 ms
1.375 ms
1.155 ms
1.157 ms
1.317 ms
1.357 ms
1.176 ms
1.388 ms
1.415 ms
1.129 ms
1.311 ms
1.218 ms
1.144 ms
1.366 ms
1.181 ms
1.163 ms
1.354 ms
19.309 ms
16.828 ms
1.438 ms
1.388 ms
1.151 ms
1.144 ms
1.578 ms
1.343 ms
1.346 ms
1.153 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.748 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.611 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.526 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.791 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.339 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.050 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
Before

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.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 hop2.137 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.588 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.389 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.279 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 hop6.558 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.425 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.227 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop1.782 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop29.636 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.190 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.265 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.880 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.223 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.156 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.514 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.173 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop68.239 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.525 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.506 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.171 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.236 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.829 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.203 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.247 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop60.332 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.219 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.784 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.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.298 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.204 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.489 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.404 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.656 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.123 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.458 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.397 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop21.390 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.425 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.224 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.447 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.025 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.768 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.418 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.179 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 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.360 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination16.299 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.117 msAS8002 · Stealth0.227 msAS8002 · StealthSame responder
20.192 msAS8002 · Stealth1.782 msAS8002 · StealthSame responder
3Not recorded29.636 msNot 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.611 msAS8002 · Stealth0.190 msAS8002 · StealthSame responder
20.526 msAS8002 · Stealth0.265 msAS8002 · StealthSame responder
30.791 ms10.880 msSame responder
4No replyNo replyNot established
54.339 msAS13335 · Cloudflare2.223 msAS13335 · CloudflareDifferent responders
6No reply1.156 msAS13335 · CloudflareNot established
72.050 msAS13335 · CloudflareNot recordedNot 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.389 msAS8002 · Stealth0.173 msAS8002 · StealthSame responder
20.279 msAS8002 · Stealth0.185 msAS8002 · StealthSame responder
3No reply68.239 msAS13335 · CloudflareNot established
4No replyNo replyNot established
56.558 msAS13335 · Cloudflare1.525 msAS13335 · CloudflareDifferent responders
61.425 msAS13335 · Cloudflare1.506 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.366 msUsual round trip before the event
Last recorded event RTT1.181 msLast successful event recording
Event p95 RTT17.286 ms95th percentile of successful recordings
Change from baseline-0.185 msLast event RTT compared with the baseline
Successful / expected recordings110 / 110Recorded 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