is zdnet.com down (updated) blocked on Comcast?

Ok, as a followup to my favorite Netflix is down post, I am unable to reach zdnet.com/news or zdnet.com/blog

Anyone one else experiencing this issue? or did I mess something up again on my network security settings? Everything else seems to work for me, including downloads.zdnet.com

downornot.com shows zdnet is working good, but I cannot reach anything on that site. My ISP is Comcast. I am not sure when the issue started, but I first discovered it at about 10:15am EST today

*** Update *** 11:35am EST
I have tried from another computer at my current location and received the same errors, I have also tried accessing it from my cell phone using my cell carrier for the ISP (Sprint) instead of Comcast, and it is working fine, but when I put my phone on wifi and connect to my network, it is blocked from there also.

*** Update *** 12:39pm EST

still unable to connect from home, all other websites work fine. I’ve run some tests and even changed my DNS entries to remove comcast.


C:\Windows\system32>tracert zdnet.com

Tracing route to zdnet.com [216.239.116.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ************************* 2 43 ms 29 ms 29 ms ************************* 3 9 ms 8 ms 9 ms ************************* 4 11 ms 12 ms 8 ms ************************* 5 13 ms 13 ms 13 ms te-1-3-ar02.savannah.ga.savannah.comcast.net [68.86.250.97] 6 17 ms 16 ms 15 ms te-8-8-ar01.westside.fl.jacksvil.comcast.net [68.86.168.209] 7 27 ms 27 ms 28 ms te-1-0-0-1-cr01.charlotte.nc.ibone.comcast.net [68.86.93.169] 8 33 ms 32 ms 30 ms pos-3-15-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.225] 9 35 ms 35 ms 35 ms pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.86] 10 31 ms 31 ms 41 ms 66.208.229.218 11 50 ms 52 ms 49 ms tge16-1.fr3.dal.llnw.net [68.142.125.17] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:\Windows\system32>nslookup zdnet.com
Server: cdns01.comcast.net
Address: 75.75.75.75

Non-authoritative answer:
Name: zdnet.com
Address: 216.239.116.157

C:\Windows\system32>nslookup zdnet.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

C:\Windows\system32>ping 216.239.116.157

Pinging 216.239.116.157 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.239.116.157:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Non-authoritative answer:
Name: zdnet.com
Address: 216.239.116.157

C:\Windows\system32>

I then tried a traceroute from my Cell phone…

# /system/xbin/busybox traceroute 216.239.116.157
traceroute to 216.239.116.157 (216.239.116.157), 30 hops max, 38 byte packets
1  ****************************        394.470 ms   86.303 ms  125.550 ms
2  ****************************         91.034 ms   89.569 ms  106.568 ms
3  ****************************        139.923 ms  136.292 ms  270.050 ms
4  68.28.245.69 (68.28.245.69)         169.830 ms  244.751 ms  230.164 ms
5  144.223.135.121 (144.223.135.121)   304.443 ms  216.858 ms  227.814 ms
6  144.232.25.115 (144.232.25.115)     214.782 ms  
   144.232.4.45 (144.232.4.45)         211.884 ms  
   144.232.25.115 (144.232.25.115)     224.548 ms
7  144.232.25.55 (144.232.25.55)       158.600 ms  
   144.232.25.117 (144.232.25.117)     117.797 ms  
   144.232.2.189 (144.232.2.189)       205.444 ms
8  144.232.18.234 (144.232.18.234)     194.030 ms  184.754 ms  221.557 ms
9  4.69.138.126 (4.69.138.126)         266.510 ms  204.926 ms  286.407 ms
10  4.69.140.142 (4.69.140.142)        229.339 ms  225.311 ms  178.193 ms
11  4.69.148.253 (4.69.148.253)        190.643 ms  234.008 ms  194.855 ms
12  4.69.134.21 (4.69.134.21)          174.835 ms  289.795 ms  449.829 ms
13  4.69.132.77 (4.69.132.77)          251.526 ms  213.044 ms  288.421 ms
14  4.69.148.202 (4.69.148.202)        303.009 ms  354.676 ms  331.573 ms
15  4.69.148.142 (4.69.148.142)        413.544 ms  269.379 ms  263.153 ms
16  4.69.153.33 (4.69.153.33)          255.035 ms  361.939 ms  406.097 ms
17  4.69.140.153 (4.69.140.153)        335.083 ms  341.430 ms  222.839 ms
18  4.69.140.145 (4.69.140.145)        156.372 ms  348.267 ms  345.398 ms
19  4.69.133.149 (4.69.133.149)        319.336 ms  323.516 ms  297.790 ms
20  4.53.132.2 (4.53.132.2)            339.081 ms  313.660 ms  217.193 ms
21  216.239.127.38 (216.239.127.38)    181.030 ms  288.055 ms  341.584 ms
22  216.239.116.157 (216.239.116.157)  336.456 ms  334.961 ms  328.094 ms
#


Sent from my HTC Evo unrEVOked forever.  Running MikG 2.4.1 rooted Gingerbread Rom with HTC Sense 2.1+ 3.0

*** Update *** 1:00pm EST
since I am sure someone will ask, yes I have cleared all browsing data, cache, and cookies

*** Update *** 5:20pm EST
all seems to be working now

About

3 thoughts on “is zdnet.com down (updated) blocked on Comcast?

    1. I have only received 17 hits on this page, so not sure how widespread the issue is (when I posted about netflix down, granted there are more users, but I had 1400 hits in 3 hours or so…)

      as I mentioned above, it works fine from my cell phone.

Leave a Reply

13 visitors online now
0 guests, 13 bots, 0 members
Max visitors today: 15 at 07:30 am UTC
This month: 58 at 01-20-2019 02:22 pm UTC
This year: 58 at 01-20-2019 02:22 pm UTC
All time: 1100 at 08-08-2011 08:11 pm UTC