Well, i could be wrong but it looks like the static bing data is delivered by amazon and/or akamai. When loading the sim you can see mfs bashing these servers to receive data. Most of it from amazon, up to 20 to 50 mbit if no data is cached. So even though it’s bing data, it looks like not to be delivered from ms.
The only data I’m seeing coming and sending from/to ms is volatile real time data (multiplayer etc…)
I would suspect this data looks to be a snapshot (when a new world or region is build). It’s not real time bing data. This data could already be 1,2,3 or more months old. When Asobo took/got a snapshot, and bing had issues. It will get malformed data. Like now when a new high resolution image is cut into 16/32 regions, but the “zoom” level which uses the 32 cut parts, is not updated with these new cuts.
Why does Asobo uses snapshots (as it looks that way)? Well they can’t afford modified satalite images which alters the world in an unexpected way. Because if they did, you can end up like the current situation. This because satalite images are of more then not, taken in different hours/days/weeks/seasons/etc… This is the reason that different images can be shown on different zoom levels. Satalite images, yes are quite static, but also dangerously volatile when used as content.
So, i think:
- They create/get a snapshot of different altitudes,
- They build a new world/regions on azure (spatial data/blackshark),
- Publish to Amazon/Akamai and mfs region (like wu5) download location
- These networks dispatch internally to regions (eu-west for example)
- Mfs uses this data.
So to fix this they probably need to rebuild.
But again, it’s all speculation. But it definitely looks like a snapshot and imagery is coming from Akamai and Amazon.