Would like my connection routed around troublesome Level3 node

talthos
Grasshopper

I am getting consistent packet loss and a latency jump greater than 30ms for the "lag-111.ear3.Seattle1.Level3.net" Level3 node in Seattle, while connected to Planetside 2 on the Connery server (64.37.174.142 is one of their 'gateway servers').

 

I would like my connection to be routed around this troublesome Level3 node, at least for this one application. Is it possible to alter the routing behaviour to get my connection to avoid the packet-dropping, latency-spiking Level3 nodes in Seattle?

Labels (1)
8 Replies

I think this is more than just that games server, it’s a...

s2celerity
Grasshopper

I think this is more than just that games server, it’s a routing issue for any streaming service as well, has the exact same thing happen

 

i was told an engineer is looking into it last week, no news this week yet 

0 Kudos
Reply
Loading...

I recall submitting a ticket sometime last month regardin...

talthos
Grasshopper

I recall submitting a ticket sometime last month regarding this issue, and a few days later, I was told that the ticket had been 'escalated'. The routing path itself hasn't changed since then.

0 Kudos
Reply
Loading...

Hey  the route is outside of our control when it reaches...

Moderator
Moderator

Hey @talthos the route is outside of our control when it reaches Seattle. Have you tried connecting with Planetside 2 support to see if they are able to make any changes?

0 Kudos
Reply
Loading...

Yes, I have. And they weren't able to do much, either. So...

talthos
Grasshopper

Yes, I have. And they weren't able to do much, either. So what you're saying, is that there's no way to, I dunno, blacklist the Seattle node? I have its IP address: lag-111.ear3.Seattle1.Level3.net

That node is the only one that causes me problems. If I can avoid it, things should be good again.

Otherwise, I might have to experiment with a VPN service to try and 'trick' my connection into going east first...

0 Kudos
Reply
Loading...

Routing is routing, whether it is the GPS in your vehicle...

mdk
Grasshopper

Routing is routing, whether it is the GPS in your vehicle deciding on the "best" route to the nearest TarBucks, or IP-packets on the Internet.

For me, in Victoria, the routing to the IP-address that you specified is:

Tracing route to lvspsn-liv-gw03.station.sony.com [64.37.174.142]

  3      8 ms  rd2cv-tge0-1-0-13-1.gv.shawcable.net [64.59.162.97]
  4    10 ms  rd1bb-tge0-4-3-0.no.shawcable.net [66.163.72.22]
  5    13 ms  rc1wt-be40.wa.shawcable.net [66.163.68.18]
  6    12 ms  rc2wt-be18-1.wa.shawcable.net [66.163.64.82]
  7    11 ms  lag-111.ear3.Seattle1.Level3.net [4.71.152.133]
  8    45 ms  ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]
  9    45 ms    46 ms    45 ms  SWITCH-COMM.bar1.LasVegas1.Level3.net [4.35.35.38]
 10   45 ms  be176.las-n9s1-core2.switch.com [66.209.64.117]
 11   44 ms  be1912.las-agg7s3-2.switch.com [66.209.64.226]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

although I doubt that packets leaving GV ("Greater Victoria") go through NO ("Nanaimo") to get to WA ("Washington State").

I think that the FQDN: rd1bb-tge0-4-3-0.no.shawcable.net does not reflect its physical location, that I am guessing is VA ("Vancouver").

So, I don't see the FQDN that you see. To me, that implies that you're *NOT* located in Victoria.

Thus, the "routing tables" cause a different routing for you than for me.  So, where are you?

Those routing tables also set a "priority" for each router-to-router path, just as your vehicle's GPS seems to prefer "main" streets over "locally-known-shortcuts".  So, rather than a "blacklist" entry, the "network engineers" can tweak the priority of each route -- "given a choice to route from A to B to get to D, it would be optimal to route from A to C to get to D, as long as C has not gone offline, leaving only B as an active path to D".

0 Kudos
Reply
Loading...

Sigh! The "edit reply" functioning is not letting me edit...

mdk
Grasshopper

