Visitor
•
2 Messages
YouTube cache node 50.151.220.26 not accepting TCP from my area (YouTube buffering)
Since at least 2026-09-11, YouTube playback stalls because the Google Global Cache
node inside the Comcast network at 50.151.220.26 is not accepting connections.
Evidence, gathered 2026-09-11 from two different machines on my LAN:
- Hostnames rr6---sn-bvvbaxivnuxqjvhj5nu-hp56.googlevideo.com and
rr11---sn-bvvbaxivnuxqjvhj5nu-hp56.googlevideo.com resolve to 50.151.220.x.
- TCP connections to 50.151.220.26 on ports 443 and 80 time out (no SYN-ACK).
- ICMP ping to the same address succeeds (~15 ms), and traceroute reaches it
via 50.150.167.218 > 50.146.186.158 > 50.151.220.26.
- The sibling cache nodes at 50.218.242.23 / .87 / .15 (hostnames ending in
-hp5e and -hp5l) connect in ~20 ms and work normally.
- My router has no firewall, IPS, or QoS rule affecting this address.
YouTube keeps directing my clients to the dead node, and each retry causes
multi-second buffering. Please have network engineering check the host at
50.151.220.26 or remove it from rotation. Happy to provide account details
and my public IP by private message.
user_63zlv0
Visitor
•
1 Message
13 hours ago
Same cluster, same problem here (Broward County, FL). It's not just .26. 50.151.220.21, .24 and .26 all ignore TCP 443 from my connection. Ping to them works fine at ~12 ms, the SYN just never gets answered.
It breaks Play Store downloads too, not only YouTube. Android resolves rr9.sn-bvvbaxivnuxqjvhj5nu-hp56.gvt1.com to .24 and hangs on it for 130 seconds every time. Updates sit on Pending, then fail.
0
0
XfinityAirelle
Official Employee
•
3.6K Messages
2 hours ago
Hi there! We sincerely apologize for how long it has taken us to respond. A 26-day gap is far too long, especially after you provided such detailed troubleshooting and network information upfront.
We can see that you had already narrowed this down extensively and identified 50.151.220.26 as the specific cache node that was timing out while nearby nodes were responding normally. You also confirmed the route was reachable and that there were no local firewall, IPS, or QoS rules affecting the connection, so we understand why you were asking for this to be reviewed beyond basic home-network troubleshooting.
Are you still experiencing the YouTube buffering issue or seeing traffic directed to 50.151.220.26? If so, we’d like to pick this back up from where you left off rather than having you repeat the troubleshooting you already completed.
2
0
EG
Expert
•
121.9K Messages
56 minutes ago
@user_63zlv0 @XfinityMartyR
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