Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 Streamyx Sabah Traceroute to USWEST.battle.net, Lag issues

views
     
TScelentt
post Jan 6 2011, 02:03 PM, updated 15y ago

New Member
*
Newbie
1 posts

Joined: Jan 2011
when I do a traceroute uswest.battle.net I get the following which never reaches Blizzard, anyone else get this?
Doing this from Sabah streamyx

traceroute: Warning: uswest.battle.net has multiple addresses; using 63.241.83.107
traceroute to uswest.battle.net (63.241.83.107), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.834 ms 1.053 ms 0.967 ms
2 219.93.218.177 (219.93.218.177) 29.777 ms * *
3 219.93.218.85 (219.93.218.85) 25.263 ms 26.740 ms 24.266 ms
4 * 10.55.32.110 (10.55.32.110) 50.204 ms 48.851 ms
5 ix-10-0-0-0.tcore1.lvw-losangeles.as6453.net (216.6.84.49) 263.563 ms 261.708 ms 262.036 ms
6 192.205.35.129 (192.205.35.129) 262.025 ms 264.051 ms 261.585 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *

TScelentt
post Jan 6 2011, 03:02 PM

New Member
*
Newbie
1 posts

Joined: Jan 2011
QUOTE(gaeria84 @ Jan 6 2011, 02:27 PM)
Last few hops to a US datacentre are firewalls. If you get the 'Destination Unreachable' error while performing a traceroute, it's normal.
*
I was under the impression that we only hit a firewall after getting to blizzard's doorstep containing
"-USWEST: attens.net (example: mdf2-bi8k-2-eth-1-1.rwc1.attens.net)"

I can see this when I do a traceroute from outside of Malaysia.
Anyone else want to share their traceroutes?

 

Change to:
| Lo-Fi Version
0.0145sec    0.49    6 queries    GZIP Disabled
Time is now: 9th December 2025 - 08:50 PM