U

Visitor

 • 

1 Message

Friday, July 14th, 2023 11:37 AM

Closed

Abrupt lagouts while gaming, traceroute issues

https://forums.xfinity.com/conversations/your-home-network/traceroute-issue-with-valorant-servers-washington/64a9d5e86059bc2b7f1cc323

Similar to this post.

I've spent too many hours troubleshooting our Xfinity Internet, including multiple customer calls. We have the 1000Mbps service with unlimited data. We have the XB7 gateway and support says everything is up to date and running fine. I have tested multiple ethernet cables and changed what port it is in the gateway. No fix. Toggled almost every single setting on the admin settings on and off to test it. No fix.

For context, I frequently, abruptly, disconnect randomly from online games on my Xbox Series S despite having zero lag aside from these abrupt disconnects. I never lose full connection; for example I never disconnect from party chat or xbox live, and my live streams stay up… I just lose connection during online games. I am on ethernet and never had these issues until a few months ago. My NAT type is open, I 

have troubleshooted/factory reset the console, the console is not the issue. It is something with the internet.

I was advised to run traceroute tests to several of the IP addresses near the game servers. I do not know much about these logs, admittedly, but from what I can tell and what I have researched there are definitely some issues at 96.108.46.113 and the whole 96.108 range in general. Here are some examples: 

traceroute to 52.23.63.224 (52.23.63.224), 64 hops max, 52 byte packets

 1  10.0.0.1 (10.0.0.1)  7.827 ms  1.553 ms  1.952 ms

 2  100.92.33.67 (100.92.33.67)  14.396 ms

    100.92.33.66 (100.92.33.66)  19.096 ms

    100.92.33.67 (100.92.33.67)  18.411 ms

 3  po-309-393-rur901.woburn.ma.boston.comcast.net (68.87.156.109)  11.065 ms

    68.87.156.141 (68.87.156.141)  12.136 ms

    po-309-393-rur901.woburn.ma.boston.comcast.net (68.87.156.109)  16.787 ms

 4  po-2-rur901.woburn.ma.boston.comcast.net (96.110.116.113)  10.891 ms

    po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  14.124 ms

    po-2-rur901.woburn.ma.boston.comcast.net (96.110.116.113)  12.267 ms

 5  * po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  17.736 ms *

 6  be-300-arsc1.needham.ma.boston.comcast.net (96.110.116.89)  19.732 ms

    be-501-ar01.needham.ma.boston.comcast.net (162.151.52.34)  15.741 ms

    be-300-arsc1.needham.ma.boston.comcast.net (96.110.116.89)  15.672 ms

 7  be-1003-pe02.onesummer.ma.ibone.comcast.net (68.86.90.173)  15.729 ms

    162.151.52.50 (162.151.52.50)  16.630 ms

    be-1005-pe11.onesummer.ma.ibone.comcast.net (68.86.90.66)  13.208 ms

 8  be-1005-pe11.onesummer.ma.ibone.comcast.net (68.86.90.66)  15.593 ms

    66.208.228.190 (66.208.228.190)  12.634 ms

    be-1003-pe02.onesummer.ma.ibone.comcast.net (68.86.90.173)  13.999 ms

 9  52.93.76.72 (52.93.76.72)  25.345 ms

    50.248.119.190 (50.248.119.190)  15.745 ms

    52.93.76.106 (52.93.76.106)  26.889 ms

10  150.222.71.41 (150.222.71.41)  14.003 ms

    52.93.76.113 (52.93.76.113)  14.330 ms

    150.222.71.25 (150.222.71.25)  17.611 ms

11  * 52.93.76.47 (52.93.76.47)  15.721 ms *

12  * * *

13  * * *

14  * * *

