Are marketplace downloads deliberately throttled to 2mbps?

Every single download in the marketplace starts off at a snails pace of 2mbps and only ramps up after around 3-5 minutes. It really discourages me from using it because it ties everything up for ages especially with multiple purchases as each download reverts back to 2mbps.

2 Likes

Either deliberate or deliberately neglected

I’ve seen 2mb/s, 6mb/s, and 150mb/s.
It’s always quite variable.

The SU13 update started around 50mb/s, dropped to 8, then rose to 150, where it stayed for a while, then back down to around 20.

I remember trying to convince Bright House (now Spectrum) that there was a problem on their end when trying to stream the old Sony PlayTV app to my TV. I had a bandwidth meter on my router than would display on the TV. During primetime hours, when I streamed other apps, like Netflix, I’d see 20mb/s. As soon as I switched to PlayTV, it dropped to 1-2mb/s. At 2:00am it was 15mb/s.

They tried to convince me it was a problem with my router.
I found out they throttle certain programming based on demand in certain areas, at certain times.

I’m so glad I have Frontier fiber now.

So my answer is: I don’t know. The ISP’s may throttle, and Microsoft may throttle. Or load-balancing internet routers may throttle.

1 Like

I can assure you it’s not either of these in my case

Downloading now, normal speeds so far.

There are widely reported problems with download speeds for MSFS updates, Marketplace downloads, and scenery that go through Microsoft servers.

These reports come from different places all over the world with little commonality, but most of them sound like an overloaded content distribution network (CDN) on Microsoft’s side, which leads to too many people trying to download through the same small minimal connection to a Microsoft CDN server even though the connections from the local ISP to the user are fast.

The easiest way to fix this appears to be to change internet service providers… which isn’t very easy :wink: … but you can approximate it by using a VPN (Virtual Private Network); connecting through a VPN server in a different location has often been reported to resolve slow download issues with MSFS because it routes around the overloaded local CDN server and might reach another one that’s more available.

This really is something that Microsoft needs to fix, and people have been complaining, bitterly, for 3 years about it.

7 Likes

skypilotYTS - But did your download start at 2.5mbps for the first few minutes of every single file in the download sequence like the OP has described and is my and loads of other users experience? I too can get up to 250mbps but since June this is limited in the first few minutes and this causing the average speed of the download to be unnecessarily slow :frowning:

See here:

Downloading 1.34.13.0 update at 2.5mbps - UK based - Alpha/Beta Archive / SU13 Beta Archive - Microsoft Flight Simulator Forums

Note I first started seeing this during SU13 beta hence my posting to the beta forum. This issue has continued to this day.

1 Like

I agree that slow download speeds have been complained about for 3 years but this ā€œlimited to 2.5mbpsā€ is a new issue which started in June. My healthy 500mbps fibre can show downloading 150-200mbps while in the world map for example, is limited to 2.5mbps for the first few minutes* when downloading market content. This does not match an ISP throttle strategy.

*of every file - sometimes there are 100s of them remember :frowning:

1 Like

The only way I could make a statement like that is if I knew the IP address(es) of the Microsoft server(s) I’m connecting to. Then I could use tracert to look at every hop, which would tell me where the slowdowns are occurring. Even then I couldn’t tell you whether there’s active throttling going on, or a simple matter of load balancing.

What you are describing is the normal, to be expected, random fluctuations of download speed during an especially popular period of a sim update. That’s not unusual for MSFS or any other gaming title.

What the OP and myself are describing is a systematic, repeatable and slow download speed which occurs when downloading market content and can happen no matter what time of the day/month/year. In fact I took some time to show (I’ll try and find my post) that the limit is consistently observed even when downloading, then deleting, then downloading the exact same addon - every time no matter what time! Moreover, the length of time that the limit applies depends upon the addon which is being downloaded, i.e. one download will spend longer at 2.5mbps than another. Note that in both cases eventually the speed returns to normal (with fluctuation) - in my case 100+mbps.

That is not ISP throttling unless the ISP knows what addon I’m downloading and favours one over the other!

Definitely not. I usually get 60-150. That’s still stupidly slow though, but if it’s 2, there’s a problem somewhere.

And a post of mine to one of the Azure PlayFab support forums was closed down, and not even visible I think, labelling it as ā€œnot suitableā€ or ā€œinapproprirateā€, words to that effect. It was just a question, neutrally worded, and without hyperbole. A disappointing response.

An interesting post I just found:

There is no throttling on the Azure side, refer to below article. If the network and client machine can handle the traffic then we will send it.

