cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
3,240 Views
Message 1 of 35

Problem reaching Google?

Go to solution

Is anyone else having issues reaching Google services tonight?

 

Through my BT Internet connection direct, I cannot access http://google.com/:

 

>tracert google.com

Tracing route to google.com [31.55.184.117]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    19 ms    20 ms    19 ms  31.55.187.212
  5     *        *        *     Request timed out.
  6     *       21 ms    21 ms  31.55.184.32
  7    22 ms    21 ms    21 ms  31.55.184.33
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *     31.55.184.33  reports: Destination net unreachable.

Trace complete.

 

 

Through a VPN I have no issues:

 

>tracert google.com

Tracing route to google.com [74.125.232.103]
over a maximum of 30 hops:

  1    53 ms    52 ms    53 ms  anon-37-3.vpn.ipredator.se [46.246.37.3]
  2    52 ms    54 ms    52 ms  anon-33-1.vpn.ipredator.se [46.246.33.1]
  3    55 ms    53 ms    54 ms  te2-3.ccr01.mmx01.atlas.cogentco.com [149.6.48.2
9]
  4    52 ms    52 ms    52 ms  te0-1-0-2.rcr21.cph01.atlas.cogentco.com [154.54
.59.101]
  5    58 ms    58 ms    58 ms  be2303.ccr41.ham01.atlas.cogentco.com [130.117.3
.161]
  6    67 ms    67 ms    67 ms  be2257.ccr41.fra03.atlas.cogentco.com [130.117.4
9.29]
  7    67 ms    67 ms    68 ms  be2184.agr21.fra03.atlas.cogentco.com [130.117.4
8.69]
  8    79 ms    80 ms    78 ms  149.6.42.46
  9    76 ms    76 ms    77 ms  209.85.240.64
 10    96 ms    81 ms    77 ms  72.14.234.231
 11    77 ms    77 ms    77 ms  209.85.242.187
 12    77 ms    77 ms    77 ms  216.239.43.45
 13    77 ms    77 ms    77 ms  209.85.254.30
 14    77 ms    77 ms    77 ms  209.85.253.149
 15    76 ms    76 ms    77 ms  arn02s05-in-f7.1e100.net [74.125.232.103]

Trace complete.

 

google.com, google.co.uk, seems to make no difference - can't access either direct.

 

Non-google websites seem unaffected.

0 Ratings
34 REPLIES 34
Highlighted
Distinguished Sage
Distinguished Sage
3,235 Views
Message 2 of 35

Re: Problem reaching Google?

Go to solution

No issues here other than your google link doesn't work because of the http://google.com/: double dots on the end.

0 Ratings
Highlighted
Contributor
3,229 Views
Message 3 of 35

Re: Problem reaching Google?

Go to solution

Hmm, definately something wrong here (01275).

 

Rebooted modem and router, no change.

0 Ratings
Highlighted
Distinguished Sage
3,223 Views
Message 4 of 35

Re: Problem reaching Google?

Go to solution
no problems here either south east kent
0 Ratings
Highlighted
Aspiring Contributor
3,195 Views
Message 5 of 35

Re: Problem reaching Google?

Go to solution
0 Ratings
Highlighted
Distinguished Guru
3,162 Views
Message 6 of 35

Re: Problem reaching Google?

Go to solution

It's working for me

>tracert google.com

