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
-
- cached copies from google are working
-
- IE8 trying to reach zdnet
-
- IE8 trying to reach zdnet
-
- IE8 trying to reach zdnet
-
- IE8 trying to reach zdnet
-
- I clicked a link from the email newsletter and got this
-
- zdnet.com failure
-
- tried to go to the news part
-
- downornot.com shows it is up
So, I was just trying to manage my Netflix account, at 10:30pm EST on August 8th 2011, and went to check on my DVD queue when I received this strange error. I tried going back to the previous page and selecting another link, but it still didn’t work. So I thought maybe there was an issue with Google Chrome, so I tried IE8, still no dice… Maybe tomorrow some other websites will have reported it, but for now The Netflix Members section is down, at least for me.
Possibly they got cut off by Comcast? Who knows, maybe it is just me? I did have a similar experience with Hotmail a while back and never heard anything about it, except for my issues. So, we shall see…
***update now I cannot get to the netflix.com page either***
10:45pm EST August 8th, 2011
Wow, talk about a fast response, by the time I added the update above there were already 25 comments on this post. Making it my post with the most! I should complain about things more often! Links to this post went out via Twitter and Google+ (Public). Sometimes it is nice to know we are not alone.
10:55pm EST August 8th, 2011
***Update 11:30pm EST August 8th, 2011 – Was just able to log in, view recommended movies, opened up my queue, all loaded nicely. Then I went back to browse DVD’s and was going to grab a screen capture when I got the “No data received” error again. 4 refreshes and 8 minutes later, I received a page again, as shown below.
-
- I was rating several movies from the suggestions page and clicked on my queue to receive this page
-
- I clicked the “Members sign in” button and 30 seconds later I was greeted by this image
-
- 11:12pm EST Some people are reporting success getting back in, this is what I just received
-
- A map of all the visitors starting just before I made this post
-
- Netflix struggles to come back up, but how many more ups and downs before it stays?
-
- updated map from 11.5 hours later showing the people that got cut off from the first one
was trying to add a link on my links page (which you probably still can’t get to) for my Microsoft Spaces page, so I went to sign into hotmail to jump to my space, and this is what I get…
( click to enlarge)
-
- Unable to connect to server?
- New blog post... Diablo III closed Beta http://t.co/dKC2ChWm
- New blog post... resolving video problems with K-L-Ubuntu and XFX Radeon 6850 http://t.co/H6bXuMqi
- New blog post... Computer upgrades http://t.co/6PWVNy4m
- $7 for $15 Worth of Hand-Tossed Pizza, Calzones, and Drinks at Andolini's Pizza Charleston, SC http://t.co/QnKwPwB
- New blog post... is zdnet.com/news down http://t.co/DThuI4r
- New blog post... Netflix Down? http://bit.ly/q74Svu
