Whiners Corner
Forums > Whiners Corner (Archives) > Thread 20202020202020202 on server/lagSearch | New Thread
Thread Locked. You cannot edit or reply to any messages.
Thread 20202020202020202 on server/lag
 
Previous Page | Page 1, ... 3, 4
EmotionallyDisturbedParakeet
Super Regular
FatGuy With
A LittleGun

P: 08/07/2021 08:17 EST
   
angry_salad wrote:
wmkbsl wrote:
Murf wrote:
My ping is now always over 100 so I ran a tracert to the server. Wtf.

Tracing route to lunaticrage.com [172.93.101.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ZenWiFi_XT8-62B0 [192.168.50.1]
2 1 ms <1 ms <1 ms 192.168.0.1
3 9 ms 6 ms 8 ms 96.120.36.249
4 12 ms 10 ms 7 ms 162.151.102.241
5 12 ms 9 ms 17 ms 96.110.5.38
6 11 ms 13 ms 11 ms 69.139.181.161
7 17 ms 20 ms 15 ms be-40-ar01.northdade.fl.pompano.comcast.net [68.86.165.161]
8 20 ms 17 ms 13 ms be-33831-cs03.miami.fl.ibone.comcast.net [96.110.45.73]
9 * 18 ms 18 ms be-1311-cr11.miami.fl.ibone.comcast.net [96.110.44.186]
10 45 ms 40 ms 40 ms be-302-cr14.houston.tx.ibone.comcast.net [96.110.39.237]
11 44 ms 44 ms 42 ms be-1314-cs03.houston.tx.ibone.comcast.net [96.110.46.141]
12 44 ms 40 ms 40 ms be-1312-cr12.houston.tx.ibone.comcast.net [96.110.46.134]
13 66 ms 52 ms 57 ms be-301-cr14.56marietta.ga.ibone.comcast.net [96.110.32.217]
14 59 ms 52 ms 56 ms be-1314-cs03.56marietta.ga.ibone.comcast.net [96.110.34.249]
15 54 ms 52 ms 52 ms be-1312-cr12.56marietta.ga.ibone.comcast.net [96.110.34.218]
16 74 ms 74 ms 71 ms be-302-cr11.chicago.il.ibone.comcast.net [96.110.38.74]
17 75 ms 74 ms 87 ms be-1211-cs02.chicago.il.ibone.comcast.net [96.110.36.21]
18 75 ms 71 ms * be-1212-cr12.chicago.il.ibone.comcast.net [96.110.36.38]
19 76 ms 70 ms 69 ms be-303-cr13.350ecermak.il.ibone.comcast.net [96.110.38.217]
20 72 ms 71 ms 72 ms be-1313-cs03.350ecermak.il.ibone.comcast.net [96.110.35.41]
21 72 ms 73 ms 70 ms be-1312-cr12.350ecermak.il.ibone.comcast.net [96.110.35.26]
22 88 ms 88 ms 90 ms be-302-cr11.newyork.ny.ibone.comcast.net [96.110.38.70]
23 90 ms 97 ms 90 ms be-1311-cs03.newyork.ny.ibone.comcast.net [96.110.35.121]
24 89 ms 90 ms 111 ms be-1312-cr12.newyork.ny.ibone.comcast.net [96.110.35.138]
25 86 ms 87 ms 88 ms be-301-cr11.newark.nj.ibone.comcast.net [96.110.36.145]
26 89 ms 89 ms 88 ms be-1211-cs02.newark.nj.ibone.comcast.net [96.110.35.69]
27 90 ms 89 ms 93 ms be-2211-pe11.newark.nj.ibone.comcast.net [96.110.33.246]
28 92 ms 87 ms 91 ms 50.208.232.130
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Will probably take a few days to a week to correct; if it's longer than that, it can be a problem. Comcast routing can get funky.

I love the route, though:

Pompano Beach->Miami->Houston->Marietta->Chicago->Somewhere, IL->NYC->Newark->Destination.

Looks like it loops back to Illinois hops 16-21, which is probably not right. Heuristics should correct eventually.

This me from Toronto:

1 <1 ms <1 ms <1 ms mynetwork [192.168.1.1]
2 21 ms 14 ms 16 ms 10.11.1.33
3 * * * Request timed out.
4 28 ms 29 ms 27 ms tcore3-toronto21_hu2/5/0/3_35.net.bell.ca [64.230.59.186]
5 * * * Request timed out.
6 33 ms 30 ms 30 ms tcore3-chicagocp-bundle-ether15.net.bell.ca [142.124.127.96]
7 29 ms 28 ms 28 ms bx6-chicagodt_0-6-0-0.net.bell.ca [64.230.79.85]
8 26 ms 26 ms 26 ms be-220-pe01.350ecermak.il.ibone.comcast.net [66.208.216.145]
9 28 ms 29 ms 39 ms be-2401-cs04.350ecermak.il.ibone.comcast.net [96.110.37.13]
10 29 ms 28 ms 29 ms be-1412-cr12.350ecermak.il.ibone.comcast.net [96.110.35.30]
11 39 ms 38 ms 38 ms be-301-cr11.newyork.ny.ibone.comcast.net [96.110.38.66]
12 39 ms 39 ms 39 ms be-1111-cs01.newyork.ny.ibone.comcast.net [96.110.35.113]
13 38 ms * 39 ms be-1112-cr12.newyork.ny.ibone.comcast.net [96.110.35.130]
14 39 ms 39 ms 39 ms be-302-cr11.newark.nj.ibone.comcast.net [96.110.36.149]
15 37 ms 38 ms 37 ms be-1111-cs01.newark.nj.ibone.comcast.net [96.110.35.65]
16 39 ms 39 ms 39 ms be-2111-pe11.newark.nj.ibone.comcast.net [96.110.33.242]
17 44 ms 43 ms 43 ms 50.208.232.130
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 43 ms 43 ms 43 ms lunaticrage.com [172.93.101.194]

After Chicago the packets travel a similar route. You're most likely right on the diagnosis, there's too much packet-dancing through Chicago/IL.

  
wmkbsl
Super Regular
Engineer Flag
Toucher

P: 08/07/2021 14:02 EST
E: 08/07/2021 14:03 EST
   
kyree wrote:
Tracing route to lunaticrage.com [2607:7700:0:19:0:1:ac5d:65c2]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms mobile.hotspot [2607:fb90:822b:f186:7444:fdfb:f177:de8b]
2 49 ms 28 ms 38 ms 2607:fb90:822b:f186:0:36:3f92:4640
A T-Mobile hotspot? Is it 5G? Looks to be LTE based on the 1-2 latency...

What kind of packet loss are you working with typically? That's friggin dedication right there.
  
kyree
Super Regular
Killer Scout

P: 08/07/2021 14:52 EST
E: 08/07/2021 15:25 EST
    lemme throw a net_graph on and check it..I never bothered looking LOL...I am used to my grenades beeping twice instead of 3 times...I often miss an ele conc and emp jumps are tough

4G LTE I believe

*Edit
10-50 loss at any given time
  
sp0t
Super Regular
Assault Cannon
Lover

P: 08/07/2021 14:55 EST
    I have no idea what this means

Tracing route to LunaticRage.com [172.93.101.194]
over a maximum of 30 hops:

1 2 ms 1 ms 4 ms modem.lan [192.168.0.1]
2 18 ms 21 ms 22 ms 71-38-0-254.lsv2.qwest.net [71.38.0.254]
3 21 ms 30 ms 20 ms lsv2-agw1.inet.qwest.net [75.160.224.33]
4 22 ms 26 ms 19 ms 4.68.144.90
5 30 ms 25 ms 27 ms ae-1-3501.edge7.LosAngeles1.Level3.net [4.69.219.41]
6 31 ms 25 ms 26 ms be3050.ccr41.lax04.atlas.cogentco.com [154.54.10.197]
7 24 ms 24 ms 24 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
8 34 ms 33 ms 34 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85]
9 41 ms 41 ms 62 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
10 58 ms 57 ms 56 ms be2927.ccr41.iah01.atlas.cogentco.com [154.54.29.221]
11 72 ms 82 ms 88 ms be2687.ccr41.atl01.atlas.cogentco.com [154.54.28.69]
12 85 ms 86 ms 82 ms be2112.ccr41.dca01.atlas.cogentco.com [154.54.7.157]
13 85 ms 85 ms 86 ms be2806.ccr41.jfk02.atlas.cogentco.com [154.54.40.105]
14 88 ms 85 ms 88 ms be2235.rcr21.ewr01.atlas.cogentco.com [154.54.44.214]
15 86 ms 90 ms 86 ms be3227.rcr21.ewr06.atlas.cogentco.com [154.24.56.154]
16 87 ms 89 ms 89 ms be3551.nr51.b033057-0.ewr06.atlas.cogentco.com [154.24.54.154]
17 86 ms 93 ms 87 ms 38.122.245.114
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 124 ms 86 ms 87 ms lunaticrage.com [172.93.101.194]

