Jump to content


Wargaming side connection problem, 10:47 am Eastern Nov 15

Started by Lephturn, Nov 15 2016 04:01 PM

  • Please log in to reply
7 replies to this topic

Lephturn #1 Posted 15 November 2016 - 04:01 PM

    First Sergeant

  •
  • Club Wargaming
  • 17512 battles
  • 3,647
  • [III-S]
  • Member since:
    07-28-2014

Trace routes below. Problem is intermittent but on the second last node before the login server, WG problem. dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1739 ms

Nomticket because support team doesn't know what to do with this.

 

Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max.


4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=16 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=33 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=14 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=66 ms
8 78.152.53.146 (78.152.53.146) time=52 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1739 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=48 ms 
*** Traceroute at destination ***


Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max

4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=21 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=17 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=16 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=63 ms
8 78.152.53.146 (78.152.53.146) time=47 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=750 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=48 ms 
*** Traceroute at destination ***
Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max.
4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=32 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=13 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=21 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=73 ms
8 78.152.53.146 (78.152.53.146) time=51 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1671 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=51 ms 
*** Traceroute at destination ***


Edited by Lephturn, 15 November 2016 - 07:58 PM.

Lephturn Triarii Signature Media Producer

Host of the World of Tanks Blitz podcast TANK BOOM!

 

Search for "tank boom" on iTunes, Stitcher, SoundCloud or your podcast player of choice!

Android user? Get the Tank Boom! App: https://play.google.com/store/apps/details?id=com.tank.boom

VonMiller58 #2 Posted 15 November 2016 - 04:06 PM

    Chicken Farmer

  •
  • Players
  • 19415 battles
  • 3,129
  • [JFGF]
  • Member since:
    04-17-2016

had some lag problems last night


o...:...:I:...:...o

     ..58..58..

PixelBucket #3 Posted 15 November 2016 - 04:09 PM

    Level 90 Loser

  •
  • Players
  • 19298 battles
  • 3,247
  • [PRT]
  • Member since:
    12-31-2014

Edited by PixelBucket, 15 November 2016 - 04:10 PM.

