Mrczech777's profile

New Poster

 • 

18 Messages

Saturday, February 13th, 2021 7:00 PM

Closed

Intermittent Lag/Rubber-Banding when Online Gaming

Hello Comcast forums,

 

After lurking for a while and trying to troubleshoot this issue on my own, I thought I should post and see what the experts here have to say. So, this has been a long standing issue with my home network. I used to have an old Arris modem from Xfinity and a router from Synology, and I just recently switched to an all-in-one Gateway from Xfinity. I'm on the 200 mbps plan, so I don't think I have any worries there. I currently play on a wireless connection, which I know would be an obvious solution, however it is difficult to be wired with my current housing layout. 

 

Now that everything's laid out, I'll give some context to my issue. In the past few months when gaming online with my brother who lives with me, he had always experienced this sort of lag. Nothing obvious tipped us off to what would be the fix, so he just kind of grinned and beared it. I never had these problems, so I assumed it was something with his PC (we both built our own) and/or wireless adapter. Anyways, the Gateway was recently giving us problems, so we had a Tech come out and work on it. Everything looked fine according to what he said, apart from the end of one of the cables outside in our box that the casing had cracked due to the cold winters we experience where we live. He replaced the end, restarted the Gateway, and went on his merry way.

 

When gaming with my brother later that night, I too began to experience the same lag he had been describing for so long. It's really frustrating, especially when I just had a tech out and there are still problems. As I mentioned in the start of my post, I did some of my own research, so as such I found the vast troubleshooting articles posted by Xfinity; I will post the connection specs below:

 

Downstream:

https://imgur.com/a/wjutx1P

 

 

Upstream:

https://imgur.com/a/TCCy198

 

 

Codewords:

https://imgur.com/a/Q1wgdx4

 

 

Event Log(s):

https://imgur.com/a/jVsIRaj

 

 

Traceroute:

traceroute to comcast.net (69.252.80.75), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  4.296 ms  4.031 ms  5.122 ms
 2  96.120.116.205 (96.120.116.205)  17.607 ms  13.942 ms  14.556 ms
 3  24.124.172.13 (24.124.172.13)  14.149 ms  15.716 ms  16.091 ms
 4  be-15-ar01.roseville.mn.minn.comcast.net (162.151.54.101)  19.165 ms  19.986 ms  18.603 ms
 5  be-13367-cr02.350ecermak.il.ibone.comcast.net (68.86.94.81)  25.168 ms  30.995 ms  28.280 ms
 6  be-1302-cs03.350ecermak.il.ibone.comcast.net (96.110.36.105)  34.489 ms  32.865 ms  30.625 ms
 7  be-1314-cr14.350ecermak.il.ibone.comcast.net (96.110.35.58)  28.990 ms  28.996 ms  27.121 ms
 8  be-301-cr12.pittsburgh.pa.ibone.comcast.net (96.110.39.158)  35.944 ms
    be-302-cr12.pittsburgh.pa.ibone.comcast.net (96.110.39.162)  39.851 ms
    be-301-cr12.pittsburgh.pa.ibone.comcast.net (96.110.39.158)  39.406 ms
 9  be-1312-cs03.pittsburgh.pa.ibone.comcast.net (96.110.38.153)  40.497 ms
    be-1212-cs02.pittsburgh.pa.ibone.comcast.net (96.110.38.149)  41.979 ms  37.347 ms
10  be-1111-cr11.pittsburgh.pa.ibone.comcast.net (96.110.38.130)  36.139 ms
    be-1211-cr11.pittsburgh.pa.ibone.comcast.net (96.110.38.134)  41.669 ms  42.423 ms
11  be-302-cr12.ashburn.va.ibone.comcast.net (96.110.32.101)  50.136 ms  43.500 ms
    be-301-cr12.ashburn.va.ibone.comcast.net (96.110.39.165)  41.001 ms
12  be-1312-cs03.ashburn.va.ibone.comcast.net (96.110.32.209)  41.836 ms
    be-1412-cs04.ashburn.va.ibone.comcast.net (96.110.32.213)  40.938 ms
    be-1312-cs03.ashburn.va.ibone.comcast.net (96.110.32.209)  43.039 ms
13  96.110.42.110 (96.110.42.110)  46.063 ms
    be-31223-ar03.newcastle.de.panjde.comcast.net (96.110.42.102)  52.667 ms
    96.110.42.98 (96.110.42.98)  44.077 ms
14  ae100-ur11-d.newcastlerdc.de.panjde.comcast.net (68.85.158.90)  43.906 ms  45.664 ms  44.739 ms
15  urlrw01.cable.comcast.com (69.252.80.75)  45.862 ms  44.211 ms  53.155 ms

 

 

Ping test:

