Texas Server Routing causing high ping?

"
Hey there,

Thanks for your patience.

Our network administrators have raised an issue with our provider regarding this. We will be in touch once we receive an update.



Maybe the light at the end of the tunnel?

Negative, pretty much getting the run around while they are focusing on DC information given ignoring the texas routing issue.

Year long email series now.

Wew.
Just looked at the op again and saw this...
"
lif44 wrote:

Edit Since people like shovelcut exist and scrolling past two posts is just too much to ask here is a spoiler of imgur links with more than the packets the original test was run.

Spoiler
https://i.imgur.com/fDc1Dvs.png https://imgur.com/a/yGJ29gm https://i.imgur.com/F8Yiide.png https://i.imgur.com/weupij3.png https://i.imgur.com/E8xb5TQ.png https://imgur.com/a/yGJ29gm


Ill add to this spoiler as more screen shots are taken.

You do realize people browse this site on things other than computers right? I often browse this site on my tablet and as I've already explained the few "links" I looked at were all less than 300 packets worth of data, it's not my fault you didn't bother to use url tags. When people post lots of url's I can't click on I tend to just pick them at random since it's a fucking nightmare trying to copy/paste things on a mobile device. I just chose random url's from random pages in this thread, I'm so sorry the few I bothered with weren't the "right" ones for you...

They're not "links" if you can't click them btw, they're just url's. And you'll find that lots of people aren't going to bother with them unless you use the url tags and make them clickable.

Let me also apologize for ever trying to help. I'm sorry I ever clicked on this thread.
Just a lowly standard player. May RNGesus be with you.
I had typed out some stuff in response to you Shovel, but its futile. glhf

From GGG technical support things were escalated/corrected with their providers for the DC servers (and at least for me I had a solid 48-51 MS all night), Texas (68-132ms from last night) server data from last night is being looked into and maybe just maybe I can go back to playing on the server that is supposed to return the most stable experience.

Hopefully this is almost the end.
"
Shovelcut wrote:
Just looked at the op again and saw this...
"
lif44 wrote:

Edit Since people like shovelcut exist and scrolling past two posts is just too much to ask here is a spoiler of imgur links with more than the packets the original test was run.

Spoiler
https://i.imgur.com/fDc1Dvs.png https://imgur.com/a/yGJ29gm https://i.imgur.com/F8Yiide.png https://i.imgur.com/weupij3.png https://i.imgur.com/E8xb5TQ.png https://imgur.com/a/yGJ29gm


Ill add to this spoiler as more screen shots are taken.

You do realize people browse this site on things other than computers right? I often browse this site on my tablet and as I've already explained the few "links" I looked at were all less than 300 packets worth of data, it's not my fault you didn't bother to use url tags. When people post lots of url's I can't click on I tend to just pick them at random since it's a fucking nightmare trying to copy/paste things on a mobile device. I just chose random url's from random pages in this thread, I'm so sorry the few I bothered with weren't the "right" ones for you...

They're not "links" if you can't click them btw, they're just url's. And you'll find that lots of people aren't going to bother with them unless you use the url tags and make them clickable.

Let me also apologize for ever trying to help. I'm sorry I ever clicked on this thread.


No one, and I mean no one, is asking for your "input" or "help".

The technical support forum is full of this latency issue. If you can't see that, then you must be using a braille reader.
"
Smear wrote:
No one, and I mean no one, is asking for your "input" or "help".

This is a community driven technical help subforum, as it says in the sticky threads you didn't read. By posting in it you're essentially asking the community for help. So yeah...

If you want a direct GGG response I'd suggest you send them an email. But they're just going to ask you to do the same thing I'm asking you to do.

"
Smear wrote:

The technical support forum is full of this latency issue. If you can't see that, then you must be using a braille reader.


Unless you're living in the same house as these other people having "this latency issue" you're more than likely not having the same problem. So unless you're going to post your own MTR results you're adding even less than I am to these threads.
Just a lowly standard player. May RNGesus be with you.
Ongoing.

Not really expecting a reply until Monday NZ, getting pushed to a higher latency Texas + DC server today though. Even with their provider having made adjustments.

Really all just feels pretty futile tbh, its taken 9 months of emails to get to this point, and really no closer to having the issue resolved.

Edit I missed an email from this morning:

The relevant MTR (spoiler after) is being overlooked and I'm being told to basically deal with it/its fine.

Best support in the business.

Spoiler
Ah sorry, forgot to attach the relevant mtr, but lo and behold and I log back into the texas servers and I have a nice surprise waiting for me: https://i.imgur.com/UiUxWdu.png
MTR was ran with a 10s interval in pings to avoid possibly triggering deprioritization protocol of the packets.

