Skip to main content
Dangerdad137
1st Topic
1st Like

Visitor

 • 

13 Messages

Saturday, July 25th, 2026 6:24 PM

Unable to view videos on X: tracert shows a loop in the routing

This problem comes up, goes away, then recurs.  When attempting to view videos on x.com it sometimes doesn't load. I managed to get a tracert from the network and I see the following:

Here are the tracert problem: tracert video.twimg.com
1 (my network)
2 10 ms 11 ms 11 ms 100.93.193.26
3 11 ms 11 ms 17 ms po-104-rur301.yubacity.ca.ccal.comcast.net [96.217.70.1]
4 12 ms 11 ms 10 ms po-300-xar01.yubacity.ca.ccal.comcast.net [96.216.198.57]
5 16 ms 16 ms 15 ms be-15-arsc1.sacramento.ca.ccal.comcast.net [96.216.129.77]
6 15 ms 15 ms 15 ms ae-501-ar01.sacramento.ca.ccal.comcast.net [96.216.129.194]
7 21 ms 16 ms 16 ms be-501-arsc1.sacramento.ca.ccal.comcast.net [96.216.129.193]
8 17 ms 42 ms 13 ms ae-501-ar01.sacramento.ca.ccal.comcast.net [96.216.129.194]
9 17 ms 15 ms 16 ms be-501-arsc1.sacramento.ca.ccal.comcast.net [96.216.129.193]

Question

 • 

Updated 

10 hours ago

124

3

Oldest First
Selected Oldest First
XfinityMartyR

Official Employee

 • 

3.5K Messages

23 days ago

 

Dangerdad137  Thank you for reaching out! I would recommend going through the following How to Troubleshoot Your Xfinity Internet and WiFi connection post to ensure everything is working well with your Xfinity Internet connection. 

 

8

0

gta_

Visitor

 • 

4 Messages

7 days ago

Wow. Hadn’t done the dns change yet, but note my Route trace is showing this Fresno location over and over and over. Upon rerun of it, it went back to the Sacramento location you had listed…

 65 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182) 20.955 ms 22.691 ms 24.053 ms
 66 be-501-arsc1.fresno.ca.ccal.comcast.net (96.216.129.181) 19.501 ms 21.218 ms 22.648 ms
 67 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182) 20.674 ms 22.706 ms 24.158 ms
 68 be-501-arsc1.fresno.ca.ccal.comcast.net (96.216.129.181) 18.686 ms 20.109 ms 21.304 ms
 69 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182) 18.133 ms 19.616 ms 25.921 ms
 70 be-501-arsc1.fresno.ca.ccal.comcast.net (96.216.129.181) 18.658 ms 26.159 ms 28.508 ms
 71 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182) 19.644 ms 21.098 ms 22.226 ms

19

0

Dangerdad137

Visitor

 • 

13 Messages

Yep, there's a Fresno backend having the same problem.

Like

Reply

7 days ago

0

XfinityFrank

Official Employee

 • 

2.5K Messages

@Dangerdad137, these types of issues usually correct themselves over time. Are you still seeing the issue on the original DNS settings?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

6 days ago

0

Dangerdad137

Visitor

 • 

13 Messages

No change. Coming up on a month of outage.

Like

Reply

6 days ago

0

XfinityFrank

Official Employee

 • 

2.5K Messages

Thanks, @Dangerdad137. To rule out any other issues, are you using a VPN at all? Also, are you using a rented modem or your own? If rented, is there a stand-alone router in your setup?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

6 days ago

0

Dangerdad137

Visitor

 • 

13 Messages

Not using a VPN. In fact, with VPN it works fine. Using own modem and router.

Not having problem with cellular phone on cell provider connection either, only when connected to wifi and using comcast DNS.

Setting my own DNS servers in my router makes the problem go away.

Like

Reply

6 days ago

0

klockheed

New Poster

 • 

2 Messages

7 days ago

I've had same issue for a least a week. Different tracert though.


1

0

XfinityDilary

Official Employee

 • 

3.6K Messages

 

Thanks for sharing that picture, klockheed. The traceroute appears normal. Latency remains consistent throughout the Comcast network and reaches the Fastly/Twitter destination in approximately 20-25 ms. The timeout at hop 9 is not indicative of a service issue since the destination responds successfully afterward. No routing abnormalities, excessive latency, or packet loss are evident from this trace. What specific issues are you currently experiencing? 
 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

5 days ago

0

forum icon

New to the Community?

Start Here