Has Google blown up?

[FourWheelDrift]

.com & .co.uk are just hanging or is it just a local DNS problem for me. All else seems to be working though.

[BliarOut]

It's just you. Sorry.

[FourWheelDrift]

Maybe I've been banned

[zumbruk]

No, I'm having trouble with Google. Yahoo, PH & the beeb are fine.

Perhaps someone's launched a DoS attck on them?

[aranell]

What ISPs are you all on? I've had a couple of people running BT Broadband complain, but not everyone on BT seems to be affected...just wondering if it's a coincidence or not

[zumbruk]

aranell said:

What ISPs are you all on? I've had a couple of people running BT Broadband complain, but not everyone on BT seems to be affected...just wondering if it's a coincidence or not

Tiscali.

Perhaps the ISPs have decided to drop net neutrality early ...

[FourWheelDrift]

I'm on a BT Broadband connection.

[Kinky]

I'm on BTB and no problems at all - all working 100% AOK - PH, Google, Beeb, etc.

K

[FourWheelDrift]

It comes and goes at the moment, right now it's working.

[FourWheelDrift]

Now it's not working again.

[_dobbo_]

from a command prompt what does a tracert to www.google.co.uk show?

Start->Run->cmd

tracert www.google.co.uk

[FourWheelDrift]

It's working for now, I'll do it when it breaks down again.

[Frik]

It's a familiar feeling to some of us on NTHell.

Unusually not this time though.

[Mrs Trackside]

It's not working for me. I'm on BT broadband

I had trouble with PH a couple of weeks ago.

[hut49]

Dead as a dodo for me too!

[_dobbo_]

Mrs T, if you can't get to google but can get to other sites, it will be for one of four main reasons.

1.) Google is down. This is exceedingly unlikely.
2.) You can't get DNS resolution for google. This would likely be down to your ISPs DNS servers not working.
3.) DNS and Google are both fine, but you have a problem somewhere inbetween you and Google that stops you from getting to the servers.
4.) Your ISP uses proxy servers which aren't working correctly.

2, 3 and 4 are far far more likely to be the cause. There could be other explanations but it gets harder to test for these.

Some checks you can run: Try the tracert test I mentioned above - see what happens. You would expect to see something like this:

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

1 2 ms 2 ms 2 ms localhost.domain.dom [xx.xx.xx.xx]
2 8 ms 8 ms 8 ms 62.7.60.33
3 8 ms 8 ms 8 ms core2-pos6-2.ealing.ukcore.bt.net [194.72.9.253]
4 8 ms 8 ms 8 ms core2-pos1-0-0.telehouse.ukcore.bt.net [194.74.65.121]
5 28 ms 8 ms 8 ms 195.66.226.251
6 8 ms 8 ms 8 ms 195.219.96.70
7 9 ms 9 ms 9 ms ix-9-2.core2.LDN-London.Teleglobe.net [195.219.67.206]
8 9 ms 9 ms 9 ms 72.14.238.242
9 30 ms 29 ms 29 ms 216.239.49.254
10 36 ms 25 ms 19 ms 64.233.174.113
11 29 ms 29 ms 29 ms 72.14.232.239
12 38 ms 32 ms 32 ms 64.233.174.18
13 29 ms 36 ms 35 ms 66.102.9.104

Trace complete.


If this all works as above, then both DNS and connectivity are fine, leaving the only likely cause to be "4" - stinky ISP equipment..

Edited by _dobbo_ on Monday 17th July 21:52

[_dobbo_]

Just re-reading that and marvelling at how many times I managed to use the word likely in such a short time.

[hut49]

So here's the tracert report

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

1 <1 ms <1 ms <1 ms 10.0.0.1
2 10 ms 9 ms 9 ms esr1.ealing5.broadband.bt.net [217.47.155.140]
3 9 ms 10 ms 9 ms 217.47.155.13
4 10 ms 10 ms 9 ms 212.140.233.1
5 10 ms 10 ms 10 ms 217.41.168.66
6 11 ms 10 ms 10 ms 217.41.168.78
7 10 ms 9 ms 10 ms 217.41.168.54
8 9 ms 10 ms 10 ms 217.47.87.242
9 9 ms 10 ms 10 ms core2-pos11-1.ealing.ukcore.bt.net [194.72.17.21
3]
10 10 ms 10 ms 10 ms core2-pos1-0-0.telehouse.ukcore.bt.net [194.74.6
5.121]
11 10 ms 10 ms 10 ms 195.66.226.251
12 17 ms 17 ms 18 ms if-7-0.core1.LHX-London.teleglobe.net [195.219.1
5.214]
13 18 ms 18 ms 18 ms if-1-3.mcore3.LHX-London.teleglobe.net [195.219.
196.13]
14 18 ms 18 ms 18 ms if-6-0.core1.AD1-Amsterdam.teleglobe.net [80.231
.80.29]
15 18 ms 18 ms 18 ms Vlan4.msfc1.AD1-Amsterdam.teleglobe.net [80.231.
82.185]
16 19 ms 18 ms 19 ms Vlan198.msfc1.AD1-Amsterdam.teleglobe.net [80.23
1.82.194]
17 22 ms 21 ms 21 ms 64.233.175.246
18 21 ms 21 ms 21 ms 72.14.233.83
19 24 ms 21 ms 32 ms 66.249.94.54
20 24 ms 22 ms 21 ms 66.249.93.104

Trace complete.

So it looks like BT broadband is the culprit (for me)

[Mrs Trackside]

I think it's likely to be BT, especially as we have 3 computers at home and they all had :

problems with seeing my smilies which are hosted on photobucket

problems getting onto pistonheads when it was working fine for friends and working fine from work.

Now I've got problems with google.

[hut49]

Interesting - if I enter http://66.102.11.99/ I get to the Google UK site and the search engine works fine. If I enter www.google.co.uk I get to the same webpage (apparently) but the search function doesn't work? Doesn't this suggest a DNS problem?

ANyway, if you're having a problem with Google try the above