Start an order
Root cause analysis / Investigation

copilot.com

Reference RCA-F42FACE97F396A40

Microsoft 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

09 Nov 2026 14:35 – 09 Nov 2026 17:04 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
6.307 ms
6.331 ms
6.362 ms
6.295 ms
6.367 ms
6.379 ms
6.311 ms
6.291 ms
6.339 ms
6.268 ms
6.360 ms
6.345 ms
6.346 ms
6.286 ms
6.272 ms
6.412 ms
6.413 ms
6.659 ms
6.328 ms
6.308 ms
6.285 ms
6.381 ms
6.648 ms
6.304 ms
6.364 ms
6.393 ms
6.379 ms
6.287 ms
6.367 ms
6.293 ms
6.278 ms
6.346 ms
6.299 ms
6.485 ms
6.468 ms
6.474 ms
6.490 ms
6.504 ms
6.521 ms
6.498 ms
6.483 ms
6.477 ms
6.467 ms
6.463 ms
6.493 ms
6.498 ms
6.509 ms
6.518 ms
6.472 ms
6.503 ms
6.495 ms
6.468 ms
6.468 ms
6.474 ms
6.468 ms
6.492 ms
6.484 ms
6.479 ms
6.488 ms
6.467 ms
6.487 ms
6.479 ms
6.462 ms
6.501 ms
6.478 ms
6.485 ms
6.482 ms
6.458 ms
6.490 ms
6.511 ms
6.522 ms
6.458 ms
6.484 ms
6.477 ms
6.492 ms
6.498 ms
6.549 ms
6.451 ms
6.468 ms
6.607 ms
6.493 ms
6.469 ms
6.470 ms
6.460 ms
6.485 ms
6.516 ms
6.766 ms
6.791 ms
6.717 ms
6.817 ms
6.744 ms
6.750 ms
6.580 ms
6.687 ms
6.575 ms
6.555 ms
6.626 ms
6.545 ms
6.668 ms
6.564 ms
6.545 ms
6.574 ms
6.625 ms
6.592 ms
6.579 ms
6.540 ms
6.865 ms
6.490 ms
6.456 ms
6.523 ms
6.488 ms
6.540 ms
6.524 ms
6.479 ms
6.462 ms
6.510 ms
6.516 ms
6.485 ms
6.471 ms
6.528 ms
6.475 ms
6.461 ms
6.478 ms
6.475 ms
17.691 ms
17.689 ms
17.662 ms
17.688 ms
17.704 ms
17.707 ms
17.735 ms
17.695 ms
17.696 ms
17.716 ms
17.686 ms
17.696 ms
17.688 ms
17.694 ms
17.736 ms
17.695 ms
17.695 ms
17.685 ms
6.073 ms
6.060 ms
6.085 ms
6.063 ms
6.072 ms
6.106 ms
6.071 ms
6.110 ms
6.096 ms
6.106 ms
6.085 ms
6.070 ms
6.075 ms
6.085 ms
6.088 ms
6.069 ms
6.102 ms
6.097 ms
6.118 ms
6.078 ms
6.087 ms
6.088 ms
6.111 ms
6.109 ms
6.095 ms
6.106 ms
6.071 ms
6.079 ms
6.068 ms
6.126 ms
6.143 ms
6.125 ms
6.099 ms
6.131 ms
6.076 ms
6.114 ms
6.121 ms
6.101 ms
6.090 ms
6.103 ms
6.081 ms
6.115 ms
6.106 ms
6.094 ms
6.100 ms
6.092 ms
6.082 ms
6.141 ms
6.079 ms
6.075 ms
6.065 ms
6.104 ms
6.070 ms
6.075 ms
6.070 ms
6.067 ms
6.129 ms
6.113 ms
6.089 ms
6.089 ms
6.086 ms
6.123 ms
6.122 ms
6.080 ms
6.108 ms
6.076 ms
6.137 ms
6.078 ms
6.089 ms
6.104 ms
6.148 ms
6.145 ms
6.069 ms
6.104 ms
6.080 ms
6.082 ms
6.073 ms
6.144 ms
6.150 ms
6.064 ms
6.069 ms
6.107 ms
6.065 ms
17.541 ms
17.605 ms
17.627 ms
17.577 ms
17.605 ms
17.619 ms
17.579 ms
17.573 ms
17.579 ms
17.589 ms
17.621 ms
17.590 ms
17.569 ms
18.003 ms
17.998 ms
17.980 ms
17.982 ms
18.003 ms
17.989 ms
18.169 ms
18.005 ms
17.972 ms
17.974 ms
17.985 ms
17.992 ms
18.000 ms
18.018 ms
17.995 ms
17.973 ms
17.970 ms
17.988 ms
17.977 ms
18.027 ms
18.005 ms
17.996 ms
18.011 ms
17.617 ms
17.608 ms
17.544 ms
17.610 ms
17.627 ms
17.581 ms
17.590 ms
17.595 ms
17.601 ms
17.629 ms
17.589 ms
17.604 ms
17.603 ms
17.598 ms
17.616 ms
17.579 ms
17.608 ms
17.625 ms
17.581 ms
17.572 ms
17.584 ms
17.582 ms
17.572 ms
17.978 ms
17.990 ms
17.987 ms
17.987 ms
17.975 ms
17.989 ms
17.982 ms
17.978 ms
17.984 ms
18.005 ms
18.043 ms
17.993 ms
18.003 ms
17.990 ms
18.004 ms
Network path / recorded observations

