Probably server-side thing. They mentioned the live weather had some cache issue on server-side a few patches ago.
My speculation is that MB provides forecast in non-distributable form (text file like CSV, etc.) and Asobo has to make it distributable and streamable on the server side. This requires some system design and a key concept is caching logic. So whenever there’s a new data from MB, Asobo has to replace all exsiting cache with this new update. Consider if a user is streaming from the cache that needs to be updated, there could be things gone wrong. Therefore, if we can have a user report summary by time, then we probably would see spikes of issues during cache updates.
Just my 2 cents without knowing anything about how Asobo architect MSFS