31 replies to this topic

[_stellabug_]

put your head between your knees and kiss your fun goodbye...

 

(Noon Australia = 9pm New York USA)

Currently Ping from Australia to Blitz West Coast Server 175ms

current server load West Coast ~9,000
Ping the East Coast Blitz Server ~225ms

current server load East Coast ~23,000

 

Load Blitz, Enter battle, you now have 30 seconds to get somewhere that you can shoot blind for the rest of the game.

At the 30 second mark ping starts climbing, climbs rapidly until it exceeds 250,000ms, at which point disconnected from server.

why?

All other internet activity is uninterrupted, so I not getting randomly bombed, and my isp is not dropping packets.

SB>(dad)

(Archos Platinum 80b, Android 4.2.2)

Edited by _stellabug_, 19 January 2016 - 03:12 AM.

[MSixteen]

I enjoyed the title of this thread.

[_Willy]

the ping isn't that bad.

[LoweExpectations]

My ping is a stable 20-30 still.

[reluctanttheist]

Ok guys, let's work the problem here: so SB, you're in Australia? and trying to connect to WG's NA server?  Have you tried the Asia server?

[tlouie]

This can't be right. The current wotb server load is 13,000.

 

https://api.worldoft...=demo&game=wotb

 

{"status":"ok","data":{"wotb":[{"players_online":13171,"server":"NA"}]}}

Edited by tlouie, 19 January 2016 - 03:30 AM.

[acrisis]

SB, is that cable still out as linked in the other thread?

Can you post traceroutes to login.wotblitz.com?
Just overwrite over your own IP for privacy 

 

 

[Camoisland]

no lag here (?)

[_stellabug_]

acrisis, on 19 January 2016 - 03:41 AM, said:

SB, is that cable still out as linked in the other thread?

Can you post traceroutes to login.wotblitz.com?
Just overwrite over your own IP for privacy

 

I cant find the thread about the cable -

this is the trace route - why am I going from AUS through Europe on the way to USA - why not straight to West Coast?

How do I configure Blitz to use West Coast Server????

my IP changes each router reboot

 1     1 ms     1 ms    <1 ms  192.168.1.1
  2    86 ms     *      150 ms  lo0.bng1.bne7.on.ii.net [150.101.32.93]
  3    84 ms    64 ms    66 ms  ae3.cr1.bne7.on.ii.net [150.101.34.30]
  4    62 ms    86 ms    70 ms  ae6.br1.syd4.on.ii.net [150.101.33.12]
  5   213 ms   219 ms   222 ms  te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
  6   214 ms   222 ms   211 ms  hibernia-netherlands.as5580.any2ix.coresite.com [206.72.210.212]

7     *        *        *     Request timed out.
  8   307 ms   305 ms   359 ms  ae00.edge01.ash02.us.as5580.net [78.152.34.61]
  9     *      292 ms     *     78.152.53.146
 10     *      288 ms   290 ms  dc11-n5596-fe-1-vl231.fe.core.pw [92.223.118.163]
 11   285 ms     *      310 ms  dc11-sl-a32.worldoftanks.com [162.216.228.32]

 

======================

tlouie, on 19 January 2016 - 03:29 AM, said:

This can't be right. The current wotb server load is 13,000.

 

https://api.worldoft...=demo&game=wotb

 

{"status":"ok","data":{"wotb":[{"players_online":13171,"server":"NA"}]}}

TWO servers in USA - that appears to West Coast only

http://wiki.wargaming.net/en/Servers

 

======================

reluctanttheist, on 19 January 2016 - 03:27 AM, said:

Ok guys, let's work the problem here: so SB, you're in Australia? and trying to connect to WG's NA server?  Have you tried the Asia server?

 

Asia Server, was always very busy for us. - worse lag than USA - but lately something is pushing us through the Netherlands on the way to the USA???

as above - can I configure Blitz to use West Coast Server and by shortest route???

SB>(dad)

Edited by _stellabug_, 20 January 2016 - 04:44 PM.

[tlouie]

Those are WoT servers, not wotb servers.

[_stellabug_]

tlouie, on 20 January 2016 - 05:13 PM, said:

Those are WoT servers, not wotb servers.

got it - (loading the wrong bookmark) - still, why am i routed through netherlands to get there??

[tlouie]

_stellabug_, on 20 January 2016 - 11:06 PM, said:

got it - (loading the wrong bookmark) - still, why am i routed through netherlands to get there??

 

Geolocation listings are notoriously inaccurate.  The Netherlands "location" could be one such inaccuracy: the node may not actually be in the Netherlands.

[acrisis]

https://au.news.yaho...-slow-internet/

 

[_stellabug_]

acrisis, on 21 January 2016 - 05:00 AM, said:

https://au.news.yaho...-slow-internet/

the allegation is that has been fixed.

========================

current in game ping is 20,000, down from a peak earlier of 250,000,

totally unplayable.

 

it is the hop immediately after hibernia/netherlands that is killing us,

and "hibernia" belongs to a company called coresite and may be IN Denver Colorado - (which is a data-center)

 

The WotBlitz Login Server is in California, (162.216.228.14)

so how do I avoid the Denver hop? (which appears to be the bottleneck)

 

