Announcement

Collapse
No announcement yet.

Downloads really slow

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Downloads really slow

    My downloads have been really slow lately. They seem to be going at about 50 or 60 KB/s, which means that a full video would take about 6 hours to download. My internet speed seems to be fine. Various on-line speed tests give me a download speed of about 5000 Kb/s, which is a bit over 600 KB/s. So my download speed is at about a tenth of what it could be on my connection. There used to be an option to choose between different download servers, but that doesn't seem to be available any more. Any idea what could be going wrong?

    #2
    I have similar situation

    Originally posted by louseboy View Post
    My downloads have been really slow lately. They seem to be going at about 50 or 60 KB/s, which means that a full video would take about 6 hours to download. My internet speed seems to be fine. Various on-line speed tests give me a download speed of about 5000 Kb/s, which is a bit over 600 KB/s. So my download speed is at about a tenth of what it could be on my connection. There used to be an option to choose between different download servers, but that doesn't seem to be available any more. Any idea what could be going wrong?
    I am also having downloading issues. noticed about a week ago.

    Comment


      #3
      Hey guys,

      Whilst we're not having server issues, and most folks seem to be able to download fine, you're not alone here. I've received several similar reports of reduced download speed over the past few days.

      In the spirit of getting a clearer idea of what is going wrong where, I'd really appreciate if you could give me a tracer route test. What it does is send some data from you to us and back again, this generates a little list of co-ordinates listing what 'path' the data took. We can then look at that and see if we can figure out why it's going slower, and what we can do to fix that.

      Here's what we need you to do:

      (1) Open a DOS prompt, START menu, Run..., type "cmd"
      without the quotes (or "command" if you're using
      anything older than Windows 7). A black window will
      open up with a flashing cursor. Very 1991, eh?

      (2) Typethe following; it has to be exact, letter for
      letter, space for space:

      tracert cdn.abbywinters.com > c:\abbytracecdn.txt

      (3) After typing, press the ENTER key on your keyboard.
      Not much will happen. After a minute or so, you'll
      go back to a DOS prompt with a flashing cursor.
      If you get a message, you'll need to type it again.

      (4) You're done here. Type "exit", press ENTER, the
      black screen will go away.

      (5) Double click on your "My Computer" icon (usually,
      top left corner of your screen)

      (6) Double click on your C Drive icon

      (7) Look for this file:

      abbytracecdn.txt

      (8) Double click on them, one by one. Each time it will
      open a program called Notepad, with a bunch of web
      addresses and numbers and stuff in it.

      (9) Hold down the CTRL ("control") button on your
      keyboard, and tap the "A" key. This is a shortcut
      to "select all". The text will go white, and the
      background black. Let go of the CTRL key.

      (10) Hold down CTRL again, and tap the "C" key, then
      let go of the CTRL key. This will copy that stuff
      into the computers memory. If it all disappears and
      is replaces with the letter c, you need to hold
      down CTRL again, and tap the Z key. This will undo
      the last action. Go back to step 9 above, and try
      again.

      (11) Open a reply to this thread, hold down the CTRL key,
      and tap the V key. Your trace info should appear
      there as if by magic.

      Alternately, you could send an email to accounts@abbywinters.com, where I'll receive it and be able to contact you 1 on 1.

      If you can do this for us, we'll hopefully be able to more clearly state why your speed is slower than usual, and the prospects for improvement.

      Cheers!

      Comment


        #4
        I think you can attach the abbytracecdn.txt file as well.. attachment to the reply. Easier then copy/paste
        The file you want is usually in C:\Users\your-pc-user-name-here (not in Documents, but one above it).

        Do note that a full traceroute will include your IP-address and somewhat of location since it shows the route you take from your pc to the abbywinters server. Mailing the full trace to support might be better.

        You could remove your own IP from trace, usually 2nd line, but that might not be enough to anomize it. This part of the forums is publicy readable, full traces are more helpful.
        Attached Files

        Comment


          #5
          I have been having the same issue. Downloading files and streaming are both very slow, I first noticed this earlier this week. Thanks for your help!

          Comment


            #6
            The tail end of my traceroute looks like this:

            5 0.xe-3-3-0.br2.nyc4.alter.net (152.63.23.133) 24.490 ms
            0.xe-7-1-0.br2.nyc4.alter.net (152.63.22.253) 25.567 ms
            0.xe-3-3-0.br2.nyc4.alter.net (152.63.23.133) 24.255 ms
            6 204.255.168.114 (204.255.168.114) 80.370 ms 75.344 ms
            204.255.168.110 (204.255.168.110) 71.375 ms
            7 be2063.mpd22.jfk02.atlas.cogentco.com (154.54.47.57) 71.345 ms 76.491 ms
            be2060.ccr21.jfk02.atlas.cogentco.com (154.54.31.9) 73.833 ms
            8 be2116.mpd21.ord01.atlas.cogentco.com (154.54.7.26) 92.361 ms
            be2115.ccr22.ord01.atlas.cogentco.com (154.54.6.190) 87.269 ms 89.578 ms
            9 be2004.ccr21.ord03.atlas.cogentco.com (154.54.5.10) 95.174 ms
            be2003.ccr21.ord03.atlas.cogentco.com (154.54.29.22) 91.961 ms 89.465 ms
            10 te2-1.mag01.ord03.atlas.cogentco.com (154.54.40.174) 138.862 ms 108.731 ms 106.136 ms
            11 vl3505.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.6) 114.564 ms
            vl3805.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.10) 110.666 ms 107.896 ms
            12 38.104.102.126 (38.104.102.126) 107.061 ms 107.170 ms 107.840 ms
            13 * * *
            14 * * *
            15 * * *
            16 * * *
            17 * * *
            18 * * *
            19 * * *
            20 * * *
            21 * * *
            22 * * *
            23 * * *
            24 * * *
            25 * * *
            26 * * *
            27 * * *
            28 * * *
            29 * * *
            30 * * *
            31 * * *
            32 * * *
            33 * * *
            34 * * *
            35 * * *
            36 * * *
            37 * * *
            38 * * *
            39 * * *
            40 * * *
            41 * * *
            42 * * *
            43 * * *
            44 * * *
            45 * * *
            46 * * *
            47 * * *
            48 * * *
            49 * * *
            50 * * *
            51 * * *
            52 * * *
            53 * * *
            54 * * *
            55 * * *
            56 * * *
            57 * * *
            58 * * *
            59 * * *
            60 * * *
            61 * * *
            62 * * *
            63 * * *
            64 * * *
            Last edited by louseboy; 5 February 2014, 08:06 PM.

            Comment


              #7
              I can add that my traceroute is essentially the same, I just cut it off after the endless * * * rows. Note that the last hop is the same as reported above.

              traceroute to cdn.platypusbv.com (149.255.32.185), 64 hops max, 52 byte packets
              1 wireless_broadband_router (192.168.1.1) 2.341 ms 1.188 ms 1.509 ms
              2 10.5.35.112 (10.5.35.112) 6.434 ms 12.894 ms 6.555 ms
              3 g0-13-0-4.nwrknj-lcr-22.verizon-gni.net (130.81.110.68) 7.903 ms 7.830 ms 9.399 ms
              4 130.81.162.84 (130.81.162.84) 7.713 ms
              ae4-0.nwrk-bb-rtr2.verizon-gni.net (130.81.199.194) 9.016 ms
              so-6-1-0-0.nwrk-bb-rtr2.verizon-gni.net (130.81.199.16) 7.789 ms
              5 0.xe-11-2-0.br2.nyc4.alter.net (152.63.20.221) 14.382 ms
              0.xe-3-2-0.br2.nyc4.alter.net (152.63.20.213) 11.753 ms 7.830 ms
              6 204.255.168.114 (204.255.168.114) 89.302 ms 85.118 ms 80.125 ms
              7 be2060.ccr21.jfk02.atlas.cogentco.com (154.54.31.9) 86.681 ms 86.541 ms
              be2062.mpd21.jfk02.atlas.cogentco.com (154.54.7.13) 81.352 ms
              8 be2115.ccr22.ord01.atlas.cogentco.com (154.54.6.190) 94.401 ms
              be2117.mpd22.ord01.atlas.cogentco.com (154.54.7.58) 94.444 ms 91.896 ms
              9 be2005.ccr21.ord03.atlas.cogentco.com (66.28.4.74) 90.645 ms 93.096 ms
              be2004.ccr21.ord03.atlas.cogentco.com (154.54.5.10) 94.547 ms
              10 te2-1.mag01.ord03.atlas.cogentco.com (154.54.40.174) 128.765 ms 127.646 ms 131.546 ms
              11 vl3505.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.6) 135.238 ms
              vl3805.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.10) 127.273 ms
              vl3505.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.6) 127.385 ms
              12 38.104.102.126 (38.104.102.126) 132.374 ms 126.123 ms 128.658 ms
              13 * * *
              14 * * *
              15 * * *
              16 * * *
              17 * * *

              Comment


                #8
                Good, good! Keep 'em coming in. I'm brushing up on my Ancient Sumerian and sourcing some virgin lamb's blood. Together I think we should be able to invoke the Elder Geeks without incurring their wrath. Providing these eldritch and dire masters of the ether are of a benevolent and merciful disposition, there's every likelyhood they'll be able to scry into these reports and offer meaningful (if cryptic) analysis.

                That or a pox on 13 generations of our descendants; hard to say...

                Comment


                  #9
                  I'll add myself to the list of people seeing very slow downloads.

                  traceroute cdn.abbywinters.com
                  traceroute to cdn.platypusbv.com (149.255.32.185), 64 hops max, 52 byte packets
                  1 192.168.1.1 (192.168.1.1) 1.078 ms 0.322 ms 0.272 ms
                  2 96.120.64.145 (96.120.64.145) 7.814 ms 9.276 ms 8.608 ms
                  3 te-7-2-ur01.clinton.ct.hartford.comcast.net (68.85.141.1) 15.797 ms 8.127 ms 8.255 ms
                  4 be-64-ar01.chartford.ct.hartford.comcast.net (68.85.162.190) 11.576 ms 12.162 ms 11.658 ms
                  5 pos-3-8-0-0-ar01.needham.ma.boston.comcast.net (69.139.220.101) 19.278 ms 15.758 ms 15.997 ms
                  6 he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.93.185) 31.116 ms 24.577 ms 24.801 ms
                  7 he-0-12-0-0-pe03.111eighthave.ny.ibone.comcast.net (68.86.83.106) 20.399 ms 21.196 ms 20.127 ms
                  8 be7922.ccr21.jfk10.atlas.cogentco.com (154.54.13.161) 81.835 ms 69.635 ms 71.404 ms
                  9 be2073.ccr21.jfk05.atlas.cogentco.com (154.54.0.229) 82.491 ms 70.301 ms 71.131 ms
                  10 be2056.ccr21.jfk02.atlas.cogentco.com (154.54.44.217) 72.208 ms
                  be2057.ccr22.jfk02.atlas.cogentco.com (154.54.80.177) 71.484 ms 74.076 ms
                  11 be2115.ccr22.ord01.atlas.cogentco.com (154.54.6.190) 83.344 ms 85.246 ms
                  be2117.mpd22.ord01.atlas.cogentco.com (154.54.7.58) 86.250 ms
                  12 be2003.ccr21.ord03.atlas.cogentco.com (154.54.29.22) 86.290 ms
                  be2004.ccr21.ord03.atlas.cogentco.com (154.54.5.10) 84.115 ms 84.856 ms
                  13 te2-1.mag01.ord03.atlas.cogentco.com (154.54.40.174) 83.549 ms 83.362 ms 83.567 ms
                  14 * vl3805.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.10) 83.968 ms
                  vl3505.na41.b002281-5.ord03.atlas.cogentco.com (38.20.49.6) 83.621 ms
                  15 38.104.102.126 (38.104.102.126) 52.359 ms 45.538 ms 43.418 ms
                  16 * * *
                  17 * * *

                  Comment


                    #10
                    Frans is better equipped to comment on this than most; it's my understanding that what we're seeing here (~100ms latency) isn't catastrophically slow...

                    Not to say you aren't having slow speeds; rather that the problem may not be in the packet latency. Maybe.

                    Comment


                      #11
                      Right, latency in traceroutes doesn't tell you all that much. What a tracroute DOES tell, is how traffic goes from A to B. Which route it traces so to speak
                      All traces seem to end on 38.104.102.126 which might be interested, best to forward this to the network people.

                      Comment


                        #12
                        after over a week still having problems. Sent tracerts and ping before.

                        i still think this is YOUR server, or routers (I believe its router. Have you rebooted / reset it lately)

                        Comment


                          #13
                          after over a week still having problems. Sent tracerts and ping before.

                          i still think this is YOUR server, or routers (I believe its router. Have you rebooted / reset it lately)

                          not sure if coincidence or not, but it appears that both I and bringer5 are in eastern MA USA.

                          here is a tracert from today
                          Tracing route to cdn.platypusbv.com [149.255.32.185]
                          over a maximum of 30 hops:

                          1 <1 ms <1 ms <1 ms 192.168.1.1
                          2 7 ms 6 ms 7 ms L100.BSTNMA-VFTTP-107.verizon-gni.net [98.110.18
                          7.1]
                          3 9 ms 11 ms 7 ms G0-14-1-1.BSTNMA-LCR-22.verizon-gni.net [130.81.
                          217.190]
                          4 10 ms 9 ms 7 ms ae10-0.BOS-BB-RTR2.verizon-gni.net [130.81.163.1
                          72]
                          5 33 ms 32 ms 17 ms 0.xe-5-1-0.BR2.NYC4.ALTER.NET [152.63.21.221]
                          6 98 ms 97 ms 96 ms 204.255.168.114
                          7 97 ms 94 ms * be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
                          13]
                          8 95 ms 92 ms 94 ms be2117.mpd22.ord01.atlas.cogentco.com [154.54.7.
                          58]
                          9 98 ms 97 ms 94 ms be2006.ccr21.ord03.atlas.cogentco.com [154.54.5.
                          18]
                          10 96 ms 94 ms 94 ms te2-1.mag01.ord03.atlas.cogentco.com [154.54.40.
                          174]
                          11 97 ms 95 ms 91 ms vl3805.na41.b002281-5.ord03.atlas.cogentco.com [
                          38.20.49.10]
                          12 142 ms 95 ms 95 ms 38.104.102.126
                          13 97 ms 94 ms 96 ms 185.32.255.149.static.swiftway.net [149.255.32.1
                          85]

                          Trace complete.

                          Comment


                            #14
                            Hey buyerclub22; the problem could indeed be on our end, but it doesn't seem to be affecting the vast majority of users. I don't have the technical expertise to diagnose this one on my lonesome, so the matter has been escalated to the dim, dark, and dank caverns where the nerds live. You are right about the location thing. All reports I have received thus far seem to be coming out of the USA, particularly VA, MI, and MA. Could be a coincidence, perhaps not.

                            Comment


                              #15
                              Also currently in eastern MA. Traceroutes still going to 38.104.102.126, followed by scads of * * * rows.

                              Comment


                                #16
                                I don't see any encouraging messages from the techies at AW. Is anyone actually doing something about resolving this issue? It sure hasn't resolved itself.

                                Comment


                                  #17
                                  An update.... This problem WENT AWAY for awhile for me last week. I noticed it is back again starting last night. Very strange. Did speed tests using speeedtest.net seeing download speeds to several servers @ over 70mbps. - So the problem is isolated to some route. If there are tests that you want me to do (Beyond the tracerts that I have already provided.) let me know.

                                  I also just did a tracert, which I will copy below. However notice that like louseboy The latency issue seems to be at 38.104.102.126 Doing a whois to that IP address I get Spencer Stuart International. You may want to check with your IP supplier.
                                  Click image for larger version

