I was doing this part from your previous comment, "so unless several people report a similar problem." I am, in fact, reporting a similar (same) problem.
I found this thread after experiencing the issue in flight. So no, I wasn't able to time travel backwards to pull the ADSB logs per your earlier suggestion.
Further, I don't expect your "help them help you" snarky response to a commercial software product with a paid subscription. I would expect that on my github account, but not here. I pay more money for this software product every year than all other software I use combined. That comes with certain expectations about how bugs are handled. A polite recommendation to grab a log file next time it occurs would be fine, though considering the very busy cockpit environment that had both pilots working feverishly on planning diversion alternates to changing weather conditions in busy airspace makes getting a log file pretty low on the priority list. Lastly, missing radar chunks (data blocks) is a common ADSB issue across several products when the software isn't correctly merging the data frames from multiple gound site broadcasts. Though I can't know whether this is a stratux software bug or an ifly bug, the development team here should definitely recognize the signature from the screenshots provided.