There is an Azure download speed test site, and you can choose where in the world to download from:

It lets you download a 100MB test file from many different world regions. On my work connection, which is on a 20GB/s JANET pipe, it’s done before I even get to see the download rate. I’ll have to test this at home as well. But could be used as a possible comparison to how MSFS performs, and indicate no local internet issues.

For example, I’m in the UK, and was getting this for West India:

Western Europe

UK South

There is potentially some useful information to be gained from that site. It keeps a list of all Azure IP ranges.

https://www.azurespeed.com/Information/AzureIpRanges

When I download something from the Marketplace, I can use Wireshark to identify the IP I am downloading from. What I could then do is confirm that IP exists on that list, and then determine which Azure region I am downloading from. If it’s not from the one of the UK or Europe ones, it would be nice to know why.

The thing is, they do know. That’s what I spoke of when I related my story about Bright House. They specifically throttled Netflix at certain times in order to maintain overall average network bandwidth at certain times. I couldn’t believe it when I learned about it, but the proof was evident.

Again, I’m not saying that’s what Microsoft is doing, or that it’s not the cause of the slow initial download speed. I’ve experienced it myself and I can only say with certainty that I don’t why it’s happening. Anything else would be pure speculation.

Not at the level I’m describing. Yes they can inspect TCP packets to assess the general type of content plus the source server but you think my ISP is looking at individual packets and then depending on which addon it is I’m trying to download will slow it down only for a few minutes before allowing it to return to full speed? And all the other posters having this problem with different ISPs found theirs do the same starting in June? Really?

ETA. Remember with a https connection these packets are encrypted and so would make no sense to the ISP. Which is why I say they can only detect the general form of the data

ETA2: it’s very easy to throttle just Netflix at a particular time and not other streaming services as you can see the source server address in the packet header.

Known issue, there’s a thread with a ā€œBug loggedā€ tag.
Unfortunately people tend to be unprecise when reporting:

Yeah, I too get the full speed on my cable connection, but only after each larger file starts veeeeery slow with the 2Mbps the OP mentioned.
I have described it here, including video:

It may not effect everyone, but it seems to effect many.
And with it marked as identified and reproduced on the devs end (being the essence of the ā€œbug loggedā€ tag) I would have expected a fix or at least some sort of reaction, but there’s nothing but silence.

1 Like

I have some sympathy with Asobo in this matter of information updates as there must be many 100s (1000s?) of open bugs and getting an update on each one would be a big task. Especially when the bug isn’t universal. However the bug you and I are seeing is stopping me from buying any market content while it remains unsolved although I don’t think Microsoft will notice my ā€˜protest’ on their bank balance :slight_smile:

1 Like

You insist on implying that I’m claiming I know why it’s happening. I’m only offering possible explanations. Unless you have some insider knowledge that most don’t, you have exactly the same level of understanding regarding the granularity of an ISP’s, or Microsoft’s server side packet inspection as I do.

I attended a seminar yesterday that featured one of Intel’s chief engineers. What she told us reinforced my notion that in this brave new world of AI, hardware and software are far more imposing (some would say intrusive) than we think.

You can have the last word. I’m out.

Yes, but I consider this a major bug, as it could prevent you from using the software. There are reports from users with the need to reinstall large portions of the sim after the flawed update process with SU13, and it took them DAYS to finish this reinstall due to the atrocious download process.
Although it has not been confirmed that these two incidents are intertwined, I have a strong suspicion that they share a common cause.
Considering the awkward update process and the many interdependencies (Marketplace, Content Manager, Gaming Services, X-Box App…) I’d rather have the issue fixed before the next WU - just in case.

And I’m only explaining (with supporting facts) why your ā€˜possible explanations’ are incorrect. Not sure why you appear to have taken offence at this - it was not my intention.

I posted the same suspicion on the official update thread a couple of hours into the maelstrom that was the update process only to be informed by a tech support that the two were not linked. I remain sceptical. I too hope it’s fixed in SU14 but I won’t hold my breath.

(For clarity - as I seem to be upsetting folk today! - I’m agreeing with you and I really think that periodic bug updates from Asobo is important and would love to see that happening.

I feel that posting a bug in this forum is like shouting into the void. Sometimes your voice is heard, sometimes it isn’t. At any time you don’t know whether it was or not! Sadly the same applies even in the beta forum where communication and feedback with testers should be even more important).

This is all off topic so perhaps we should respect the OP but happy to chat further elsewhere if you need to :slight_smile:

1 Like