Announcement

Collapse
No announcement yet.

Disney+ download is slowly

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

    #16
    Originally posted by djhanje View Post
    i have updated streamfab with the download from the streamfab site it self, with the extended service I have, I just download them and install them (not the update in the streamfab program)
    when I do a speedtest on my pc I have the full 950/950 speed on the port on my router with 2500 internet speed, the network card in the pc (Win 11) is a 1000 speed network card.
    i have a utp to USB-C option also that worked fine but windows have with the latest update removed that option and try to reinstall it with the drivers but won't help to get it again active so I get higher speeds.
    when I download in streamfab with the Prime video app it give me full speed to 35 and higher, the topspeed I get yesterday was around 60 download speed, so it must be disney+ that is giving the problems.
    I'm gonna try to change the dns on my router from the dns of my provider to dns from google 1.1.1.1 if that give a better result.
    try using cellular connection and see if you get the same result.

    Comment


      #17
      Location location location. I may get 7 to 25MB/s in the USA.
      It's usually not SF, but at times with Pluto and tubi I found it was and using different downloaders got better speeds.
      All you can do is change DNS maybe try a VPN or just queue a number of movies/shows and go to bed, and they will be downloaded when you get up.
      For me, the versions of SF get worse and worse. It takes a number of attempts to even get SF to analyze.
      And doing shows through Disney+/Hulu SF would actually stop for several minutes and then start up again to download.

      Download speed I have and is now available through Xfinity in my area up to 1.5Gig.
      Last edited by Stan001; 03-23-2025, 09:50 PM.
      Usual locations for temp, and cache files. Windows Streamfab.
      %HOMEPATH%/Documents/DVDFab/StreamFab/Temp
      Usual locations for log files.
      %HOMEPATH%/Documents/DVDFab/StreamFab/log

      Comment


        #18
        i have changed my ip address, dns set on google 8.8.8.8, try disney+ again but it's the same with the speeds, it's only disney+ that gives me problems with speed that drops to kb.
        with VPN also no changing speeds.
        I think it's the server where I connect to disney+ that is slow and gives me the problems, Primevideo and sky showtime works perfect, HBO max also.

        Comment


          #19
          Originally posted by djhanje View Post
          I think it's the server where I connect to disney+ that is slow and gives me the problems
          You think? Why don't you find out for sure by using ping and/or tracert as I previously wrote in a post that was totally ignored (like usual)? They have been used as speed/latency diagnostics since the beginning of the Internet. As it stands now, you guys, are just throwing darts at the wall trying to find out where the problem is. You can't fix a problem until you know what is causing the problem and where it is located.

          Comment


            #20
            Originally posted by Cats4U View Post

            You think? Why don't you find out for sure by using ping and/or tracert as I previously wrote in a post that was totally ignored (like usual)? They have been used as speed/latency diagnostics since the beginning of the Internet. As it stands now, you guys, are just throwing darts at the wall trying to find out where the problem is. You can't fix a problem until you know what is causing the problem and where it is located.
            i have get so much mails with reaction, I have must read not your message, I"m gonna try what you say here, I'm gonna ping disney+ to see where it's going wrong, strange that this was no problem last week but came this week suddenly.


            PING disneyplus.com (34.110.155.89): 56 data bytes

            64 bytes from 34.110.155.89: icmp_seq=0 ttl=59 time=7.030 ms

            64 bytes from 34.110.155.89: icmp_seq=1 ttl=59 time=8.384 ms

            64 bytes from 34.110.155.89: icmp_seq=2 ttl=59 time=8.294 ms

            64 bytes from 34.110.155.89: icmp_seq=3 ttl=59 time=8.043 ms

            64 bytes from 34.110.155.89: icmp_seq=4 ttl=59 time=8.228 ms

            64 bytes from 34.110.155.89: icmp_seq=5 ttl=59 time=7.951 ms

            64 bytes from 34.110.155.89: icmp_seq=6 ttl=59 time=7.957 ms

            64 bytes from 34.110.155.89: icmp_seq=7 ttl=59 time=7.935 ms

            64 bytes from 34.110.155.89: icmp_seq=8 ttl=59 time=8.108 ms

            64 bytes from 34.110.155.89: icmp_seq=9 ttl=59 time=8.275 ms

            64 bytes from 34.110.155.89: icmp_seq=10 ttl=59 time=10.441 ms

            64 bytes from 34.110.155.89: icmp_seq=11 ttl=59 time=8.358 ms

            64 bytes from 34.110.155.89: icmp_seq=12 ttl=59 time=8.077 ms

            64 bytes from 34.110.155.89: icmp_seq=13 ttl=59 time=8.081 ms

            64 bytes from 34.110.155.89: icmp_seq=14 ttl=59 time=8.248 ms

            64 bytes from 34.110.155.89: icmp_seq=15 ttl=59 time=15.595 ms

            64 bytes from 34.110.155.89: icmp_seq=16 ttl=59 time=8.753 ms

            64 bytes from 34.110.155.89: icmp_seq=17 ttl=59 time=7.972 ms

            64 bytes from 34.110.155.89: icmp_seq=18 ttl=59 time=8.522 ms

            64 bytes from 34.110.155.89: icmp_seq=19 ttl=59 time=8.309 ms

            64 bytes from 34.110.155.89: icmp_seq=20 ttl=59 time=8.108 ms

            64 bytes from 34.110.155.89: icmp_seq=21 ttl=59 time=8.439 ms

            64 bytes from 34.110.155.89: icmp_seq=22 ttl=59 time=8.090 ms

            64 bytes from 34.110.155.89: icmp_seq=23 ttl=59 time=8.134 ms

            64 bytes from 34.110.155.89: icmp_seq=24 ttl=59 time=7.936 ms

            64 bytes from 34.110.155.89: icmp_seq=25 ttl=59 time=8.691 ms

            64 bytes from 34.110.155.89: icmp_seq=26 ttl=59 time=8.441 ms

            64 bytes from 34.110.155.89: icmp_seq=27 ttl=59 time=8.658 ms

            64 bytes from 34.110.155.89: icmp_seq=28 ttl=59 time=7.902 ms

            64 bytes from 34.110.155.89: icmp_seq=29 ttl=59 time=8.422 ms

            64 bytes from 34.110.155.89: icmp_seq=30 ttl=59 time=8.153 ms

            Request timeout for icmp_seq 31

            64 bytes from 34.110.155.89: icmp_seq=32 ttl=59 time=8.119 ms

            64 bytes from 34.110.155.89: icmp_seq=33 ttl=59 time=8.329 ms

            64 bytes from 34.110.155.89: icmp_seq=34 ttl=59 time=8.536 ms

            64 bytes from 34.110.155.89: icmp_seq=35 ttl=59 time=8.255 ms

            64 bytes from 34.110.155.89: icmp_seq=36 ttl=59 time=7.955 ms

            Comment


              #21
              You are pinging to the wrong place. Disneyplus.com is the website for Disney+. You need to, preferably, tracert to the server from which you download your movie/episode from, which would be a CDN. Start to play your movie/episode. The URL will be displayed at the top of the screen. Anything including and after a "?", you can skip. The address for the URL will be unique to your location. The tracert will show step-by-step from your computer to the CDN, noting how much time it takes at each hop. Don't worry too much about hops that don't list anything, as they are blocked from reporting anything for security reasons. Odds are that you'll clearly see what server is giving you the slowdown and then follow Germania's directions to work around it. I, personally, like to use a VPN to come at the CDN from a different direction. That's how I solved a previous Peacock problem a while back where I had to VPN into a Boston IP even though I live in Pennsylvania.

              Comment


                #22
                Originally posted by Cats4U View Post
                You are pinging to the wrong place. Disneyplus.com is the website for Disney+. You need to, preferably,
                tracert to the server from which you download your movie/episode from, which would be a CDN..
                Correct - that's why I wrote:
                Originally posted by Germania View Post
                from vod-ftc-eu-north-2.media.dssott.com

                Comment


                  #23
                  Try flushing your DNS cache

                  Code:
                  ipconfig /flushdns

                  Comment


                    #24
                    vod-ftc-eu-north-2.media.dssott.com appears to be your CDN. Are you saying that it is his as well? Or are you just using that as an example of what a CDN address might look like?

                    Unfortunately, I've never subscribed to Disney+ as there is nothing of interest for me there. Otherwise, I'd do a test diagnostic myself, just as an example of what a Disney+ tracert should look like.

                    Comment


                      #25
                      Originally posted by Cats4U View Post
                      vod-ftc-eu-north-2.media.dssott.com appears to be your CDN. Are you saying that it is his as well?
                      Or are you just using that as an example of what a CDN address might look like?
                      vod-ftc-eu-north-2.media.dssott.com is my D+ connection in Frankfurt - biggest CIX in Germany:

                      Originally posted by wiki
                      The DE-CIX Internet exchange point (IXP) situated in Frankfurt, Germany,
                      is one of the largest IXPs worldwide and the largest in Europe in terms of peak traffic
                      edit:
                      via Belgium I get "only" varnish06-c05-fra1-dss-vod-dssc-shield.tr.eu.prod.dssedge.com
                      This is because I can't "really" test D+ via Belgium - because EU laws (info)

                      via France I get vod-ftc-eu-south-1.media.dssott.com - also ftc = Frankfurt (Germany) via FAST
                      or Akamai: vod-akc-eu-south-1.media.dssott.com​
                      Last edited by Germania; 03-24-2025, 06:20 PM.

                      Comment


                        #26
                        i get varnish05-c03-fra1-dss-vod-dssc-shield.tr.eu.prod.dssedge.com/
                        this is when i watch Vaiana2

                        Comment


                          #27
                          Originally posted by djhanje View Post
                          So, what are you getting when you enter - "tracert varnish05-c03-fra1-dss-vod-dssc-shield.tr.eu.prod.dssedge.com" (no quotes) - into your terminal?

                          Comment


                            #28
                            i have done that and getting this:



                            1 my own router.....

                            2 185.142.225.193 (185.142.225.193) 5.921 ms 5.833 ms 5.569 ms

                            3 109.233.104.154 (109.233.104.154) 5.983 ms

                            109.233.104.218 (109.233.104.218) 6.055 ms 5.783 ms

                            4 brx-b4-link.ip.twelve99.net (62.115.151.140) 5.957 ms 6.256 ms

                            109.233.104.152 (109.233.104.152) 5.969 ms

                            5 brx-b4-link.ip.twelve99.net (62.115.151.140) 6.287 ms

                            brx-b3-link.ip.twelve99.net (62.115.117.56) 6.266 ms 6.348 ms

                            6 brx-b3-link.ip.twelve99.net (62.115.117.56) 6.346 ms *

                            prs-bb1-link.ip.twelve99.net (62.115.116.238) 10.342 ms

                            7 prs-bb1-link.ip.twelve99.net (62.115.116.238) 9.717 ms

                            ffm-bb1-link.ip.twelve99.net (62.115.123.12) 17.170 ms *

                            8 ffm-b5-link.ip.twelve99.net (62.115.136.213) 18.119 ms

                            ffm-b5-link.ip.twelve99.net (62.115.114.89) 17.780 ms

                            ffm-bb1-link.ip.twelve99.net (62.115.123.12) 17.902 ms

                            9 * ffm-b5-link.ip.twelve99.net (62.115.114.89) 19.393 ms

                            ffm-b5-link.ip.twelve99.net (62.115.136.213) 18.092 ms

                            10 * * *

                            11 * * *

                            it goes through a Lott of ip addresses of the servers of my provider, is that normal?????

                            Comment


                              #29
                              Originally posted by djhanje View Post
                              i have done that and getting this:
                              I have a shorter route from Germany
                              Code:
                              varnish05-c03-fra1-dss.vod-dssc-shield.tr.eu.prod.dssedge.com [139.104.117.30]
                              
                              1    <1 ms    <1 ms    <1 ms  my Router
                              2     5 ms     4 ms     5 ms  my Provider
                              3     5 ms     5 ms     5 ms  my Provider in my town
                              4     4 ms     4 ms     4 ms  my provider in Frankfurt (ffm)
                              
                              5     5 ms     5 ms     4 ms  bei-b3-link.ip.twelve99.net [62.115.112.90]
                              6    18 ms    17 ms    17 ms  ffm-bb2-link.ip.twelve99.net [62.115.136.76]
                              7    18 ms    17 ms    17 ms  ffm-b5-link.ip.twelve99.net [62.115.114.91]
                              8    17 ms    17 ms    17 ms  disney-ic-377807.ip.twelve99-cust.net [213.248.79.237]
                              9    17 ms    17 ms    16 ms  139.104.117.30

                              Comment


                                #30
                                it goes through a Lott of ip addresses of the servers of my provider, is that normal?????
                                While the latency of your hops is not bad, there are a lot of twelve99.net hops. Twelve99.net seems to be a Swedish company. What you should try as an experiment is to VPN to a server located in German, preferably in Frankfurt or nearby. See if that shortens the hops and increases your Disney+ download speed.

                                Comment

                                Working...
                                X