Posted on 12/17/2021 1:53:41 PM PST by Brookhaven
The Epoch Times techies are telling the newsroom that Xfinity is blocking customers from opening the news web site, as well as the backend editing functions. Any Instapundit readers encountering this problem? If you are, please call Xfinity and RAISE HOLY HELL!
Update (from Steve): For what it’s worth, I’m on Xfinity and can’t get Epoch Times to load. But it loads just fine on cellular when I turn my phone’s wifi off.
(Excerpt) Read more at pjmedia.com ...
Using “1.1.1.1” as my DNS server does now work correctly. Looks like the Comcast DNS servers are at fault....they are “75.75.75.75” & “76.76.76.76”.
turning on vpn in norton works also.
Its not working for me and I don’t use comcast’s DNS.
If you’re using Chrome click on English translation. My browser (Chrome) came up in Chinese but when I clicked on English, it translated.
epoch times became a spinning beachball for me around 1500 EDT, just about the time that I received an email from ET about “5 foods never to buy from China”.
I could not get that link to load, nor any bookmarked or archived ET pages.
I suspect malware in that email.
Just got off the phone with comcast. The rep could not get on either. I can get on the site going through blokada vpb and pia vpn, just not through xfinity. They had no solution. Evil. Is this where we are that technocrat fascists can block content they dislike? What a very dark place they take us to.
I’m on Fios and nothing. I have ATT cellular and nothing their either. Could the site be down?
Yeah something is up...the “1.1.1.1” DNS worked earlier...now not so much. Do we have a correct IP for “theepochtimes.com”?? My “traceroute” to their supposed IP of “151.139.128.11” times out after 3 hops:
~ % traceroute www.theepochtimes.com
traceroute to s9y9b6x8.stackpathcdn.com (151.139.128.11), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.832 ms 0.450 ms 0.344 ms
2 96.120.84.209 (96.120.84.209) 17.744 ms 9.320 ms 12.911 ms
3 ae-152-1210-rur02.clovis.ca.ccal.comcast.net (68.87.203.117) 12.033 ms 11.490 ms 11.919 ms
4 * * *
5 * * *
6 * * *
7 * * *
It stops at a local Comcast router.
Their site is up, I can get to it using my VPN (”SurfShark”, San Jose CA server)...just not with my “regular” DNS/connection.
Suddenly resumed working for me on Xfinity.
1950 MST working again. Earlier it only worked if I turned off wifi on my phone.
Phone was never an issue for me (AT&T) unless I had it tethered to my home Xfinity wifi.
Most likely it was China hacking.
Aye, and most likely linked to the email I cited upstream...really out to get those who anti-Chinaphiles.
Yeah, now back for me as well...I did a “DNS cache flush” and changed my primary DNS to “1.1.1.1”, so I am not sure if Comcast fixed their router tables or DNS servers or if my changes fixed it...oh well, OK for now.
Good alternate DNS server:
C:\Users\jpsb>ping theepochtimes.com
Pinging theepochtimes.com [34.107.251.210] with 32 bytes of data:
Reply from 34.107.251.210: bytes=32 time=21ms TTL=115
Reply from 34.107.251.210: bytes=32 time=27ms TTL=115
Reply from 34.107.251.210: bytes=32 time=22ms TTL=115
Reply from 34.107.251.210: bytes=32 time=23ms TTL=115
Ping statistics for 34.107.251.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 27ms, Average = 23ms
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.