This is what I'm seeing.... (Note: We aren't actually a Cogent customer, but it looks as if this upstream uses them for one of THEIR upstreams... I know they have several...) # traceroute www.google.com traceroute: Warning: www.google.com has multiple addresses; using 64.233.179.99 traceroute to www.l.google.com (64.233.179.99), 30 hops max, 38 byte packets 1 7206-ge-0-1-10 (207.244.153.1) 1.840 ms 0.258 ms 0.652 ms 2 208.99.192.133 (208.99.192.133) 2.312 ms 1.822 ms 1.702 ms 3 204.8.32.85 (204.8.32.85) 1.702 ms 2.318 ms 1.273 ms 4 38.112.26.185 (38.112.26.185) 2.356 ms 2.318 ms 2.350 ms 5 g3-8.core01.sea01.atlas.cogentco.com (66.250.15.137) 2.218 ms 2.083 ms 2.955 ms 6 p14-0.core01.sfo01.atlas.cogentco.com (66.28.4.54) 32.661 ms 32.820 ms 32.382 ms 7 p15-0.core01.sfo01.atlas.cogentco.com (66.28.4.69) 32.386 ms 32.870 ms 33.349 ms 8 p4-0.core01.sjc01.atlas.cogentco.com (66.28.4.94) 32.823 ms 32.072 ms 32.652 ms 9 g12-0-0.core01.sjc03.atlas.cogentco.com (154.54.2.238) 31.998 ms 31.737 ms 32.092 ms 10 google.sjc03.atlas.cogentco.com (154.54.10.254) 22.814 ms 22.389 ms 21.870 ms 11 66.249.94.2 (66.249.94.2) 23.564 ms 23.119 ms 23.220 ms 12 * * * It peters out after that. That last hop IS Google though... I wonder if it could be a routing issue where that traffic can't find their way back to me...(?) I have an InterNAP connection as well, and things are working fine if they pass through there. Thanks, Rick On Mon, 17 Apr 2006, Tuc at T-B-O-H wrote:

...

Is anyone else having problems reaching Google through Cogent's network right now?

What signs are you seeing? Can you show pings/traceroutes/mtr/etc.

Thanks, Tuc/TBOH