Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-6E73EAF655856774

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. 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

29 Oct 2026 12:35 – 29 Oct 2026 22: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.424 ms
1.431 ms
4.050 ms
1.198 ms
1.228 ms
1.199 ms
1.219 ms
1.425 ms
1.220 ms
1.381 ms
1.412 ms
1.408 ms
1.226 ms
1.410 ms
2.157 ms
1.422 ms
6.323 ms
1.179 ms
1.240 ms
1.199 ms
1.442 ms
1.416 ms
1.427 ms
1.185 ms
1.413 ms
1.431 ms
1.184 ms
1.201 ms
1.408 ms
1.167 ms
1.213 ms
1.177 ms
1.434 ms
1.264 ms
1.373 ms
19.536 ms
1.491 ms
1.159 ms
1.379 ms
1.368 ms
1.390 ms
1.169 ms
1.453 ms
1.190 ms
1.384 ms
1.527 ms
1.410 ms
1.514 ms
1.378 ms
1.248 ms
1.527 ms
1.234 ms
1.214 ms
1.202 ms
1.290 ms
1.444 ms
1.423 ms
1.249 ms
1.199 ms
1.186 ms
1.188 ms
1.802 ms
1.181 ms
1.419 ms
16.250 ms
8.388 ms
1.435 ms
1.638 ms
1.436 ms
1.208 ms
3.463 ms
1.653 ms
1.169 ms
1.200 ms
1.381 ms
1.388 ms
1.188 ms
1.443 ms
1.430 ms
1.252 ms
1.425 ms
18.236 ms
1.538 ms
1.460 ms
1.423 ms
1.402 ms
1.390 ms
1.399 ms
1.167 ms
1.468 ms
1.152 ms
1.400 ms
1.406 ms
1.392 ms
1.189 ms
1.380 ms
1.199 ms
1.215 ms
1.224 ms
1.221 ms
1.404 ms
1.590 ms
2.775 ms
1.386 ms
13.833 ms
16.889 ms
1.193 ms
17.859 ms
18.472 ms
4.330 ms
1.189 ms
1.444 ms
1.207 ms
1.416 ms
1.380 ms
1.353 ms
1.375 ms
1.409 ms
1.369 ms
1.372 ms
1.423 ms
1.238 ms
1.411 ms
1.375 ms
1.218 ms
2.908 ms
1.485 ms
1.395 ms
1.404 ms
17.158 ms
15.548 ms
14.353 ms
1.222 ms
1.394 ms
1.424 ms
1.432 ms
1.479 ms
1.453 ms
19.229 ms
17.357 ms
1.339 ms
17.963 ms
4.281 ms
1.181 ms
1.439 ms
16.300 ms
1.377 ms
1.169 ms
5.643 ms
19.117 ms
1.394 ms
1.166 ms
5.299 ms
1.439 ms
1.265 ms
1.160 ms
4.646 ms
1.400 ms
1.220 ms
1.232 ms
1.443 ms
1.195 ms
1.187 ms
1.377 ms
1.162 ms
1.602 ms
1.204 ms
1.193 ms
1.435 ms
10.003 ms
1.420 ms
1.161 ms
1.188 ms
1.376 ms
1.179 ms
2.055 ms
1.160 ms
1.178 ms
15.971 ms
1.219 ms
1.163 ms
18.610 ms
8.124 ms
1.401 ms
5.873 ms
6.797 ms
1.172 ms
1.200 ms
2.115 ms
1.734 ms
1.385 ms
6.033 ms
1.170 ms
1.160 ms
1.414 ms
1.401 ms
1.405 ms
1.186 ms
1.399 ms
1.437 ms
1.390 ms
1.411 ms
16.522 ms
1.437 ms
8.404 ms
16.063 ms
1.205 ms
1.195 ms
1.446 ms
3.680 ms
1.405 ms
1.168 ms
1.393 ms
1.405 ms
1.415 ms
1.394 ms
1.397 ms
1.161 ms
1.172 ms
1.181 ms
1.242 ms
12.141 ms
11.385 ms
1.402 ms
1.416 ms
15.613 ms
1.443 ms
1.399 ms
1.418 ms
1.530 ms
1.459 ms
1.159 ms
3.252 ms
2.946 ms
1.218 ms
1.220 ms
1.197 ms
1.201 ms
1.407 ms
1.172 ms
1.205 ms
1.447 ms
17.103 ms
1.180 ms
1.397 ms
1.178 ms
1.437 ms
1.430 ms
1.375 ms
18.510 ms
1.505 ms
1.191 ms
1.481 ms
1.406 ms
1.208 ms
1.378 ms
1.414 ms
1.431 ms
1.398 ms
1.196 ms
1.216 ms
1.417 ms
1.225 ms
1.407 ms
1.435 ms
1.194 ms
1.425 ms
1.423 ms
1.165 ms
1.408 ms
1.146 ms
1.232 ms
1.184 ms
1.503 ms
1.521 ms
1.155 ms
1.468 ms
1.388 ms
1.467 ms
1.176 ms
1.173 ms
1.354 ms
1.399 ms
1.372 ms
1.194 ms
1.413 ms
1.183 ms
1.378 ms
1.334 ms
1.352 ms
1.266 ms
1.200 ms
1.385 ms
1.383 ms
1.183 ms
1.168 ms
1.281 ms
1.436 ms
1.390 ms
1.620 ms
1.392 ms
1.415 ms
1.157 ms
1.372 ms
2.268 ms
1.231 ms
1.577 ms
1.192 ms
1.359 ms
1.189 ms
1.450 ms
5.331 ms
1.188 ms
1.385 ms
1.389 ms
1.394 ms
1.154 ms
1.372 ms
1.124 ms
1.399 ms
1.399 ms
1.199 ms
1.426 ms
1.162 ms
1.468 ms
1.202 ms
1.205 ms
1.148 ms
1.392 ms
1.486 ms
1.397 ms
1.158 ms
1.157 ms
1.133 ms
1.370 ms
1.183 ms
1.203 ms
1.178 ms
1.146 ms
1.216 ms
1.378 ms
1.397 ms
1.411 ms
1.427 ms
1.262 ms
1.192 ms
1.358 ms
1.445 ms
1.161 ms
1.360 ms
1.170 ms
1.159 ms
1.406 ms
1.174 ms
1.222 ms
1.403 ms
1.292 ms
1.433 ms
1.200 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.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.638 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.253 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.949 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.981 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.302 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.212 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.195 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.729 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 hop1.286 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.223 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop44.716 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.681 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.601 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.553 msReply RTT AS13335 · Cloudflare
During

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.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.925 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.975 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.151 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.121 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.466 msReply RTT AS13335 · Cloudflare
During

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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop54.496 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.318 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.398 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.029 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop3.418 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.941 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.416 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.057 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop14.112 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.462 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.284 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 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 hop41.430 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.448 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.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.203 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.734 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.247 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop40.491 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.616 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.426 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.638 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.024 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.165 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.395 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.765 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.277 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.398 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.134 msAS8002 · Stealth0.134 msAS8002 · StealthSame responder
20.212 msAS8002 · Stealth0.182 msAS8002 · StealthSame responder
3Not recorded12.553 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.176 msAS8002 · Stealth0.141 msAS8002 · StealthSame responder
20.200 msAS8002 · Stealth0.181 msAS8002 · StealthSame responder
344.716 msAS13335 · Cloudflare24.925 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.681 msAS13335 · Cloudflare3.975 msAS13335 · CloudflareDifferent responders
6No reply1.151 msAS13335 · CloudflareNot established
71.601 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.

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.382 msUsual round trip before the event
Last recorded event RTT1.172 msLast successful event recording
Event p95 RTT16.818 ms95th percentile of successful recordings
Change from baseline-0.210 msLast event RTT compared with the baseline
Successful / expected recordings975 / 980Recorded 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