Tracing route to login.wotblitz.com [162.216.228.14]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    20 ms    22 ms  lo0.bng1.bne7.on.ii.net [150.101.32.93]
  3    24 ms    38 ms    20 ms  ae3.cr1.bne7.on.ii.net [150.101.34.30]
  4    75 ms    37 ms    30 ms  ae6.br1.syd4.on.ii.net [150.101.33.12]
  5   179 ms   177 ms   178 ms  te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
  6   178 ms   178 ms   201 ms  hibernia-netherlands.as5580.any2ix.coresite.com [206.72.210.212]
  7     *        *        *     Request timed out.
  8   240 ms   239 ms   239 ms  ae00.edge01.ash02.us.as5580.net [78.152.34.61]
  9   240 ms   240 ms   240 ms 

 

 

[acrisis]

I'd actually try and ask coresite what is up. Because where they push you fron the Ndtherlands to Massachussetts or Nova Scotia is crap.

[_stellabug_]

I asked my ISP call center - they blame WarGaming, a joke, WG have nothing to do with where my ISP lands me into the USA,
I have bypassed the ISP call center and sent a direct request for help, because as far as I can see iinet decide where to drop us into the USA,

and coresite routing algorithms are clearly failing...

i also contacted coresite.

SB>(dad)

[tlouie]

_stellabug_, on 21 January 2016 - 12:59 AM, said:

the allegation is that has been fixed.

========================

current in game ping is 20,000, down from a peak earlier of 250,000,

totally unplayable.

 

it is the hop immediately after hibernia/netherlands that is killing us,

and "hibernia" belongs to a company called coresite and may be IN Denver Colorado - (which is a data-center)

 

The WotBlitz Login Server is in California, (162.216.228.14)

so how do I avoid the Denver hop? (which appears to be the bottleneck)

 

Tracing route to login.wotblitz.com [162.216.228.14]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    20 ms    22 ms  lo0.bng1.bne7.on.ii.net [150.101.32.93]
  3    24 ms    38 ms    20 ms  ae3.cr1.bne7.on.ii.net [150.101.34.30]
  4    75 ms    37 ms    30 ms  ae6.br1.syd4.on.ii.net [150.101.33.12]
  5   179 ms   177 ms   178 ms  te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
  6   178 ms   178 ms   201 ms  hibernia-netherlands.as5580.any2ix.coresite.com [206.72.210.212]
  7     *        *        *     Request timed out.
  8   240 ms   239 ms   239 ms  ae00.edge01.ash02.us.as5580.net [78.152.34.61]
  9   240 ms   240 ms   240 ms 

 

 

 

Have you power cycled your router and your device?  Do you still have long pings after the resets?

 

Regarding the asterisks at hop #7 above, they do not necessarily indicate a problem with the network routing, only that hop 7 didnt reply back within the time allotted.  You can try running traceroute with a longer wait time for response, something like -w 10 See here for more details:

 

https://en.m.wikiped...wiki/Traceroute

 

 

Edited by tlouie, 21 January 2016 - 12:41 PM.

[_stellabug_]

I'' cycle the router in a moment and then sleep time, we generally cycle everything every 2 days.

 

this is the trace with a wait-time of 15 - & 8 servers had problems... (it's 2am here)

and still #7 is dead. if we were playing blitz we could be up to 45 seconds late getting into the battle!

 

Tracing route to login.wotblitz.com [162.216.228.14]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    35 ms    14 ms    14 ms  lo0.bng1.bne7.on.ii.net [150.101.32.93]
  3     *       64 ms    80 ms  ae3.cr1.bne7.on.ii.net [150.101.34.30]
  4    81 ms   193 ms    60 ms  ae6.br1.syd4.on.ii.net [150.101.33.12]
  5     *      267 ms   217 ms  te0-1-1-3.br2.lax1.on.ii.net [150.101.33.195]
  6   189 ms     *      260 ms  hibernia-netherlands.as5580.any2ix.coresite.com [206.72.210.212]
  7     *        *        *     Request timed out.
  8   307 ms     *      283 ms  ae00.edge01.ash02.us.as5580.net [78.152.34.61]
  9   261 ms     *      274 ms  78.152.53.146
 10   260 ms     *      263 ms  dc11-n5596-fe-1-vl231.fe.core.pw [92.223.118.163]
 11   280 ms     *      296 ms  us4-slave-14.worldoftanks.com [162.216.228.14]

Trace complete.

Edited by _stellabug_, 21 January 2016 - 04:29 PM.

[tlouie]

The asterisks you see at hop 7 may not be a problem. See these two pages for explanations.

http://webmasters.st...traceroute-mean

http://www.exit109.c...te.html#reading

Edited by tlouie, 21 January 2016 - 08:43 PM.

[_stellabug_]

maybe we are looking in the wrong place,

Today when i ping the login server the ping is 224 - good for here,

and when l load blitz the news is readable and garage scrolls freely, (sometimes pages take minutes to load, and scrolling in the garage is slooow and judders)

 

but when we go to Battle - ping is 12,000+ - and by the time we get onto the battlefield we are long dead.

 

there are 12,000 people on the server.

SB>(dad)

Edited by _stellabug_, 22 January 2016 - 11:49 PM.