Start an order
Root cause analysis / Investigation

copilot.com

Reference RCA-71C0214C63436820

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

05 Nov 2026 11:55 – 05 Nov 2026 14:39 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.756 ms
6.821 ms
6.733 ms
6.752 ms
6.737 ms
6.756 ms
6.773 ms
6.755 ms
6.723 ms
6.742 ms
6.787 ms
6.737 ms
6.724 ms
6.752 ms
6.714 ms
6.741 ms
6.751 ms
6.760 ms
6.749 ms
6.739 ms
6.719 ms
6.774 ms
6.740 ms
6.737 ms
6.749 ms
6.757 ms
6.734 ms
6.785 ms
6.716 ms
6.769 ms
6.758 ms
6.753 ms
6.733 ms
6.735 ms
6.737 ms
6.726 ms
6.751 ms
6.736 ms
6.748 ms
6.793 ms
6.748 ms
6.776 ms
6.797 ms
6.743 ms
6.732 ms
6.764 ms
6.706 ms
6.750 ms
6.735 ms
6.740 ms
6.762 ms
6.846 ms
6.724 ms
6.758 ms
6.737 ms
6.796 ms
6.727 ms
6.777 ms
6.747 ms
6.742 ms
6.739 ms
6.741 ms
6.746 ms
6.787 ms
6.773 ms
6.763 ms
6.769 ms
6.731 ms
6.756 ms
7.478 ms
6.750 ms
6.733 ms
6.751 ms
6.766 ms
6.764 ms
6.752 ms
6.752 ms
6.728 ms
6.760 ms
6.740 ms
6.741 ms
6.788 ms
6.734 ms
6.766 ms
6.733 ms
6.749 ms
6.780 ms
6.719 ms
6.742 ms
6.732 ms
6.777 ms
6.733 ms
6.790 ms
6.743 ms
6.748 ms
6.807 ms
6.816 ms
6.720 ms
6.763 ms
6.741 ms
6.743 ms
6.797 ms
6.805 ms
6.750 ms
6.776 ms
6.725 ms
6.759 ms
6.766 ms
6.757 ms
6.731 ms
6.825 ms
6.732 ms
6.734 ms
6.736 ms
6.778 ms
6.775 ms
6.715 ms
6.739 ms
6.717 ms
6.719 ms
22.955 ms
22.934 ms
22.892 ms
22.849 ms
22.829 ms
22.878 ms
22.856 ms
22.837 ms
22.882 ms
22.833 ms
22.873 ms
22.789 ms
22.855 ms
22.860 ms
22.826 ms
22.846 ms
22.830 ms
22.786 ms
22.874 ms
22.851 ms
22.781 ms
22.885 ms
22.854 ms
22.863 ms
22.837 ms
22.826 ms
22.857 ms
22.839 ms
22.869 ms
22.849 ms
22.874 ms
22.826 ms
22.815 ms
22.857 ms
22.829 ms
22.865 ms
22.822 ms
22.851 ms
22.864 ms
22.840 ms
22.871 ms
22.892 ms
22.845 ms
22.872 ms
22.825 ms
22.873 ms
22.862 ms
22.840 ms
22.829 ms
22.900 ms
22.846 ms
22.827 ms
22.820 ms
22.869 ms
22.840 ms
22.865 ms
22.834 ms
22.883 ms
7.120 ms
6.728 ms
6.741 ms
6.742 ms
6.725 ms
6.733 ms
6.882 ms
6.794 ms
6.732 ms
6.748 ms
6.778 ms
6.752 ms
6.775 ms
6.792 ms
6.745 ms
6.840 ms
7.022 ms
6.723 ms
6.760 ms
6.729 ms
6.741 ms
6.760 ms
6.720 ms
6.815 ms
6.721 ms
6.737 ms
6.986 ms
6.752 ms
6.745 ms
6.740 ms
6.743 ms
6.831 ms
6.743 ms
6.720 ms
6.744 ms
6.745 ms
6.740 ms
6.842 ms
6.753 ms
6.770 ms
6.728 ms
6.813 ms
6.758 ms
6.731 ms
6.743 ms
6.749 ms
6.746 ms
6.716 ms
6.794 ms
6.716 ms
6.712 ms
6.737 ms
6.798 ms
7.066 ms
6.763 ms
7.163 ms
6.724 ms
6.730 ms
6.730 ms
6.757 ms
6.734 ms
6.819 ms
6.744 ms
6.708 ms
6.716 ms
6.731 ms
6.747 ms
6.803 ms
6.806 ms
6.746 ms
6.726 ms
6.723 ms
6.706 ms
6.782 ms
7.394 ms
6.723 ms
6.754 ms
6.734 ms
6.733 ms
6.732 ms
6.768 ms
6.712 ms
6.718 ms
6.721 ms
6.744 ms
6.802 ms
6.750 ms
6.816 ms
6.282 ms
6.300 ms
6.264 ms
6.241 ms
6.272 ms
6.335 ms
6.310 ms
6.308 ms
6.320 ms
6.283 ms
6.368 ms
6.306 ms
6.249 ms
6.274 ms
6.276 ms
6.253 ms
6.290 ms
6.293 ms
6.249 ms
6.270 ms
6.268 ms
6.690 ms
6.710 ms
6.708 ms
6.743 ms
6.717 ms
6.706 ms
6.735 ms
6.711 ms
6.723 ms
6.693 ms
6.730 ms
6.764 ms
6.714 ms
6.700 ms
6.736 ms
6.717 ms
6.728 ms
6.721 ms
6.712 ms
6.795 ms
6.721 ms
6.700 ms
6.743 ms
6.731 ms
6.701 ms
6.739 ms
6.723 ms
6.738 ms
6.719 ms
6.707 ms
6.730 ms
6.737 ms
6.711 ms
6.733 ms
6.707 ms
6.723 ms
6.750 ms
6.732 ms
6.733 ms
6.744 ms
6.708 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.119 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.138 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 hop32.870 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop6.420 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 Destination7.032 msReply RTT AS8075 · Microsoft
Before

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.224 msReply RTT AS8002 · Stealth
Before

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.147 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.811 msReply RTT ASN unavailable
  3. TTL 3 Probe hop0.876 msReply RTT AS8075 · Microsoft
  4. TTL 4 Probe hop6.795 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop6.466 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.526 msReply RTT AS8075 · Microsoft
