Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-409BC33AF1B07A5B

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

05 Nov 2026 12:25 – 05 Nov 2026 23: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.360 ms
1.363 ms
1.341 ms
1.358 ms
1.150 ms
1.371 ms
1.108 ms
1.215 ms
1.154 ms
1.179 ms
1.345 ms
1.373 ms
1.204 ms
1.216 ms
1.412 ms
1.146 ms
1.122 ms
1.466 ms
1.150 ms
1.348 ms
1.139 ms
1.156 ms
1.359 ms
1.340 ms
1.138 ms
1.372 ms
1.358 ms
1.205 ms
1.130 ms
1.325 ms
1.214 ms
1.142 ms
1.146 ms
1.380 ms
1.401 ms
1.372 ms
1.376 ms
1.384 ms
1.114 ms
1.180 ms
1.150 ms
1.373 ms
1.136 ms
1.430 ms
1.128 ms
1.249 ms
1.140 ms
1.192 ms
1.339 ms
1.109 ms
1.336 ms
1.329 ms
1.170 ms
1.450 ms
1.418 ms
1.153 ms
1.180 ms
1.386 ms
1.340 ms
1.121 ms
1.399 ms
1.168 ms
1.345 ms
1.191 ms
1.318 ms
1.335 ms
1.163 ms
1.337 ms
1.368 ms
1.151 ms
1.355 ms
1.134 ms
1.344 ms
1.361 ms
1.440 ms
1.480 ms
1.140 ms
1.182 ms
1.366 ms
1.140 ms
1.174 ms
1.331 ms
1.429 ms
1.175 ms
1.133 ms
1.163 ms
1.353 ms
1.501 ms
1.162 ms
1.355 ms
1.391 ms
1.218 ms
1.330 ms
1.372 ms
1.338 ms
1.457 ms
1.377 ms
1.347 ms
1.362 ms
1.345 ms
1.349 ms
1.336 ms
1.175 ms
1.372 ms
1.143 ms
1.694 ms
1.382 ms
1.369 ms
1.365 ms
1.130 ms
1.384 ms
1.355 ms
1.364 ms
1.142 ms
1.139 ms
1.153 ms
1.131 ms
1.342 ms
1.355 ms
1.224 ms
1.490 ms
1.371 ms
1.388 ms
1.350 ms
1.310 ms
6.928 ms
1.425 ms
1.255 ms
18.596 ms
1.169 ms
1.178 ms
1.216 ms
13.821 ms
1.130 ms
1.338 ms
1.163 ms
13.945 ms
4.898 ms
1.177 ms
2.857 ms
1.161 ms
17.104 ms
20.103 ms
1.848 ms
10.781 ms
16.711 ms
1.136 ms
1.172 ms
18.863 ms
5.243 ms
17.342 ms
17.415 ms
11.482 ms
19.398 ms
14.931 ms
11.676 ms
1.169 ms
12.111 ms
19.715 ms
18.116 ms
13.090 ms
8.043 ms
2.399 ms
8.845 ms
3.595 ms
1.373 ms
1.398 ms
1.180 ms
12.430 ms
7.123 ms
2.840 ms
18.050 ms
2.763 ms
16.990 ms
18.576 ms
6.310 ms
16.289 ms
19.224 ms
12.736 ms
20.403 ms
15.135 ms
16.740 ms
15.008 ms
9.832 ms
19.702 ms
2.298 ms
16.182 ms
17.616 ms
1.157 ms
13.212 ms
18.765 ms
15.321 ms
4.099 ms
5.563 ms
1.770 ms
4.557 ms
1.277 ms
17.538 ms
8.491 ms
1.375 ms
1.135 ms
7.255 ms
1.419 ms
1.124 ms
14.472 ms
1.158 ms
1.152 ms
17.172 ms
4.063 ms
1.373 ms
1.439 ms
1.377 ms
1.180 ms
1.176 ms
1.376 ms
1.157 ms
1.394 ms
8.293 ms
1.153 ms
1.138 ms
1.480 ms
1.357 ms
1.175 ms
1.190 ms
1.158 ms
1.397 ms
3.320 ms
1.365 ms
1.179 ms
5.218 ms
1.578 ms
1.413 ms
1.156 ms
1.372 ms
1.149 ms
1.345 ms
1.147 ms
1.362 ms
1.520 ms
1.428 ms
1.433 ms
12.147 ms
1.422 ms
1.345 ms
1.497 ms
1.389 ms
1.353 ms
1.398 ms
1.137 ms
1.137 ms
1.185 ms
1.399 ms
1.150 ms
1.135 ms
1.167 ms
1.218 ms
1.421 ms
1.368 ms
1.171 ms
1.422 ms
1.115 ms
1.393 ms
1.146 ms
1.172 ms
1.398 ms
1.370 ms
1.168 ms
1.186 ms
1.365 ms
1.327 ms
1.362 ms
1.332 ms
1.247 ms
1.360 ms
1.379 ms
1.342 ms
1.156 ms
1.161 ms
1.417 ms
3.385 ms
1.371 ms
1.310 ms
1.715 ms
1.365 ms
1.138 ms
1.343 ms
1.165 ms
1.139 ms
1.365 ms
1.141 ms
1.375 ms
1.357 ms
1.402 ms
7.654 ms
1.409 ms
1.372 ms
1.306 ms
1.151 ms
1.141 ms
1.395 ms
1.331 ms
1.339 ms
1.146 ms
1.383 ms
1.450 ms
1.366 ms
1.151 ms
19.933 ms
1.358 ms
1.162 ms
1.349 ms
1.374 ms
1.137 ms
1.378 ms
1.414 ms
1.285 ms
1.429 ms
1.133 ms
1.139 ms
1.328 ms
1.365 ms
1.182 ms
1.139 ms
1.171 ms
1.147 ms
1.161 ms
1.574 ms
1.148 ms
1.365 ms
1.162 ms
1.146 ms
1.170 ms
1.362 ms
1.191 ms
1.132 ms
10.152 ms
1.131 ms
1.489 ms
1.459 ms
1.154 ms
1.438 ms
1.348 ms
1.394 ms
1.155 ms
1.416 ms
1.139 ms
1.143 ms
1.170 ms
1.329 ms
1.332 ms
1.137 ms
1.136 ms
1.346 ms
10.976 ms
1.137 ms
1.149 ms
1.480 ms
1.151 ms
1.368 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.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.643 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.138 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.095 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.243 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.188 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.170 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.224 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.192 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.665 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.268 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.245 msReply RTT AS13335 · Cloudflare
Before

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.284 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.408 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.509 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.482 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.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.446 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.194 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.236 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop8.850 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.372 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination17.648 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.164 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.227 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.214 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.242 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.716 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.353 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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.259 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.486 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.346 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.172 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.424 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.670 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.216 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.095 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.011 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.248 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.989 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.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop1.719 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop4.049 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination10.040 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.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.176 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.378 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.380 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.188 msAS8002 · Stealth0.146 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.187 msAS8002 · StealthSame responder
31.170 msAS13335 · Cloudflare4.446 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.158 msAS8002 · Stealth0.194 msAS8002 · StealthSame responder
20.284 msAS8002 · Stealth0.236 msAS8002 · StealthSame responder
37.408 ms8.850 msSame responder
4No replyNo replyNot established
51.509 msAS13335 · Cloudflare1.372 msAS13335 · CloudflareDifferent responders
61.482 msAS13335 · Cloudflare17.648 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.369 msUsual round trip before the event
Last recorded event RTT1.428 msLast successful event recording
Event p95 RTT19.137 ms95th percentile of successful recordings
Change from baseline+0.059 msLast event RTT compared with the baseline
Successful / expected recordings1103 / 1120Recorded 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