Network path observations.

16 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.727 msReply RTT ASN unavailable
Before

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 hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop7.155 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hop7.189 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Destination6.375 msReply RTT AS8075 · Microsoft
Before

ICMP traceroute · Recorded address 3

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop20.774 msReply RTT AS8075 · Microsoft
Before

TCP traceroute / 443 · Recorded address 3

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.170 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop49.954 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop8.548 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Destination6.789 msReply RTT AS8075 · Microsoft
During

ICMP traceroute · Recorded address 3

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.245 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 3

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop7.446 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hop7.151 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop7.473 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Probe hopNo replyNo comparable RTT ASN unavailable
  12. TTL 12 Destination6.839 msReply RTT AS8075 · Microsoft
During

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.160 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.849 msReply RTT AS8075 · Microsoft
  3. TTL 3 Probe hop21.631 msReply RTT AS8075 · Microsoft
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.209 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.742 msReply RTT AS8075 · Microsoft
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop7.036 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hop6.303 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Probe hopNo replyNo comparable RTT ASN unavailable
  12. TTL 12 Destination6.437 msReply RTT AS8075 · Microsoft
During

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.136 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.333 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop3.755 msReply RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop6.670 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Destination6.225 msReply RTT AS8075 · Microsoft
After

ICMP traceroute · Recorded address 1

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.110 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.940 msReply RTT ASN unavailable
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.169 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop14.053 msReply RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop104.228 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hopNo replyNo comparable RTT ASN unavailable
  7. TTL 7 Probe hopNo replyNo comparable RTT ASN unavailable
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Probe hopNo replyNo comparable RTT ASN unavailable
  12. TTL 12 Destination6.548 msReply RTT AS8075 · Microsoft
After

ICMP traceroute · Recorded address 4

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.122 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 4

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.132 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop19.225 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop19.217 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop18.267 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop19.929 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hop20.080 msReply RTT AS8075 · Microsoft
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Probe hopNo replyNo comparable RTT ASN unavailable
  12. TTL 12 Probe hopNo replyNo comparable RTT ASN unavailable
  13. TTL 13 Destination17.599 msReply RTT AS8075 · Microsoft
After

ICMP traceroute · Recorded address 4

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.136 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 4

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.141 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.978 msReply RTT AS8075 · Microsoft
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hop19.080 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop19.489 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hopNo replyNo comparable RTT ASN unavailable
  9. TTL 9 Probe hopNo replyNo comparable RTT ASN unavailable
  10. TTL 10 Probe hopNo replyNo comparable RTT ASN unavailable
  11. TTL 11 Probe hopNo replyNo comparable RTT ASN unavailable
  12. TTL 12 Destination18.200 msReply RTT AS8075 · Microsoft

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 3

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.132 msAS8002 · Stealth0.245 msAS8002 · StealthSame responder
220.774 msAS8075 · MicrosoftNot recordedNot established
TCP traceroute / 443 · Recorded address 3

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.170 msAS8002 · Stealth0.160 msAS8002 · StealthSame responder
2No replyNo replyNot established
3No replyNo replyNot established
449.954 msAS8075 · Microsoft7.446 msAS8075 · MicrosoftDifferent responders
58.548 msAS8075 · MicrosoftNo replyNot established
6No reply7.151 msAS8075 · MicrosoftNot established
7No reply7.473 msAS8075 · MicrosoftNot established
8No replyNo replyNot established
9No replyNo replyNot established
10No replyNo replyNot established
116.789 msAS8075 · MicrosoftNo replyNot established
12Not recorded6.839 msAS8075 · MicrosoftNot 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.

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.
  • The measured destination address changed across the comparison period.

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 RTT6.720 msUsual round trip before the event
Last recorded event RTT6.101 msLast successful event recording
Event p95 RTT17.707 ms95th percentile of successful recordings
Change from baseline-0.619 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