Visitor
•
1 Message
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.


No Responses!