Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Big lags started yday ingame/TOFN EU.

STAR WARS: The Old Republic > English > Customer Service (Read-Only)
Big lags started yday ingame/TOFN EU.
 
First BioWare Post First BioWare Post

Roudyzor's Avatar


Roudyzor
12.13.2012 , 06:24 AM | #31
I would just to like to give heads up on whats going on to evreybody who is playing this - I contacted my ISP multiple times and after quite some time received an exact answer on why do I have 160+ MS


BIOWARE SERVERS ARE NOT ALWAYS CAPABLE TO HOLD LARGE AMOUNT OF PLAYERS SO THATS WHY YOU ARE SENT TO USA and YOU PATH GOES TO USA SERVERS IN ORDER for BW TO BE ABLE TO HANDLE LARGE AMOUNT OF PLAYERS ON SERVERS.

I just dont get it....arent you even ashamed of what you do BioWare? Sending players to USA and by USA routs just because ur EU servers are bad? AND IM PAYING MONEY FOR THIS?

Roudyzor's Avatar


Roudyzor
12.14.2012 , 06:35 AM | #32
I understand connecting F2P players to EU servers via USA routs, but I am subscriber...this is just ridiculous

OwenBrooks's Avatar


OwenBrooks
12.14.2012 , 07:45 AM | #33
Quote: Originally Posted by Roudyzor View Post
I would just to like to give heads up on whats going on to evreybody who is playing this - I contacted my ISP multiple times and after quite some time received an exact answer on why do I have 160+ MS


BIOWARE SERVERS ARE NOT ALWAYS CAPABLE TO HOLD LARGE AMOUNT OF PLAYERS SO THATS WHY YOU ARE SENT TO USA and YOU PATH GOES TO USA SERVERS IN ORDER for BW TO BE ABLE TO HANDLE LARGE AMOUNT OF PLAYERS ON SERVERS.

I just dont get it....arent you even ashamed of what you do BioWare? Sending players to USA and by USA routs just because ur EU servers are bad? AND IM PAYING MONEY FOR THIS?
That does not make sense the europe servers are different IPs to the US servers, the backbone that your ISP uses will determine the path you will take from your router to the destination IP.
How can someone play with someone else on the europe servers if you think they are being sent to the US servers ?

Roudyzor's Avatar


Roudyzor
12.14.2012 , 07:55 AM | #34
Quote: Originally Posted by OwenBrooks View Post
That does not make sense the europe servers are different IPs to the US servers, the backbone that your ISP uses will determine the path you will take from your router to the destination IP.
How can someone play with someone else on the europe servers if you think they are being sent to the US servers ?
they are not send to the US servers, they are being sent THROUGH them and then to EU.

Roudyzor's Avatar


Roudyzor
12.14.2012 , 07:57 AM | #35
and this ONLY happens with SWTOR

OwenBrooks's Avatar


OwenBrooks
12.14.2012 , 08:04 AM | #36
Quote: Originally Posted by Roudyzor View Post
and this ONLY happens with SWTOR
The destination is governed by the routing path in the routers made between backbone providers

this is your trouble in level3.net sending this traffic via the US

18 73 ms 73 ms 73 ms ae-1-100.ebr2.Amsterdam1.Level3.net [4.69.141.170]
19 80 ms 80 ms 80 ms ae-47-47.ebr2.London1.Level3.net [4.69.143.78]
20 148 ms 149 ms 147 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

Below is another tracepath via a different Ru ISP backbone

1 <1 мс <1 мс <1 мс
2 <1 мс <1 мс <1 мс
3 1 ms 1 ms <1 мс cs7604-v19.rinet.ru []
4 <1 мс <1 мс <1 мс hq-ix-r2.rinet.net []
5 1 ms 1 ms 1 ms ae3-232.RT.MR.MSK.RU.retn.net [87.245.253.41]
6 23 ms 23 ms 23 ms ae1-7.RT1.TC1.STO.SE.retn.net [87.245.233.22]
7 24 ms 23 ms 23 ms ae1-xcr1.skt.cw.net [166.63.221.217]
8 62 ms 62 ms 62 ms xe-0-3-1-xcr2.amd.cw.net [195.2.9.217]
9 62 ms 71 ms 62 ms ae3-xcr1.amd.cw.net [195.2.30.105]
10 50 ms 50 ms 50 ms xe-4-0-0-xcr1.lsw.cw.net [195.2.25.201]
11 61 ms 61 ms 61 ms xe-11-0-0-xcr1.duc.cw.net [195.2.21.246]
12 63 ms 62 ms 62 ms bioware-gw2.duc.cw.net [195.2.27.90]
13 62 ms 62 ms 62 ms 159.153.72.252

Roudyzor's Avatar


Roudyzor
12.14.2012 , 08:13 AM | #37
Quote: Originally Posted by OwenBrooks View Post
The destination is governed by the routing path in the routers made between backbone providers

this is your trouble in level3.net sending this traffic via the US

18 73 ms 73 ms 73 ms ae-1-100.ebr2.Amsterdam1.Level3.net [4.69.141.170]
19 80 ms 80 ms 80 ms ae-47-47.ebr2.London1.Level3.net [4.69.143.78]
20 148 ms 149 ms 147 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

Below is another tracepath via a different Ru ISP backbone

1 <1 мс <1 мс <1 мс
2 <1 мс <1 мс <1 мс
3 1 ms 1 ms <1 мс cs7604-v19.rinet.ru []
4 <1 мс <1 мс <1 мс hq-ix-r2.rinet.net []
5 1 ms 1 ms 1 ms ae3-232.RT.MR.MSK.RU.retn.net [87.245.253.41]
6 23 ms 23 ms 23 ms ae1-7.RT1.TC1.STO.SE.retn.net [87.245.233.22]
7 24 ms 23 ms 23 ms ae1-xcr1.skt.cw.net [166.63.221.217]
8 62 ms 62 ms 62 ms xe-0-3-1-xcr2.amd.cw.net [195.2.9.217]
9 62 ms 71 ms 62 ms ae3-xcr1.amd.cw.net [195.2.30.105]
10 50 ms 50 ms 50 ms xe-4-0-0-xcr1.lsw.cw.net [195.2.25.201]
11 61 ms 61 ms 61 ms xe-11-0-0-xcr1.duc.cw.net [195.2.21.246]
12 63 ms 62 ms 62 ms bioware-gw2.duc.cw.net [195.2.27.90]
13 62 ms 62 ms 62 ms 159.153.72.252
but whats the reason for level3.net to send me to usa and by usa routs? aint that expesnive for them or smth

OwenBrooks's Avatar


OwenBrooks
12.14.2012 , 08:16 AM | #38
No this is the backbone they have so it makes sense for them to use it.

Amsterdam, London and New York are all Level 3 routers it is their network.

Without knowing Ru ISPs if you swapped to rinet.ru you will get the other path.

Roudyzor's Avatar


Roudyzor
12.14.2012 , 08:58 AM | #39
so its the problem of level3.net?

if it is any advices on how to solve the matter?

OwenBrooks's Avatar


OwenBrooks
12.14.2012 , 09:05 AM | #40
Quote: Originally Posted by Roudyzor View Post
so its the problem of level3.net?

if it is any advices on how to solve the matter?
The maximum permissable hops is meant to be 30 and it appears your current routing path exceeds this because at hop 30 you didn't reach your destination, take both routing paths to comstar and tell them that the current path is unacceptable. What you need is if they can talk to stream or if comstar have alternative to stream and see if a different path can be found for the destination IP address.