PING comcast.net (69.252.80.75): 56 data bytes
64 bytes from 69.252.80.75: icmp_seq=0 ttl=49 time=47.773 ms
64 bytes from 69.252.80.75: icmp_seq=1 ttl=49 time=44.576 ms
64 bytes from 69.252.80.75: icmp_seq=2 ttl=49 time=48.643 ms
64 bytes from 69.252.80.75: icmp_seq=3 ttl=49 time=53.653 ms
64 bytes from 69.252.80.75: icmp_seq=4 ttl=49 time=51.761 ms
64 bytes from 69.252.80.75: icmp_seq=5 ttl=49 time=45.337 ms
64 bytes from 69.252.80.75: icmp_seq=6 ttl=49 time=50.986 ms
64 bytes from 69.252.80.75: icmp_seq=7 ttl=49 time=50.502 ms
64 bytes from 69.252.80.75: icmp_seq=8 ttl=49 time=44.474 ms
64 bytes from 69.252.80.75: icmp_seq=9 ttl=49 time=51.857 ms
64 bytes from 69.252.80.75: icmp_seq=10 ttl=49 time=50.980 ms
64 bytes from 69.252.80.75: icmp_seq=11 ttl=49 time=52.510 ms
64 bytes from 69.252.80.75: icmp_seq=12 ttl=49 time=47.845 ms
64 bytes from 69.252.80.75: icmp_seq=13 ttl=49 time=47.922 ms
64 bytes from 69.252.80.75: icmp_seq=14 ttl=49 time=50.628 ms
64 bytes from 69.252.80.75: icmp_seq=15 ttl=49 time=48.662 ms
64 bytes from 69.252.80.75: icmp_seq=16 ttl=49 time=58.160 ms
64 bytes from 69.252.80.75: icmp_seq=17 ttl=49 time=49.193 ms
64 bytes from 69.252.80.75: icmp_seq=18 ttl=49 time=49.482 ms
64 bytes from 69.252.80.75: icmp_seq=19 ttl=49 time=48.942 ms
64 bytes from 69.252.80.75: icmp_seq=20 ttl=49 time=56.244 ms
64 bytes from 69.252.80.75: icmp_seq=21 ttl=49 time=50.222 ms
64 bytes from 69.252.80.75: icmp_seq=22 ttl=49 time=50.942 ms
64 bytes from 69.252.80.75: icmp_seq=23 ttl=49 time=57.231 ms
64 bytes from 69.252.80.75: icmp_seq=24 ttl=49 time=49.563 ms
64 bytes from 69.252.80.75: icmp_seq=25 ttl=49 time=47.502 ms
64 bytes from 69.252.80.75: icmp_seq=26 ttl=49 time=48.886 ms
64 bytes from 69.252.80.75: icmp_seq=27 ttl=49 time=43.840 ms
64 bytes from 69.252.80.75: icmp_seq=28 ttl=49 time=52.851 ms
64 bytes from 69.252.80.75: icmp_seq=29 ttl=49 time=41.224 ms
64 bytes from 69.252.80.75: icmp_seq=30 ttl=49 time=48.448 ms
64 bytes from 69.252.80.75: icmp_seq=31 ttl=49 time=50.219 ms
64 bytes from 69.252.80.75: icmp_seq=32 ttl=49 time=45.391 ms
64 bytes from 69.252.80.75: icmp_seq=33 ttl=49 time=51.076 ms
64 bytes from 69.252.80.75: icmp_seq=34 ttl=49 time=49.601 ms
64 bytes from 69.252.80.75: icmp_seq=35 ttl=49 time=48.711 ms
64 bytes from 69.252.80.75: icmp_seq=36 ttl=49 time=48.439 ms
64 bytes from 69.252.80.75: icmp_seq=37 ttl=49 time=41.713 ms
64 bytes from 69.252.80.75: icmp_seq=38 ttl=49 time=41.558 ms
64 bytes from 69.252.80.75: icmp_seq=39 ttl=49 time=40.709 ms
64 bytes from 69.252.80.75: icmp_seq=40 ttl=49 time=49.934 ms
64 bytes from 69.252.80.75: icmp_seq=41 ttl=49 time=48.686 ms
64 bytes from 69.252.80.75: icmp_seq=42 ttl=49 time=48.044 ms
64 bytes from 69.252.80.75: icmp_seq=43 ttl=49 time=48.631 ms
64 bytes from 69.252.80.75: icmp_seq=44 ttl=49 time=46.848 ms
64 bytes from 69.252.80.75: icmp_seq=45 ttl=49 time=54.933 ms
64 bytes from 69.252.80.75: icmp_seq=46 ttl=49 time=43.582 ms
64 bytes from 69.252.80.75: icmp_seq=47 ttl=49 time=48.446 ms
64 bytes from 69.252.80.75: icmp_seq=48 ttl=49 time=44.764 ms
64 bytes from 69.252.80.75: icmp_seq=49 ttl=49 time=42.458 ms
64 bytes from 69.252.80.75: icmp_seq=50 ttl=49 time=49.059 ms
64 bytes from 69.252.80.75: icmp_seq=51 ttl=49 time=64.766 ms
64 bytes from 69.252.80.75: icmp_seq=52 ttl=49 time=70.376 ms
64 bytes from 69.252.80.75: icmp_seq=53 ttl=49 time=41.895 ms
64 bytes from 69.252.80.75: icmp_seq=54 ttl=49 time=46.187 ms
64 bytes from 69.252.80.75: icmp_seq=55 ttl=49 time=49.527 ms
64 bytes from 69.252.80.75: icmp_seq=56 ttl=49 time=48.143 ms
64 bytes from 69.252.80.75: icmp_seq=57 ttl=49 time=49.158 ms
64 bytes from 69.252.80.75: icmp_seq=58 ttl=49 time=50.321 ms
64 bytes from 69.252.80.75: icmp_seq=59 ttl=49 time=50.403 ms
64 bytes from 69.252.80.75: icmp_seq=60 ttl=49 time=52.537 ms

 

 

Not sure how (and/or if) this is helpful to you all, but I would really appreciate some help with my connection troubles! Also, let me know if I can run any more diagnostics that would be helpful to you all. Thanks!

 

 

This conversation is no longer open for comments or replies and is no longer visible to community members.

New Poster

 • 

3 Messages

4 years ago

I'm having the same issue it started at the 1st of the year.
forum icon

New to the Community?

Start Here