Tracing route to google.com [74.125.230.136]
over a maximum of 30 hops:

  1   216 ms    99 ms    99 ms  BThomehub.home [192.168.1.254]
  2     9 ms     9 ms     9 ms  217.32.145.132
  3    12 ms     9 ms     9 ms  217.32.145.174
  4    10 ms     9 ms     9 ms  213.120.156.218
  5    10 ms     9 ms    10 ms  217.41.168.43
  6    10 ms     9 ms     9 ms  217.41.168.107
  7    10 ms     9 ms    10 ms  acc1-10GigE-0-2-0-5.l-far.21cn-ipp.bt.net [109.1
59.249.99]
  8    10 ms    10 ms    10 ms  core4-te0-0-0-18.faraday.ukcore.bt.net [109.159.
249.45]
  9    12 ms    10 ms    12 ms  peer5-te0-0-0-5.telehouse.ukcore.bt.net [194.72.
31.93]
 10    10 ms    11 ms    10 ms  109.159.253.67
 11    11 ms    11 ms    14 ms  209.85.244.184
 12    10 ms    11 ms    10 ms  209.85.250.171
 13    11 ms    10 ms    10 ms  lhr08s05-in-f8.1e100.net [74.125.230.136]

Trace complete.

 (for those who are wondering, 1e100.net is an alias that Google uses)

0 Ratings
Highlighted
Beginner
3,130 Views
Message 7 of 35

Re: Problem reaching Google?

Go to solution

Yeah this issue mirrors 2 similar topics in this category relating to BT suddenly disrupting access to Google services. I've been upable to use YouTube and Google Play since Wednesday evening. Both work flawlessly from my mobile network (EE) and from another ISP but whether wired or otherwise, BT refuses to play videos or update my apps, whether it be on my phone, desktop PC, tablet or home consoles. I placed a call to them early evening and went through every user contributed action to get it to work but to no avail and the rep said it was the first he has heard of it and until such time as the issue becomes widespread then it wouldn't be considered an issue.

I know BT have recently gone on a tear, blocking certain websites (sans court order, weirdly enough.) I can only surmise that something happened during the blocking caused Google services to be blocked for some.

Another user found that restarting your router and gaining a fresh IP may solve this issue. Including the couple of time BT asked me to restart I have tried this 9 times to no avail, so hopefully BT can shed some light on it. I have Dundee's technical support number, which I'm going to use in the morning and hopefully I can get some results here - any of which will be posted in the YouTube issues thread.

Good luck to all suffering.

Edit, I did similar routetrace and only found it timing out requests on a couple of entries. Not sure if that means I should or shouldn't be able to access. All I know is I can't. heh.

tracert google.com

Tracing route to google.com [74.125.230.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    11 ms    12 ms    11 ms  31.55.187.224
  5    13 ms    13 ms    13 ms  195.99.127.52
  6    16 ms    15 ms    15 ms  peer5-te0-9-0-5.telehouse.ukcore.bt.net [194.72.
31.83]
  7    12 ms    12 ms    12 ms  109.159.253.67
  8    12 ms    12 ms    12 ms  209.85.244.182
  9    14 ms    13 ms    14 ms  72.14.238.185
 10    12 ms    12 ms    13 ms  lhr14s24-in-f3.1e100.net [74.125.230.99]

Trace complete.
0 Ratings
Highlighted
Aspiring Contributor
3,119 Views
Message 8 of 35

Re: Problem reaching Google?

Go to solution

Yes, having the exact same problem here since last night. Rebooted my router this morning with no effect. I can also access all Google services via a VPN but straight though I'm getting nothing at all.

 

 

0 Ratings
Highlighted
Contributor
3,112 Views
Message 9 of 35

Re: Problem reaching Google?

Go to solution

Okay, having looked a little more into it it seems to be a problem if you do not use BT DNS

 

If you -are- using BT DNS then Google services resolve to a BT IP range (whaaat?) - and this works

 

If you use a non-Google DNS (Google's 8.8.8.8, OpenDNS, etc) then Google resolves to the proper IPs, but BT now doesn't route them.

 

This is NOT good.

 

I want to be able to use my own choice of DNS, as I have for the past years.

 

Problem started yesterday morning.

Highlighted
Expert
3,090 Views
Message 10 of 35

Re: Problem reaching Google?

Go to solution

Same problem here as CH.

I think the Chromecast issue I have is related to it having a hardcoded DNS setting as even resetting the DNS on router and AP doesn't help.

 

Not happy.

0 Ratings