Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-9BCDA79614C5D058

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

28 Oct 2026 12:35 – 28 Oct 2026 23:34 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.401 ms
1.422 ms
1.261 ms
1.866 ms
5.211 ms
1.422 ms
1.275 ms
1.216 ms
1.403 ms
1.418 ms
1.375 ms
1.465 ms
1.203 ms
1.433 ms
1.366 ms
1.218 ms
1.221 ms
1.245 ms
1.427 ms
1.401 ms
1.376 ms
1.390 ms
2.473 ms
1.190 ms
1.435 ms
1.403 ms
1.238 ms
7.294 ms
1.385 ms
1.204 ms
1.197 ms
1.399 ms
1.414 ms
1.379 ms
1.755 ms
1.174 ms
1.363 ms
1.162 ms
1.411 ms
1.168 ms
1.173 ms
1.399 ms
1.177 ms
8.228 ms
1.398 ms
1.217 ms
1.427 ms
1.399 ms
1.234 ms
2.050 ms
1.291 ms
1.407 ms
1.254 ms
1.484 ms
13.414 ms
1.226 ms
1.165 ms
12.119 ms
1.380 ms
18.360 ms
1.379 ms
1.415 ms
1.490 ms
1.423 ms
1.169 ms
1.198 ms
1.327 ms
1.411 ms
1.382 ms
1.467 ms
13.679 ms
1.185 ms
4.553 ms
1.473 ms
1.446 ms
1.382 ms
1.225 ms
1.442 ms
5.123 ms
1.485 ms
1.219 ms
18.807 ms
1.461 ms
1.374 ms
1.383 ms
1.417 ms
1.209 ms
1.411 ms
1.452 ms
1.404 ms
1.711 ms
1.247 ms
1.240 ms
1.378 ms
1.183 ms
1.429 ms
1.394 ms
1.182 ms
1.218 ms
1.433 ms
1.183 ms
3.827 ms
1.382 ms
1.355 ms
16.267 ms
1.249 ms
1.196 ms
1.235 ms
1.427 ms
1.220 ms
1.190 ms
1.176 ms
1.275 ms
1.345 ms
1.222 ms
1.413 ms
1.398 ms
1.401 ms
1.196 ms
1.386 ms
5.113 ms
1.264 ms
4.554 ms
1.402 ms
16.869 ms
1.412 ms
1.200 ms
8.486 ms
6.177 ms
1.404 ms
1.429 ms
1.209 ms
2.313 ms
11.406 ms
16.574 ms
19.734 ms
8.394 ms
15.704 ms
5.005 ms
6.737 ms
1.416 ms
3.522 ms
16.965 ms
13.761 ms
2.370 ms
18.456 ms
6.475 ms
16.530 ms
1.543 ms
11.623 ms
1.171 ms
5.234 ms
2.541 ms
1.228 ms
1.169 ms
1.412 ms
10.806 ms
1.416 ms
1.174 ms
10.499 ms
11.187 ms
1.224 ms
1.430 ms
1.321 ms
1.431 ms
20.474 ms
18.001 ms
1.187 ms
5.434 ms
3.008 ms
13.491 ms
3.834 ms
1.173 ms
1.650 ms
19.553 ms
1.449 ms
9.285 ms
6.070 ms
16.471 ms
15.841 ms
1.211 ms
9.138 ms
1.228 ms
1.190 ms
1.399 ms
8.295 ms
1.424 ms
1.415 ms
6.328 ms
1.198 ms
1.174 ms
13.060 ms
1.196 ms
1.211 ms
2.931 ms
1.414 ms
1.165 ms
1.554 ms
1.198 ms
1.438 ms
1.262 ms
1.150 ms
1.465 ms
1.448 ms
1.392 ms
1.403 ms
4.120 ms
1.396 ms
1.414 ms
1.178 ms
1.271 ms
1.632 ms
7.214 ms
1.218 ms
1.254 ms
1.359 ms
1.377 ms
1.249 ms
1.170 ms
1.388 ms
1.183 ms
1.270 ms
1.440 ms
1.376 ms
2.919 ms
1.179 ms
1.373 ms
1.784 ms
1.385 ms
1.388 ms
1.405 ms
18.254 ms
1.413 ms
1.260 ms
15.152 ms
4.769 ms
1.421 ms
1.187 ms
1.171 ms
1.458 ms
1.167 ms
1.316 ms
1.464 ms
1.177 ms
1.398 ms
1.260 ms
1.266 ms
1.444 ms
5.447 ms
1.172 ms
1.245 ms
1.253 ms
1.395 ms
1.628 ms
1.405 ms
1.235 ms
1.413 ms
1.419 ms
1.405 ms
1.430 ms
1.166 ms
1.466 ms
1.184 ms
1.193 ms
1.191 ms
1.391 ms
1.214 ms
1.420 ms
1.495 ms
1.409 ms
1.429 ms
1.222 ms
1.396 ms
1.337 ms
1.403 ms
1.374 ms
1.159 ms
1.410 ms
1.232 ms
1.465 ms
1.196 ms
1.201 ms
1.219 ms
1.406 ms
1.221 ms
1.443 ms
1.422 ms
1.183 ms
1.180 ms
1.222 ms
1.196 ms
1.427 ms
1.192 ms
1.433 ms
1.163 ms
1.200 ms
1.190 ms
1.239 ms
1.179 ms
1.234 ms
1.263 ms
1.181 ms
1.189 ms
2.444 ms
1.181 ms
1.198 ms
2.774 ms
1.428 ms
1.548 ms
1.417 ms
1.440 ms
1.387 ms
1.537 ms
1.498 ms
1.680 ms
1.523 ms
2.719 ms
1.444 ms
1.396 ms
1.250 ms
1.235 ms
5.967 ms
1.192 ms
16.428 ms
1.191 ms
1.415 ms
1.200 ms
8.531 ms
1.550 ms
1.207 ms
1.411 ms
3.793 ms
8.498 ms
1.424 ms
15.390 ms
1.218 ms
1.235 ms
1.197 ms
14.726 ms
1.166 ms
1.189 ms
1.200 ms
1.513 ms
1.385 ms
17.932 ms
1.415 ms
1.416 ms
1.448 ms
1.192 ms
1.183 ms
1.439 ms
1.401 ms
16.190 ms
1.208 ms
1.458 ms
1.398 ms
1.176 ms
1.450 ms
1.354 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.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.905 msReply RTT AS13335 · Cloudflare
Before

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.360 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.815 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop1.706 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop7.787 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.534 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.492 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.646 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.222 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop23.262 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.071 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.522 msReply RTT AS13335 · Cloudflare
Before

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.256 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.662 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.928 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.333 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.159 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.238 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.236 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop3.982 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.952 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination17.513 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.727 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.158 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.187 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.204 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.397 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.237 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.197 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.200 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop69.453 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.225 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.199 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop34.211 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.543 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.399 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.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.185 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.177 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.205 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.433 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.231 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.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.976 msReply RTT AS13335 · Cloudflare
After

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.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.051 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.255 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop3.800 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.286 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.582 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop6.346 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.059 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.551 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.174 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.636 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.286 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.358 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.120 msAS8002 · Stealth0.159 msAS8002 · StealthSame responder
20.492 msAS8002 · Stealth0.193 msAS8002 · StealthSame responder
30.646 msAS13335 · CloudflareNot recordedNot established
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.222 msAS8002 · Stealth0.238 msAS8002 · StealthSame responder
20.187 msAS8002 · Stealth0.236 msAS8002 · StealthSame responder
323.262 msAS13335 · Cloudflare3.982 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.071 msAS13335 · Cloudflare1.952 msAS13335 · CloudflareSame responder
61.522 msAS13335 · CloudflareNo replyNot established
7Not recorded17.513 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.177 msAS8002 · Stealth0.158 msAS8002 · StealthSame responder
20.256 msAS8002 · Stealth0.187 msAS8002 · StealthSame responder
31.662 msAS13335 · Cloudflare1.204 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.928 msAS13335 · Cloudflare2.397 msAS13335 · CloudflareDifferent responders
6No replyNo replyNot established
72.333 msAS13335 · Cloudflare2.237 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.378 msUsual round trip before the event
Last recorded event RTT1.458 msLast successful event recording
Event p95 RTT18.752 ms95th percentile of successful recordings
Change from baseline+0.080 msLast event RTT compared with the baseline
Successful / expected recordings944 / 1080Recorded 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