I started off by tested with pingplotter from my local machine to comcast.com and was seeing massive latency spikes.
Called customer support, after 6 transfers was told my line had low readings. however the tech wasnt being honest and the line is actually ok it tured out after i looked my self.
Downstream Channel Bonding Value Index 1 2 3 4 5 6 7 8 Lock Status Locked Locked Locked Locked Locked Locked Locked Locked Frequency 669 MHz 627 MHz 633 MHz 639 MHz 645 MHz 651 MHz 657 MHz 663 MHz SNR 37.5 dB 37.2 dB 37.1 dB 37.1 dB 37.2 dB 37.2 dB 37.5 dB 37.4 dB Power -2.2 dBmV -2.6 dBmV -2.5 dBmV -2.2 dBmV -1.8 dBmV -1.8 dBmV -2.0 dBmV -2.1 dBmV Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256
Upstream Channel Bonding Value Index 1 2 3 4 Lock Status Locked Locked Locked Not locked Frequency 21 MHz 34 MHz 27 MHz Symbol Rate 5120 Ksym/sec 5120 Ksym/sec 5120 Ksym/sec Power Level 34.8 dBmV 34.8 dBmV 34.8 dBmV Modulation ATDMA ATDMA ATDMA Channel ID 12 10 11
I wasnt getting anywhere with the tech so I gave in and let them schedule a call.
After the call ended I pinged my public IP (taken from whatismyip.com) from a server hosted on leaseweb and am still seeing the latency spikes
Used "ping -i 3 73.53.139.222" so it would ping at a more reasionable rate of once every 3 seconds.
64 bytes from 73.53.139.222: icmp_req=38 ttl=47 time=3383 ms
64 bytes from 73.53.139.222: icmp_req=39 ttl=47 time=384 ms
64 bytes from 73.53.139.222: icmp_req=40 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=41 ttl=47 time=152 ms
64 bytes from 73.53.139.222: icmp_req=42 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=43 ttl=47 time=152 ms
64 bytes from 73.53.139.222: icmp_req=44 ttl=47 time=149 ms
64 bytes from 73.53.139.222: icmp_req=45 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=46 ttl=47 time=152 ms
64 bytes from 73.53.139.222: icmp_req=47 ttl=47 time=149 ms
64 bytes from 73.53.139.222: icmp_req=48 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=50 ttl=47 time=150 ms
64 bytes from 73.53.139.222: icmp_req=51 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=52 ttl=47 time=151 ms
64 bytes from 73.53.139.222: icmp_req=53 ttl=47 time=152 ms
64 bytes from 73.53.139.222: icmp_req=55 ttl=47 time=2145 ms
After this I called tech support back and they were now able to verify that there is an issue with my connection "beyond the pole" However a tech is still required to visit the physical location in order for the issue to be escalated and fixed.
Its insane that comcast would roll a truck to a home to create a ticket regarding an internal network issue, and the issue is reproducable from external networks. Now im waiting 3 days for a tech to come out, run tests to verify whats publically verifable and create an internal escalation so someone at the NOC can look into the issue.