Start an order
Root cause analysis / Investigation

chatgpt.com

Reference RCA-6DE330D7D5A06648

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

06 Nov 2026 23:20 – 07 Nov 2026 01:49 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.121 ms
1.575 ms
1.202 ms
1.574 ms
1.143 ms
1.585 ms
1.152 ms
1.591 ms
1.572 ms
1.634 ms
1.136 ms
1.646 ms
1.696 ms
1.116 ms
1.574 ms
1.578 ms
1.163 ms
1.159 ms
1.661 ms
1.131 ms
1.126 ms
1.133 ms
1.603 ms
1.611 ms
1.123 ms
1.129 ms
1.145 ms
1.651 ms
1.129 ms
1.610 ms
1.112 ms
1.575 ms
1.124 ms
1.596 ms
1.155 ms
1.674 ms
1.573 ms
1.159 ms
1.563 ms
1.125 ms
1.578 ms
1.141 ms
1.189 ms
1.265 ms
1.138 ms
1.580 ms
1.545 ms
1.130 ms
1.199 ms
1.673 ms
1.583 ms
1.551 ms
1.127 ms
1.132 ms
1.125 ms
1.614 ms
1.572 ms
1.717 ms
1.153 ms
1.128 ms
1.581 ms
1.167 ms
1.612 ms
1.636 ms
1.718 ms
1.174 ms
1.590 ms
1.587 ms
1.584 ms
1.169 ms
1.125 ms
1.190 ms
1.152 ms
1.151 ms
1.574 ms
1.572 ms
1.568 ms
1.627 ms
1.139 ms
1.124 ms
1.605 ms
1.735 ms
1.143 ms
1.633 ms
1.147 ms
1.120 ms
1.605 ms
1.589 ms
1.120 ms
1.583 ms
1.167 ms
1.174 ms
1.140 ms
1.596 ms
1.568 ms
1.110 ms
1.618 ms
1.164 ms
1.331 ms
1.571 ms
1.617 ms
1.152 ms
1.578 ms
1.731 ms
1.182 ms
1.125 ms
1.592 ms
1.161 ms
1.567 ms
1.621 ms
1.569 ms
1.603 ms
1.143 ms
1.123 ms
1.653 ms
1.582 ms
1.284 ms
1.157 ms
1.144 ms
1.168 ms
1.679 ms
1.673 ms
1.589 ms
1.565 ms
1.660 ms
1.159 ms
1.136 ms
1.593 ms
1.579 ms
9.764 ms
1.579 ms
1.584 ms
1.161 ms
1.656 ms
7.687 ms
1.564 ms
1.149 ms
1.574 ms
1.155 ms
1.143 ms
1.619 ms
1.157 ms
1.142 ms
1.569 ms
1.625 ms
1.556 ms
1.124 ms
1.583 ms
1.123 ms
18.642 ms
1.566 ms
1.237 ms
1.163 ms
1.683 ms
1.562 ms
1.160 ms
1.582 ms
1.169 ms
1.248 ms
1.753 ms
1.654 ms
1.708 ms
1.623 ms
1.138 ms
1.154 ms
1.140 ms
1.561 ms
1.705 ms
1.150 ms
1.153 ms
1.141 ms
1.551 ms
1.178 ms
1.171 ms
1.624 ms
1.142 ms
1.556 ms
1.230 ms
1.151 ms
1.580 ms
1.126 ms
1.148 ms
1.114 ms
1.669 ms
1.159 ms
1.599 ms
1.322 ms
1.620 ms
1.578 ms
1.578 ms
1.154 ms
1.121 ms
1.615 ms
1.127 ms
7.227 ms
1.273 ms
1.134 ms
1.570 ms
1.592 ms
1.123 ms
1.586 ms
1.131 ms
1.600 ms
1.557 ms
1.151 ms
1.123 ms
1.153 ms
1.159 ms
1.158 ms
1.127 ms
1.210 ms
1.648 ms
1.566 ms
1.132 ms
1.593 ms
1.624 ms
19.140 ms
1.568 ms
1.158 ms
1.586 ms
1.612 ms
1.616 ms
1.719 ms
1.581 ms
2.112 ms
1.575 ms
1.190 ms
1.556 ms
1.576 ms
1.178 ms
1.594 ms
1.134 ms
1.136 ms
1.568 ms
1.581 ms
1.667 ms
1.600 ms
1.602 ms
1.620 ms
1.790 ms
1.740 ms
1.163 ms
1.270 ms
1.698 ms
1.163 ms
1.670 ms
1.170 ms
1.128 ms
1.588 ms
1.159 ms
1.616 ms
1.136 ms
1.564 ms
1.172 ms
1.644 ms
1.586 ms
1.609 ms
1.567 ms
1.162 ms
1.120 ms
1.566 ms
1.598 ms
1.223 ms
1.570 ms
1.144 ms
1.576 ms
1.800 ms
1.569 ms
1.125 ms
1.167 ms
1.551 ms
1.131 ms
8.721 ms
1.164 ms
1.132 ms
1.588 ms
1.140 ms
1.646 ms
1.142 ms
1.784 ms
1.652 ms
1.160 ms
1.614 ms
1.133 ms
1.168 ms
1.186 ms
1.127 ms
1.577 ms
1.564 ms
1.127 ms
1.567 ms
1.204 ms
1.644 ms
1.585 ms
1.166 ms
1.134 ms
1.626 ms
1.635 ms
1.136 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 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop15.974 msReply RTT ASN unavailable
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.207 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.424 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.918 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.618 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 17 traces


