Don't worry, it's not your computer!
1 post,
1 voice
tyler
15 post(s)
|
I have talked to a friend who works with Zap2it and he has told me that the problem is being worked on and they are trying to get the service back up and running asap! The reason you may be experiencing problems while updating your data is because the Zap2it data server is not responding. Here are some stats: PING OF 206.18.98.145 (Zap2it) @ 7:23PM EST Ping has started … PING 206.18.98.145 (206.18.98.145): 56 data bytes
TRACEROUTE Traceroute has started … traceroute to 206.18.98.145 (206.18.98.145), 64 hops max, 40 byte packets 1 192.168.2.1 (192.168.2.1) 1.734 ms 1.401 ms 1.318 ms 2 10.250.158.1 (10.250.158.1) 10.222 ms 7.799 ms 7.888 ms 3 gw01.orgl.phub.net.cable.rogers.com (66.185.91.33) 9.877 ms 11.793 ms 8.208 ms 4 so-5-0-0.gw02.wlfdle.phub.net.cable.rogers.com (64.71.240.101) 12.208 ms 9.514 ms 7.871 ms 5 so-5-1-3.gw02.mtnk.phub.net.cable.rogers.com (66.185.81.181) 24.050 ms 23.697 ms 11.098 ms 6 so-2-0-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.80.41) 11.283 ms 8.905 ms 9.888 ms 7 pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com (66.185.80.190) 25.402 ms 29.088 ms 27.337 ms 8 pos2-1.ar2.dca3.gblx.net (208.51.239.201) 32.179 ms 42.851 ms 41.270 ms 9 192.205.33.33 (192.205.33.33) 40.283 ms 34.181 ms 52.289 ms 10 tbr1.wswdc.ip.att.net (12.122.84.158) 39.626 ms 37.178 ms 38.739 ms 11 tbr2.phlpa.ip.att.net (12.122.2.86) 39.152 ms 37.391 ms 40.355 ms 12 tbr2.cgcil.ip.att.net (12.122.10.93) 37.993 ms 37.870 ms 40.448 ms 13 12.122.99.73 (12.122.99.73) 36.950 ms 36.159 ms 44.511 ms 14 12-122-254-50.attens.net (12.122.254.50) 39.164 ms 41.380 ms 39.682 ms 15 mdf1-bi8k-2-eth-1-1.chi1.attens.net (63.240.128.134) 40.269 ms 39.347 ms 39.918 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * PORT SCAN Port Scan has started … Port Scanning host: 206.18.98.145 No open ports found! So as you can see, nothing is coming through… I guess we will just have to try our best to deal without this great service until it comes back online. Cheers! |