Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-1E47E11E7CEC9832

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

03 Nov 2026 13:00 – 04 Nov 2026 00:49 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.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
6.203 ms
1.398 ms
1.459 ms
1.214 ms
3.219 ms
1.433 ms
1.359 ms
1.336 ms
1.374 ms
1.182 ms
1.381 ms
1.384 ms
1.625 ms
1.377 ms
1.384 ms
1.153 ms
1.372 ms
1.173 ms
14.314 ms
1.431 ms
1.134 ms
17.783 ms
1.359 ms
1.392 ms
1.159 ms
13.267 ms
1.852 ms
7.801 ms
1.382 ms
17.371 ms
1.422 ms
1.168 ms
1.143 ms
8.708 ms
1.385 ms
11.919 ms
16.244 ms
6.932 ms
1.367 ms
5.483 ms
17.131 ms
1.153 ms
1.357 ms
12.781 ms
1.445 ms
15.601 ms
1.180 ms
1.343 ms
9.337 ms
1.456 ms
1.432 ms
1.411 ms
10.242 ms
14.926 ms
1.178 ms
1.410 ms
14.925 ms
1.897 ms
18.548 ms
3.565 ms
1.395 ms
4.267 ms
16.775 ms
1.512 ms
1.184 ms
1.389 ms
12.876 ms
1.179 ms
8.293 ms
11.251 ms
1.129 ms
1.357 ms
1.353 ms
1.392 ms
1.402 ms
1.369 ms
1.403 ms
1.150 ms
1.404 ms
17.848 ms
1.205 ms
1.762 ms
1.251 ms
1.364 ms
14.271 ms
1.379 ms
1.164 ms
1.665 ms
1.409 ms
1.195 ms
1.371 ms
1.176 ms
1.378 ms
1.187 ms
1.391 ms
1.150 ms
1.717 ms
1.557 ms
1.173 ms
1.374 ms
1.360 ms
1.357 ms
1.355 ms
1.208 ms
1.223 ms
1.208 ms
1.132 ms
11.637 ms
5.246 ms
1.200 ms
1.162 ms
1.351 ms
3.282 ms
19.432 ms
1.396 ms
14.199 ms
1.193 ms
1.180 ms
1.170 ms
1.151 ms
1.157 ms
1.640 ms
1.205 ms
1.428 ms
1.360 ms
1.314 ms
1.149 ms
1.375 ms
1.131 ms
1.411 ms
1.393 ms
14.251 ms
1.216 ms
1.422 ms
1.128 ms
4.339 ms
1.350 ms
1.374 ms
1.307 ms
1.465 ms
1.456 ms
1.153 ms
1.179 ms
1.239 ms
1.199 ms
10.178 ms
1.433 ms
1.253 ms
1.347 ms
1.377 ms
1.152 ms
1.173 ms
1.361 ms
1.329 ms
1.129 ms
1.388 ms
1.393 ms
1.356 ms
1.177 ms
1.426 ms
1.158 ms
1.158 ms
1.197 ms
1.194 ms
1.153 ms
1.207 ms
1.179 ms
1.189 ms
1.220 ms
1.401 ms
17.621 ms
1.168 ms
1.180 ms
1.224 ms
2.160 ms
1.339 ms
1.472 ms
1.136 ms
1.361 ms
1.151 ms
1.345 ms
1.150 ms
1.363 ms
1.172 ms
1.358 ms
1.234 ms
1.472 ms
1.451 ms
1.206 ms
1.531 ms
1.363 ms
1.150 ms
1.190 ms
1.373 ms
1.406 ms
1.363 ms
1.358 ms
1.353 ms
1.178 ms
1.142 ms
10.550 ms
1.305 ms
1.374 ms
1.400 ms
1.204 ms
1.145 ms
1.397 ms
1.371 ms
1.128 ms
1.241 ms
1.370 ms
1.405 ms
1.377 ms
1.331 ms
1.409 ms
1.139 ms
1.499 ms
1.389 ms
4.831 ms
1.155 ms
1.165 ms
5.212 ms
1.183 ms
1.340 ms
1.132 ms
1.350 ms
1.404 ms
1.354 ms
1.342 ms
1.353 ms
1.446 ms
14.826 ms
1.203 ms
1.366 ms
1.214 ms
1.360 ms
1.194 ms
1.164 ms
Network path / recorded observations

Network path observations.

18 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.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.240 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.165 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.463 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.455 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.175 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.867 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.300 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.261 msReply RTT AS13335 · Cloudflare
Before

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
Before

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
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.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.722 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.166 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.230 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.189 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.910 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.993 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.116 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.445 msReply RTT ASN unavailable
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.244 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.767 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.514 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.428 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.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.213 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.706 msReply RTT ASN unavailable
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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.094 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.901 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.252 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.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.928 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.200 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.532 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.426 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.250 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop26.424 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.177 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop17.007 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop9.358 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.546 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.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.077 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.142 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.692 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.909 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.192 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.129 msAS8002 · Stealth0.117 msAS8002 · StealthSame responder
20.192 msAS8002 · Stealth0.185 msAS8002 · StealthSame responder
31.528 msAS13335 · Cloudflare1.722 msAS13335 · CloudflareSame responder
41.547 msAS13335 · CloudflareNot recordedNot established
53.147 msAS13335 · CloudflareNot recordedNot established
61.222 msAS13335 · CloudflareNot recordedNot established
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.133 msAS8002 · Stealth0.138 msAS8002 · StealthSame responder
20.179 msAS8002 · Stealth0.213 msAS8002 · StealthSame responder
31.455 msAS13335 · Cloudflare1.706 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.146 msAS8002 · Stealth0.166 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.230 msAS8002 · StealthSame responder
30.887 msAS13335 · Cloudflare1.189 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.623 msAS13335 · Cloudflare1.910 msAS13335 · CloudflareDifferent responders
61.375 msAS13335 · CloudflareNo replyNot established
7Not recorded1.993 msAS13335 · CloudflareNot 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.348 msUsual round trip before the event
Last recorded event RTT1.170 msLast successful event recording
Event p95 RTT17.556 ms95th percentile of successful recordings
Change from baseline-0.178 msLast event RTT compared with the baseline
Successful / expected recordings1172 / 1180Recorded 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