Trace complete.
  
angry_salad
Super Regular
Medic Capping
Service

P: 08/07/2021 14:59 EST
    I think you have to reinstall Windows.  
wmkbsl
Super Regular
Engineer Flag
Toucher

P: 08/07/2021 15:04 EST
   
sp0t wrote:
I have no idea what this means

Trace complete.
Broadly speaking, it means you live in Vegas and have CenturyLink DSL. If that's a fiber connection, however, there are ways to improve the latency which I can detail.

  
wmkbsl
Super Regular
Engineer Flag
Toucher

P: 08/07/2021 15:37 EST
   
kyree wrote:
lemme throw a net_graph on and check it..I never bothered looking LOL...I am used to my grenades beeping twice instead of 3 times...I often miss an ele conc and emp jumps are tough

4G LTE I believe

*Edit
10-50 loss at any given time
Lots of 'ifs' and 'unknowns' regarding T-Mobile coverage where you live, but if you have the ability to access to 5G, you may see a significant reduction in latency and, RF dependent, a reduction in your packet loss. I'm generally neutral on the benefits of 5G for the average phone user, but for a hotspot, it's perfect as it's a better overall air interface. Like anything, try before you buy and make sure you have adequate 5G coverage where you reside.

Food for thought.
  
Nookie
Super Regular
Shotgun Quick
Draw

