64 bytes from 50.174.106.1: icmp_seq=579 ttl=255 time=180.391 ms
64 bytes from 50.174.106.1: icmp_seq=580 ttl=255 time=191.445 ms
64 bytes from 50.174.106.1: icmp_seq=581 ttl=255 time=184.840 ms
64 bytes from 50.174.106.1: icmp_seq=582 ttl=255 time=100.994 ms
64 bytes from 50.174.106.1: icmp_seq=583 ttl=255 time=123.883 ms
64 bytes from 50.174.106.1: icmp_seq=584 ttl=255 time=78.710 ms
64 bytes from 50.174.106.1: icmp_seq=585 ttl=255 time=97.007 ms
64 bytes from 50.174.106.1: icmp_seq=586 ttl=255 time=120.788 ms
64 bytes from 50.174.106.1: icmp_seq=587 ttl=255 time=137.364 ms
64 bytes from 50.174.106.1: icmp_seq=588 ttl=255 time=146.512 ms
64 bytes from 50.174.106.1: icmp_seq=589 ttl=255 time=19.653 ms
Request timeout for icmp_seq 597
Request timeout for icmp_seq 598
Request timeout for icmp_seq 599
Request timeout for icmp_seq 600
Request timeout for icmp_seq 601
Request timeout for icmp_seq 602
Request timeout for icmp_seq 603
Request timeout for icmp_seq 604
Request timeout for icmp_seq 605
Request timeout for icmp_seq 606
Request timeout for icmp_seq 607
Request timeout for icmp_seq 608
Request timeout for icmp_seq 609
64 bytes from 50.174.106.1: icmp_seq=608 ttl=255 time=2862.261 ms
64 bytes from 50.174.106.1: icmp_seq=609 ttl=255 time=1861.965 ms
64 bytes from 50.174.106.1: icmp_seq=610 ttl=255 time=862.106 ms
64 bytes from 50.174.106.1: icmp_seq=611 ttl=255 time=10.016 ms
64 bytes from 50.174.106.1: icmp_seq=612 ttl=255 time=22.393 ms
Request timeout for icmp_seq 615
Request timeout for icmp_seq 616
Request timeout for icmp_seq 617
Request timeout for icmp_seq 618
The Comcast support rep was unable to find anything wrong, despite understanding all the information above. He said he could not receive email so I could not supply this info and could only suggest that yet another tech should come out.
10 minutes after I agree to send another tech and hang up, the connection is again working fine:
$ ping 50.174.106.1
PING 50.174.106.1 (50.174.106.1): 56 data bytes
64 bytes from 50.174.106.1: icmp_seq=0 ttl=254 time=38.244 ms
64 bytes from 50.174.106.1: icmp_seq=1 ttl=254 time=13.285 ms
64 bytes from 50.174.106.1: icmp_seq=2 ttl=254 time=12.524 ms
64 bytes from 50.174.106.1: icmp_seq=3 ttl=254 time=11.720 ms
64 bytes from 50.174.106.1: icmp_seq=4 ttl=254 time=10.986 ms
64 bytes from 50.174.106.1: icmp_seq=5 ttl=254 time=14.048 ms
64 bytes from 50.174.106.1: icmp_seq=6 ttl=254 time=12.569 ms
^C
--- 50.174.106.1 ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.986/16.197/38.244/9.048 ms
I monitor my home connection with Pingdom. The 30 day results are quite telling:
Yes, my connection has been down 102 times in the last 30 days. If you look at the last 7 days, the week I've had to work from home recovering from knee surgery, when I really need my connection to be reliable:
The Comcast tech support guy agreed with my assessment that there's got to be a problem somewhere upstream, and that yes, there's some advanced networking group within Comcast whose job it is to fix this issue. He did not however know how to contact that group, nor do I.
In a previous attempt to cancel, the retention specialist vowed to find that group and get them engaged. But I never heard back and continue to have this issue. Then the next retention specialist who begged for one last chance said she would do a "thorough review" of the account notes and call me back. She never did.
Why am I still with Comcast? Because when it works, it works well and is somewhat reasonably priced (as long as you threaten to cancel if you don't get the promo pricing). ATT Uverse is not a great option, and there's only one other cable provider in my area (Astound) with decent bandwidth but their cable offerings are subpar.
So Comcast, here's the challenge: fix my internet, this week, or I'm switching to Astound for internet and I'll happily go back to Dish for my TV needs, or just cut the cord.