Sigh! The "edit reply" functioning is not letting me edit my reply.

So, ignore my comment that I do *NOT* see the router that you reference, because I do:

 

    7    11 ms  lag-111.ear3.Seattle1.Level3.net [4.71.152.133]

But, still, "where are you"?

Hint: if you switch to that other company that uses "fibre", your routing probably will be much different, i.e., not using Shaw's route from Vancouver to Seattle.

 

 

0 Kudos
Reply
Loading...

Here's the traceroute I performed using WinMTR, yesterday...

talthos
Grasshopper

Here's the traceroute I performed using WinMTR, yesterday:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 | 1675 | 1675 |    2 |   14 |  246 |    9 |
|                             70.67.160.1 -    0 | 1672 | 1672 |    7 |   14 |  246 |   12 |
|    rd2cv-tge0-4-0-11-1.gv.shawcable.net -    1 | 1657 | 1656 |    7 |   16 |  351 |   10 |
|       rd1bb-tge0-4-3-0.no.shawcable.net -    1 | 1656 | 1655 |   10 |   17 |  311 |   17 |
|             rc1wt-be40.wa.shawcable.net -    1 | 1652 | 1651 |    9 |   18 |  236 |   20 |
|           rc2wt-be18-1.wa.shawcable.net -    0 | 1670 | 1670 |   13 |   20 |  236 |   16 |
|        lag-111.ear3.Seattle1.Level3.net -    4 | 1070 | 1036 |   13 |   21 |  279 |   14 |
|        ae-1-4.bar1.LasVegas1.Level3.net -    1 | 1659 | 1658 |   41 |   49 |  314 |   44 |
|   SWITCH-COMM.bar1.LasVegas1.Level3.net -    1 | 1601 | 1597 |   43 |   51 |  315 |   45 |
|         be176.las-n9s1-core2.switch.com -    1 | 1653 | 1652 |   46 |   53 |  317 |   48 |
|          be1912.las-agg7s3-2.switch.com -    0 | 1671 | 1671 |   46 |   53 |  306 |   48 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   88 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

The handful of 1% packet loss hops was an extremely rare occurrence that time; 99% of the time, all hops except for that one Seattle hop remain at 0% packet loss.

0 Kudos
Reply
Loading...

Okay, new traceroute observation today: I am now getting...

talthos
Grasshopper

Okay, new traceroute observation today: I am now getting packet loss on two of the hops to the Connery server. And unsurprisingly, it's another Level3 node.

 

Here's the new traceroute:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             70.67.160.1 -    0 | 2595 | 2595 |    1 |   13 |  175 |   10 |
|                             70.67.160.1 -    0 | 2594 | 2594 |    7 |   14 |  154 |   15 |
|    rd2cv-tge0-4-0-11-1.gv.shawcable.net -    0 | 2595 | 2595 |    8 |   15 |  153 |   16 |
|       rd1bb-tge0-4-3-0.no.shawcable.net -    0 | 2594 | 2594 |   11 |   17 |  164 |   21 |
|             rc1wt-be40.wa.shawcable.net -    0 | 2594 | 2594 |   11 |   17 |  154 |   17 |
|           rc2wt-be18-1.wa.shawcable.net -    0 | 2593 | 2593 |   13 |   19 |  151 |   18 |
|        lag-111.ear3.Seattle1.Level3.net -    3 | 1742 | 1695 |   13 |   19 |  149 |   19 |
|        ae-1-4.bar1.LasVegas1.Level3.net -    0 | 2594 | 2594 |   43 |   49 |  176 |   46 |
|   SWITCH-COMM.bar1.LasVegas1.Level3.net -    4 | 1608 | 1554 |   44 |   49 |  168 |   47 |
|         be176.las-n9s1-core2.switch.com -    0 | 2594 | 2594 |   46 |   52 |  191 |   47 |
|          be1912.las-agg7s3-2.switch.com -    0 | 2594 | 2594 |   46 |   52 |  197 |   51 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  131 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
0 Kudos
Reply
Loading...
TALK TO US
Need more help?