Start an order
Root cause analysis / Investigation

api.mistral.ai

Reference RCA-513F72E75CA6D13D

Mistral API endpoint

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

07 Nov 2026 01:05 – 07 Nov 2026 03: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.196 ms
1.359 ms
1.274 ms
6.917 ms
1.366 ms
1.346 ms
1.358 ms
1.376 ms
1.343 ms
1.272 ms
1.307 ms
1.371 ms
1.229 ms
5.251 ms
1.406 ms
1.241 ms
1.208 ms
1.268 ms
1.395 ms
1.182 ms
1.350 ms
1.210 ms
1.411 ms
1.199 ms
1.210 ms
1.429 ms
1.183 ms
1.237 ms
1.378 ms
1.335 ms
1.203 ms
1.205 ms
1.183 ms
1.352 ms
1.303 ms
1.303 ms
1.214 ms
1.238 ms
1.204 ms
1.354 ms
1.433 ms
1.197 ms
1.279 ms
1.355 ms
1.342 ms
1.325 ms
1.239 ms
1.343 ms
1.177 ms
1.339 ms
1.235 ms
1.362 ms
1.172 ms
1.363 ms
1.217 ms
1.591 ms
1.200 ms
1.340 ms
1.330 ms
1.224 ms
1.315 ms
1.390 ms
1.208 ms
1.333 ms
1.343 ms
1.191 ms
1.387 ms
1.319 ms
1.230 ms
2.823 ms
1.340 ms
1.345 ms
1.354 ms
1.310 ms
1.323 ms
7.174 ms
1.340 ms
1.571 ms
1.333 ms
1.353 ms
1.346 ms
1.192 ms
1.423 ms
1.366 ms
1.335 ms
1.168 ms
1.256 ms
1.341 ms
1.310 ms
1.372 ms
1.342 ms
1.331 ms
1.327 ms
1.320 ms
1.354 ms
1.196 ms
1.399 ms
1.346 ms
1.320 ms
1.225 ms
1.391 ms
1.195 ms
1.376 ms
1.359 ms
1.210 ms
1.217 ms
1.249 ms
1.340 ms
1.350 ms
1.309 ms
1.297 ms
1.179 ms
1.405 ms
1.596 ms
1.231 ms
1.375 ms
1.358 ms
1.346 ms
1.298 ms
1.348 ms
1.189 ms
1.434 ms
1.262 ms
1.220 ms
1.252 ms
1.228 ms
5.022 ms
1.375 ms
1.292 ms
1.353 ms
19.608 ms
1.311 ms
1.198 ms
1.269 ms
1.214 ms
1.444 ms
19.190 ms
1.314 ms
1.345 ms
1.227 ms
1.206 ms
1.342 ms
1.200 ms
1.338 ms
1.495 ms
1.237 ms
1.190 ms
13.531 ms
1.351 ms
1.562 ms
1.369 ms
1.336 ms
1.353 ms
1.196 ms
1.193 ms
1.327 ms
1.321 ms
1.330 ms
1.216 ms
1.194 ms
1.329 ms
1.293 ms
1.368 ms
1.383 ms
1.248 ms
1.230 ms
1.381 ms
1.210 ms
1.315 ms
1.238 ms
1.326 ms
1.377 ms
1.379 ms
1.314 ms
1.332 ms
1.228 ms
5.702 ms
1.327 ms
1.259 ms
1.466 ms
1.371 ms
1.339 ms
1.333 ms
1.204 ms
1.347 ms
1.314 ms
1.386 ms
1.232 ms
1.309 ms
1.264 ms
1.334 ms
1.190 ms
1.208 ms
1.332 ms
1.282 ms
1.249 ms
1.335 ms
1.203 ms
1.390 ms
1.318 ms
1.220 ms
1.198 ms
1.398 ms
1.207 ms
1.339 ms
1.227 ms
1.325 ms
1.346 ms
1.217 ms
1.862 ms
1.318 ms
1.390 ms
1.331 ms
1.359 ms
1.350 ms
1.207 ms
1.351 ms
1.308 ms
1.303 ms
1.279 ms
1.185 ms
1.356 ms
1.202 ms
1.191 ms
1.222 ms
1.366 ms
1.361 ms
1.215 ms
1.186 ms
1.343 ms
1.209 ms
1.395 ms
1.345 ms
1.352 ms
1.228 ms
1.324 ms
1.203 ms
1.425 ms
1.388 ms
1.217 ms
1.328 ms
1.210 ms
1.186 ms
1.228 ms
1.342 ms
1.312 ms
1.217 ms
1.225 ms
1.188 ms
1.368 ms
1.167 ms
1.189 ms
1.307 ms
1.318 ms
1.391 ms
1.317 ms
1.194 ms
1.186 ms
1.360 ms
1.325 ms
1.323 ms
1.207 ms
1.358 ms
1.245 ms
1.402 ms
1.256 ms
1.355 ms
1.375 ms
1.192 ms
1.192 ms
1.328 ms
1.207 ms
1.320 ms
1.217 ms
1.228 ms
1.451 ms
1.177 ms
1.199 ms
1.206 ms
1.193 ms
1.341 ms
1.186 ms
1.320 ms
1.266 ms
1.340 ms
1.193 ms
1.374 ms
1.194 ms
1.393 ms
1.184 ms
1.218 ms
1.326 ms
1.273 ms
1.370 ms
1.352 ms
1.276 ms
1.373 ms
1.337 ms
1.226 ms
1.251 ms
1.377 ms
1.187 ms
1.197 ms
1.240 ms
1.214 ms
1.207 ms
1.316 ms
1.323 ms
1.356 ms
1.198 ms
1.381 ms
1.251 ms
1.197 ms
1.234 ms
1.239 ms
1.292 ms
1.231 ms
1.398 ms
1.322 ms
1.362 ms
1.340 ms
1.251 ms
1.192 ms
1.347 ms
1.196 ms
1.744 ms
1.216 ms
1.249 ms
1.175 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.137 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.580 msReply RTT ASN unavailable
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.204 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.745 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.187 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.884 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Destination 1

