Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-533FA3DBFA910383

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

06 Nov 2026 14:55 – 06 Nov 2026 22:29 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.144 ms
1.128 ms
1.615 ms
1.156 ms
1.675 ms
1.581 ms
1.605 ms
10.468 ms
1.130 ms
1.121 ms
1.210 ms
1.585 ms
1.286 ms
18.029 ms
1.590 ms
1.207 ms
1.121 ms
1.642 ms
1.156 ms
1.126 ms
1.613 ms
1.139 ms
1.192 ms
18.555 ms
1.570 ms
8.027 ms
1.128 ms
1.126 ms
1.614 ms
1.137 ms
1.135 ms
1.578 ms
1.575 ms
1.122 ms
1.124 ms
1.582 ms
1.141 ms
1.117 ms
17.596 ms
1.133 ms
3.572 ms
1.159 ms
1.204 ms
1.594 ms
1.638 ms
1.107 ms
3.216 ms
4.129 ms
1.172 ms
1.130 ms
1.165 ms
1.617 ms
1.631 ms
1.137 ms
1.144 ms
1.583 ms
2.138 ms
1.118 ms
1.592 ms
1.554 ms
1.609 ms
1.823 ms
15.079 ms
1.173 ms
1.635 ms
1.716 ms
1.622 ms
1.698 ms
1.608 ms
1.887 ms
1.575 ms
1.560 ms
1.556 ms
1.140 ms
1.588 ms
1.562 ms
1.128 ms
1.165 ms
1.590 ms
1.157 ms
1.144 ms
1.124 ms
1.609 ms
1.604 ms
1.860 ms
1.633 ms
1.674 ms
1.571 ms
1.122 ms
1.498 ms
1.126 ms
1.914 ms
1.551 ms
1.563 ms
1.158 ms
1.657 ms
1.642 ms
1.568 ms
1.163 ms
1.118 ms
1.168 ms
1.573 ms
1.605 ms
1.165 ms
1.144 ms
1.150 ms
1.140 ms
1.742 ms
1.136 ms
1.142 ms
1.161 ms
1.705 ms
1.575 ms
1.116 ms
1.160 ms
2.169 ms
1.125 ms
1.563 ms
2.962 ms
7.807 ms
1.168 ms
1.666 ms
1.590 ms
1.150 ms
1.126 ms
1.177 ms
1.139 ms
1.605 ms
1.195 ms
1.144 ms
1.146 ms
1.623 ms
4.720 ms
1.617 ms
1.581 ms
13.100 ms
1.131 ms
1.136 ms
1.135 ms
8.195 ms
1.580 ms
1.573 ms
1.649 ms
12.047 ms
1.572 ms
1.684 ms
14.038 ms
1.177 ms
1.156 ms
1.587 ms
1.569 ms
1.575 ms
1.557 ms
1.153 ms
5.667 ms
1.144 ms
1.658 ms
1.587 ms
1.151 ms
1.157 ms
1.566 ms
1.568 ms
1.138 ms
1.602 ms
2.801 ms
19.817 ms
1.577 ms
1.605 ms
1.569 ms
1.619 ms
1.653 ms
1.574 ms
1.574 ms
16.945 ms
1.656 ms
19.633 ms
6.898 ms
1.132 ms
1.209 ms
1.677 ms
1.565 ms
1.699 ms
1.632 ms
10.967 ms
1.133 ms
1.615 ms
1.625 ms
8.388 ms
1.146 ms
1.192 ms
1.650 ms
1.159 ms
1.557 ms
3.108 ms
1.138 ms
1.576 ms
1.574 ms
1.544 ms
1.655 ms
1.134 ms
1.255 ms
1.561 ms
1.671 ms
1.558 ms
1.163 ms
1.122 ms
1.267 ms
1.633 ms
1.737 ms
1.708 ms
1.627 ms
1.143 ms
1.575 ms
9.435 ms
1.162 ms
1.589 ms
1.641 ms
3.066 ms
1.159 ms
15.302 ms
1.713 ms
1.166 ms
10.272 ms
11.841 ms
1.142 ms
1.118 ms
1.586 ms
1.739 ms
1.159 ms
1.660 ms
1.572 ms
1.590 ms
1.662 ms
1.151 ms
1.638 ms
1.138 ms
1.123 ms
1.655 ms
1.201 ms
1.133 ms
1.633 ms
1.128 ms
1.607 ms
1.596 ms
1.153 ms
1.236 ms
1.562 ms
1.148 ms
1.115 ms
1.152 ms
1.599 ms
1.583 ms
1.166 ms
1.152 ms
1.148 ms
1.867 ms
1.151 ms
1.202 ms
1.561 ms
1.565 ms
1.550 ms
1.242 ms
1.127 ms
1.136 ms
1.154 ms
1.589 ms
1.585 ms
1.149 ms
1.695 ms
1.629 ms
1.196 ms
1.566 ms
1.655 ms
1.565 ms
1.141 ms
17.595 ms
1.580 ms
1.586 ms
1.184 ms
1.209 ms
1.689 ms
12.622 ms
1.605 ms
1.122 ms
1.110 ms
1.170 ms
1.571 ms
1.685 ms
1.134 ms
1.137 ms
1.176 ms
1.123 ms
1.571 ms
1.559 ms
1.598 ms
1.662 ms
1.736 ms
1.138 ms
1.642 ms
1.132 ms
1.180 ms
1.118 ms
1.146 ms
1.691 ms
1.571 ms
1.563 ms
12.620 ms
1.212 ms
1.575 ms
1.582 ms
1.584 ms
1.157 ms
1.629 ms
1.652 ms
1.580 ms
1.163 ms
1.551 ms
1.150 ms
1.173 ms
1.137 ms
1.180 ms
1.134 ms
1.161 ms
1.256 ms
1.654 ms
1.141 ms
1.149 ms
1.609 ms
1.707 ms
1.567 ms
1.182 ms
1.621 ms
1.167 ms
1.662 ms
1.603 ms
1.340 ms
1.597 ms
1.570 ms
1.130 ms
1.569 ms
1.629 ms
1.121 ms
1.569 ms
1.148 ms
1.136 ms
1.147 ms
1.558 ms
1.617 ms
1.123 ms
1.574 ms
1.140 ms
1.542 ms
1.614 ms
1.572 ms
1.684 ms
1.185 ms
1.629 ms
1.112 ms
Network path / recorded observations