P: 08/07/2021 17:41 EST
    Only get 5g if you can afford to deal with cancer  
nesemann
Super Regular
Rocket Jumping
Capper

P: 08/07/2021 19:06 EST
E: 08/07/2021 19:07 EST
    Ooo! THis is fun!

14 38 ms 27 ms 28 ms lunaticrage.com [172.93.101.194]

edit: here I thought LPBs were a thing of the past
  
Ritual_Masturbator
Super Regular
Engineer Flag
Toucher

P: 08/07/2021 22:14 EST
    Using TekSavvy DSL in the GTA:

Tracing route to lunaticrage.com [172.93.101.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms amplifi.lan [10.0.163.1]
2 6 ms 9 ms 6 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 12 ms 6 ms 8 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 7 ms 6 ms 6 ms et-1-0-17.cr2-tor1.ip4.gtt.net [209.120.130.205]
5 17 ms 42 ms 54 ms ae0.cr2-nyc4.ip4.gtt.net [213.200.112.166]
6 19 ms 19 ms 17 ms ip4.gtt.net [76.74.94.206]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 17 ms 17 ms 17 ms lunaticrage.com [172.93.101.194]

Trace complete.
  
angry_salad
Super Regular
Medic Capping
Service

P: 08/08/2021 14:25 EST
    GTT can rot in hell. Morons, all of them.  
Previous Page | Page 1, ... 3, 4
Forums > Whiners Corner (Archives) > Thread 20202020202020202 on server/lag