==================================================================== SPECTRUM REGIONAL ROUTING DIAGNOSTIC REPORT ISSUE: Regional Node Packet Loss & High Latency Spikes ==================================================================== SUMMARY OF FINDINGS: -------------------- - Local Home Network (Wi-Fi / Deco Mesh / ONT): 0.0% Packet Loss - Primary Bottleneck Node: 65.29.1.28 (lag-25.rcr01clmkohpe.netops.charter.com) - Observed Node Behavior: 5.0% - 9.0% sustained packet loss, latency spikes up to 156ms. - Control Test (Cloudflare WARP/VPN Tunnel): 0.0% Packet Loss across 50/50 test packets. - Conclusion: Physical line and local gear are operational. Bottleneck is isolated to Spectrum's regional routing network in Ohio. -------------------------------------------------------------------- TEST 1: PATHPING DIAGNOSTIC (TO 8.8.8.8) -------------------------------------------------------------------- Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 [REDACTED_LOCAL_CLIENT] 0/ 100 = 0% | 1 17ms 0/ 100 = 0% 0/ 100 = 0% 192.168.68.1 (Local Gateway) 0/ 100 = 0% | 2 30ms 0/ 100 = 0% 0/ 100 = 0% vlan-200.ana03wnhmoh05.netops.charter.com [142.254.228.249] 0/ 100 = 0% | 3 57ms 0/ 100 = 0% 0/ 100 = 0% lag-60.wnhmoh0502h.netops.charter.com [24.164.103.142] 0/ 100 = 0% | 4 29ms 0/ 100 = 0% 0/ 100 = 0% lag-40.pltsohae01r.netops.charter.com [24.33.101.186] 0/ 100 = 0% | 5 39ms 9/ 100 = 9% 9/ 100 = 9% lag-25.rcr01clmkohpe.netops.charter.com [65.29.1.28] 0/ 100 = 0% | 6 47ms 0/ 100 = 0% 0/ 100 = 0% lag-415-10.chctilwc00w-bcr00.netops.charter.com [66.109.6.54] 0/ 100 = 0% | 7 47ms 0/ 100 = 0% 0/ 100 = 0% lag-41.chcgildt87w-bcr00.netops.charter.com [66.109.0.228] 0/ 100 = 0% | 8 40ms 0/ 100 = 0% 0/ 100 = 0% 74.125.48.174 0/ 100 = 0% | 9 42ms 0/ 100 = 0% 0/ 100 = 0% 74.125.251.183 0/ 100 = 0% | 10 --- 100/ 100 =100% 100/ 100 =100% 142.251.60.211 (ICMP Rate Limited) 0/ 100 = 0% | 11 39ms 0/ 100 = 0% 0/ 100 = 0% dns.google [8.8.8.8] -------------------------------------------------------------------- TEST 2: DIRECT CONTINUOUS PING TO AFFECTED NODE (65.29.1.28) -------------------------------------------------------------------- Pinging 65.29.1.28 with 32 bytes of data: Reply from 65.29.1.28: bytes=32 time=18ms TTL=60 Reply from 65.29.1.28: bytes=32 time=13ms TTL=60 Reply from 65.29.1.28: bytes=32 time=73ms TTL=60 Reply from 65.29.1.28: bytes=32 time=16ms TTL=60 ... Request timed out. Request timed out. Reply from 65.29.1.28: bytes=32 time=68ms TTL=60 ... Request timed out. Reply from 65.29.1.28: bytes=32 time=19ms TTL=60 Request timed out. Request timed out. ... Reply from 65.29.1.28: bytes=32 time=156ms TTL=60 ... Reply from 65.29.1.28: bytes=32 time=112ms TTL=60 Ping statistics for 65.29.1.28: Packets: Sent = 100, Received = 95, Lost = 5 (5% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 156ms, Average = 26ms -------------------------------------------------------------------- TEST 3: CONTROL TEST - VIA CLOUDFLARE WARP TUNNEL -------------------------------------------------------------------- Ping statistics for 8.8.8.8 (Over WARP): Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 140ms, Average = 39ms ====================================================================