My Top Tanks: Lowe (#880), Type 61 (#834), Helsing H0 (#797), Pz. S35 739 (#778), ARL 44 (#661), T7 Car (#654), STB-1 (#502), MT-25 (#442), Excelsior (ironically) (#422), M22 Locust (#322), T23E3 (#223), Pz. 38 (t) nA (#211), Alecto (#197), Pz 35 (t) (#168),

T-25 (#166), Stridsvagn 74A2 (#151), Angry Connor (#63!), T-15 (#51!), Pz. 38 (t) (#34!)

In My Garage: T-25, Tetrarch, Pz 38 (t), Pz 35 (t),  SU-122-44, Helsing H0, Kuro Mori Mine, Pz IV Anko SP, E 50 M, T7 Car, T2 Light, Locust, T-15, Stridsvagn 74A2, T23E3, Angry Connor, Lowe, Leopard 1, T25/2, 112, STB-1, AMX M4 45, Chaffee, STA-1, Type 61

Lines I am currently grinding: T110E4 (Currently at T25/2), AMX 50B (Currently at AMX M4 45)

"not concep"

Bronyman50 #4 Posted 15 November 2016 - 04:20 PM

    Offical Horse Guy (Platinum Legacy Forum Title Holder)

  •
  • Players
  • 21408 battles
  • 3,216
  • [FLEET]
  • Member since:
    09-26-2013
Man talk about funky numbers I think someone somewhere turned off their server and the signal got caught in a loop for a while

"The Mountain Goat Strikes Again" -Anonymous (Ingame)

I Swear It's Like A Potato Farm With The Current Playerbase

Bronyman50 A.K.A TheOriginalHorseGuy

acrisis #5 Posted 15 November 2016 - 04:57 PM

    First Sergeant

  •
  • Players
  • 18298 battles
  • 8,235
  • [EQ-TR]
  • Member since:
    12-27-2014

Nice catch, lephturn.

 

So often we go through these things in game, only for it to be momentary and by the time you can run a traceroute it is like the problem did not exist ... 


 

   Blitz   Community   Coalition   
 BCC Forum Thread | BCC Discord invite

 Mission Poll  |  Goose Event Poll  | ... 
Looney Tooners  ||  Triarii  ||  Blitz University  ||  Basic Training  ||  Mentor
2.8 Blitz Economy - A visual of the credit coefficients | Got lag? =>  Pingplotter thread

Anino_ng_Kamatayan #6 Posted 15 November 2016 - 05:56 PM

    First Sergeant

  •
  • Players
  • 10018 battles
  • 1,219
  • [MAHOU]
  • Member since:
    12-17-2015

View PostLephturn, on 15 November 2016 - 04:01 PM, said:

Trace routes below. Problem is intermittent but on the second last node before the login server, WG problem. dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1739 ms

Nomticket because support team doesn't know what to do with this.

 

Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max.
1 10.0.1.1 (10.0.1.1) time=8 ms
2 67.231.222.58 (67.231.222.58) time=28 ms
3 *
4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=16 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=33 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=14 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=66 ms
8 78.152.53.146 (78.152.53.146) time=52 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1739 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=48 ms 
*** Traceroute at destination ***
Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max.
1 10.0.1.1 (10.0.1.1) time=8 ms
2 67.231.222.58 (67.231.222.58) time=18 ms
3 *
4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=21 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=17 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=16 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=63 ms
8 78.152.53.146 (78.152.53.146) time=47 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=750 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=48 ms 
*** Traceroute at destination ***
Traceroute to login.wotblitz.com (162.216.228.35), 64 hops max.
1 10.0.1.1 (10.0.1.1) time=9 ms
2 67.231.222.58 (67.231.222.58) time=19 ms
4 xe-1-1-3-1826-agg01-tor.teksavvy.com (107.179.130.233) time=32 ms
5 ae0-2160-bdr01-tor.teksavvy.com (192.171.59.69) time=13 ms
6 torix.edge1.tor1.ca.as5580.net (206.108.34.245) time=21 ms
7 et-08-03-00.edge01.ash02.us.as5580.net (78.152.34.253) time=73 ms
8 78.152.53.146 (78.152.53.146) time=51 ms
9 dc11-n5596-fe-1-vl231.fe.core.pw (92.223.118.163) time=1671 ms
10 dc11-sl-a35.fe.core.pw (162.216.228.35) time=51 ms 
*** Traceroute at destination ***

 

 

Ummm.. did you just got hacked or something?


"S*** CLAN U KILL ME! 1V1 ME!"  - Banzai

 

"War does not determine who is right - only who is left"  - Bertrand Russsell

 

reluctanttheist #7 Posted 15 November 2016 - 06:47 PM

    Canuck Didactics

  •
  • Players
  • 17253 battles
  • 3,922
  • [III-H]
  • Member since:
    01-12-2015
No - he's showing the hops from router to router to router between him and the WG server cluster.  That, folks, is what your traffic is doing between you and WG.

Tanks:  _X: T110E5, T110E3, FV215b(183), IS-7, Obj.140  _IX: M103, T-54  _VIII: IS-6, T34, Lowe, T-44, IS-6, IS-3D  _VII: T-43, Comet, E25, AT-15A, SU-122-44
Usually on in the evenings Pacific time.  Intake Contact for Triarii Clan (PM for details)
Watch the WoTB Users Manual Series  | Click here if you have lag  |  The best settings for your iOS device |  Check your ping with Pingplotter  | Get good: watch Bushka! | Check out tanks on Tank Compare

Lephturn #8 Posted 15 November 2016 - 07:56 PM

    First Sergeant

  •
  • Club Wargaming
  • 17512 battles
  • 3,647
  • [III-S]
  • Member since:
    07-28-2014

Trace route is the only way to see where a problem is happening with your connection. In this case it looks like the router in WG's data centre just before the login server, or at least before the load balancer, or possibly it is the load balancer. Point is, there is a connection problem and it is on Wargaming's end.

 

problems have persisted throughout the day for me.


Edited by Lephturn, 15 November 2016 - 07:56 PM.

Lephturn Triarii Signature Media Producer

Host of the World of Tanks Blitz podcast TANK BOOM!

 

Search for "tank boom" on iTunes, Stitcher, SoundCloud or your podcast player of choice!

Android user? Get the Tank Boom! App: https://play.google.com/store/apps/details?id=com.tank.boom

Back to Bug Reports (3.3)


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

  1. World of Tanks Blitz official forum
  2. → Live Archive
  3. → Dev Archive
  4. → Bug Reports (3.3)