Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 High Latency - US server

views
     
TSjexmond
post Sep 25 2014, 06:57 PM, updated 12y ago

New Member
*
Junior Member
11 posts

Joined: Apr 2006


Hey guys, anyone of you having severely bad latency like 2-3 days back ? I'm not sure if that happens only me :/
nate_nightroad
post Sep 25 2014, 07:00 PM

Endless numbered days...
*******
Senior Member
3,639 posts

Joined: Mar 2007


http://www.lowyat.net/2014/09/fault-in-aag...southeast-asia/
SUStlts
post Sep 25 2014, 07:06 PM

pee poo pee poo
******
Senior Member
1,891 posts

Joined: Apr 2008
From: Cheras
yesterday still ok...but NOW the latesy is insane rubber banding...no mood to play like that
kofan
post Sep 25 2014, 09:22 PM

New Member
*
Junior Member
7 posts

Joined: Sep 2006
From: Subang Jaya


keep disconnect from server
olman
post Sep 25 2014, 11:48 PM

Regular
******
Senior Member
1,998 posts

Joined: Jan 2003


cant login, stuck at retrieving hero list
SUStlts
post Sep 26 2014, 06:45 AM

pee poo pee poo
******
Senior Member
1,891 posts

Joined: Apr 2008
From: Cheras
as of now....all conection back to normal liao...green bar 250ms US server rclxms.gif
Quazacolt
post Sep 26 2014, 11:00 AM

Riding couple
*******
Senior Member
5,365 posts

Joined: Jan 2007
From: KL Malaysia


aus servers also sometimes congested thanks to reroutes.
cowithgun
post Sep 26 2014, 12:18 PM

A cow that can play notebook & phone
*******
Senior Member
2,248 posts

Joined: Sep 2010
About the AU server, I ran tcpdump (actually wireshark) a couple days ago and discovered that no matter if you set "OnlineService.Matchmaking.ServerPool=AU1" or not, it will still go to US server.

Today I ran it again, seem like it's back to normal. During gameplay, it will constantly connect to (for me) 12.130.244.193 and the actual game server depending on server you chose:

US Server: 12.130.245.39
AU Server: 103.4.114.11

Did a traceroute to these IP, I discovered something else. Unifi line actually hop less and faster to US server (today!). Yes 4G still using reroute in Japan and HongKong.

Just for info, you also can use http://us-looking-glass.battle.net/ to see how the packet travel from Blizzard to you. biggrin.gif It changes daily! LOL! Yesterday, both Unifi and 4G uses hop in Japan and HongKong. Today, Unifi uses hop in Singapore. 4G Yes still using Japan (which sloooowwww...)


SUSAzurues
post Sep 26 2014, 12:22 PM

▲▲▲▲
*****
Senior Member
958 posts

Joined: Aug 2007
From: forum.lowyat.net



Was ok for me yesterday night time until around 11pm.

Not sure today
deathTh3Cannon
post Sep 26 2014, 01:34 PM

Getting Started
**
Junior Member
248 posts

Joined: Aug 2011
yest ping reacch till 23**.. OMG.. unifi 5 mbps.
I<3LYN
post Sep 26 2014, 02:06 PM

On my way
****
Senior Member
614 posts

Joined: Sep 2009


QUOTE(cowithgun @ Sep 26 2014, 12:18 PM)
About the AU server, I ran tcpdump (actually wireshark) a couple days ago and discovered that no matter if you set "OnlineService.Matchmaking.ServerPool=AU1" or not, it will still go to US server.

Today I ran it again, seem like it's back to normal. During gameplay, it will constantly connect to (for me) 12.130.244.193 and the actual game server depending on server you chose:

US Server: 12.130.245.39
AU Server: 103.4.114.11

Did a traceroute to these IP, I discovered something else. Unifi line actually hop less and faster to US server (today!). Yes 4G still using reroute in Japan and HongKong.

Just for info, you also can use http://us-looking-glass.battle.net/ to see how the packet travel from Blizzard to you. biggrin.gif It changes daily! LOL! Yesterday, both Unifi and 4G uses hop in Japan and HongKong. Today, Unifi uses hop in Singapore. 4G Yes still using Japan (which sloooowwww...)
*
you missed something.

there are 2 separated 'connections'

battle.net authentication/communication uses tcp
game uses udp packets

the client will first authenticate with the actual battle.net server and its authentication service
then the client/battle.net will decide which game server to connect.


running tcpdump (or wireshark with the wrong parameters) will not get you anything.

regardless of which game server you choose, the client will always authenticated at the us/eu/asia server first.

This post has been edited by I<3LYN: Sep 26 2014, 02:07 PM
DarkNite
post Sep 26 2014, 03:10 PM

ФĻĐ ИΞШB!Ξ
********
All Stars
11,058 posts

Joined: Jun 2008
How to connect to aussie server?
cowithgun
post Sep 26 2014, 04:47 PM

A cow that can play notebook & phone
*******
Senior Member
2,248 posts

Joined: Sep 2010
QUOTE(I<3LYN @ Sep 26 2014, 02:06 PM)
you missed something.

there are 2 separated 'connections'

battle.net authentication/communication uses tcp
game uses udp packets

the client will first authenticate with the actual battle.net server and its authentication service
then the client/battle.net will decide which game server to connect.
running tcpdump (or wireshark with the wrong parameters) will not get you anything.

regardless of which game server you choose, the client will always authenticated at the us/eu/asia server first.
*
i have the same understanding, that is why i said, those are capture during gameplay.

US Server: 12.130.245.39
AU Server: 103.4.114.11

if you trace those IP, you will see that they are hosting in the respective country, which indicates that this is the game server and not the authentication server. and again, i was checking the network packet during game play not the authentication process.

another thing, contrary to popular believe, D3 game play use TCP connection and not UDP. smile.gif

ps:

QUOTE
running tcpdump (or wireshark with the wrong parameters) will not get you anything.
are u indicating that i may not know how to use tcpdump/wireshark? i am just a little, slightly, offended with that comment... sad.gif

This post has been edited by cowithgun: Sep 26 2014, 05:36 PM
I<3LYN
post Sep 26 2014, 08:13 PM

On my way
****
Senior Member
614 posts

Joined: Sep 2009


QUOTE(cowithgun @ Sep 26 2014, 04:47 PM)
i have the same understanding, that is why i said, those are capture during gameplay.

US Server: 12.130.245.39
AU Server: 103.4.114.11

if you trace those IP, you will see that they are hosting in the respective country, which indicates that this is the game server and not the authentication server. and again, i was checking the network packet during game play not the authentication process.

another thing, contrary to popular believe, D3 game play use TCP connection and not UDP. smile.gif

ps:
are u indicating that i may not know how to use tcpdump/wireshark? i am just a little, slightly, offended with that comment...  sad.gif
*
don't be offended, i didn't mean that.

it is good to learn that d3 game protocol uses tcp instead of udp.



TSjexmond
post Sep 29 2014, 05:07 PM

New Member
*
Junior Member
11 posts

Joined: Apr 2006


finally it's back to normal

 

Change to:
| Lo-Fi Version
0.0138sec    0.35    5 queries    GZIP Disabled
Time is now: 26th November 2025 - 04:44 AM