Before

TCP traceroute / 443 · Recorded address 3

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.192 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop4.041 msReply RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop67.388 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop23.596 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop23.342 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop23.724 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hop23.952 msReply RTT AS8075 · Microsoft
  9. TTL 9 Probe hop23.993 msReply RTT AS8075 · Microsoft
  10. TTL 10 Probe hop19.866 msReply RTT AS8075 · Microsoft
  11. TTL 11 Probe hop22.990 msReply RTT AS8075 · Microsoft
  12. TTL 12 Probe hopNo replyNo comparable RTT ASN unavailable
  13. TTL 13 Destination22.980 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.125 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop1.095 msReply RTT ASN unavailable
During

TCP traceroute / 443 · Recorded address 3

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop0.947 msReply RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop24.189 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop23.525 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop25.208 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop24.113 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hop24.405 msReply RTT AS8075 · Microsoft
  9. TTL 9 Probe hop23.686 msReply RTT AS8075 · Microsoft
  10. TTL 10 Probe hop20.104 msReply RTT AS8075 · Microsoft
  11. TTL 11 Probe hop22.922 msReply RTT AS8075 · Microsoft
  12. TTL 12 Probe hopNo replyNo comparable RTT ASN unavailable
  13. TTL 13 Destination24.121 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.128 msReply RTT AS8002 · Stealth
During

TCP traceroute / 443 · Recorded address 3

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.206 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop12.211 msReply RTT AS8075 · Microsoft
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop23.895 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop23.345 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop24.870 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop23.500 msReply RTT AS8075 · Microsoft
  8. TTL 8 Probe hop24.865 msReply RTT AS8075 · Microsoft
  9. TTL 9 Probe hop23.535 msReply RTT AS8075 · Microsoft
  10. TTL 10 Probe hop20.016 msReply RTT AS8075 · Microsoft
  11. TTL 11 Probe hop23.007 msReply RTT AS8075 · Microsoft
  12. TTL 12 Probe hopNo replyNo comparable RTT ASN unavailable
  13. TTL 13 Destination22.978 msReply RTT AS8075 · Microsoft
