Constant disconnects from packet loss (Level3's DNS)

They did some recent server side performance updates as per the last patch:

http://www.swtor.com/patchnotes

Is this issue still occuring?

@You_Freak

I see no issues with those ping plots , see good example here

Rule of thumb is if a hop is an issue it will appear on all further hops.

Better explained here

Same problems for me, I have traced the problem to be a company called level3, that is some sort of a telecommunication company through which the swtor data/connection goes through. They are giving me thousands of server lag everywhere, Strongholds, every planet, every location, every character, on The Progenitor EU server. It's making my game totally unplayable, DC'ing all the time, yet every single other internet using program/game works perfectly on the side. It has -nothing- to do with my computer/connection. I have contacted BW customer service for this, yet they always answer with the same automatic reply of ''Try to use our troubleshooting'', which I've tried, every single suggestion, nothing helped, its SO frustrating, since I JUST resubbed, I'm paying for their game that I'm not even able to play anymore. I contacted level3 through their facebook page, and they answered, asked me to contact my own ISP (Internet Service Provider), I did, and they said they arent able to help. How is this fair for a paying customer of Bioware/EA?

Just wondering if someone that considers themselves a good techie could help me, pretty much holding me hand to hand so to speak, to try and find a solution.

@Wristayne

If you can attach a jpg of a ping plot with www.pingplotter.com and pathpings done when the game is running would be very useful.

well, it happened again, log as follows

在上限 30 個躍點上追蹤 159.153.70.90 的路由

  1     1 ms    <1 ms     1 ms  localhost
  2     5 ms     7 ms     1 ms  n140-h254.150.118.dynamic.da.net.twx
4]
  3     7 ms     7 ms     5 ms  10.254.0.17
  4     4 ms     3 ms     3 ms  10.254.0.77
  5    11 ms     3 ms    13 ms  10.254.0.25
  6     2 ms     1 ms     2 ms  10.254.0.245
  7     2 ms     2 ms     2 ms  202-153-197-17-static.unigate.net.tw [202.153.197.1
7]
  8     2 ms     2 ms     2 ms  45-60-41-175.TWGATE-IP.twgate.net [175.41.60.45]
  9     3 ms     3 ms     3 ms  203.78.181.133
 10   155 ms   155 ms   156 ms  6-60-41-175.TWGATE-IP.twgate.net [175.41.60.6]
 11   145 ms   145 ms   145 ms  xe-9-0-0.bar1.SanFrancisco1.Level3.net [4.53.132.17
]
 12     *        *        *     要求等候逾時。
 13     *        *        *     要求等候逾時。
 14   162 ms   161 ms   162 ms  4.28.172.102
 15   151 ms   151 ms   151 ms  159.153.68.46
 16   153 ms   153 ms   153 ms  159.153.70.90

追蹤完成。

@DarthRevan1234

The tracert looks fine, but a tracert is a snapshot of the instant you ran it.

pathping or pingplotter is better to look for issues, but looking at the tracert it looks fine at the time it was ran.

hops 12 and 13 can be ignored just means ICMP is currently set to ignore and isnt affecting forward path