Visitor
•
3 Messages
BGP routing loop — Fastly prefix 199.232.252.0/22 unreachable from Fresno market
Requesting Tier 2 / Network Engineering. This is NOT a modem or in-home issue — please do not dispatch a technician or reset my gateway. Account and WAN IP available via DM.
Market: Fresno, CA | Observed: 2026-07-29 15:47 PDT | Duration: ~3 weeks
PROBLEM
Fastly prefix 199.232.252.0/22 (origin AS54113) is unreachable from my connection. TCP connect fails in ~21ms with EHOSTUNREACH. Dead across all four /24s (199.232.252-255.x); 199.232.251.x and below are fine.
Traceroute loops between two of your own routers and never reaches your backbone:
6 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182)
7 be-501-arsc1.sacramento.ca.ccal.comcast.net (96.216.129.193)
8 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182)
9 be-501-arsc1.sacramento.ca.ccal.comcast.net (96.216.129.193)
10 ae-501-ar01.fresno.ca.ccal.comcast.net (96.216.129.182)
CONTROL — a different Fastly prefix from the same source exits normally:
traceroute 151.101.196.158
6 be-42-arsc1.sacramento.ca.ccal.comcast.net (96.110.62.193)
6 be-36421-cs02.sunnyvale.ca.ibone.comcast.net (96.110.41.101) <- backboneNOT A DESTINATION PROBLEM
199.232.252.0/22 is announced by AS54113 and visible to 330 of 330 RIPE RIS peers as of 2026-07-29 16:00 UTC, continuously announced since 2020-09-25. The prefix is globally reachable. Comcast is the only network that cannot route to it.
CUSTOMER IMPACT
Comcast's resolver hands Fresno-market customers addresses inside this prefix for video.twimg.com, so all X/Twitter video playback fails in every browser. The error X displays is generic, so affected customers blame X rather than reporting it. Third-party DNS works around it but does not fix the route.
ASK
Please correct the next-hop / route for 199.232.252.0/22 in the Fresno market so it reaches the backbone as sibling Fastly prefixes do.
simpleshadow
Visitor
•
3 Messages
22 hours ago
Is this not the place to make this request?
0
0
XfinityJorge
Official Employee
•
3.1K Messages
21 hours ago
Click "Sign In" if necessary
Click the "Direct Messaging" icon
Click the "Start new conversation" (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.
https://forums.xfinity.com/conversations/guidelines/how-to-direct-messaging-within-the-forum/697ba1e570934d009185c514
2
0
EG
Expert
•
119.7K Messages
21 hours ago
@simpleshadow @XfinityJorge
Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0
0
user_fkb9t4
Visitor
•
1 Message
13 hours ago
Will this problem with routing with x/twitter videos be fixed or any information moving forward?
0
0