traceroute to 199.255.40.131 (199.255.40.131), 64 hops max, 52 byte packets

 1  10.0.0.1 (10.0.0.1)  4.593 ms  1.447 ms  2.022 ms

 2  100.92.33.67 (100.92.33.67)  31.116 ms

    100.92.33.66 (100.92.33.66)  19.210 ms

    100.92.33.67 (100.92.33.67)  14.768 ms

 3  po-309-393-rur901.woburn.ma.boston.comcast.net (68.87.156.109)  13.967 ms

    68.87.156.141 (68.87.156.141)  15.049 ms

    po-309-393-rur901.woburn.ma.boston.comcast.net (68.87.156.109)  15.130 ms

 4  po-2-rur901.woburn.ma.boston.comcast.net (96.110.116.113)  12.339 ms

    po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  13.024 ms

    po-2-rur901.woburn.ma.boston.comcast.net (96.110.116.113)  12.229 ms

 5  * po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  14.631 ms *

 6  * 162.151.52.50 (162.151.52.50)  17.794 ms *

 7  * be-501-ar01.needham.ma.boston.comcast.net (162.151.52.34)  14.835 ms *

 8  * ae0.11.bar1.raleigh1.level3.net (4.69.137.177)  33.012 ms *

 9  * ae0.11.bar1.raleigh1.level3.net (4.69.137.177)  33.535 ms *

10  * * *

11  * * *

12  * * *

traceroute to 34.201.164.207 (34.201.164.207), 64 hops max, 52 byte packets

 1  10.0.0.1 (10.0.0.1)  5.857 ms  1.908 ms  1.833 ms

 2  100.92.33.66 (100.92.33.66)  18.317 ms

    100.92.33.67 (100.92.33.67)  45.370 ms

    100.92.33.66 (100.92.33.66)  17.312 ms

 3  68.87.156.141 (68.87.156.141)  14.350 ms

    po-309-393-rur901.woburn.ma.boston.comcast.net (68.87.156.109)  11.849 ms

    68.87.156.141 (68.87.156.141)  11.949 ms

 4  po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  15.017 ms

    po-2-rur901.woburn.ma.boston.comcast.net (96.110.116.113)  12.368 ms

    po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  11.034 ms

 5  po-200-xar01.woburn.ma.boston.comcast.net (96.108.46.113)  13.024 ms *  8.234 ms

 6  162.151.52.50 (162.151.52.50)  23.928 ms *

    be-501-ar01.needham.ma.boston.comcast.net (162.151.52.34)  17.840 ms

 7  162.151.52.50 (162.151.52.50)  16.337 ms

    be-1005-pe11.onesummer.ma.ibone.comcast.net (68.86.90.66)  15.860 ms

    be-501-ar01.needham.ma.boston.comcast.net (162.151.52.34)  16.809 ms

 8  23.30.206.34 (23.30.206.34)  11.836 ms

    be-1003-pe02.onesummer.ma.ibone.comcast.net (68.86.90.173)  15.787 ms

    50.248.118.254 (50.248.118.254)  17.180 ms

 9  50.248.118.254 (50.248.118.254)  11.266 ms

    52.93.76.136 (52.93.76.136)  13.987 ms

    50.248.118.254 (50.248.118.254)  16.770 ms

10  52.93.76.29 (52.93.76.29)  16.609 ms

    150.222.71.21 (150.222.71.21)  14.441 ms

    52.93.76.97 (52.93.76.97)  14.318 ms

11  52.93.76.79 (52.93.76.79)  16.002 ms *  19.351 ms

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * 52.93.29.24 (52.93.29.24)  25.464 ms *

18  * 52.93.29.28 (52.93.29.28)  28.529 ms *

19  * * *

20  * * *

21  * * *

What am I to do to fix this issue I’m having? I have tried everything over tech support and on calls and they tell me everything is fine but clearly it is not. I would not be having this constant issues if there was no problem and it is very frustrating when they assure me nothing is wrong on their end over the phone. 

Retired Employee

 • 

729 Messages

2 years ago

I am sorry to see this is happening! Please send us a direct message, we will be happy to help. Thank you. 

Expert

 • 

111.2K Messages

2 years ago

@user_2ea267 @XfinityRuben 

Here's how to send a direct message (private message);


Click "Sign In" if necessary.
 
Click the "Direct Message" icon  in the upper right corner or https://forums.xfinity.com/direct-messaging  
 
Click the "New message" (pencil and paper) icon.
 
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there.
 
As you are typing a drop-down list appears. Select "Xfinity Support" from that list.
 
An "Xfinity Support" graphic replaces the "To:" line.
 
Type your message in the text area near the bottom of the window.
 
Press Enter to send it.


See https://comca.st/3KQF8q9 for an example.

[Permission from and credit given to BruceW].

forum icon

New to the Community?

Start Here