Level3 issues? Post some info here

I use Conney and I keep getting routed from ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109 to ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109] then to the server.

Did you mis-paste a double or do you mean you have 2 identical hops?

Post the whole trace?

That's doesn't look like the case here, Netflix is not even available in my country
Devs on Reddit said that these recent lag issues might not be Level 3 related though, they are aware and working on fixing them (soon™).

We'll see, I guess.

You are correct I messed up on pasting kind of... It was ae14.edge2.Seattle1.Level3.net [4.68.62.189] to ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]. The slow response time is gone, but there are also two ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109] listed.

I forgot to save the trace from last night when this was happening, but here it is from today.
Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 96 ms 67 ms 24 ms boid-dsl-gw15.boid.qwest.net [184.99.64.15]
3 26 ms 24 ms 26 ms boid-agw1.inet.qwest.net [184.99.65.113]
4 38 ms 38 ms 38 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 38 ms 38 ms 82 ms ae14.edge2.Seattle1.Level3.net [4.68.62.189]
6 67 ms 67 ms 67 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

7 67 ms 67 ms 66 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

8 68 ms 68 ms 68 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
9 67 ms 67 ms 67 ms vl3101.lvssw-1.sonyonline.net [64.37.168.6]
10 * 68 ms 67 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]


Trace complete.

Yeah that is odd and not usually normal, but its not causing any issues it seems.

You do have some high jitter on your first ISP hop, 96ms 67ms and 24 ms, could be nothing but it also could be an issue.

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 45 ms 45 ms 45 ms L100.LSANCA-DSL-04.verizon-gni.net [71.108.32.1]

3 50 ms 50 ms 49 ms G0-13-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.
45.190]
4 89 ms 47 ms 49 ms ae9-0.LAX01-BB-RTR1.verizon-gni.net [130.81.163.
240]
5 * * * Request timed out.
6 49 ms 49 ms 49 ms 0.ae6.BR1.LAX15.ALTER.NET [140.222.225.137]
7 50 ms 49 ms 49 ms ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
8 53 ms 52 ms 54 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

9 53 ms 53 ms 52 ms ae-1-4.bar1.LasVegas1.Level3.net [4.69.133.109]

10 65 ms 55 ms 55 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
11 55 ms 55 ms 54 ms lp.soe.com [64.37.171.24]

Trace complete.

I play on Connery, it goes nasty after while :l

Tracing route to lvspsn-liv-gw01.station.sony.com [64.37.174.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.251.64.1
3 * * * Request timed out.
4 10 ms 14 ms 10 ms ACCESS-MR-01-tengig10-6.ip4.012.net.il [212.199.
24.217]
5 10 ms 11 ms 11 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.1
99.5.62]
6 11 ms 12 ms 10 ms BRDR-CORE-MR-xe-3-1-0-3011.ip4.012.net.il [212.1
99.5.62]
7 12 ms 12 ms 12 ms BRDR-CORE-MR-ae0-3024.ip4.012.net.il [212.199.5.
105]
8 63 ms 62 ms 64 ms 80.179.166.134.static.012.net.il [80.179.166.134
]
9 260 ms * * 77.67.61.145
10 270 ms 260 ms 249 ms xe-5-2-1.fra44.ip4.gtt.net [89.149.181.230]
11 * * 213 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

12 441 ms * * ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

13 212 ms 213 ms 213 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
14 214 ms 214 ms 215 ms vl3101.lvssw-1.sonyonline.net [64.37.168.6]
15 212 ms 213 ms 212 ms lvspsn-liv-gw01.station.sony.com [64.37.174.140]

that specific 441ms spike is what makes it impossible for me to play this game, i used to get 230 ping to Connery (ingame reading, high i know but im now getting 250ms on cobalt where i would get less than 100)
and its unplayable now, it spikes to a ping with 4 digits every minute or so.
That 4.69.148.125 level3 hop is what ***** up my game


Trace complete.

No its not. That is a router rate limiting ICMP traffic destined to itself and is common.

Notice you have steady 212-215 ms latencies past that hop.


Note also this trace is only valid for Connery this route has nothing to do with Cobalt, and 212ms for going across the atlantic and most of the US is very good.

I opened a support ticket about ping and was told to post my problems here:

D‚termination de l'itin‚raire vers lp.soe.com [64.37.171.24]
avec un maximum de 30 sautsÿ:

1 <1 ms <1 ms <1 ms box [192.168.1.1]
2 21 ms 21 ms 21 ms 1.10.16.109.rev.sfr.net [109.16.10.1]
3 21 ms 21 ms 21 ms 238.92.118.80.rev.sfr.net [80.118.92.238]
4 22 ms 23 ms 23 ms 66.61.6.109.rev.sfr.net [109.6.61.66]
5 31 ms 27 ms 32 ms 29.12.6.109.rev.sfr.net [109.6.12.29]
6 29 ms 27 ms 27 ms 54.247.5.109.rev.sfr.net [109.5.247.54]
7 * 56 ms 27 ms xe-0-0-3.parigi32.par.seabone.net [213.144.183.196]
8 27 ms 27 ms 26 ms ae9.edge4.Paris1.Level3.net [4.68.62.21]
9 168 ms 168 ms 168 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
10 168 ms 168 ms 168 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
11 169 ms 168 ms 168 ms lp.soe.com [64.37.171.24]

