Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-BBC0CC412A3FBDE1

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

02 Nov 2026 22:55 – 03 Nov 2026 01:24 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.138 ms
1.383 ms
1.186 ms
1.355 ms
1.138 ms
1.404 ms
1.362 ms
1.357 ms
1.376 ms
3.990 ms
1.384 ms
1.528 ms
1.353 ms
1.379 ms
1.118 ms
1.168 ms
1.401 ms
1.226 ms
1.132 ms
1.371 ms
1.350 ms
1.193 ms
1.172 ms
1.173 ms
1.124 ms
1.150 ms
1.389 ms
1.146 ms
1.394 ms
1.238 ms
1.339 ms
1.378 ms
1.346 ms
4.322 ms
1.135 ms
2.292 ms
1.474 ms
1.172 ms
1.164 ms
5.939 ms
1.134 ms
1.232 ms
1.173 ms
1.324 ms
1.402 ms
1.150 ms
1.160 ms
1.356 ms
1.201 ms
1.167 ms
1.180 ms
1.193 ms
1.420 ms
1.205 ms
1.407 ms
1.374 ms
1.365 ms
1.380 ms
1.173 ms
1.222 ms
1.170 ms
1.347 ms
1.396 ms
1.423 ms
1.366 ms
1.147 ms
1.252 ms
1.156 ms
1.156 ms
1.161 ms
1.415 ms
1.371 ms
1.334 ms
1.165 ms
1.432 ms
1.334 ms
1.183 ms
1.365 ms
1.363 ms
1.140 ms
1.394 ms
1.176 ms
1.185 ms
1.238 ms
1.366 ms
1.205 ms
1.139 ms
1.155 ms
1.172 ms
1.156 ms
1.383 ms
1.357 ms
1.471 ms
1.216 ms
1.455 ms
1.374 ms
1.145 ms
1.131 ms
1.139 ms
1.375 ms
6.089 ms
1.152 ms
1.388 ms
1.397 ms
1.342 ms
1.382 ms
1.342 ms
1.427 ms
1.347 ms
1.148 ms
1.180 ms
1.364 ms
1.397 ms
1.179 ms
1.361 ms
1.395 ms
1.339 ms
1.349 ms
1.396 ms
1.354 ms
1.370 ms
6.980 ms
1.142 ms
1.169 ms
1.421 ms
1.329 ms
1.174 ms
1.171 ms
1.149 ms
1.226 ms
1.380 ms
1.350 ms
1.426 ms
1.169 ms
1.373 ms
1.167 ms
1.244 ms
1.402 ms
1.125 ms
8.597 ms
17.983 ms
4.778 ms
19.563 ms
17.463 ms
3.816 ms
1.188 ms
1.183 ms
1.200 ms
1.596 ms
1.374 ms
1.376 ms
1.191 ms
1.347 ms
1.564 ms
3.342 ms
1.370 ms
1.350 ms
1.194 ms
1.347 ms
1.167 ms
1.178 ms
1.164 ms
1.220 ms
1.142 ms
1.437 ms
1.143 ms
1.139 ms
1.388 ms
1.152 ms
1.361 ms
1.164 ms
1.361 ms
1.214 ms
1.159 ms
1.221 ms
1.369 ms
1.171 ms
1.134 ms
1.330 ms
1.215 ms
1.346 ms
1.388 ms
1.185 ms
1.152 ms
1.370 ms
1.172 ms
1.428 ms
1.142 ms
1.168 ms
3.315 ms
1.182 ms
3.745 ms
1.364 ms
1.373 ms
1.198 ms
5.078 ms
1.345 ms
1.359 ms
1.165 ms
1.401 ms
1.370 ms
1.181 ms
1.390 ms
1.382 ms
1.410 ms
1.132 ms
1.367 ms
1.135 ms
1.186 ms
1.366 ms
1.346 ms
1.356 ms
12.939 ms
1.242 ms
1.363 ms
1.156 ms
2.400 ms
1.113 ms
1.334 ms
1.347 ms
1.144 ms
1.156 ms
1.163 ms
1.418 ms
1.383 ms
1.326 ms
1.386 ms
1.153 ms
1.162 ms
1.293 ms
1.350 ms
1.137 ms
1.147 ms
1.291 ms
1.796 ms
3.154 ms
1.371 ms
1.184 ms
1.482 ms
1.852 ms
1.173 ms
8.349 ms
1.215 ms
1.163 ms
1.167 ms
1.390 ms
1.386 ms
10.889 ms
1.166 ms
1.342 ms
1.340 ms
1.389 ms
1.169 ms
1.313 ms
14.762 ms
1.360 ms
1.386 ms
1.341 ms
1.530 ms
1.128 ms
1.383 ms
1.349 ms
1.127 ms
1.177 ms
1.352 ms
1.329 ms
1.157 ms
1.195 ms
1.150 ms
1.169 ms
1.388 ms
1.163 ms
1.149 ms
1.141 ms
1.180 ms
1.453 ms
1.358 ms
1.116 ms
1.165 ms
1.173 ms
1.393 ms
2.514 ms
1.148 ms
1.150 ms
1.166 ms
1.129 ms
1.371 ms
1.167 ms
1.130 ms
1.370 ms
1.262 ms
1.172 ms
1.346 ms
1.160 ms
1.357 ms
1.379 ms
1.373 ms
1.127 ms
1.374 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 replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.539 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.483 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.274 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.159 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.291 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.674 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.679 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.383 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.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.265 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.208 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.384 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.262 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.145 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.720 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.160 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.573 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.205 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.204 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.415 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.220 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.889 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.619 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.823 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.134 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.197 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.160 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.146 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.855 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.824 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.469 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.547 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop23.346 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.253 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop29.164 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.835 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.664 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.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.201 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.629 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.179 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.053 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.902 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.402 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.444 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop60.027 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.149 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop12.488 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.860 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.072 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.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop25.242 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.547 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.928 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.164 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.377 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.153 msAS8002 · Stealth0.205 msAS8002 · StealthSame responder
20.195 msAS8002 · Stealth0.204 msAS8002 · StealthSame responder
31.539 msAS13335 · Cloudflare1.415 msAS13335 · CloudflareSame responder
41.483 msAS13335 · CloudflareNot recordedNot established
52.274 msAS13335 · CloudflareNot recordedNot established
61.159 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.141 msAS8002 · Stealth0.134 msAS8002 · StealthSame responder
20.196 msAS8002 · Stealth0.197 msAS8002 · StealthSame responder
3Not recorded3.160 msAS13335 · CloudflareNot 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.145 msAS8002 · Stealth0.150 msAS8002 · StealthSame responder
20.189 msAS8002 · Stealth0.220 msAS8002 · StealthSame responder
31.720 msAS13335 · Cloudflare3.889 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.160 msAS13335 · Cloudflare1.619 msAS13335 · CloudflareDifferent responders
61.573 msAS13335 · CloudflareNo replyNot established
7Not recorded1.823 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.

Latency anomaly. 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.343 msUsual round trip before the event
Last recorded event RTT1.215 msLast successful event recording
Event p95 RTT9.040 ms95th percentile of successful recordings
Change from baseline-0.128 msLast event RTT compared with the baseline
Successful / expected recordings60 / 60Recorded 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