Network path observations.

25 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.321 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.211 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 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.279 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.007 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 17 traces


to UTC

  1. TTL 1 Stealth associated hop0.123 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.184 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.572 msMedian reply RTT16/17 replies · 94.1%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP/443 traceroute · Destination 2

Comparison window · median of 16 traces


to UTC

  1. TTL 1 Stealth associated hop0.158 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.192 msMedian reply RTT16/16 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.627 msMedian reply RTT12/16 replies · 75.0%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.388 msMedian reply RTT15/16 replies · 93.8%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 13 traces


to UTC

  1. TTL 1 Stealth associated hop0.123 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop14.252 msMedian reply RTT11/13 replies · 84.6%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP/443 traceroute · Destination 4

Comparison window · median of 14 traces


to UTC

  1. TTL 1 Stealth associated hop0.145 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.181 msMedian reply RTT14/14 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.155 msMedian reply RTT14/14 replies · 100.0%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.416 msMedian reply RTT9/14 replies · 64.3%ASN unavailable
  7. TTL 7 Destination reply1.814 msMedian reply RTT5/14 replies · 35.7%ASN unavailable
Before

ICMP traceroute · Recorded address 1

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.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.146 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.199 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.257 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.746 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.170 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.185 msReply RTT AS13335 · Cloudflare
Before

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 hop16.673 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop19.481 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.254 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.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.054 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.571 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.709 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop22.122 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop6.077 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination5.003 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.254 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop27.797 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.243 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.214 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop16.057 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop11.069 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination3.549 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.128 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.192 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop7.402 msMedian reply RTT11/15 replies · 73.3%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 2

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.155 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.188 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.495 msMedian reply RTT10/15 replies · 66.7%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.324 msMedian reply RTT13/15 replies · 86.7%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

ICMP traceroute · Destination 3

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.133 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.190 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.515 msMedian reply RTT10/15 replies · 66.7%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 4

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.168 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.218 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.180 msMedian reply RTT11/15 replies · 73.3%AS13335 · Cloudflare
  4. TTL 4 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.368 msMedian reply RTT12/15 replies · 80.0%ASN unavailable
  7. TTL 7 Destination reply1.914 msMedian reply RTT3/15 replies · 20.0%ASN unavailable
During

ICMP traceroute · Recorded address 1

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.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop30.367 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.218 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.920 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.538 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.357 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.120 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.000 msReply RTT AS13335 · Cloudflare
After

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.245 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop19.769 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.959 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.264 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.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.632 msReply RTT ASN unavailable
After

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.175 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.174 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.649 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.583 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.148 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.255 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop37.111 msReply RTT ASN unavailable
After

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.209 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop40.711 msReply RTT ASN unavailable
  4. TTL 4 Probe hop2.561 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop4.137 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.396 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.124 msAS8002 · Stealth0.144 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.174 msAS8002 · StealthSame responder
31.146 msAS13335 · Cloudflare16.054 msSame 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.149 msAS8002 · Stealth0.571 msAS8002 · StealthSame responder
20.185 msAS8002 · Stealth0.709 msAS8002 · StealthSame responder
316.673 ms22.122 msSame responder
4No replyNo replyNot established
519.481 msAS13335 · Cloudflare6.077 msAS13335 · CloudflareDifferent responders
61.254 msAS13335 · Cloudflare5.003 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

Findings differ by destination.

Findings differ between destination comparisons. The evidence does not point to one location for the whole event.

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.358 msUsual round trip before the event
Last recorded event RTT1.201 msLast successful event recording
Event p95 RTT15.719 ms95th percentile of successful recordings
Change from baseline-0.158 msLast event RTT compared with the baseline
Successful / expected recordings667 / 670Recorded 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