During

ICMP traceroute · Recorded address 2

Recorded trace · destination not reached by this trace


to UTC

  1. TTL 1 Probe hop0.135 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hop1.035 msReply RTT ASN unavailable
During

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 hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hopNo replyNo comparable RTT ASN unavailable
  4. TTL 4 Probe hop60.207 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hop8.019 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop7.430 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.567 msReply RTT AS8075 · Microsoft
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
After

TCP traceroute / 443 · Recorded address 2

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.311 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 hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop8.828 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop8.106 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop8.436 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.636 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.127 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 1

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.144 msReply RTT AS8002 · Stealth
  2. TTL 2 Probe hopNo replyNo comparable RTT ASN unavailable
  3. TTL 3 Probe hop0.878 msReply RTT AS8075 · Microsoft
  4. TTL 4 Probe hop7.108 msReply RTT AS8075 · Microsoft
  5. TTL 5 Probe hopNo replyNo comparable RTT ASN unavailable
  6. TTL 6 Probe hop81.187 msReply RTT AS8075 · Microsoft
  7. TTL 7 Probe hop8.124 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.297 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.134 msReply RTT AS8002 · Stealth
After

TCP traceroute / 443 · Recorded address 4

Recorded trace · destination replied


to UTC

  1. TTL 1 Probe hop0.172 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 hopNo replyNo comparable RTT ASN unavailable
  5. TTL 5 Probe hop8.327 msReply RTT AS8075 · Microsoft
  6. TTL 6 Probe hop8.288 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.765 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 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.224 msAS8002 · Stealth0.135 msAS8002 · StealthSame responder
2Not recorded1.035 msNot established
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.147 msAS8002 · Stealth0.151 msAS8002 · StealthSame responder
20.811 msNo replyNot established
30.876 msAS8075 · MicrosoftNo replyNot established
46.795 msAS8075 · Microsoft60.207 msAS8075 · MicrosoftDifferent responders
56.466 msAS8075 · Microsoft8.019 msAS8075 · MicrosoftDifferent responders
6No reply7.430 msAS8075 · MicrosoftNot established
7No replyNo replyNot established
8No replyNo replyNot established
9No replyNo replyNot established
10No replyNo replyNot established
116.526 msAS8075 · Microsoft6.567 msAS8075 · MicrosoftSame responder
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.192 msAS8002 · Stealth0.144 msAS8002 · StealthSame responder
24.041 ms0.947 msSame responder
3No replyNo replyNot established
467.388 msAS8075 · Microsoft24.189 msAS8075 · MicrosoftSame responder
523.596 msAS8075 · Microsoft23.525 msAS8075 · MicrosoftSame responder
623.342 msAS8075 · Microsoft25.208 msAS8075 · MicrosoftSame responder
723.724 msAS8075 · Microsoft24.113 msAS8075 · MicrosoftSame responder
823.952 msAS8075 · Microsoft24.405 msAS8075 · MicrosoftSame responder
923.993 msAS8075 · Microsoft23.686 msAS8075 · MicrosoftSame responder
1019.866 msAS8075 · Microsoft20.104 msAS8075 · MicrosoftDifferent responders
1122.990 msAS8075 · Microsoft22.922 msAS8075 · MicrosoftDifferent responders
12No replyNo replyNot established
1322.980 msAS8075 · Microsoft24.121 msAS8075 · MicrosoftSame 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

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.
  • Stored traces were compared using matching source and destination addresses.
  • 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.760 msUsual round trip before the event
Last recorded event RTT6.743 msLast successful event recording
Event p95 RTT22.889 ms95th percentile of successful recordings
Change from baseline-0.017 msLast event RTT compared with the baseline
Successful / expected recordings89 / 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