Again, just to be clear, I live in Louisiana, 4-5 hours from Dallas where the first two mtrs are suppossed to be going.
Running MTR while standing in town.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.attlocal.net - 0 | 60 | 60 | 0 | 0 | 1 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 60 | 60 | 1 | 1 | 5 | 1 |
| 99.24.65.104 - 0 | 60 | 60 | 2 | 2 | 8 | 2 |
| 99.183.77.86 - 0 | 60 | 60 | 13 | 13 | 21 | 13 |
| 99.183.77.119 - 0 | 60 | 60 | 13 | 14 | 21 | 13 |
| 12.83.102.17 - 0 | 60 | 60 | 13 | 15 | 18 | 16 |
| 12.122.157.6 - 0 | 60 | 60 | 21 | 24 | 28 | 21 |
| gar24.attga.ip.att.net - 0 | 60 | 60 | 20 | 22 | 25 | 24 |
| 192.205.33.42 - 0 | 60 | 60 | 20 | 23 | 36 | 25 |
| dls-b22-link.telia.net - 0 | 60 | 60 | 29 | 31 | 44 | 38 |
|servers-com-ic-314904-dls-b22.c.telia.net - 0 | 60 | 60 | 103 | 135 | 165 | 155 |
| 209.205.116.241 - 0 | 60 | 60 | 54 | 60 | 72 | 64 |
| 209.205.126.158 - 0 | 60 | 60 | 110 | 135 | 160 | 119 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Running MTR while in hideout

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.attlocal.net - 0 | 60 | 60 | 0 | 0 | 2 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 60 | 60 | 0 | 1 | 5 | 1 |
| 99.24.65.104 - 0 | 60 | 60 | 2 | 2 | 6 | 2 |
| 99.183.77.86 - 0 | 60 | 60 | 13 | 13 | 20 | 13 |
| 99.183.77.119 - 0 | 60 | 60 | 13 | 14 | 21 | 14 |
| 12.83.102.17 - 0 | 60 | 60 | 13 | 14 | 18 | 16 |
| 12.122.157.6 - 0 | 60 | 60 | 20 | 24 | 28 | 21 |
| gar24.attga.ip.att.net - 0 | 60 | 60 | 20 | 22 | 26 | 21 |
| 192.205.33.42 - 0 | 60 | 60 | 20 | 21 | 28 | 20 |
| dls-b22-link.telia.net - 0 | 60 | 60 | 29 | 29 | 36 | 29 |
|servers-com-ic-317520-dls-b22.c.telia.net - 0 | 60 | 60 | 107 | 135 | 171 | 163 |
| se-us01-s2.servers.com - 0 | 60 | 60 | 56 | 59 | 100 | 59 |
| 173.0.144.87 - 0 | 60 | 60 | 56 | 61 | 75 | 61 |
| 142.0.201.220 - 0 | 60 | 60 | 105 | 133 | 155 | 147 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This is the texas server from the screen shot throwing me at 140 ms etc.

Haven't gotten a playable texas instance in ten recreates in blood aqua.

First recreate in a DC instance (again with 10s intervals)

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.attlocal.net - 0 | 36 | 36 | 0 | 0 | 1 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 36 | 36 | 1 | 1 | 3 | 1 |
| 99.24.65.104 - 0 | 36 | 36 | 2 | 2 | 6 | 2 |
| 99.183.77.86 - 0 | 36 | 36 | 13 | 13 | 18 | 13 |
| 99.183.77.119 - 0 | 36 | 36 | 13 | 13 | 17 | 13 |
| 12.83.102.17 - 0 | 36 | 36 | 13 | 15 | 20 | 14 |
| 12.122.157.6 - 0 | 36 | 36 | 20 | 24 | 28 | 26 |
| 12.122.141.233 - 0 | 36 | 36 | 20 | 22 | 24 | 22 |
| be7018.ccr41.atl04.atlas.cogentco.com - 0 | 36 | 36 | 21 | 21 | 22 | 21 |
| be2847.ccr41.atl01.atlas.cogentco.com - 0 | 36 | 36 | 20 | 20 | 23 | 20 |
| be2112.ccr41.dca01.atlas.cogentco.com - 0 | 36 | 36 | 36 | 37 | 38 | 36 |
| be2806.ccr41.jfk02.atlas.cogentco.com - 0 | 36 | 36 | 40 | 40 | 41 | 41 |
| be3294.ccr31.jfk05.atlas.cogentco.com - 0 | 36 | 36 | 40 | 40 | 41 | 41 |
|be2809.rcr21.b007023-2.jfk05.atlas.cogentco.com - 0 | 36 | 36 | 40 | 41 | 43 | 42 |
| 38.140.230.162 - 0 | 36 | 36 | 41 | 43 | 82 | 53 |
| 185.7.225.183 - 0 | 36 | 36 | 40 | 40 | 41 | 40 |
| 107.182.226.94 - 0 | 36 | 36 | 40 | 40 | 40 | 40 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hopefully this is finally enough data to show theres an issue?


I think to them this isn't an issue, basically you post MTRs for people to tell you its on your connection. But when it falls on GGG action doesn't occur, you end up stuck in a 9 month email chain where they hope things organically fix themselves.

It hasn't fixed its self, its been 3+ leagues of this shit with no end in sight.

Unless something drastic occurs this is gonna be the last update, I'm giving up.

Edit 3:

Spoiler


This is considered fine by the technical team.

