Comcast is having some serious latency issues today here in New England. Here's a sample of an extended ping test:
64 bytes from 4.2.2.1: icmp_seq=29 ttl=245 time=692.306 ms 64 bytes from 4.2.2.1: icmp_seq=30 ttl=245 time=14.676 ms 64 bytes from 4.2.2.1: icmp_seq=31 ttl=245 time=15.476 ms 64 bytes from 4.2.2.1: icmp_seq=32 ttl=245 time=22.278 ms 64 bytes from 4.2.2.1: icmp_seq=33 ttl=245 time=17.601 ms 64 bytes from 4.2.2.1: icmp_seq=34 ttl=245 time=16.962 ms 64 bytes from 4.2.2.1: icmp_seq=35 ttl=245 time=16.724 ms 64 bytes from 4.2.2.1: icmp_seq=36 ttl=245 time=16.030 ms 64 bytes from 4.2.2.1: icmp_seq=37 ttl=245 time=16.624 ms 64 bytes from 4.2.2.1: icmp_seq=38 ttl=245 time=16.592 ms 64 bytes from 4.2.2.1: icmp_seq=39 ttl=245 time=31.364 ms 64 bytes from 4.2.2.1: icmp_seq=40 ttl=245 time=25.638 ms 64 bytes from 4.2.2.1: icmp_seq=41 ttl=245 time=375.706 ms 64 bytes from 4.2.2.1: icmp_seq=42 ttl=245 time=17.400 ms 64 bytes from 4.2.2.1: icmp_seq=43 ttl=245 time=26.002 ms 64 bytes from 4.2.2.1: icmp_seq=44 ttl=245 time=19.152 ms 64 bytes from 4.2.2.1: icmp_seq=45 ttl=245 time=1623.906 ms 64 bytes from 4.2.2.1: icmp_seq=46 ttl=245 time=621.079 ms 64 bytes from 4.2.2.1: icmp_seq=47 ttl=245 time=19.087 ms 64 bytes from 4.2.2.1: icmp_seq=48 ttl=245 time=24.977 ms 64 bytes from 4.2.2.1: icmp_seq=49 ttl=245 time=18.197 ms 64 bytes from 4.2.2.1: icmp_seq=50 ttl=245 time=16.497 ms 64 bytes from 4.2.2.1: icmp_seq=51 ttl=245 time=19.426 ms 64 bytes from 4.2.2.1: icmp_seq=52 ttl=245 time=18.620 ms
I called technical support and spoke with George, who confirmed there was work going on in the area.
