Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-2CC4F9EA9BFA7AC4

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 01:35 – 05 Nov 2026 06: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; displayed points are a sample of the retained records.
Recorded at (UTC)RTT
1.172 ms
1.256 ms
16.206 ms
3.763 ms
1.178 ms
1.161 ms
1.155 ms
1.142 ms
1.152 ms
1.375 ms
1.181 ms
1.160 ms
1.173 ms
1.153 ms
1.396 ms
1.144 ms
1.390 ms
1.155 ms
1.364 ms
1.408 ms
20.245 ms
1.381 ms
1.148 ms
1.359 ms
1.353 ms
1.394 ms
1.394 ms
1.394 ms
1.154 ms
1.346 ms
1.155 ms
1.385 ms
1.142 ms
1.362 ms
1.352 ms
1.354 ms
1.352 ms
1.382 ms
1.148 ms
1.179 ms
1.361 ms
1.149 ms
1.358 ms
1.137 ms
1.161 ms
1.400 ms
1.124 ms
15.203 ms
1.187 ms
1.483 ms
1.402 ms
1.382 ms
1.152 ms
1.370 ms
1.362 ms
1.148 ms
1.151 ms
1.365 ms
1.167 ms
1.342 ms
1.164 ms
19.532 ms
11.255 ms
2.922 ms
1.461 ms
1.215 ms
1.404 ms
1.180 ms
1.160 ms
1.220 ms
1.133 ms
1.228 ms
1.397 ms
1.376 ms
1.389 ms
1.254 ms
1.222 ms
1.161 ms
1.121 ms
2.293 ms
1.495 ms
1.311 ms
1.162 ms
1.186 ms
1.157 ms
1.156 ms
3.793 ms
1.407 ms
1.173 ms
1.424 ms
1.168 ms
1.127 ms
1.352 ms
1.402 ms
1.386 ms
2.020 ms
1.488 ms
1.385 ms
1.358 ms
1.348 ms
1.378 ms
1.525 ms
1.363 ms
1.185 ms
1.167 ms
1.256 ms
11.571 ms
1.359 ms
1.391 ms
1.333 ms
1.392 ms
1.446 ms
3.760 ms
1.331 ms
1.127 ms
1.173 ms
1.237 ms
1.351 ms
1.129 ms
1.152 ms
1.357 ms
1.392 ms
1.179 ms
1.375 ms
1.371 ms
1.164 ms
1.201 ms
1.347 ms
7.357 ms
1.160 ms
1.409 ms
1.375 ms
4.377 ms
1.424 ms
1.178 ms
8.200 ms
1.173 ms
1.475 ms
1.392 ms
1.369 ms
12.697 ms
1.397 ms
19.519 ms
18.752 ms
18.908 ms
18.916 ms
18.827 ms
19.040 ms
19.404 ms
15.936 ms
18.976 ms
15.285 ms
1.353 ms
15.830 ms
18.013 ms
16.073 ms
11.888 ms
15.560 ms
14.444 ms
16.045 ms
1.126 ms
19.408 ms
15.261 ms
9.468 ms
1.363 ms
1.201 ms
5.741 ms
5.006 ms
1.129 ms
18.787 ms
17.864 ms
18.444 ms
10.325 ms
6.948 ms
6.334 ms
17.591 ms
15.630 ms
1.158 ms
1.134 ms
1.382 ms
1.142 ms
1.353 ms
1.379 ms
4.847 ms
1.170 ms
1.150 ms
1.144 ms
1.157 ms
1.487 ms
1.142 ms
14.051 ms
1.160 ms
1.195 ms
1.330 ms
1.149 ms
1.328 ms
16.067 ms
1.162 ms
1.121 ms
5.683 ms
1.153 ms
1.344 ms
1.140 ms
1.134 ms
1.105 ms
1.221 ms
1.138 ms
1.377 ms
1.467 ms
1.149 ms
1.122 ms
1.430 ms
1.341 ms
1.335 ms
1.139 ms
1.370 ms
1.135 ms
1.160 ms
1.164 ms
1.308 ms
1.135 ms
1.169 ms
1.387 ms
1.143 ms
16.973 ms
2.526 ms
1.180 ms
1.212 ms
1.393 ms
1.397 ms
1.355 ms
1.130 ms
1.200 ms
1.318 ms
1.425 ms
1.831 ms
1.125 ms
1.175 ms
1.175 ms
1.363 ms
1.152 ms
1.401 ms
1.148 ms
1.407 ms
1.152 ms
1.332 ms
1.119 ms
1.367 ms
1.422 ms
1.364 ms
1.170 ms
1.134 ms
1.358 ms
1.205 ms
1.127 ms
1.360 ms
1.342 ms
1.150 ms
1.194 ms
1.200 ms
1.370 ms
1.454 ms
3.728 ms
1.398 ms
4.199 ms
1.182 ms
1.127 ms
1.122 ms
2.520 ms
1.165 ms
1.178 ms
1.370 ms
1.118 ms
1.176 ms
1.145 ms
1.354 ms
1.139 ms
5.714 ms
9.540 ms
1.358 ms
1.119 ms
1.145 ms
1.146 ms
1.131 ms
1.122 ms
1.337 ms
1.134 ms
1.130 ms
1.342 ms
1.142 ms
1.322 ms
1.362 ms
1.448 ms
1.352 ms
1.156 ms
1.343 ms
1.335 ms
1.196 ms
1.149 ms
1.341 ms
1.314 ms
1.386 ms
1.353 ms
1.375 ms
1.192 ms
1.325 ms
1.172 ms
1.135 ms
1.161 ms
1.161 ms
1.369 ms
1.338 ms
1.335 ms
1.140 ms
1.305 ms
1.147 ms
1.225 ms
1.347 ms
1.128 ms
1.240 ms
1.341 ms
1.330 ms
1.336 ms
1.370 ms
1.377 ms
1.339 ms
1.127 ms
1.106 ms
1.116 ms
1.327 ms
1.363 ms
1.132 ms
1.381 ms
1.144 ms
1.346 ms
1.357 ms
1.428 ms
1.375 ms
1.347 ms
1.397 ms
1.564 ms
1.346 ms
1.134 ms
1.347 ms
1.151 ms
1.143 ms
1.118 ms
1.357 ms
1.324 ms
1.138 ms
1.126 ms
1.172 ms
1.146 ms
1.120 ms
1.323 ms
2.211 ms
1.157 ms
1.341 ms
1.506 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.113 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.998 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.176 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.254 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.419 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.273 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.944 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.124 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.795 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.713 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.424 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.555 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.181 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.778 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.473 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.192 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.742 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop24.217 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.528 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.106 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.191 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop18.697 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.174 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.275 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.323 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.241 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.262 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.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.602 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.151 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.646 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.886 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.913 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.136 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.070 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.196 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.721 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.565 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.352 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.156 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.911 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.139 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.209 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.862 msReply RTT ASN unavailable
  4. TTL 4 Probe hop1.901 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop2.987 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.559 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.150 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.272 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.708 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.244 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.250 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.833 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.138 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.503 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.115 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.494 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.161 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.243 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.928 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.817 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.873 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.113 msAS8002 · Stealth0.106 msAS8002 · StealthSame responder
20.190 msAS8002 · Stealth0.191 msAS8002 · StealthSame responder
30.998 ms18.697 msAS13335 · CloudflareSame 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.144 msAS8002 · Stealth0.174 msAS8002 · StealthSame responder
20.182 msAS8002 · Stealth0.275 msAS8002 · StealthSame responder
30.742 msAS13335 · Cloudflare2.323 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
524.217 msAS13335 · Cloudflare2.241 msAS13335 · CloudflareDifferent responders
61.528 msAS13335 · CloudflareNo replyNot established
7Not recorded2.262 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.176 msAS8002 · Stealth0.151 msAS8002 · StealthSame responder
20.254 msAS8002 · Stealth0.184 msAS8002 · StealthSame responder
31.419 ms0.646 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
52.273 msAS13335 · Cloudflare4.886 msAS13335 · CloudflareSame responder
60.944 msAS13335 · Cloudflare0.913 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.357 msUsual round trip before the event
Last recorded event RTT1.363 msLast successful event recording
Event p95 RTT19.700 ms95th percentile of successful recordings
Change from baseline+0.006 msLast event RTT compared with the baseline
Successful / expected recordings330 / 330Recorded 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