@cloudflare can't reach your CDN at 198.41.215.186 from Comcast in SF. all other IPs are fine but resolver keeps picking that one. HALP!
-
-
Replying to @s5
@s5 What do you see in a traceroute to the domain or IP address? Directions for a traceroute: https://support.cloudflare.com/hc/en-us/articles/200169336-How-do-I-run-a-traceroute- …1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare it reaches the end. last hop is 11 198.41.215.186 (198.41.215.186) 15.472 ms 13.402 ms 13.444 ms2 replies 0 retweets 0 likes -
Replying to @s5
@s5 Can you put the trace in something like http://pastebin.com ? Much easier for me to share with OPs (had one other report & will check)2 replies 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare I can connect by hand: http://pastebin.com/f7a6s4dZ but in any browser I try, it hangs and hangs, even after reboot and cache clear.2 replies 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare restarted all network equipment and tried another computer, same problem. switched over to AT&T LTE, and it connects.1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare thanks. now I'm seeing the same problem with Cloudfront. Is it at all possible that Comcast is blocking/slowing CDNs?2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.