Problem with ear2.SanJose1.Level3.net

Servers are down at the moment but here's the results

Ping statistics for 192.168.1.1:
    Packets: Sent = 98, Received = 98, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Ping statistics for 175.156.64.1:
    Packets: Sent = 101, Received = 101, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms

Ping statistics for 159.153.68.252:
    Packets: Sent = 71, Received = 71, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 187ms, Maximum = 190ms, Average = 187ms

@leto_cleon

They look fine , this may not be showing up until under load.

may have to wait until after maintenance to confirm they still look like this

I am trying to ascertain why the packet loss appearing , this is what will hurt a connection more then a ping spike.

I am in Australia so I will be asleep by the time the servers are back up

Where all the previous tests done with the game running ? it is possible for a connection to look ok until under load

If it is only appearing with swtor running , I would look at the firewall in the router initially.

Testing remotely is difficult so want to eliminate the closest question on the results and move outwards.

Except for the ping -t ones, the rest of the tests were done while the game was running.

Here is what winmtr looks like at the moment with the servers down:

@leto_cleon

Looks mostly fine at present , I am not concerned with those level 3 hops at present as it is not affecting the hops after them.

Interesting the packet loss is gone now.

If you read that guide I linked , pings to a router utilise what is known as the slow path to get a response , whilst pings transiting to another hop use what is known as the fast path through the same router, this is why a ping to and through a particular router can respond differently.

Rule of thumb is packet loss at a hop isn't an issue unless it affects all hops after that hop, hence why that loss appearing at the first hop past your router and continuing all through the test is more concerning.

That packet loss would have an affect on the game , in that there would be delays in actions occurring as the packets are required to be resent. 

All I can respond to is my interpretation of the results your posting , I am not even looking at the game side of things at present.

@leto_cleon

Pathping is another test you can run

it is run much like tracert in the command prompt

for testing to the servers

pathping -n 159.153.68.252

looking at the hops involved this test will take 5 minutes to complete on each run through

To interpret the results of that test see here and packet loss on the numbered lines isn't usually bad but packet loss between numbered hops is what will hurt a net connection 

I ran pathping and winmtr side by side and here's the results. And now that the servers just came up, its the non-load result

@leto_cleon

Be interesting to see the difference with the game running now

Ok here's the winmtr thus far. No responsiveness problems at the moment.

@leto_cleon

So with results like below , game play is ok still ? is that what you mean by responsiveness ?

Ok here's the pathping and winmtr that were running at the same time. WTFast is also recording zero packet loss at the moment as well. No problems with moving around, accessing vendor, activating abilities. Might have resolved itself somehow. Your probably right that the level3 ping spike wasn't the main issue.

@leto_cleon

Lets see how it goes over time , I'll keep an eye on this thread for a few days

If the responsiveness issue appears again see what changes in these results.

In theory the packet loss at the router should be 0% at all times particularly your router , I have a RT - AC87 2400 here but monitoring for changes is the best thing at present.

For referenece here's the wtfast stats to compare:

@leto_cleon

When you log into the router , go to the firewall tab , for now can you put " Enable Dos protection " to No ( if it isn't already )

See if that eliminates the packet loss reporting at the modem itself.

Here is the winmtr and wtfast stats with DoS disabled. Strange that wtfast shows that the packet loss from the router is so high. No problems in game.