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)  <- backbone

NOT 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.

Responses

Oldest First

Selected Oldest First

Community Best Answer

XfinitySara

Official Employee

•

2.9K Messages

42 minutes ago

Hello, @simpleshadow - We've received a final confirmation from our Engineering team that there's nothing else (from a Comcast perspective) we can do or offer at this time. It's been suggested that you may reach out to Fastly directly for further investigation, which we hope goes well! As mentioned in my latest DM, we appreciate your time on this, and we remain here to help if you have any other questions or concerns. You're always welcome to start a new post down the line if other things come up, and we'll be here to support you the best we can!

0

S

simpleshadow

Visitor

•

8 Messages

2 months ago

Is this not the place to make this request?

0

XfinityJorge

Official Employee

•

3.3K Messages

2 months ago

simpleshadow Hi there! Thanks for using our Forums and our team is here happy to work with you to help with your internet concerns. We appreciate all the details you shared about your connection and we are here to see how we can help. To get started can you send us a DM with your full name and the address. To send a "Direct Message" to Xfinity Support:
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

7

0

S

simpleshadow

Visitor

•

8 Messages

Hi @XfinityJorge,

When I created this post I did send a message to Xfinity Support the same day.

(edited)

Like

Reply

2 months ago

0

XfinityVictor

Official Employee

•

2.5K Messages

simpleshadow We can certainly help. Can you please send us a DM by following the steps my colleague provided?

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

2 months ago

0

S

simpleshadow

Visitor

•

8 Messages

See above, I already did? https://forums.xfinity.com/conversations/your-home-network/bgp-routing-loop-fastly-prefix-199232252022-unreachable-from-fresno-market/6a6a8610e768fbe286156c1f?commentId=6a6cce93b3ed1847a0ae10ec&replyId=6a6d40beb3ed1847a0b514fb

(edited)

Like

Reply

2 months ago

0

S

simpleshadow

Visitor

•

8 Messages

Any updates? Still an issue.

Like

Reply

2 months ago

XfinityNatalie

Official Employee

•

1K Messages

simpleshadow, Please send us another direct message as we have not received it from this end. To ensure you successfully send us a direct message you will need to follow these steps below:

-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.

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

2 months ago

0

EG

Expert

•

121.2K Messages

2 months 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

U

user_fkb9t4

Visitor

•

1 Message

2 months ago

Will this problem with routing with x/twitter videos be fixed or any information moving forward?

1

XfinityCliff

Official Employee

•

654 Messages

Hello @user_fkb9t4, and thanks for asking such a great question on our Xfinity Community forums!

I can definitely understand why you'd want an update, especially when this issue is impacting something as common as video playback on X/Twitter. Please know that your concerns are being heard, and we've made sure the feedback and reports received on this issue are visible to the appropriate teams for review.

If you have specific data or workarounds to share, please do so here.

At this time, we do not have any new information or updates to share regarding a resolution. We understand how frustrating it can be when an issue persists, and we appreciate everyone who has taken the time to provide detailed information and reporting. In the meantime, we appreciate your patience and continued feedback.

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

2 months ago

0

XfinitySara

Official Employee

•

2.9K Messages

1 month ago

@simpleshadow - In case you don't see my our latest DM right away, I wanted to tag you here. Our Engineering team is looking for additional information if you're able to provide that to me back in our private chat, thanks!

0

XfinitySara

Official Employee

•

2.9K Messages

1 month ago

@simpleshadow - Before we close this case, I wanted to check back in, just in case you've been busy. Would you like to proceed with leveraging the support of our backend/engineering teams?

2

0

S

simpleshadow

Visitor

•

8 Messages

@XfinitySara — Hi, yes, please proceed with Engineering. The issue is not resolved. I've replied in the DM (ticket [Edited: "Personal Information"]).

Re-tested today 2026-08-18. Simplest way to see it — ask four resolvers for the same Fastly hostname:

dig @75.75.75.75 dualstack.video.twitter.map.fastly.net  -> 199.232.252.158  DEADdig @1.1.1.1     dualstack.video.twitter.map.fastly.net  -> 151.101.40.158   okdig @8.8.8.8     dualstack.video.twitter.map.fastly.net  -> 146.75.92.158    okdig @9.9.9.9     dualstack.video.twitter.map.fastly.net  -> 151.101.40.158   ok

Comcast's resolver is the only one that returns an address inside 199.232.252.0/22 — the one prefix Comcast's Fresno market cannot route to. traceroute 199.232.252.158 still loops between ar01.fresno and arsc1.sacramento and never reaches your backbone.

Anyone else in the Fresno / Madera market: X / Twitter video almost never plays, in any browser. Setting your router's DNS to 1.1.1.1 works around it.

(edited)

Like

Reply

1 month ago

S

simpleshadow

Visitor

•

8 Messages

@XfinitySara — Any updates here? I'm still experiencing the issue.

Like

Reply

28 days ago

0

Your Home Network

simpleshadow

BGP routing loop — Fastly prefix 199.232.252.0/22 unreachable from Fresno market

XfinitySara

simpleshadow

XfinityJorge

simpleshadow

XfinityVictor

simpleshadow

simpleshadow

XfinityNatalie

EG

user_fkb9t4

XfinityCliff

XfinitySara

XfinitySara

simpleshadow

simpleshadow

New to the Community?