Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-D2CE306262CD0873

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

29 Oct 2026 01:50 – 29 Oct 2026 04:19 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.338 ms
10.888 ms
4.953 ms
17.661 ms
1.156 ms
2.034 ms
1.400 ms
6.735 ms
1.468 ms
1.197 ms
1.227 ms
11.285 ms
1.186 ms
1.230 ms
1.409 ms
1.216 ms
1.205 ms
1.423 ms
1.245 ms
1.244 ms
1.165 ms
1.427 ms
1.237 ms
1.404 ms
1.178 ms
1.430 ms
1.416 ms
1.408 ms
1.225 ms
1.264 ms
1.419 ms
1.409 ms
1.217 ms
1.237 ms
1.409 ms
1.423 ms
1.479 ms
1.263 ms
1.173 ms
1.183 ms
1.435 ms
1.429 ms
1.208 ms
1.176 ms
1.187 ms
1.215 ms
4.099 ms
1.179 ms
1.663 ms
1.490 ms
1.209 ms
1.205 ms
1.429 ms
1.169 ms
1.397 ms
8.724 ms
1.189 ms
1.270 ms
1.312 ms
1.216 ms
1.209 ms
1.217 ms
1.179 ms
1.196 ms
1.846 ms
1.223 ms
1.210 ms
1.213 ms
1.228 ms
1.194 ms
1.215 ms
1.335 ms
1.195 ms
1.388 ms
1.482 ms
1.403 ms
1.194 ms
1.398 ms
1.659 ms
1.596 ms
11.036 ms
1.361 ms
1.407 ms
1.221 ms
4.725 ms
1.367 ms
1.199 ms
1.217 ms
1.492 ms
1.423 ms
9.409 ms
1.250 ms
1.287 ms
1.169 ms
1.407 ms
1.190 ms
1.391 ms
1.196 ms
1.428 ms
1.407 ms
1.197 ms
1.207 ms
1.175 ms
1.489 ms
1.434 ms
1.518 ms
1.249 ms
1.407 ms
1.356 ms
1.245 ms
1.213 ms
1.371 ms
1.172 ms
1.418 ms
1.169 ms
1.169 ms
1.140 ms
1.388 ms
1.564 ms
1.526 ms
1.416 ms
1.163 ms
9.762 ms
1.196 ms
6.245 ms
1.380 ms
1.275 ms
1.572 ms
1.354 ms
1.397 ms
2.812 ms
1.207 ms
1.373 ms
1.627 ms
12.385 ms
12.838 ms
1.245 ms
1.233 ms
1.181 ms
1.399 ms
1.419 ms
1.435 ms
1.182 ms
1.413 ms
16.644 ms
1.201 ms
1.176 ms
1.408 ms
1.198 ms
1.470 ms
1.193 ms
1.406 ms
1.205 ms
1.166 ms
1.367 ms
1.408 ms
1.432 ms
1.410 ms
1.409 ms
1.369 ms
1.393 ms
3.910 ms
1.389 ms
1.157 ms
1.405 ms
1.374 ms
1.437 ms
1.206 ms
1.385 ms
1.412 ms
1.413 ms
1.204 ms
1.366 ms
1.440 ms
1.174 ms
1.214 ms
1.404 ms
1.391 ms
1.283 ms
1.367 ms
1.388 ms
1.404 ms
1.177 ms
1.390 ms
1.179 ms
1.503 ms
1.275 ms
1.483 ms
1.356 ms
1.525 ms
1.151 ms
1.408 ms
16.456 ms
1.204 ms
1.151 ms
1.413 ms
1.245 ms
1.399 ms
1.168 ms
1.468 ms
1.179 ms
10.601 ms
1.382 ms
1.217 ms
1.194 ms
1.435 ms
1.383 ms
1.414 ms
1.193 ms
1.405 ms
1.453 ms
1.405 ms
1.447 ms
1.268 ms
1.382 ms
1.179 ms
1.185 ms
1.778 ms
6.467 ms
1.394 ms
1.373 ms
1.156 ms
1.387 ms
1.380 ms
1.183 ms
1.404 ms
1.143 ms
1.185 ms
1.426 ms
1.441 ms
1.216 ms
1.223 ms
1.379 ms
1.388 ms
1.371 ms
1.163 ms
1.150 ms
1.400 ms
1.214 ms
1.165 ms
1.406 ms
1.226 ms
1.187 ms
1.172 ms
1.387 ms
1.210 ms
1.249 ms
1.254 ms
1.580 ms
1.388 ms
1.178 ms
1.169 ms
1.166 ms
1.407 ms
1.389 ms
1.224 ms
1.163 ms
1.401 ms
1.367 ms
1.419 ms
1.169 ms
1.406 ms
1.212 ms
1.170 ms
1.215 ms
1.229 ms
1.216 ms
1.400 ms
1.396 ms
1.195 ms
1.435 ms
1.882 ms
1.267 ms
1.248 ms
1.426 ms
1.223 ms
1.421 ms
1.221 ms
1.427 ms
1.495 ms
1.485 ms
1.397 ms
1.161 ms
1.404 ms
1.385 ms
1.246 ms
1.396 ms
1.972 ms
1.404 ms
1.396 ms
1.456 ms
1.226 ms
1.195 ms
1.399 ms
1.396 ms
1.415 ms
1.477 ms
1.388 ms
1.182 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.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.721 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.218 msReply RTT AS13335 · Cloudflare
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.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.826 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.543 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.014 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination11.778 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.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.917 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


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 hop1.521 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.510 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.928 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.651 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.541 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.724 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop13.837 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.064 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.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.368 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.180 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.492 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.677 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.658 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.178 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.188 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.215 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.617 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.294 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.959 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


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 hop1.695 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.430 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.320 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.217 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.668 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.757 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.011 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.223 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.969 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.167 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.214 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.940 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.367 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.225 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.169 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.187 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.256 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop21.621 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop5.207 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.385 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.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.221 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.108 msReply RTT AS13335 · Cloudflare
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.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.767 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.529 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.412 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.132 msAS8002 · Stealth0.178 msAS8002 · StealthSame responder
20.187 msAS8002 · Stealth0.188 msAS8002 · StealthSame responder
30.917 msAS13335 · Cloudflare1.215 msAS13335 · CloudflareSame responder
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.159 msAS8002 · Stealth0.124 msAS8002 · StealthSame responder
20.721 msAS8002 · Stealth0.177 msAS8002 · StealthSame responder
34.218 msAS13335 · Cloudflare1.368 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.156 msAS8002 · Stealth0.180 msAS8002 · StealthSame responder
20.651 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
31.541 msAS13335 · Cloudflare4.492 msAS13335 · CloudflareSame responder
41.724 msAS13335 · CloudflareNo replyNot established
513.837 msAS13335 · Cloudflare1.677 msAS13335 · CloudflareDifferent responders
6No replyNo replyNot established
72.064 msAS13335 · Cloudflare1.658 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.

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.373 msUsual round trip before the event
Last recorded event RTT1.367 msLast successful event recording
Event p95 RTT9.893 ms95th percentile of successful recordings
Change from baseline-0.006 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