High Ping Tegan since hotfix #3

Since the last hotfix, my ping on Tegan (all accts) has jumped from 25ms to 160ms. This is still playable. It is what I usually have on EU servers (oddly enough when I logged on to Grimmag today it is running better than usual at 155ms )

 

I have the same issue on Agathon mine was 92ms and now its 180ms please fix it

 

This hotfix basically traded the Nebula Plague for an extra 40ms for me. I am not sure I like it. -_-

 

_Baragain_ and I have both done trace route commands and all trafic to Agathon is now going to China and back.

I had latency of around 45ms, now is around 170ms. _Baragain_s was initially lower and last night was way higher than even mine. He put in a service ticket to get BP to talk to the entities that maintain the major internet backbone lines where the problems actually are.

If you want to see, open up command prompt and type either "tracert agathon.drakensang.com" or "tracert tegan.drakensang.com" then press [enter].

 

My latency is still between 9ms and 13ms.

The tegan tracert is still bouncing off the server 20 miles from me here in California.

The agathon tracert shows the same route.

 

Here is my information, to follow up on what TwiliShadow is saying.

This actually started before the patch. It kicked off on Tuesday night. I was playing with my normal 17ms latency (there are a couple of perks to living on that side of the country), but my significant other, who was playing on the same network as me had 160+. I troubleshot and could not find anything on her computer to explain the issue, so she just got off for the night. Later that evening (2 hours or so), my latency jumped up to 160 also.

The issue was still present the next day, so I actually began my troubleshooting in earnest. I did my Traceroute and noticed two Chinese servers in the path. I figured that my ISP's DNS had gotten poisoned, jacked, or otherwise messed up, so I started changing my DNS through all the reputable free DNS services (google's, OpenDNS, etc) and quickly discovered that they were all equally messed up. I've done everything short of putting a static route in my router, and that is because I don't have a clean Traceroute to go off of.

As TwiliShadow said, it is a backbone provider, "Level3.net," that is routing traffic to the Agathon and Tegan servers, which are physically located in southern California, through China for no apparent reason. That means that, for a change, it is not BP's fault.

I've since contacted support and provided them a summery and evidence of everything I've done to troubleshoot this issue. They informed me that they passed it to the network team who has passed it to the US Data Center. Because this issue is out of BP's control, we are at the mercy of the company that operates the data center that houses Agathon and Tegan, and their communication with Level3.net.

If you can, can you post a screenshot of your tracert with your public IP blocked out? I'm curious what would happen if I tried to pin other servers before the actual game server. I'm wondering if you are just close enough that you never end up having to pass over Level3's backbone.

 

OK, now I'm confused. Tegan and Agathon are on 49.51.45.77 and 49.51.45.46 for me (and according to "whatismyipaddress.com"), but your last hop is a comcast address, and what's more, the same address.

Congrats on being lucky/having Comcast?

But, it is worth noting that if I ping your last hop, I get 16-18 ms, which is what I'd expect for Agathon.

 

Seems like the first tracerts had a hiccup and didn't fully bounce back.

I've uploaded a new image

 

Interesting... wonder what happened there.

Well, I can ping the telia.net hop address, so that is good. It comes out to about what I would expect for a trip to Agathon. I obviously cant ping the 10.x.x.x address since it is in a private IP space, but that makes me curious what's going on that gives you a 10.x.x.x address in the hop before the server. I must say, you have a very interesting internet connection.

 

I am on the East Coast of the US. My ping was 18 before the great "move" a year + ago. After that it moved to the 80-100 mark unless I was with a group and then it would spike a few hundred higher in boss battles. Now, this is what it is like:



It is not a side effect of a bad internet connection. I am getting a new modem shortly so the speeds should increase to 300+ on the download but this is what it was just after doing the above tracerts:

 

If I do a tracert to any of the silicon valley companies, I get a 10.1 in the final pings, so my guess is that they are using a google server in the mix.

When DSO announced the server move a couple years back, the pings changed from near Los Angeles to Palo Alto and I've been in the 12ms to 17ms ever since.

 

Your route inspired me to try another ISP. Well, sort of. Since I can't just change my home internet provider, I used my phone's hotspot. It takes a totally different route. The latency is higher than my normal 15-17 at 50-70, but it is better than the 160-170 while the route from my home internet is messed up.

 

On the Southeast Side of the US. I'm also a victim of this weird routing.

TEGAN



AGATHON

 

What you see on display doesn't necessarily mean it is true.
Dirtbag ISPs can mask or filter TTL ... they can do whatever the hell they want for your money.
Especially with the new net neutrality law in US they can rout you to wherever they want and slow you down as much as they please.

 

And that is true. That tracert shows a host, it doesn't mean that your packet has ever been there. That tracert doesn't show a host record at all, it doesn't mean that your packet hasn't been there. And on top of that, you can't see the IP adress of half of the hops recorded (in case of some of you).

 

That is simply because a great many network devices disable ICMP to favor performance. No big deal.

You have a better method? The traceroute is still the single best troubleshooting method for this sort of thing, and the addresses do indicate a device that the path passed through... now GEOIP services are questionable, but with a little bit of research and common sense, it is quite possible to determine the rough geographical server location.

 

Looks like the high ping finally caught up to me.

That dreaded 212 London route popped up for me today. Going from 13-17ms to 165 - 175ms is plenty of reason for me to go on another hiatus from DSO.

 

I got word back from Support and their answer was to contact my ISP...

It's possible that it is an ISP issue, but the way it is spreading makes it seem like they're wrong. If it was one or two ISPs, maybe... but multiple ISPs across the country? I'm not convinced.

 

I expect to get the same answer from support when they choose to get back to me.

If it is my ISP, thankfully they chose to only slow down my connection to DSO and not my ability to visit any website, my movie streaming or either of the two big popular games that I play.

It does seem odd that players 3000 miles apart are now seeing the same route, but that excuse works for me as long as everything else on the internet besides DSO works perfectly for me.



Edit to add:

So out of morbid curiosity I contacted my ISP to see if they in fact decided to specifically slow down my connection only to the DSO server for whatever reason. Their answer was no. In fact my service is running 5x5 as usual and nothing was done on their end to slow my connection.

They stated that nothing from the ISP changed from yesterday to today and suggested that I contact the game technical support to see what changes the game may have implemented in the last 24 hours.

I have not heard back from DSO support yet, but when they do respond, I expect that their answer will be to check with my ISP.

Since I cannot find any other slow connection anywhere on the internet or with my streaming or other games I am doubtful that it is an ISP problem.

One interesting thing, I ran a tracert to each of the DSO servers and get the exact same latency range 160-175ms with all of them. HMMMMMMM.

On the other two games that I play, my latency is still 20ms on average as they have been.