Itin‚raire d‚termin‚.

Thanks.

could you elaborate please?
to my understanding its the weakest link that decides the ping, how is this wrong?
if i ping cobalt i get a list of "request timed out* and a ping that spikes up to the thousands while playing.
what has changed then?
i used to be able to play on Connery flawlessly too, ill change isp and report back if it changed anything

Routers are designed to do one thing and do it really really fast, route traffic not destined for it from one interface to another and its all done "in hardware" without the main CPU and software even touching 99.9999% of the packets. When you run a trace it ping that router directly that has to be done in software by the main CPU, well that routers last priority is to respond to pings that are sent directly to it, and most are programmed to rate limit ICMP to itself, hence why that hop is slow or somewhat unresponsive.

Now ICMP packets passing through the router are treated just like any other packet, and are routed at full speed.


Think of it this way, In order to reach the last hop (in this case 64.37.174.140) you have to go through 4.69.148.125, now you can reach 64.37.174.140 in 212ms but the laetency for 4.69.148.125 is 400+ms. how can it take longer to get to a hop farther away? simple 4.69.148.125 is delaying its response. but you dont care how fast 4.69.148.125 can respond to you you only care how fast 64.37.174.140 can.

It would be like to taking longer to drive from Israel to Lebanon then it would to drive Israel to Turkey.

Routenverfolgung zu lp.soe.com [64.37.171.24] ber maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms 192.168.178.1
2 28 ms 28 ms 29 ms 62.27.93.145
3 29 ms 29 ms 28 ms 62.27.94.245
4 28 ms 117 ms 28 ms 62.27.94.173
5 30 ms 29 ms 28 ms 194.25.210.85
6 32 ms 31 ms 31 ms f-sb1-i.F.DE.NET.DTAG.DE [62.154.14.213]
7 29 ms 29 ms 29 ms f-ee5-i.F.DE.NET.DTAG.DE [62.154.14.246]
8 50 ms 29 ms 29 ms 62.157.250.74
9 188 ms 188 ms 188 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]
10 189 ms 189 ms 189 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50]
11 189 ms 188 ms 188 ms lp.soe.com [64.37.171.24]

I live in Berlin, since 20.10. ping issues. I have DSL 50k with cable downstream 5,2 MB/s up 1,6 MB/s

Are you playing on a US West coast server? If not that trace means dick.. What server are you playing on?

My problem with packet loss of 100%.

Who can exert pressure on Level 3 because they have service agreement? SOE or my ISP?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Vincent>tracert 64.37.171.24

Tracing route to lp.soe.com [64.37.171.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 10 ms 9 ms 10.250.83.1
3 9 ms 9 ms 10 ms ppp-206-80-245-49.nas01.totftds.ext.distributel.
net [206.80.245.49]
4 8 ms 9 ms 9 ms ppp-206-80-245-49.nas01.totftds.ext.distributel.
net [206.80.245.49]
5 8 ms 9 ms 14 ms 206.80.255.226
6 10 ms 9 ms 11 ms te0-0-1-1.nr11.b019082-1.ymq02.atlas.cogentco.co
m [38.104.152.41]
7 11 ms 10 ms 10 ms 154.24.35.61
8 9 ms 10 ms 10 ms multi-use.cogentco.com [154.24.6.109]
9 16 ms 17 ms 20 ms be2090.ccr21.yyz02.atlas.cogentco.com [154.54.30
.205]
10 16 ms 16 ms 24 ms level3.yyz02.atlas.cogentco.com [154.54.11.210]

11 82 ms 82 ms 116 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

12 84 ms 83 ms 83 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.1
6.50]
13 83 ms 84 ms 82 ms lp.soe.com [64.37.171.24]

Trace complete.



I live in Canada, Quebec, Montreal.

Except there is no packet loss past those hops, again that is those routers ignoring ICMP because it is not a priority, or they are configured to drop all ICMP redirected at them.

It you had "100%" packet loss at those hops there would be no response after those hops, ask yourself how can a router have 100% packet loss yet you can get responses past those hops..

If it was true packet loss ever hop after would show similar loss.

Depends on who has the issues with Level 3, since it seems only some ISPs do its up to them, if everyone had an issues it would point to SOE or SOE's Level3 connection, but it doesn't.

What server do you play on? because that trace is not to a game server at all, but it does go to a server in the same datacenter as the US West server Connery.

If its Emerald trace to 69.174.216.27

I found this, Everyone should give this a read before spouting off about stuff they have no clue on.

https://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf

Pages 29-31 have a good part about the limits of routers responding to tracert's and pings directed AT them instead of TROUGH them. This is also why some providers filter/block ICMP/UDP/etc on the routers.

Pages 46-48 have great information about how MPLS effects traces, note Level 3 does use MPLS in most of their network.