Post by jetjockPost by PaulPost by jetjockSecond day now that Yahoo.com is down. Just me, or others having a
problem too?
When sites have load distribution and are trying to be globe-wide,
individual outages could quite easily happen for reasons we can't see.
My result is likely too far from you to be meaningful. But generally
speaking "they're not out of business at the moment".
*******
http://news.yahoo.com/ Working
(that's one of those infinite-scroll pages like an ntp.msn.com)
http://www.yahoo.com/ [redirects to country-specific page https://ca.yahoo.com/?p=us ]
All of those Sites return the same message: "We can't connect to the
server at xxx.yahoo.com".
As I told Frank Slootweg, it appears to be Win 7 specific.
Run
nslookup some.dodgy.site
and DNS should list IPV4 and IPV6 addresses for you.
If you run this kind of command
ping 44.33.222.111
then you can try to get an IPV4 ping response. "Ping" is at a level that
the ends of the link do not care about WinXP, Win7, Win12. That command
works in Linux, Unix, FreeBSD, MacOS, Windows.
ping # Name is the same everywhere
nslookup # Name is the same everywhere
tracert # Can be tracert or traceroute, depending on length restrictions
Servers can be configured to not support ping. All of ICMP can be
turned off (not a good thing to do). Or just the ping component
of ICMP can be turned off. Both ping and tracert are doing "ping-like things"
C:\>ping 66.218.84.40
Pinging 66.218.84.40 with 32 bytes of data:
Reply from 66.218.84.40: bytes=32 time=16ms TTL=54
Reply from 66.218.84.40: bytes=32 time=16ms TTL=54
Reply from 66.218.84.40: bytes=32 time=16ms TTL=54
Reply from 66.218.84.40: bytes=32 time=16ms TTL=55
Ping statistics for 66.218.84.40:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 16ms, Average = 16ms
C:\>
The other thing you can try, low level, is traceroute
C:\>tracert 66.218.84.40
Tracing route to o3.ycpi.vip.bf1.yahoo.com [66.218.84.40]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 12 ms 12 ms [my ISP]
3 13 ms 12 ms 13 ms [my ISP]
4 15 ms 15 ms 15 ms yahoo-xe1.torontointernetxchange.net [206.108.35.41]
5 22 ms 19 ms 19 ms ae-2.pat1.bfz.yahoo.com [209.191.64.167]
6 16 ms 20 ms 16 ms et-9-0-8.msr2.bf1.yahoo.com [74.6.227.139]
7 18 ms 15 ms 16 ms et-18-0-0.clr2-a-gdc.bf1.yahoo.com [74.6.122.37]
8 16 ms 16 ms 16 ms lo0.fab1-2-gdc.bf1.yahoo.com [74.6.123.228]
9 16 ms 15 ms 16 ms lo0.usw1-1-lba.bf1.yahoo.com [98.137.192.166]
10 15 ms 15 ms 15 ms o3.ycpi.vip.bf1.yahoo.com [66.218.84.40]
Trace complete.
C:\>
Almost none of the intermediate nodes, should match what yours shows.
The Internet is efficient and picks reasonably short paths, without
"going around the world twice" by accident :-)
Be patient with tracert. It takes time.
If both ping and tracert work, maybe it does not like your browser.
If that was the case, it *still* takes a few packets to make a white
screen and a "Done" at the bottom of the page. If the TCP/IP is broken,
then there won't be a "Done" and eventually, there will be a comms failure
message in the middle of the browser. Give it two minutes.
Paul