Comparison window · median of 21 traces


to UTC

  1. TTL 1 Stealth associated hop0.133 msMedian reply RTT21/21 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.185 msMedian reply RTT21/21 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.409 msMedian reply RTT20/21 replies · 95.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 12 traces


to UTC

  1. TTL 1 Stealth associated hop0.169 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.192 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.807 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.237 msMedian reply RTT9/12 replies · 75.0%ASN unavailable
  7. TTL 7 Unidentified or changing hopUnavailableMedian reply RTTReply coverage unavailableASN unavailable
Before

ICMP traceroute · Destination 3

Comparison window · median of 9 traces


to UTC

  1. TTL 1 Stealth associated hop0.134 msMedian reply RTT9/9 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT9/9 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.718 msMedian reply RTT9/9 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
Before

TCP/443 traceroute · Destination 4

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.167 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.184 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.081 msMedian reply RTT17/18 replies · 94.4%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.428 msMedian reply RTT14/18 replies · 77.8%ASN unavailable
  7. TTL 7 Destination reply1.534 msMedian reply RTT4/18 replies · 22.2%ASN unavailable
Before

ICMP traceroute · Recorded address 2

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

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.153 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.265 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.588 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.123 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.047 msReply RTT AS13335 · Cloudflare
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.185 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.182 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.922 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop20.240 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.281 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.131 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.189 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.488 msReply RTT ASN unavailable
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.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.878 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.518 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.239 msReply RTT AS13335 · Cloudflare
During

ICMP traceroute · Destination 1

Comparison window · median of 18 traces


to UTC

  1. TTL 1 Stealth associated hop0.133 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.186 msMedian reply RTT18/18 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.718 msMedian reply RTT18/18 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 15 traces


to UTC

  1. TTL 1 Stealth associated hop0.185 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.195 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.471 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 Destination reply1.344 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 12 traces


to UTC

  1. TTL 1 Stealth associated hop0.127 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.184 msMedian reply RTT12/12 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.591 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 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.210 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  2. TTL 2 Stealth associated hop0.200 msMedian reply RTT15/15 replies · 100.0%ASN unavailable
  3. TTL 3 First responding external hop1.430 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 Destination reply1.276 msMedian reply RTT10/15 replies · 66.7%ASN unavailable
  7. TTL 7 Destination reply1.894 msMedian reply RTT5/15 replies · 33.3%ASN unavailable
During

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.253 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.790 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.391 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.230 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.654 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.777 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination2.487 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.192 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.467 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.654 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.222 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.228 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.323 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop3.310 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination0.863 msReply RTT AS13335 · Cloudflare
After

ICMP traceroute · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.130 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.768 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hop8.313 msReply RTT AS13335 · Cloudflare
  5. TTL 5 Probe hop1.803 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.444 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.183 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.307 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.897 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.561 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.126 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop10.205 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.308 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.266 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop4.145 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.690 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.329 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.154 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.186 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.815 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.179 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.664 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.883 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.509 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.134 msAS8002 · Stealth0.131 msAS8002 · StealthSame responder
20.181 msAS8002 · Stealth0.189 msAS8002 · StealthSame responder
31.816 msAS13335 · Cloudflare1.488 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.185 msAS8002 · Stealth0.145 msAS8002 · StealthSame responder
20.182 msAS8002 · Stealth0.179 msAS8002 · StealthSame responder
310.922 ms0.878 msSame responder
4No replyNo replyNot established
520.240 msAS13335 · Cloudflare1.518 msAS13335 · CloudflareDifferent responders
6No reply1.239 msAS13335 · CloudflareNot established
71.281 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.348 msUsual round trip before the event
Last recorded event RTT1.862 msLast successful event recording
Event p95 RTT3.600 ms95th percentile of successful recordings
Change from baseline+0.513 msLast event RTT compared with the baseline
Successful / expected recordings90 / 90Recorded 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