Edit4:



And this one.

Edit 5: Another one



Only reason the screenshots are extended is so that the time does not get twisted, this is occurring right now but I'm being told this is fine and normal.

If someone from GGG takes the time to look through the forums please feel free to send me a message about what I can do in order to understand how this is ok?



Login server latencies.


WinMTR's for the three servers shown above (five second intervals to avoid deprio)
Spoiler


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 310 | 310 | 0 | 0 | 3 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 310 | 310 | 0 | 1 | 8 | 1 |
| 99.24.65.106 - 0 | 310 | 310 | 5 | 5 | 10 | 5 |
| 99.183.77.90 - 0 | 310 | 310 | 11 | 11 | 21 | 15 |
| 99.183.77.121 - 0 | 310 | 310 | 11 | 11 | 20 | 11 |
| 12.83.102.13 - 0 | 310 | 310 | 11 | 13 | 25 | 15 |
| 12.122.157.34 - 0 | 310 | 310 | 19 | 23 | 30 | 24 |
| gar27.dlstx.ip.att.net - 0 | 310 | 310 | 19 | 21 | 25 | 21 |
| 192.205.37.50 - 0 | 310 | 310 | 19 | 20 | 41 | 20 |
| dls-b22-link.telia.net - 0 | 310 | 310 | 20 | 20 | 41 | 21 |
|servers-com-ic-314904-dls-b22.c.telia.net - 0 | 310 | 310 | 41 | 91 | 142 | 103 |
| 209.205.116.241 - 0 | 310 | 310 | 41 | 43 | 78 | 43 |
| 209.205.125.46 - 0 | 310 | 310 | 41 | 41 | 53 | 41 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 406 | 406 | 0 | 0 | 3 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 406 | 406 | 0 | 1 | 12 | 1 |
| 99.24.65.106 - 0 | 406 | 406 | 5 | 5 | 16 | 12 |
| 99.183.77.90 - 0 | 406 | 406 | 11 | 11 | 19 | 13 |
| 99.183.77.121 - 0 | 406 | 406 | 11 | 11 | 19 | 12 |
| 12.83.102.13 - 0 | 406 | 406 | 11 | 12 | 18 | 12 |
| 12.122.157.34 - 0 | 406 | 406 | 18 | 22 | 27 | 22 |
| gar27.dlstx.ip.att.net - 0 | 406 | 406 | 19 | 21 | 24 | 20 |
| 192.205.37.50 - 0 | 406 | 406 | 19 | 20 | 57 | 19 |
| dls-b22-link.telia.net - 0 | 406 | 406 | 19 | 20 | 35 | 20 |
|servers-com-ic-317519-dls-b22.c.telia.net - 0 | 406 | 406 | 40 | 41 | 58 | 43 |
| 209.205.116.241 - 0 | 406 | 406 | 41 | 42 | 47 | 43 |
| 209.205.120.34 - 0 | 406 | 406 | 40 | 41 | 55 | 41 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 364 | 364 | 0 | 0 | 2 | 0 |
|104-14-76-1.lightspeed.jcsnms.sbcglobal.net - 0 | 364 | 364 | 0 | 1 | 11 | 1 |
| 99.24.65.106 - 0 | 364 | 364 | 5 | 5 | 15 | 5 |
| 99.183.77.90 - 0 | 364 | 364 | 11 | 11 | 22 | 11 |
| 99.183.77.121 - 0 | 364 | 364 | 11 | 11 | 19 | 11 |
| 12.83.102.21 - 0 | 364 | 364 | 11 | 13 | 25 | 15 |
| 12.122.157.34 - 0 | 364 | 364 | 19 | 23 | 28 | 21 |
| gar27.dlstx.ip.att.net - 0 | 364 | 364 | 19 | 21 | 28 | 20 |
| 192.205.37.50 - 0 | 364 | 364 | 19 | 20 | 52 | 19 |
| dls-b22-link.telia.net - 0 | 364 | 364 | 20 | 20 | 62 | 20 |
|servers-com-ic-317520-dls-b22.c.telia.net - 0 | 364 | 364 | 69 | 114 | 155 | 104 |
| 209.205.116.241 - 0 | 364 | 364 | 42 | 44 | 78 | 42 |
| 209.205.120.94 - 0 | 364 | 364 | 41 | 41 | 48 | 41 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Last edited by lif44 on Oct 26, 2018, 10:14:39 PM
Waiting for Email response.
Update: New rep reforwarding information up the chain?

Got told best bet is to just use DC for the time being, I assume you're doing the same already Organic, if not heres a heads up.
Update"

Thomas_GGG was kind enough to hit me up to get some more information, provided the logs and heres hoping it helps find the resolution.

Edit: Unstable instances tonight on both Texas and DC making the game completely unplayable on lockstep and not worth the risk to losing another character to predictive rubber banding.

I was hopeful after being contacted by Thomas, but I really shouldn't have been.
Last edited by lif44 on Oct 30, 2018, 9:30:06 PM

Report Forum Post

Report Account:

Report Type

Additional Info