Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-003102F655F81D22

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

04 Nov 2026 13:00 – 04 Nov 2026 22: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.149 ms
1.140 ms
1.154 ms
1.225 ms
1.209 ms
1.370 ms
1.223 ms
1.450 ms
1.397 ms
12.998 ms
1.526 ms
1.144 ms
1.188 ms
1.244 ms
1.357 ms
1.176 ms
1.432 ms
1.284 ms
1.369 ms
1.363 ms
1.408 ms
1.380 ms
1.416 ms
1.152 ms
1.155 ms
1.247 ms
1.156 ms
1.140 ms
1.558 ms
1.400 ms
1.129 ms
1.145 ms
1.150 ms
1.190 ms
1.408 ms
1.178 ms
1.146 ms
1.155 ms
1.384 ms
1.162 ms
1.126 ms
1.141 ms
1.277 ms
1.157 ms
1.350 ms
3.958 ms
1.141 ms
1.168 ms
1.130 ms
1.447 ms
1.148 ms
1.165 ms
1.139 ms
1.409 ms
1.146 ms
1.367 ms
1.388 ms
1.342 ms
1.390 ms
4.223 ms
1.167 ms
1.427 ms
1.165 ms
1.376 ms
1.155 ms
1.209 ms
1.364 ms
1.348 ms
1.355 ms
1.607 ms
1.372 ms
1.221 ms
1.434 ms
1.163 ms
1.149 ms
1.384 ms
1.153 ms
1.355 ms
1.380 ms
1.359 ms
4.570 ms
1.356 ms
1.165 ms
1.162 ms
1.325 ms
1.245 ms
2.176 ms
1.396 ms
1.350 ms
1.128 ms
1.354 ms
1.179 ms
1.189 ms
1.347 ms
1.372 ms
1.425 ms
1.202 ms
1.374 ms
1.182 ms
1.141 ms
1.126 ms
1.147 ms
1.168 ms
1.169 ms
1.164 ms
1.545 ms
1.353 ms
1.356 ms
1.128 ms
1.149 ms
1.362 ms
1.223 ms
1.252 ms
1.168 ms
1.390 ms
1.393 ms
1.339 ms
1.139 ms
1.120 ms
1.124 ms
1.131 ms
1.376 ms
1.446 ms
1.189 ms
1.134 ms
1.363 ms
3.899 ms
1.727 ms
1.423 ms
3.238 ms
1.136 ms
1.430 ms
1.378 ms
1.164 ms
1.148 ms
1.172 ms
1.198 ms
1.492 ms
1.217 ms
1.383 ms
14.617 ms
17.474 ms
18.096 ms
20.747 ms
16.707 ms
16.265 ms
1.388 ms
11.350 ms
14.064 ms
9.164 ms
12.062 ms
15.896 ms
17.068 ms
11.504 ms
13.985 ms
17.724 ms
11.437 ms
4.365 ms
18.138 ms
11.390 ms
1.601 ms
10.802 ms
14.293 ms
6.164 ms
1.221 ms
19.121 ms
15.703 ms
13.703 ms
16.480 ms
1.238 ms
11.959 ms
1.543 ms
1.169 ms
1.476 ms
10.438 ms
1.125 ms
1.136 ms
17.520 ms
4.272 ms
19.689 ms
17.193 ms
18.597 ms
16.092 ms
16.206 ms
19.813 ms
11.619 ms
20.362 ms
18.381 ms
16.544 ms
18.758 ms
15.661 ms
10.107 ms
15.379 ms
19.946 ms
20.101 ms
12.683 ms
17.295 ms
17.419 ms
1.182 ms
4.750 ms
16.645 ms
6.658 ms
12.872 ms
16.405 ms
12.078 ms
14.757 ms
1.397 ms
1.192 ms
1.357 ms
16.700 ms
18.741 ms
15.376 ms
1.165 ms
5.034 ms
1.175 ms
1.399 ms
6.253 ms
18.375 ms
1.376 ms
1.424 ms
1.169 ms
1.242 ms
1.145 ms
1.209 ms
2.982 ms
1.407 ms
1.459 ms
1.383 ms
1.315 ms
1.176 ms
18.610 ms
1.191 ms
1.189 ms
1.252 ms
1.392 ms
1.217 ms
1.152 ms
2.068 ms
1.399 ms
1.364 ms
1.188 ms
1.401 ms
1.613 ms
1.411 ms
1.168 ms
1.409 ms
1.392 ms
1.386 ms
5.105 ms
1.357 ms
1.156 ms
1.190 ms
1.193 ms
1.128 ms
1.428 ms
1.393 ms
1.201 ms
1.212 ms
1.299 ms
1.414 ms
1.193 ms
1.182 ms
1.177 ms
1.170 ms
1.459 ms
1.475 ms
1.175 ms
1.365 ms
1.359 ms
1.232 ms
2.962 ms
1.376 ms
1.384 ms
1.333 ms
1.483 ms
1.385 ms
1.137 ms
1.209 ms
1.372 ms
8.075 ms
1.206 ms
1.365 ms
1.330 ms
1.359 ms
1.372 ms
1.151 ms
2.226 ms
1.132 ms
1.171 ms
1.341 ms
1.148 ms
1.194 ms
1.156 ms
1.191 ms
1.169 ms
1.178 ms
1.159 ms
1.387 ms
1.322 ms
1.371 ms
1.346 ms
1.157 ms
1.414 ms
1.389 ms
1.357 ms
1.352 ms
1.346 ms
1.147 ms
1.173 ms
1.175 ms
1.218 ms
1.165 ms
1.361 ms
1.130 ms
1.622 ms
1.409 ms
1.163 ms
1.123 ms
1.152 ms
1.149 ms
1.381 ms
1.184 ms
1.152 ms
1.386 ms
1.204 ms
1.233 ms
1.392 ms
1.201 ms
1.342 ms
1.157 ms
1.375 ms
1.349 ms
1.151 ms
1.144 ms
1.155 ms
1.429 ms
1.154 ms
1.359 ms
1.135 ms
1.372 ms
1.149 ms
1.393 ms
1.315 ms
1.204 ms
1.162 ms
1.211 ms
1.355 ms
1.398 ms
1.130 ms
1.331 ms
1.142 ms
1.309 ms
1.177 ms
1.377 ms
1.366 ms
1.151 ms
1.370 ms
1.375 ms
1.168 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.983 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.632 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.876 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.311 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.118 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.857 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.162 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.312 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.494 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.734 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.254 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.245 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.193 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.088 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.069 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.744 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.108 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.911 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.652 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.490 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.422 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.176 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.117 msReply RTT AS13335 · Cloudflare
During

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.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop78.042 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.777 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.340 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
After

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.177 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.381 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.161 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.602 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.155 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 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.396 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.238 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.182 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.244 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop11.825 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.390 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop58.055 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.214 msReply RTT AS13335 · Cloudflare
After

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.268 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.279 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.465 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.386 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.118 msAS8002 · Stealth0.133 msAS8002 · StealthSame responder
20.180 msAS8002 · Stealth0.176 msAS8002 · StealthSame responder
34.857 msAS13335 · Cloudflare5.117 msAS13335 · CloudflareSame 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.162 msAS8002 · Stealth0.170 msAS8002 · StealthSame responder
20.180 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
31.312 msAS13335 · Cloudflare1.744 msSame responder
4No replyNo replyNot established
52.494 msAS13335 · Cloudflare1.108 msAS13335 · CloudflareDifferent responders
61.734 msAS13335 · Cloudflare0.911 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.159 msAS8002 · Stealth0.153 msAS8002 · StealthSame responder
20.254 msAS8002 · Stealth0.184 msAS8002 · StealthSame responder
31.245 ms16.652 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.193 msAS13335 · Cloudflare1.490 msAS13335 · CloudflareDifferent responders
61.088 msAS13335 · Cloudflare1.422 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.347 msUsual round trip before the event
Last recorded event RTT1.364 msLast successful event recording
Event p95 RTT19.685 ms95th percentile of successful recordings
Change from baseline+0.017 msLast event RTT compared with the baseline
Successful / expected recordings936 / 960Recorded 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