google troubles?

2013-07-10 Thread Mike Jackson
I can see the Google IP space (64.71.240.0/20) from Verizon/AS701, but not from Rogers/AS812 in Toronto. I've done a few other test traceroutes through Rogers to verify that they didn't filter UDP/ICMP. At this point nothing would surprise me from Rogers. AS701 = TOR2-CORE-R1#traceroute www

Re: google troubles?

2013-07-10 Thread Mike Jackson
14 701 6461 812 205.205.23.121 from 205.205.23.121 (137.39.8.42) Origin IGP, localpref 100, valid, external, best TOR2-CORE-R1# Thanks, - Mike On Wed, Jul 10, 2013 at 11:28 AM, Mike Jackson wrote: > I can see the Google IP space (64.71.240.0/20) from Verizon/AS701, but

Re: google troubles?

2013-07-10 Thread Mike Jackson
late) Type escape sequence to abort. Tracing the route to www3.l.google.com (66.185.84.30) Cheers, - Mike On Wed, Jul 10, 2013 at 2:18 PM, Christopher Morrow wrote: > On Wed, Jul 10, 2013 at 12:20 PM, Mike Jackson wrote: > > I just realized that it's not Google IP

Re: google troubles?

2013-07-10 Thread Mike Jackson
>> > >> TOR2-CORE-R1#show ip bgp 66.185.85.29 > >> BGP routing table entry for 66.185.80.0/20, version 13095115 > >> Paths: (1 available, best #1, table default) > >> Advertised to update-groups: > >> 14 > >> 701 6461 812 > >

Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?

2013-10-04 Thread Mike Jackson
The below information is taken from an "internal" router directly connected to 701 == CORE-R1#show ip bgp 200.10.150.169 BGP routing table entry for 200.10.150.0/24, version 46722748 Paths: (1 available, best #1, table default) Not advertis