Flight aware is dependent on UAT receivers operated by public to populate FLIGHT AWARE system. Having drop in coverage is normal due to coverage of the receivers around the country is less than 100%. This is not how 1090 systems work, just the UAT systems.
Since your Flight ID mismatch is not “always” reporting RED, I’m going to say it was random due to reasons unknown . I don’t think you can or need to do anything but keep a check on it by running another report monthly maybe. IF you want to try to change , change the sensitivity IF you are sniffing the 327 transponder, directions on how to do on the UAVIONIX web site. If you are wired from transponder, to EchoUAT, no sensitivity to change.
Is this a new EchoUAT install?
If not, been running fine, Id just move on, but check monthly. Big flaw I see in ADSB, is no way to know when not reporting correctly, UAT or 1090 method, unless ATC tells you, or you find by running a report by chance.
I was an early adopter of the EchoUAT, lots of struggles early on with bad transponders, the GPS antenna being shadowed etc. I believe you are good, just a random error likely due to coverage. Lots of errors when first departing rural airports . You can take your failed report, REPLY to it asking for review. FAA can send you back a when/where this error happened that may help you determine if random or something more.
RV6A Purchased N72TX