Name:	2014-03-02_115605.jpg
Views:	1
Size:	22.2 KB
ID:	646826
                                  Microsoft Windows [Version 6.1.7601]
                                  Copyright (c) 2009 Microsoft Corporation. All rights reserved.

                                  C:\Users\jon>tracert cdn.abbywinters.com

                                  Tracing route to cdn.platypusbv.com [149.255.32.185]
                                  over a maximum of 30 hops:

                                  1 2 ms <1 ms 252 ms Wireless_Broadband_Router.home [192.168.1.1]
                                  2 9 ms 8 ms 9 ms L100.BSTNMA-VFTTP-107.verizon-gni.net [98.110.18
                                  7.1]
                                  3 10 ms 16 ms 19 ms G0-14-1-1.BSTNMA-LCR-22.verizon-gni.net [130.81.
                                  217.190]
                                  4 40 ms 57 ms 65 ms ae10-0.BOS-BB-RTR2.verizon-gni.net [130.81.163.1
                                  72]
                                  5 21 ms 22 ms 20 ms 0.xe-7-1-0.BR2.NYC4.ALTER.NET [152.63.22.253]
                                  6 50 ms 51 ms 49 ms 204.255.168.114
                                  7 50 ms 52 ms 48 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31
                                  .9]
                                  8 65 ms 60 ms 55 ms be2114.ccr21.ord01.atlas.cogentco.com [66.28.4.2
                                  02]
                                  9 62 ms 54 ms 57 ms te0-1-0-4.ccr22.ord03.atlas.cogentco.com [66.28.
                                  4.78]
                                  10 55 ms 54 ms 57 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.
                                  182]
                                  11 58 ms 56 ms 56 ms te0-0-2-0.rcr12.b002281-5.ord03.atlas.cogentco.c
                                  om [154.54.6.250]
                                  12 * 59 ms 57 ms 38.104.102.126
                                  13 54 ms 54 ms 55 ms 185.32.255.149.static.swiftway.net [149.255.32.1
                                  85]

                                  Trace complete.

                                  C:\Users\jon>
                                  Last edited by buyerclub22; 2 March 2014, 04:56 PM.

                                  Comment


                                    #18
                                    doesnt look like it. must be beyond their capabilities

                                    Comment


                                      #19
                                      solved for me at least in the short term.

                                      so i fixed this for me, (at least for now).

                                      my ISP is FIOS in the East coast USA

                                      The process that I used was to go to the settings on my home router, and release my WAN IP address. (The IP address that the ISP provides via their DHCP server. (This is NOT your homes router's DHCP server that provides ip addresses for all your devices in your home network.)

                                      then turn athe router off (i.e. no power) and wait at least 10 minutes before you power up again. When you power up again, hopefully your home router will be assigned a new IP address.

                                      and hopefully this new ip address will use a different route to get to the AW servers in amsterdam. (at least it did for me.)

                                      Only problem of course is that once my ip address gets renewed this problem may re-appear. (I will inform you if it does)

                                      Comment


                                        #20
                                        interesting.. that would mean routing is a problem for a specific ip, or you just got lucky with the router reset as a whole?

                                        Are you really downloading from the Amsterdam servers? I would expect USA members to be send to the USA servers (in Dallas).

                                        Comment


                                          #21
                                          1. I think the routing paths cab be IP specific. (I came up this fix via reading verizon's bulletin board. Someone had a similar problem accessing European routers, and they suggested this. see below)

                                          It actually may. One bandwidth heavy user of FiOS over at DSLReports found that based on whether or not his IP address ended in an even or odd number, determined what route he would take to reach a server. He used this to his advantage by changing his IP address until he got the best route as he bonds two FiOS connections together.
                                          Hi, I use Fios Internet for online gaming and about 4 weeks ago my ping has gone up from an average of 130ms to over 300ms The trouble seems to be with one of Verizon owned routers TenGigE0-4-0-0.GW8.NYC4.ALTER.NET Late in the evening my ping returns to normal but during the day it is horrible. It s...




                                          2. Since the tracerts access Amsterdam servers , see my earlier posts, I am 'assuming this is where the files are streaming from, but i guess I don't know for sure. .

                                          Comment


                                            #22
                                            one other thing that I did notice, (which I communicated via a trouble ticket, is that speedtests to different servers in Amsterdam have dramatically different results. See the links below, so clearly there is some type of routing/speed issue going on
                                            Use Speedtest on all your devices with our free desktop and mobile apps.

                                            Use Speedtest on all your devices with our free desktop and mobile apps.

                                            Comment


                                              #23
                                              Originally posted by buyerclub22 View Post
                                              2. Since the tracerts access Amsterdam servers , see my earlier posts, I am 'assuming this is where the files are streaming from, but i guess I don't know for sure. .
                                              No, the actual download server is automatically selected based on several criteria. Does your tracert to cdn.abbywinters.com look much different now?

                                              Comment


                                                #24
                                                simple answer is nope tracert looks the same. See below and compare to the one above. And since the next to last hop is in amsterdam, (see above) and the last hope seems to be located in ireland? I am pretty sure that were not being served from within the USA.

                                                I determined the last hops location by using the following
                                                http://www.iplocation.net/index.php and entering the ip address of the last hop.
                                                Microsoft Windows [Version 6.0.6002]
                                                Copyright (c) 2006 Microsoft Corporation. All rights reserved.

                                                C:\Users\Jason>tracert cdn.abbywinters.com

                                                Tracing route to cdn.platypusbv.com [149.255.32.185]
                                                over a maximum of 30 hops:

                                                1 <1 ms <1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
                                                2 11 ms 12 ms 10 ms L100.BSTNMA-VFTTP-107.verizon-gni.net [98.110.18
                                                7.1]
                                                3 12 ms 7 ms 14 ms G0-14-1-1.BSTNMA-LCR-21.verizon-gni.net [130.81.
                                                217.188]
                                                4 12 ms 11 ms 7 ms ae9-0.BOS-BB-RTR1.verizon-gni.net [130.81.163.16
                                                4]
                                                5 16 ms 18 ms 15 ms 0.xe-11-3-0.BR2.NYC4.ALTER.NET [152.63.23.137]
                                                6 28 ms 25 ms 28 ms 204.255.168.110
                                                7 27 ms 25 ms 28 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31
                                                .9]
                                                8 44 ms 42 ms 42 ms be2114.ccr21.ord01.atlas.cogentco.com [66.28.4.2
                                                02]
                                                9 41 ms 39 ms 47 ms te0-1-0-4.ccr22.ord03.atlas.cogentco.com [66.28.
                                                4.78]
                                                10 84 ms * 38 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.
                                                182]
                                                11 38 ms * 38 ms te0-0-2-3.rcr12.b002281-5.ord03.atlas.cogentco.c
                                                om [154.54.1.210]
                                                12 33 ms 34 ms 36 ms 38.104.102.126
                                                13 44 ms 45 ms 42 ms 185.32.255.149.static.swiftway.net [149.255.32.1
                                                85]

                                                Trace complete.

                                                C:\Users\Jason>

                                                Comment


                                                  #25
                                                  also Frans, do you work for AW or are you just a community member and do you have any thoughts on the speed test results that I posted.?

                                                  Comment


                                                    #26
                                                    Originally posted by buyerclub22 View Post
                                                    also Frans, do you work for AW or are you just a community member and do you have any thoughts on the speed test results that I posted.?
                                                    I'm a forum moderator who happens to know a lot of AW and the website I don't know as much about the AW network, which is why Brent from customer-service gets to handle that part :P It could be that Verizon has a fast connect to Amsterdam (Amsterdam Internet Exchange is one of the largest ones world-wide), hence you downloading from there.

                                                    The speedtest results don't seem to show the actual server/IP you're testing to?

                                                    Comment


                                                      #27
                                                      Your correct I don't have any more info on the servers other than I can get a their web site.

                                                      Also, as I told Brent today, I ran the seed tests on another network that had Comcast as the ISP. The results were similar. So the speed test differences aren't unique to Verizon FIOS. (Although I have no idea if this means anything.)

                                                      However since I continue to no longer have issues since my release of the IP address and reboot of the router, for me now, this is all just intellectual curiosity.

                                                      If you hear others faced the same trouble, I would be curious to know if my work around helped them too.

                                                      Comment


                                                        #28
                                                        All hail Buyerclub22, hero of AW. He has (on his own ingenuity) found a workaround.

                                                        Indeed, changing the IP address assigned to you by your Internet Service Provider (ISP) seems to fix the issue. Unfortunately this isn't super easy. The short version of what you need to do is:

                                                        (1) Access your router administration User Interface
                                                        (2) Release your WAN IP address
                                                        (3) Power off the router for 10 minutes, so your ISP IP DHCP server provides you with a new address (phew, acronyms!)

                                                        If you don't know how to do this, shoot me a ticket, and we can tackle it 1 vs 1. Alternately, it's highly likely you could ask your ISP to reset your IP address for you.

                                                        We're still looking into what is causing this issue (because it'd be even better if it didn't come up), but at least now there is a workaround.

                                                        Thanks again Buyerclub22!

                                                        Comment


                                                          #29
                                                          I tried the change of IP address workaround, but I'm still getting stuck at 38.104.102.126, and downloads are still horribly slow. Should I keep trying to change the IP address? Note that I'm on Verizon DSL, not FIOS. Maybe changing the IP address on Verizon DSL doesn't get you a better route to the server?

                                                          Currently getting a bit under 50 KB/s, which makes video download pretty much impossible. This has been going on for over a month now, so I hope you can get something resolved on your end soon.

                                                          (Also, FWIW, the last number in my IP address went from odd to even when I changed it...)
                                                          Last edited by louseboy; 13 March 2014, 04:26 PM.

                                                          Comment


                                                            #30
                                                            Blast. Not to worry, I'm communing with the elder spirits of the internet. More news when I have it...

                                                            Comment

                                                            Subscribe to our e-mail newsletter

                                                             
                                                            Sign up for the abby newsletter. Don't worry, we'll NEVER share your email address with anyone.
                                                            Working...
                                                            X