to UTC

  1. TTL 1 Stealth associated hop0.131 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.187 msMedian reply RTT17/17 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.197 msMedian reply RTT15/17 replies · 88.2%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 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.171 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.194 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop2.194 msMedian reply RTT14/15 replies · 93.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.283 msMedian reply RTT14/15 replies · 93.3%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.125 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.197 msMedian reply RTT13/13 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.380 msMedian reply RTT12/13 replies · 92.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
Before

TCP/443 traceroute · Destination 4

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.160 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.185 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.499 msMedian reply RTT12/15 replies · 80.0%AS13335 · Cloudflare
  4. TTL 4 External hop4.776 msMedian reply RTT3/15 replies · 20.0%ASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.416 msMedian reply RTT12/15 replies · 80.0%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

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.731 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.273 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.140 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop31.771 msReply RTT ASN unavailable
  4. TTL 4 Probe hop18.559 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.711 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.047 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.130 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.459 msMedian reply RTT15/15 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 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
During

TCP/443 traceroute · Destination 2

Comparison window · median of 12 traces


to UTC

  1. TTL 1 Stealth associated hop0.176 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.205 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.268 msMedian reply RTT12/12 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.265 msMedian reply RTT12/12 replies · 100.0%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.131 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.189 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.500 msMedian reply RTT13/15 replies · 86.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 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.154 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.192 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.508 msMedian reply RTT18/18 replies · 100.0%AS13335 · Cloudflare
  4. TTL 4 External hop1.735 msMedian reply RTT3/18 replies · 16.7%ASN unavailable
  5. TTL 5 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
  6. TTL 6 Destination reply1.358 msMedian reply RTT17/18 replies · 94.4%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.205 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.223 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.864 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.289 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.270 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.173 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop27.524 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop2.058 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.549 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.608 msReply RTT AS13335 · Cloudflare
During

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.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop2.040 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.940 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.394 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.195 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.098 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.313 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.010 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.971 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.500 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.444 msReply RTT AS13335 · Cloudflare
During

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.185 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.405 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop7.584 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.401 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.122 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop9.102 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.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.692 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop4.320 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.407 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.133 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.711 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop20.804 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.168 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.178 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop6.686 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.517 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.275 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop14.684 msReply RTT AS13335 · Cloudflare
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.237 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.543 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.020 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.355 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.125 msAS8002 · Stealth0.173 msAS8002 · StealthSame responder
20.731 msAS8002 · Stealth0.189 msAS8002 · StealthSame responder
31.273 ms27.524 msAS13335 · CloudflareSame responder
4Not recorded2.058 msAS13335 · CloudflareNot established
5Not recorded1.549 msAS13335 · CloudflareNot established
6Not recorded1.608 msAS13335 · CloudflareNot 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.154 msAS8002 · Stealth0.125 msAS8002 · StealthSame responder
20.183 msAS8002 · Stealth0.183 msAS8002 · StealthSame responder
315.974 ms1.444 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.205 msAS8002 · Stealth0.158 msAS8002 · StealthSame responder
20.223 msAS8002 · Stealth0.185 msAS8002 · StealthSame responder
30.864 msAS13335 · Cloudflare1.405 msAS13335 · CloudflareSame responder
4No replyNo replyNot established
51.289 msAS13335 · Cloudflare7.584 msAS13335 · CloudflareDifferent responders
61.270 msAS13335 · Cloudflare1.401 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.140 msAS8002 · Stealth0.145 msAS8002 · StealthSame responder
20.180 msAS8002 · Stealth0.178 msAS8002 · StealthSame responder
331.771 ms2.040 msAS13335 · CloudflareSame responder
418.559 msAS13335 · CloudflareNo replyNot established
51.711 msAS13335 · Cloudflare1.940 msAS13335 · CloudflareDifferent responders
6No reply1.394 msAS13335 · CloudflareNot established
72.047 msAS13335 · CloudflareNot recordedNot 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

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.353 msUsual round trip before the event
Last recorded event RTT1.580 msLast successful event recording
Event p95 RTT2.049 ms95th percentile of successful recordings
Change from baseline+0.227 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