It was borked for us on Comcast and Time Warner here in Atlanta from about 14:15 to 14:35 EDT. ------------------ Aubrey Wells Director | Network Services VocalCloud 888.305.3850 support@vocalcloud.com www.vocalcloud.com On Thu, Aug 15, 2013 at 2:49 PM, Anthony Hook <anthony.hook3@gmail.com>wrote:
I'm on a Charter residential line mid-Wisconsin right now and I'm not having any difficulty:
~$ traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 gatekeeper.anthonyrhook.com (192.168.1.1) 0.130 ms 0.189 ms 0.249 ms 2 10.138.192.1 (10.138.192.1) 5.099 ms 9.709 ms 10.642 ms 3 csw01wauswi-gbe-7-26.waus.wi.charter.com (96.34.16.198) 10.885 ms 10.885 ms 10.877 ms 4 crr01stptwi-tge-0-5-0-1.stpt.wi.charter.com (96.34.24.133) 15.480 ms 15.478 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224) 14.448 ms 5 crr02euclwi-tge-0-4-0-1.eucl.wi.charter.com (96.34.17.224) 23.917 ms 24.078 ms 22.857 ms 6 bbr02euclwi-tge-0-1-0-3.eucl.wi.charter.com (96.34.1.246) 21.031 ms 17.909 ms 18.810 ms 7 bbr01chcgil-bue-1.chcg.il.charter.com (96.34.0.9) 31.531 ms 24.120 ms 21.969 ms 8 prr01chcgil-bue-2.chcg.il.charter.com (96.34.3.9) 23.552 ms 24.304 ms 25.542 ms 9 96-34-152-30.static.unas.mo.charter.com (96.34.152.30) 23.117 ms 23.123 ms 22.917 ms 10 209.85.254.120 (209.85.254.120) 23.231 ms 23.261 ms 209.85.254.128 (209.85.254.128) 23.166 ms 11 72.14.237.130 (72.14.237.130) 23.152 ms 72.14.237.108 (72.14.237.108) 23.451 ms 72.14.237.110 (72.14.237.110) 23.434 ms 12 209.85.241.22 (209.85.241.22) 33.422 ms 34.325 ms 31.144 ms 13 216.239.46.191 (216.239.46.191) 33.523 ms 216.239.43.219 (216.239.43.219) 31.478 ms 216.239.46.191 (216.239.46.191) 33.477 ms 14 * * * 15 google-public-dns-a.google.com (8.8.8.8) 36.435 ms 36.632 ms 36.058 ms
$ nslookup google.com 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53
Non-authoritative answer: Name: google.com Address: 173.194.46.70 Name: google.com Address: 173.194.46.72 Name: google.com Address: 173.194.46.78 Name: google.com Address: 173.194.46.67 Name: google.com Address: 173.194.46.68 Name: google.com Address: 173.194.46.65 Name: google.com Address: 173.194.46.71 Name: google.com Address: 173.194.46.66 Name: google.com Address: 173.194.46.64 Name: google.com Address: 173.194.46.73 Name: google.com Address: 173.194.46.69
$ nslookup google.com 8.8.4.4 Server: 8.8.4.4 Address: 8.8.4.4#53
Non-authoritative answer: Name: google.com Address: 173.194.46.70 Name: google.com Address: 173.194.46.72 Name: google.com Address: 173.194.46.78 Name: google.com Address: 173.194.46.67 Name: google.com Address: 173.194.46.68 Name: google.com Address: 173.194.46.65 Name: google.com Address: 173.194.46.71 Name: google.com Address: 173.194.46.66 Name: google.com Address: 173.194.46.64 Name: google.com Address: 173.194.46.73 Name: google.com Address: 173.194.46.69
On Thu, Aug 15, 2013 at 1:23 PM, Bret Clark <bclark@spectraaccess.com>wrote:
Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).
On 08/15/2013 02:16 PM, Nick Lopez wrote:
From my Digital Ocean VPS and office in midtown NY:
$ nslookup google.com 8.8.8.8 ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- - Anthony Hook
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages