Thursday, November 03, 2005

Google is down

I never realised how badly this impacts me. But my work has pritty much grinded to a hault because something is wrong with google.. Never thought it would have such a major impact on me. You forget how much you use google, ohwell, yahoo gets a visit again for a while.

Pinging www.yahoo.akadns.net [66.94.230.43] with 32 bytes of data:
Reply from 66.94.230.43: bytes=32 time=358ms TTL=48

Pinging www.l.google.com [66.102.7.104] with 32 bytes of data:
Request timed out.

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

1 2 ms 7 ms 3 ms SVEASOFT [192.168.1.1]
2 178 ms 108 ms 169 ms lns4.wa.westnet.com.au [202.72.147.250]
3 696 ms 176 ms 86 ms gi1-2.atm.perth.westnet.com.au [202.72.130.101]
4 301 ms 338 ms 466 ms Gigabitethernet2-2.wel19.perth.telstr.net [139.130.128.1]
5 44 ms 56 ms 88 ms GigabitEthernet7-0.wel-core3.Perth.telstra.net [203.50.115.129]
6 264 ms 309 ms 232 ms Pos-channel2.way-core4.Adelaide.telstra.net [203.50.6.193]
7 345 ms 194 ms 219 ms Pos-Channel1.exi-core1.Melbourne.telstra.net [203.50.6.161]
8 791 ms 158 ms 319 ms Pos15-0.chw-core2.Sydney.telstra.net [203.50.6.37]
9 253 ms 92 ms 244 ms 10GigabitEthernet1-0.oxf-core1.Sydney.telstra.net [203.50.6.2]
10 478 ms 131 ms 233 ms 10GigabitEthernet2-2.syd-core03.Sydney.net.reach.com [203.50.13.30]
11 356 ms 590 ms 269 ms i-2-0.sjc-core01.net.reach.com [202.84.140.25]
12 401 ms 362 ms 414 ms unknown.net.reach.com [202.84.251.114]
13 * * * Request timed out.


Neat huh? www.google.com.au still works,..

No comments: