Sorry, no updates. The nature of this issue makes it very hard to tackle. There's nothing wrong on your end, or on our end. Something or someone is messing downloads up for some members in the US. All I'm able to do at this point is pass data on to the reptilian overlord that manages all western civilisation, and our network infrastructure. Seriously though, our sysadmin is a pretty savvy cat; if there's anything he can do, he'll be all over it.
Frans for the Amaya and Bisera video i tried downloading the video in hq and it said it would take over 10hrs to download
Ah.. yeah that qualifies as slow From what host does the download come (cdnXX something) ? If possible could do a nslookup of that servername and post result (first few lines of a traceroute to the cdnXX will also do fine)
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 4 ms L100.HRBGPA-VFTTP-12.verizon-gni.net [18.104.22.168]
3 7 ms 7 ms 8 ms G0-2-1-4.HRBGPA-LCR-22.verizon-gni.net [22.214.171.124]
4 17 ms 16 ms 16 ms ae16-0.RES-BB-RTR2.verizon-gni.net [126.96.36.199]
5 17 ms 17 ms 17 ms 0.xe-2-1-1.BR1.IAD8.ALTER.NET [188.8.131.52]
6 51 ms 51 ms 51 ms te0-3-0-14.ccr41.iad02.atlas.cogentco.com [184.108.40.206]
7 51 ms 49 ms 51 ms be2176.ccr21.dca01.atlas.cogentco.com [220.127.116.11]
8 55 ms 56 ms 55 ms be2155.mpd22.ord01.atlas.cogentco.com [18.104.22.168]
9 56 ms 55 ms 57 ms be2005.ccr21.ord03.atlas.cogentco.com [22.214.171.124]
10 56 ms 55 ms 55 ms te2-1.mag01.ord03.atlas.cogentco.com [126.96.36.199]
11 55 ms 55 ms 56 ms te0-0-2-3.rcr12.b002281-5.ord03.atlas.cogentco.com [188.8.131.52]
12 56 ms 57 ms 69 ms 184.108.40.206
13 * 56 ms 56 ms 220.127.116.11.static.swiftway.net [18.104.22.168]
thanks for that info. Unfortunately that all looks ok. The nslookup returns another ip-adress for me, which is as expected as I'm in another location compared to you. I did test uysing the same ip as you get for the cdn01 server, but that still downloads at ok speed for me. The server itself is fine, it must be something in the network in between. That is harder to figure out, netwerk-admin people will need to look into that.
Frans just curious if there's anything on my end that I can do to fix this besides what I've already done do I need to contact my ISP ?
This really sucks if it helps any I can almost say its a fios issue but it isn't cause I only have problems with this site I can download video from anywhere or stream from anywhere just fine in fact I tested playing a video on a tablet over hspa+ cellular connection and it makes my the fios connection look stupid when playing video from AW but it's not preferred cause it chews up a lot of data so hopefully something can be done about this soon
I'm having the same problem lately. Really slow between the site and my computer, better within this site. Also, when get an image, at the bottom it usually reads "Image of nnn", that is, the image number is missing. This seem to cause the return to imageset always to take me back to page one. Before, and a nice feature, it took me back to the page where the image I was viewing was located. My latest abbytracecnd.txt is
Tracing route to cnd.abbywinters.com [22.214.171.124]
over a maximum of 30 hops:
1 7 ms 3 ms 3 ms homeportal [192.168.1.254]
2 31 ms 23 ms 22 ms 99-126-144-3.lightspeed.mdldtx.sbcglobal.net [126.96.36.199]
3 23 ms 24 ms 32 ms 188.8.131.52
4 29 ms 25 ms 23 ms 184.108.40.206
5 47 ms 45 ms 43 ms gar27.dlstx.ip.att.net [220.127.116.11]
6 51 ms 55 ms 47 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [18.104.22.168]
7 46 ms 47 ms 45 ms ae-1.r21.dllstx09.us.bb.gin.ntt.net [22.214.171.124]
8 109 ms 102 ms 106 ms ae-4.r21.snjsca04.us.bb.gin.ntt.net [126.96.36.199]
9 107 ms 109 ms 114 ms ae-2.r07.snjsca04.us.bb.gin.ntt.net [188.8.131.52]
10 100 ms 99 ms 99 ms xe-0-6-0-29.r07.snjsca04.us.ce.gin.ntt.net [184.108.40.206]
11 98 ms 100 ms 99 ms 220.127.116.11
12 95 ms 99 ms 107 ms 18.104.22.168.static.swiftway.net [22.214.171.124]
Also, when get an image, at the bottom it usually reads "Image of nnn", that is, the image number is missing. This seem to cause the return to imageset always to take me back to page one. Before, and a nice feature, it took me back to the page where the image I was viewing was located.
This is a different bug altogether, one that is much easier to point out as well I've notified web-team/HQ to get that fixed.
(edit to add: the above display issue has been fixed)
Last edited by Frans; 31st March 2014 at 06:38 PM.
Reason: display issue fixed
This problem has cropped up for me again. I have tried my little trick of changing the IP addresses to no avail. IMHO I "think" this is might be related to Netflix usage, but I have no idea why this would be a problem just with AW.
I know you have no idea what is causing the problem but I thought you should know.
I'm also in eastern MA, USA, also on Verizon FIOS, and also seeing very slow download speeds on almost every attempt.
Tracert to cdn.abbywinters.com:
4 8 ms 9 ms 12 ms ae10-0.BOS-BB-RTR2.verizon-gni.net [126.96.36.199]
5 17 ms 19 ms 19 ms 0.ae11.XL4.NYC1.ALTER.NET [188.8.131.52]
6 * * * Request timed out.
7 16 ms 17 ms 16 ms 0.ae2.BR2.NYC4.ALTER.NET [184.108.40.206]
8 47 ms 47 ms 47 ms 220.127.116.11
9 46 ms 61 ms 47 ms be2060.ccr21.jfk02.atlas.cogentco.com [18.104.22.168]
10 56 ms 59 ms 57 ms be2114.ccr41.ord01.atlas.cogentco.com [22.214.171.124]
11 56 ms 57 ms 56 ms te0-1-0-4.ccr22.ord03.atlas.cogentco.com [126.96.36.199]
12 54 ms 54 ms 56 ms te3-1.mag01.ord03.atlas.cogentco.com [188.8.131.52]
13 57 ms 57 ms 56 ms te0-0-2-0.rcr12.b002281-5.ord03.atlas.cogentco.com [184.108.40.206]
14 * * 56 ms 220.127.116.11
15 60 ms 59 ms 59 ms 18.104.22.168.static.swiftway.net [22.214.171.124]
here is some more information. (Just to confirm this is clearly a routing issue.) If I run hola (public VPN) I get high speeds. If I turn off hola and use the standard connection I get slow speeds. (I experimented with hola servers in USA and Amsterdam and both provided faster speeds.)
Only problem with hola is that I can only down load videos not able to see images on the screen. (If I get a request I can make some screen captures.)
I also suspect that AWs hacking algorithims are going to flag my account as being hacked as it likely looks like I am moving around
BTW, as I already requested. if AW can just put up a "G" rated phantom site on the same server I can attempt to get Verizon to look at this. But I am not going to contact them and say I am getting slow speeds downloading files from AW.
Hi, I'm having the same problem--slow downloads & streaming 50 KB/s max on Verizon Fios in Eastern USA. I just signed up for the account, so very confused why there is an issue already! Here's my trace route if anyone is still watching this thread. BTW, has anyone Googled "cogent" in relation to Verizon (see trace route below)? Looks like they've had a storied and difficult past...
Tracing route to cdn.platypusbv.com [126.96.36.199]
over a maximum of 30 hops:
1 3 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 9 ms 12 ms L101.PHLAPA-VFTTP-30.verizon-gni.net [188.8.131.52]
3 19 ms 9 ms 11 ms G0-6-3-0.PHLAPA-LCR-21.verizon-gni.net [184.108.40.206]
4 9 ms 9 ms 10 ms 220.127.116.11
5 17 ms 18 ms 17 ms 0.xe-7-1-0.BR1.IAD8.ALTER.NET [18.104.22.168]
6 16 ms 16 ms 16 ms te0-3-0-14.ccr41.iad02.atlas.cogentco.com [22.214.171.124]
7 21 ms 18 ms 19 ms be2176.ccr21.dca01.atlas.cogentco.com [126.96.36.199]
8 36 ms 36 ms 36 ms be2155.ccr42.ord01.atlas.cogentco.com [188.8.131.52]
9 35 ms 37 ms 36 ms te0-1-0-4.ccr22.ord03.atlas.cogentco.com [184.108.40.206]
10 37 ms 34 ms 36 ms te3-1.mag01.ord03.atlas.cogentco.com [220.127.116.11]
11 37 ms 35 ms 36 ms te0-0-2-0.rcr12.b002281-5.ord03.atlas.cogentco.com [18.104.22.168]
12 36 ms 36 ms 36 ms 22.214.171.124
13 36 ms 36 ms 37 ms 126.96.36.199.static.swiftway.net [188.8.131.52]
When I had joined earlier in the year, downloads took skid in speed. 6 months later I have re-upped ( and had forgot about the DL speed problem). About the most I can get is 350K when it should be 1.8 mbs. You would think that in 6 months this problem could be fixed. If the pathway is the problem, and since servers can be put just about anywhere in the world, why not move them to better location? You got a box and a connection which should be pretty simple.
I am getting about 300kbps on my 55Mbps connect. Pretty unacceptable, it's better during off peak but at night, it's completely unacceptable. I am getting directed to 184.108.40.206. Cogent and TWC are certainly at each others throats over peering compensation. Getting 5-6% loss at the last two hops. That type of lose will certainly ruin TCP sessions down to the trickle I get right now.
I canceled again, this is my second attempt at this site after being a member since 2003, every since this started this CDN distribution of their content the site is slower than free site. I am amazing it hasn't gotten better and it's been a few weeks now. Right now during peak I get 112kbps, it's literally just barely better than a fucking modem.
Last edited by zinner; 7th August 2014 at 03:49 AM.
I see a trend here. Current downloads take over 6-8 hours on my dsl. My connection tends to drop before the download ends. Transfer rates are in the 30s. Not good. Did a little troubleshooting and these are the results. I took out the first line; privacy concerns (router).
Tracing route to cdn.platypusbv.com [220.127.116.11]
over a maximum of 30 hops:
2 39 ms 38 ms 39 ms 10.1.85.1
3 43 ms 42 ms 40 ms G0-9-0-2.WASHDC-LCR-21.verizon-gni.net [18.104.22.168]
4 * * * Request timed out.
5 41 ms 41 ms 41 ms 0.ae1.BR2.IAD8.ALTER.NET [22.214.171.124]
6 42 ms 41 ms 41 ms te0-1-0-14.ccr41.iad02.atlas.cogentco.com [126.96.36.199]
7 42 ms 43 ms 42 ms be2177.ccr22.dca01.atlas.cogentco.com [188.8.131.52]
8 62 ms 61 ms 62 ms be2153.ccr42.ord01.atlas.cogentco.com [184.108.40.206]
9 61 ms 62 ms 61 ms be2003.ccr21.ord03.atlas.cogentco.com [220.127.116.11]
10 63 ms 63 ms 64 ms be2461.rcr12.b002281-5.ord03.atlas.cogentco.com [18.104.22.168]
11 63 ms 168 ms 64 ms 22.214.171.124
12 66 ms 66 ms 66 ms 126.96.36.199.static.swiftway.net [188.8.131.52]
Same problem today and no response from famed Tech Support claiming response in 15 minutes, not even a Robo reply.
That's 'cos robo-replies don't fix anything Whatever is causing these speed issues for you, it only seems to affect a few people. That doesn't help the ones affected, but it does point more to a problem outside AW reach. There's a huge amount of wire/traffic before content gets from AW to your pc, trouble is that the stuff in between is sometimes hard to get to work together nicely
I ditched Verizon (because I moved out of the area, but I might have done so anyway), and now everything seems fine. Since everyone witth problems seems to be using Verizon in the norheastern US, I suspect that Verizon may be partially to blame here...