Other companies don’t want to deal with Telekom’s ■■■■■■■■ either. For years especially gamers had problems. And to clarify, I’m still not 100% sure Telekom is really responsible for our problem. Could be some service provider inbetween.
Here is a lengthy article that explains some things
https://www.heise.de/hintergrund/Missing-Link-Regulierer-vs-Monopolisten-Streit-im-Markt-der-Peering-Anbieter-4886694.html?seite=2
@IncontnentCamel
I am able to play Elite Dangerous, DCS, Assetto Corsa, Assetto Corsa Competitione, F1 23, F1 24, iRacing, DayZ, Arma, hell even Star Citizen, Fortnite, FiFa / FC, Diablo, Dirt 5, and many more.
Only MSFS does have issues with Telekom. All these other games are able to deal with the Telekom.
Telekom is even selling the Azure service… therefor you would expect some kind of partnership relation between MS and Telekom
MS feels a bit like driving on the highway and telling people that everybody else is driving the wrong direction.
Edit:
If they knew the issues they should have tested this before selling the product.
If they can fix it going forward it is their fault, therefor they did sell a broken product.
If they didn’t know how to fix it and say it is a telekom issue then they need to stop selling it, because if someone else is selling a product knowing it does not work, you would consider this a scam.
To be fair, I did not have the connection issues, which I have now been experiencing since launch, in the technical Alpha.
So it was somehow tested but bandwidth behaves differently in the final version…
The difference here is that MSFS uses waaaay more bandwidth than any of them, constantly. Within the first week for me it used 100 GB. And just look around on the internet, there are tons of people who complain about having issues in competitive games with Telekom as ISP.
But I’m totally with you, this problem shouldn’t exist in the first place. If a company decides streaming is the way to go but doesn’t make sure the data can get to the customer at some point wrong decisions were made.
And let’s be real, the vast majority of players does not experience the issue we are discussing here. Also the Telekom theory is one I came up with and was never confirmed by MS. I just read forum threads for hours and noticed a pattern
Telekom 100 MBit line here.
A lot of problems with streaming the game, on good days and during off hours the sim loads with up to 30mbit/s, on bad days (like just now) it is between 0,1 and 1Mbit.
Usage of a VPN gives full bandwidth.
I get what you say and agree. Only one point I might have a different view.
Comparing the other Games might be not fair, how about Netflix, Prime Video, Disney+ aso streaming 4K Movies.
I would not accept that I have to start a Movie every 5 Minutes from the beginning.
And 10h of 4K movie will need about 50-70GB of data, this will be compressed as MS could do as well.
I have had issues right from the launch of MSFS. About 90% of my MSFS sessions suffer from long load times, waiting at load screens (frequently 10 or more minutes), degraded aerials.
10% of sessions are not affected, and then I get to enjoy lightning fast load times, smooth navigation through the career mode UI, and perfect scenery.
I am a Telekom DSL customer, but I run my own DNS, DHCP etc. server in my local network, I don’t rely on any services from Telekom except the transport of data packets. My DNS server forwards requests to the public Google DNS servers, and has done so for years. I feel I can say with confidence that avoiding the Telekom DNS servers did nothing for me.
If some of your MSFS sessions run fine, for whatever reason, it’s easy to assume that the last thing you tried made a difference. Some people say Cloudflare Warp helps them, but a traceroute to any Microsoft service (e.g. forums.flightsimulator.com) tells me that there’s a direct connection (“peering”) from Deutsche Telekom to Microsoft’s network (in fact, there’s only one hop, a single intermediary step, between my DSL router and the next node of Microsoft’s network (judging from the hostname *.ber30-* that node could be in Berlin, not far from where I live).
On the other hand, Telekom and Cloudflare do not have a peering agreement. When Telekom users use Warp, their traffic goes through Telekom, a 3rd party transfer net, to Cloudflare, and eventually to Microsoft’s network. That’s at least two extra steps. Because all those data packets try to stay as local as possible, it might end up in the same Azure datacenter as before, but it might also end up in a different one. I tried Warp, and as expected, the result was the same with and without: some of the time MSFS works fine, a lot of the time it doesn’t.
Warp allows switching between Telekom and Cloudflare “on the fly”, and that probably causes client connections which were hanging, starved waiting for data, to be reset. The client (ie. MSFS) will retry, and if you’re lucky, this time the request will go through, so you get the impression that “with Warp, it’s better”. There might be some confirmation bias at play.
Warp might even work reliably for some people – the fact that it does not improve the situation for others could point to differences in network topology: Telekom users using Warp in one part of Germany might end up in the same data center as before, users in other parts of Germany might end up in a datacenter in the Netherlands or the UK, network topology can be funny like that. [Yeah, I know, I said before that data packets try to stay local, but that’s an oversimplification. Let’s say they try to take the “cheapest” route, the “cost” being evaluated in time and money. Reaching a data center in, let’s say, Amsterdam might be faster and cheaper for CF in some parts of Germany, but not in others.]
I’ve heard a lot of times that a VPN helps. Warp is a bit like a VPN, but it intentionally keeps traffic as local as possible, while a “real” VPN service will allow you to pick an exit node in a different country, even on a different continent.
I totally believe that a VPN does help. If you force your data packets to travel to another continent, you will almost certainly end up in a different Azure datacenter, local to your exit node. And even though the path of the packet takes a lot longer, even if the VPN provider skimps on your bandwidth, if the server on the other side is a-rockin’, you will have a better experience than accessing the server local to you – if you’re affected by the issues discussed in this thread.
By the way, while I’m composing this novella, I’m waiting for a Cargo Transport mission to start. I planned to keep writing until it loads, but I’m running out of steam.
Anyway, just like a VPN has a high chance of working around the issues (because, as I believe, different Azure datacenter = no problem), so does changing the ISP. I’ve noticed that, e.g., Vodafone and Pyur customers have a good experience – it would be interesting to know whether they end up in a different Azure location than Telekom customers.
I’m gonna find out. Pyur had a Black Friday offer (crazy cheap for 1Gbps, but apparently with certain limitations like CGNAT, forced Wlan “community” etc. – stuff that, for me, is unacceptable from my primary ISP, so I have to keep Telekom, too). I’ll have a 2nd ISP by tomorrow. A dedicated internet connection for my gaming PC, which I use mainly for flight simming. So, yeah, this is how far we have come. I would join the chorus of people telling Telekom customers to delete their rolling cache, change their DNS server, or sacrifice a goat, but I hope to be flying instead.
PS: Still waiting for the mission to load.
PPS: Still waiting. I think I’ll kill MSFS from task manager. But before I do, this:
Funny story about this image: it only shows completed requests, ie. requests that got a response that resulted in a status code. What’s missing are incomplete requests that got stuck somewhere during the negotiation. And requests that never complete because the data transfer stalls might show up as green or not at all, depending on how the server handles logging. Also, if there’s a problem affecting only one of many instances of a certain server, those problems might be drowned out by all the successful connections of people enjoying the sim.
Show me some pie charts for the server instances that serve me, with the percentage of TCP connections that were closed, reset, or timed out. I’m betting money on it (literally, by ordering a 2nd line) that they don’t all look so green.
PPPS: Never encountered a single CTD. But I frequently have to use Task Manager to get rid of MSFS when it hangs forever and becomes totally unresponsive. Wouldn’t it be nice if at least the Esc key and Quit to desktop would still keep working when there are network issues?
I have tried all the listed DNS with no success.
Low bandwidth warning / error for live traffic
Didn’t had any connection issues with other games. IP check says ping is at 20ms.
Guess I won’t be able to fly 2024 until I could change the ISP. So sad.
Tried yesterday with Google DNS, today with Cloudflare DNS, today complete reinstall of the sim, but still the same issues. Not really playable like this, textures not loading and everything looking way worse than 2020, where in fact it should look much better 
and as we heard today, MS/Asobo claim the servers are fine, so I don’t really have any hope left how it should improve…
Same for me. Right now I am not even able to enter the flight anymore. I did not had the chance to watch the full stream, but I could not hear anything about the continues CTD.
This said, I will just call it a day and move on from here.
No reason to spend more time to troubleshoting.
Telekom fiber 200. Sometimes good, sometimes standstill, but never really perfect. Although my settings are quite moderate because of my 1080ti, which is fighting bravely but has its limits. Reminds me of the early years of 2020 when I used a VPN to download world updates. Later they got it fixed and my download rates were acceptable. But never 200 mbit.
So, yeah, it’s ridiculous how smooth the experience is when your ISP isn’t Telekom.
All I did was pull the cable from the Telekom DSL Fritzbox, and plug it into the Pyur Cable Fritzbox. Literally nothing else changed. Same PC, same firewall, same local network, same DNS servers as before, no Warp, no VPN necessary. I didn’t even bother to delete the rolling cache or restart Windows. I did a couple of flights, the only issue I’ve encountered was missing Live Traffic. No missing or blurry textures. Navigation through the UI was snappy, missions loaded within seconds.
What can I say… I hope Microsoft and Telekom get their ■■■■ together so “y’all” can enjoy MSFS, too.
*drops mic*
PS: I do not endorse Pyur. I’ve been their customer before, years ago, their support was slow, unreliable, unfriendly (typical Berliners) and didn’t care about German or European customer protection regulations (I had to get the Verbraucherzentrale involved). Under no circumstances would I rely on them as my primary ISP, only as a backup ISP and for flight simming. [edit: I made incorrect claims about CGNAT and IPv6. They were based on incomplete information, so I removed them.]
Telekom fiber 300, at evening nearly unplayable because of loading times.
Germany, XBOX S, ISP Telekom
Yesterday changed DNS to 1.1.1.1.
Sim starts much faster now.
I don’t want to pay a second ISP just because of MSFS!
And you shouldn’t have to. I could rationalize it only by telling myself that I “need” a backup ISP for work (Telekom occasionally does their network maintenance in the wee morning hours, just when I try to do mine, and when they have an outage, it can affect my DSL line as well as my mobile). And that Black Friday deal (40€/mo for 1Gbps and a Fritzbox) seemed really good. Also, I always wanted to have a 1Gbps line. Preferably fiber, but this is Germany. Thanks, Postminister Schwarz-Schilling.
So, yeah, you shouldn’t have to, but what are the chances that the issue is resolved soon? We’re still at the “it’s probably your system, but try changing the DNS server” stage.
Wake me up if someone from Microsoft actually acknowledges that there’s a problem for a significant number of customers of Europe’s largest ISP.
I just changed the topic to a bug report. Maybe this way we can get more attention form MS/ Asobo
Thank you for this report. We’ve moved your topic into the User Support Hub,
as MSFS has no control over individual IP servers.
It was a good idea, I guess MS does not like it. Maybe we need to get in contact with Jörg via linked-in and ask if he is would like to support his fellow german simmers 
I still believe MS could do something about it. Otherwise it would not work for some people via VPN.
Looks like they do not care. 
I had chat with the mod and I understand their decision. Everything is fine, no hard feelings 
But I do agree with you. MS or Asobo most likely would be able to help us
