Laelia wrote:
The servers that have .attens.net are Blizzard's servers. They don't reply to tracert requests, so any hops after you reach them will time out. If you can reach the first one with normal latency, that means there aren't any problems between you and Blizzard.
A traceroute from a Cisco router will also present ASN (Autonomous System Number) data:
Tracing the route to us.logon.worldofwarcraft.com (12.129.232.110)
1 vl-51.uonet1-gw.uoregon.edu (128.223.51.2) [AS 3582] 0 msec 0 msec 0 msec
2 3.xe-1-3-0.uonet10-gw.uoregon.edu (128.223.3.10) [AS 3582] 0 msec 0 msec 0 msec
3 vl-3.uonet9-gw.uoregon.edu (128.223.3.9) [AS 3582] 0 msec 0 msec 0 msec
4 eugn-car1-gw.nero.net (207.98.68.181) [AS 3701] 0 msec 0 msec 0 msec
5 eugn-core1-gw.nero.net (207.98.64.161) [AS 3701] 0 msec 0 msec 0 msec
6 eugnor1wce1-gige7-0.wcg.net (64.200.134.197) [AS 3356] 8 msec 8 msec 8 msec
7 ae-2-52.edge1.Seattle3.Level3.net (4.68.105.44) [AS 3356] 8 msec 8 msec 8 msec
8 192.205.36.153 [AS 7018] 8 msec 8 msec 8 msec
9 cr1.st6wa.ip.att.net (12.122.146.50) [AS 7018] [MPLS: Label 16439 Exp 0] 40 msec 40 msec 36 msec
10 cr2.sffca.ip.att.net (12.122.31.194) [AS 7018] [MPLS: Labels 18639/16008 Exp 0] 40 msec 40 msec 36 msec
11 cr2.la2ca.ip.att.net (12.122.31.133) [AS 7018] [MPLS: Labels 0/16008 Exp 0] 40 msec 40 msec 36 msec
12 cr84.la2ca.ip.att.net (12.123.30.249) [AS 7018] [MPLS: Label 16008 Exp 0] 40 msec 36 msec 40 msec
13 gar5.la2ca.ip.att.net (12.122.129.25) [AS 7018] 40 msec 36 msec 40 msec
14 12.122.255.74 [AS 7018] 36 msec 40 msec 40 msec
15 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) [AS 17233] 36 msec
mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) [AS 17233] 40 msec 40 msec
16 * * *
17 * * *
18 * * *
And ASN 17233 belongs to...
# whois -a 17233
OrgName: AT&T Enhanced Network Services
OrgID: AENS-1
Address: P.O. Box 919014
City: San Diego
StateProv: CA
PostalCode: 92191
Country: US
ASNumber: 17224 - 17233
ASName: ATT-CERFNET-BLOCK
ASHandle: AS17224
Comment:
RegDate: 2000-08-09
Updated: 2000-08-09
RTechHandle: CERF-HM-ARIN
RTechName: ATand T Enhanced Network Services
RTechPhone: +1-858-812-5000
RTechEmail:
[email protected]
It may be Blizzard services, but it's managed through AT&T. Therefore, if anything happens to the connectivity, it's still their fault.
That being said, it's very common to turn off ICMP echo-request and munge up the UDP time to live data that will foil a ping and a traceroute. It's quite probable that the servers that live behind this router were never in fact down at all from a network connectivity standpoint.
And just to throw something in from the for-what-its-worth pile:
# whois -a 12.129.232.110
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
CERFnet ATTENS-LAX1-1 (NET-12-129-192-0-1)
12.129.192.0 - 12.129.255.255
Blizzard Entertainment ATTENS-008916-004056 (NET-12-129-232-0-1)
12.129.232.0 - 12.129.233.255
(Yes, I am uberleet hax0rz coming in from the university of Oregon. That's just how I roll. Never been to Oregon, and don't plan on it any time soon.)
[End ISP Nerd Rage]