Google schlecht erreichbar, lokales Problem oder Google-Problem?
Hallo Leute, haben andere auch Probleme, Google zu erreichen? katgar:~ # ping www.google.de PING www.l.google.com (66.249.85.99) 56(84) bytes of data. 64 bytes from 66.249.85.99: icmp_seq=1 ttl=243 time=13.7 ms 64 bytes from 66.249.85.99: icmp_seq=3 ttl=243 time=16.6 ms 64 bytes from 66.249.85.99: icmp_seq=5 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=6 ttl=243 time=12.8 ms 64 bytes from 66.249.85.99: icmp_seq=7 ttl=243 time=13.3 ms 64 bytes from 66.249.85.99: icmp_seq=8 ttl=243 time=11.2 ms 64 bytes from 66.249.85.99: icmp_seq=9 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=11 ttl=243 time=11.0 ms 64 bytes from 66.249.85.99: icmp_seq=12 ttl=243 time=13.3 ms 64 bytes from 66.249.85.99: icmp_seq=13 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=14 ttl=243 time=13.5 ms 64 bytes from 66.249.85.99: icmp_seq=15 ttl=243 time=15.1 ms 64 bytes from 66.249.85.99: icmp_seq=17 ttl=243 time=10.5 ms 64 bytes from 66.249.85.99: icmp_seq=18 ttl=243 time=13.8 ms 64 bytes from 66.249.85.99: icmp_seq=23 ttl=243 time=14.0 ms 64 bytes from 66.249.85.99: icmp_seq=24 ttl=243 time=12.4 ms 64 bytes from 66.249.85.99: icmp_seq=26 ttl=243 time=11.9 ms 64 bytes from 66.249.85.99: icmp_seq=28 ttl=243 time=18.4 ms 64 bytes from 66.249.85.99: icmp_seq=33 ttl=243 time=11.8 ms 64 bytes from 66.249.85.99: icmp_seq=34 ttl=243 time=11.9 ms 64 bytes from 66.249.85.99: icmp_seq=38 ttl=243 time=13.9 ms 64 bytes from 66.249.85.99: icmp_seq=44 ttl=243 time=15.4 ms 64 bytes from 66.249.85.99: icmp_seq=47 ttl=243 time=13.2 ms 64 bytes from 66.249.85.99: icmp_seq=48 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=49 ttl=243 time=11.7 ms 64 bytes from 66.249.85.99: icmp_seq=50 ttl=243 time=11.8 ms --- www.l.google.com ping statistics --- 51 packets transmitted, 26 received, 49% packet loss, time 50034ms rtt min/avg/max/mdev = 10.588/13.177/18.485/1.737 ms Wenn Google antwortet, ist es schnell, aber die Paketverlustrate ist heftig. Bei anderen Hosts de und international tritt dies nicht auf. Sandy -- Antworten bitte nur in die Mailingliste! PMs bitte an: news-reply2 (@) japantest (.) homelinux (.) com
Guten Tag Sandy Drobic, am Samstag, 23. September 2006 um 11:23 schrieben Sie:
Hallo Leute,
haben andere auch Probleme, Google zu erreichen?
katgar:~ # ping www.google.de PING www.l.google.com (66.249.85.99) 56(84) bytes of data. 64 bytes from 66.249.85.99: icmp_seq=1 ttl=243 time=13.7 ms 64 bytes from 66.249.85.99: icmp_seq=3 ttl=243 time=16.6 ms 64 bytes from 66.249.85.99: icmp_seq=5 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=6 ttl=243 time=12.8 ms 64 bytes from 66.249.85.99: icmp_seq=7 ttl=243 time=13.3 ms 64 bytes from 66.249.85.99: icmp_seq=8 ttl=243 time=11.2 ms 64 bytes from 66.249.85.99: icmp_seq=9 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=11 ttl=243 time=11.0 ms 64 bytes from 66.249.85.99: icmp_seq=12 ttl=243 time=13.3 ms 64 bytes from 66.249.85.99: icmp_seq=13 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=14 ttl=243 time=13.5 ms 64 bytes from 66.249.85.99: icmp_seq=15 ttl=243 time=15.1 ms 64 bytes from 66.249.85.99: icmp_seq=17 ttl=243 time=10.5 ms 64 bytes from 66.249.85.99: icmp_seq=18 ttl=243 time=13.8 ms 64 bytes from 66.249.85.99: icmp_seq=23 ttl=243 time=14.0 ms 64 bytes from 66.249.85.99: icmp_seq=24 ttl=243 time=12.4 ms 64 bytes from 66.249.85.99: icmp_seq=26 ttl=243 time=11.9 ms 64 bytes from 66.249.85.99: icmp_seq=28 ttl=243 time=18.4 ms 64 bytes from 66.249.85.99: icmp_seq=33 ttl=243 time=11.8 ms 64 bytes from 66.249.85.99: icmp_seq=34 ttl=243 time=11.9 ms 64 bytes from 66.249.85.99: icmp_seq=38 ttl=243 time=13.9 ms 64 bytes from 66.249.85.99: icmp_seq=44 ttl=243 time=15.4 ms 64 bytes from 66.249.85.99: icmp_seq=47 ttl=243 time=13.2 ms 64 bytes from 66.249.85.99: icmp_seq=48 ttl=243 time=12.5 ms 64 bytes from 66.249.85.99: icmp_seq=49 ttl=243 time=11.7 ms 64 bytes from 66.249.85.99: icmp_seq=50 ttl=243 time=11.8 ms
--- www.l.google.com ping statistics --- 51 packets transmitted, 26 received, 49% packet loss, time 50034ms rtt min/avg/max/mdev = 10.588/13.177/18.485/1.737 ms
Wenn Google antwortet, ist es schnell, aber die Paketverlustrate ist heftig. Bei anderen Hosts de und international tritt dies nicht auf.
Sandy
lana:~ # ping www.google.de PING www.l.google.com (66.102.9.104) 56(84) bytes of data. 64 bytes from 66.102.9.104: icmp_seq=1 ttl=239 time=70.0 ms 64 bytes from 66.102.9.104: icmp_seq=2 ttl=239 time=69.3 ms 64 bytes from 66.102.9.104: icmp_seq=3 ttl=239 time=69.3 ms 64 bytes from 66.102.9.104: icmp_seq=4 ttl=239 time=69.5 ms 64 bytes from 66.102.9.104: icmp_seq=5 ttl=239 time=69.2 ms 64 bytes from 66.102.9.104: icmp_seq=6 ttl=239 time=69.3 ms 64 bytes from 66.102.9.104: icmp_seq=7 ttl=239 time=69.0 ms 64 bytes from 66.102.9.104: icmp_seq=8 ttl=239 time=69.4 ms 64 bytes from 66.102.9.104: icmp_seq=9 ttl=239 time=69.3 ms 64 bytes from 66.102.9.104: icmp_seq=10 ttl=239 time=69.4 ms 64 bytes from 66.102.9.104: icmp_seq=11 ttl=239 time=69.3 ms 64 bytes from 66.102.9.104: icmp_seq=12 ttl=239 time=69.5 ms 64 bytes from 66.102.9.104: icmp_seq=13 ttl=239 time=69.6 ms 64 bytes from 66.102.9.104: icmp_seq=14 ttl=239 time=69.8 ms 64 bytes from 66.102.9.104: icmp_seq=15 ttl=239 time=69.4 ms 64 bytes from 66.102.9.104: icmp_seq=16 ttl=239 time=70.1 ms 64 bytes from 66.102.9.104: icmp_seq=17 ttl=239 time=69.5 ms 64 bytes from 66.102.9.104: icmp_seq=18 ttl=239 time=69.9 ms 64 bytes from 66.102.9.104: icmp_seq=19 ttl=239 time=69.8 ms 64 bytes from 66.102.9.104: icmp_seq=20 ttl=239 time=69.9 ms 64 bytes from 66.102.9.104: icmp_seq=21 ttl=239 time=69.8 ms --- www.l.google.com ping statistics --- 21 packets transmitted, 21 received, 0% packet loss, time 20145ms rtt min/avg/max/mdev = 69.018/69.585/70.122/0.346 ms scheint alles normal. der relativ hohe ping ist ja telekom bedingt. -- Mit freundlichen Grüßen Sebastian Gödecke mailto:sgoedecke@gmx.net
Sandy Drobic schrieb:
Hallo Leute, Hi Sandy
haben andere auch Probleme, Google zu erreichen? [...] --- www.l.google.com ping statistics --- 51 packets transmitted, 26 received, 49% packet loss, time 50034ms rtt min/avg/max/mdev = 10.588/13.177/18.485/1.737 ms
PING www.l.google.com (72.14.221.99) 56(84) bytes of data. --- www.l.google.com ping statistics --- 52 packets transmitted, 52 received, 0% packet loss, time 51509ms rtt min/avg/max/mdev = 25.292/28.440/89.698/11.778 ms PING 66.249.85.99 (66.249.85.99) 56(84) bytes of data. --- 66.249.85.99 ping statistics --- 52 packets transmitted, 52 received, 0% packet loss, time 51509ms rtt min/avg/max/mdev = 24.858/26.168/29.160/0.635 ms Laufzeiten sind normal für echtes ADSL1.
Wenn Google antwortet, ist es schnell, aber die Paketverlustrate ist heftig. Bei anderen Hosts de und international tritt dies nicht auf.
Was sagt denn ein Trace zu google? Evtl. war der eine Server/Router/Switch nur im Moment etwas überlastet?!
Sandy Andy
participants (3)
-
Andreas Gehrke -
Sandy Drobic -
Sebastian Gödecke