Can't reach google, gmail, or google+ since early AM March 27 2012

[DTec]

I have a problem where I can't reach google, gmail, or google+ from any computer in my house.  All other sites seem to work fine.  There's more:

I use a VPN connection for work and can reach all these sites through that connection with no problem.

I can reach yahoo and many other sites with no problem.

nslookup resolves as expected with no problem.

Here's the interesting part of tracert:

  3     8 ms     8 ms     8 ms  P0-3.SYRCNY-LCR-01.verizon-gni.net [130.81.35.196]
  4    24 ms    23 ms    23 ms  130.81.28.184
  5    37 ms    20 ms    20 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6    42 ms    24 ms    24 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  7    42 ms    24 ms    25 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8    53 ms    35 ms    35 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

  9    49 ms    32 ms    32 ms  ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
 10    50 ms    33 ms    33 ms  ae-34-80.car4.Washington1.Level3.net [4.69.149.134]
 11    54 ms    35 ms    36 ms  CO-LOCATION.car4.Washington1.Level3.net [4.79.170.254]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

Interesting that 130.81.28.184 isn't named.

When I try to report the problem these Verizon webpage times out:

http://www22.verizon.com/Support/Residential/Internet/HighSpeedInternet/fix.htm

This page comes up basically empty:

http://www22.verizon.com/Support/Residential/Internet/HighSpeed/General+Support/Top+Questions/Top+Qu...

Strange things going on from my point of view.

[DTec · Accepted solution]

I fixed the problem I think.  I rebooted the router and everything works now.

[smith6612]

Sounds to me like a route died and things weren't exactly going well with routing around. Google shouldn't route with Level3 to reach Verizon and vice versa since Verizon has peering with Google right in New York. Since it looks like you're in Syracuse, NY, you should definitely be hitting their peering point from my viewpoint.

Per my trace in the Buffalo area:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>tracert www.google.com

Tracing route to www.l.google.com [173.194.73.105]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     9 ms     9 ms     9 ms  10.15.3.1
  3    10 ms     9 ms     9 ms  so-1-1-0-0.BUFF-CORE-RTR1.verizon-gni.net [130.81.13.73]
  4    20 ms    19 ms    19 ms  as4-0.NY325-BB-RTR1.verizon-gni.net [130.81.20.104]
  5     *       20 ms    20 ms  0.ge-7-0-0.XT1.NYC9.ALTER.NET [152.63.2.73]
  6    22 ms    23 ms    24 ms  0.so-1-0-1.XT1.NYC4.ALTER.NET [152.63.0.213]
  7    20 ms    21 ms    25 ms  TenGigE0-6-4-0.GW8.NYC4.ALTER.NET [152.63.21.121]
  8    21 ms    20 ms    20 ms  google-gw.customer.alter.net [152.179.72.62]
  9    21 ms    21 ms    21 ms  72.14.238.232
 10    31 ms    27 ms    21 ms  209.85.252.2
 11    29 ms    29 ms    33 ms  72.14.239.93
 12    40 ms    40 ms    39 ms  209.85.241.222
 13    39 ms    39 ms    38 ms  216.239.48.103
 14     *        *        *     Request timed out.
 15    52 ms    64 ms    70 ms  vb-in-f105.1e100.net [173.194.73.105]

Trace complete.

C:\Users\>

The Internet is after all a huge, complex network so I'm most likely wrong about how Syracuse routes.