Start an order
Root cause analysis / Investigation

api.mistral.ai

Reference RCA-5BFA8CC77292D67A

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

09 Nov 2026 20:00 – 09 Nov 2026 21:37 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.354 ms
1.409 ms
1.210 ms
1.334 ms
1.321 ms
13.332 ms
1.400 ms
1.255 ms
1.305 ms
1.318 ms
1.395 ms
1.211 ms
1.386 ms
1.331 ms
1.201 ms
1.382 ms
1.245 ms
18.301 ms
1.193 ms
1.437 ms
1.361 ms
1.338 ms
1.260 ms
1.240 ms
1.420 ms
1.302 ms
3.682 ms
5.314 ms
1.336 ms
1.348 ms
1.232 ms
1.260 ms
1.316 ms
1.309 ms
1.263 ms
1.319 ms
1.368 ms
1.330 ms
1.337 ms
1.367 ms
1.321 ms
1.392 ms
1.250 ms
1.219 ms
1.315 ms
1.224 ms
1.358 ms
1.402 ms
1.343 ms
7.237 ms
1.320 ms
1.448 ms
1.263 ms
1.354 ms
1.296 ms
1.556 ms
1.165 ms
14.596 ms
1.242 ms
1.417 ms
1.315 ms
1.519 ms
1.340 ms
1.368 ms
1.349 ms
2.704 ms
1.344 ms
1.310 ms
1.357 ms
18.432 ms
1.627 ms
1.261 ms
1.259 ms
1.310 ms
1.408 ms
1.258 ms
1.354 ms
1.218 ms
1.308 ms
1.372 ms
1.197 ms
1.398 ms
1.216 ms
1.185 ms
3.149 ms
1.261 ms
1.379 ms
18.218 ms
1.187 ms
1.367 ms
1.321 ms
1.405 ms
1.380 ms
1.538 ms
1.345 ms
1.315 ms
1.296 ms
1.182 ms
1.229 ms
1.367 ms
1.397 ms
1.366 ms
1.422 ms
1.190 ms
1.201 ms
1.359 ms
1.192 ms
1.179 ms
1.329 ms
1.442 ms
1.370 ms
1.185 ms
1.346 ms
1.184 ms
1.868 ms
1.411 ms
1.418 ms
1.202 ms
1.193 ms
1.190 ms
1.318 ms
1.316 ms
1.380 ms
1.333 ms
17.634 ms
1.150 ms
1.465 ms
1.385 ms
1.450 ms
1.325 ms
1.356 ms
1.318 ms
1.206 ms
1.216 ms
1.386 ms
1.363 ms
1.402 ms
8.979 ms
1.212 ms
1.329 ms
5.499 ms
1.410 ms
1.292 ms
1.207 ms
1.373 ms
1.357 ms
1.446 ms
1.361 ms
1.186 ms
1.362 ms
1.365 ms
1.363 ms
1.332 ms
1.309 ms
1.195 ms
1.371 ms
1.446 ms
1.334 ms
1.209 ms
1.363 ms
1.309 ms
1.203 ms
1.229 ms
1.354 ms
1.292 ms
1.364 ms
1.374 ms
1.195 ms
1.334 ms
1.187 ms
1.434 ms
1.324 ms
1.392 ms
1.442 ms
1.369 ms
1.392 ms
1.377 ms
1.202 ms
1.356 ms
1.178 ms
1.352 ms
1.210 ms
1.385 ms
1.360 ms
1.353 ms
1.189 ms
1.364 ms
18.011 ms
1.312 ms
1.226 ms
1.317 ms
1.189 ms
1.172 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.127 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop5.451 msReply RTT ASN unavailable
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.243 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop7.014 msReply RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.444 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.233 msReply RTT AS13335 · Cloudflare
Before

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.128 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.174 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.201 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.196 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 hop8.686 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.566 msReply RTT AS13335 · Cloudflare
Before

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.180 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.178 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop8.314 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.015 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.152 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.193 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop1.776 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.789 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop2.083 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Destination1.504 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.143 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.190 msReply RTT AS8002 · Stealth
During

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.188 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 hop19.531 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.399 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.181 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop24.453 msReply RTT AS13335 · Cloudflare
During

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.197 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop13.625 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop1.707 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.523 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.117 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.180 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.190 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.184 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 hop10.716 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.656 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.129 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop0.942 msReply RTT AS13335 · Cloudflare
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.177 msReply RTT AS8002 · Stealth
  3. TTL 3 Probe hop26.989 msReply RTT AS13335 · Cloudflare
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop11.811 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.866 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.116 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.173 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.173 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.202 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 hop13.929 msReply RTT AS13335 · Cloudflare
  6. TTL 6 Destination1.094 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.128 msAS8002 · Stealth0.152 msAS8002 · StealthSame responder
20.174 msAS8002 · Stealth0.193 msAS8002 · StealthSame responder
3Not recorded1.776 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.127 msAS8002 · Stealth0.125 msAS8002 · StealthSame responder
20.177 msAS8002 · Stealth0.181 msAS8002 · StealthSame responder
35.451 ms24.453 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.201 msAS8002 · Stealth0.141 msAS8002 · StealthSame responder
20.196 msAS8002 · Stealth0.181 msAS8002 · StealthSame responder
3No reply0.789 msAS13335 · CloudflareNot established
4No replyNo replyNot established
58.686 msAS13335 · Cloudflare2.083 msAS13335 · CloudflareDifferent responders
6No replyNo replyNot established
71.566 msAS13335 · Cloudflare1.504 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.

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

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.

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.318 msUsual round trip before the event
Last recorded event RTT1.356 msLast successful event recording
Event p95 RTT1.667 ms95th percentile of successful recordings
Change from baseline+0.038 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
Unavailable
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