Not yet fetched from API
Beast and MLAT data is being sent with different UUIDs. Recent versions of the installation script will use the same UUID for both Beast and MLAT data.
To have Beast and MLAT data fed to OARC with the same UUID, run the update script (guide to update without reconfiguring).
Your feed client is sending null as a UUID.
Where the "unique user ID" (UUID) is not unique between multiple feeders, this can be problematic and risks introducing errors in the data.
The easiest remedy is to update your OARC ADSB installation (guide to update without reconfiguring).
JavaScript is disabled or there has been an error which prevents JavaScript from updating this page with feed data.
Enable JavaScript to view IP stats and/or report issues via the OARC Discord.
Busted Beast latency display? Make sure you're feeding beast_reduce_plus_out data - you can reinstall the feed client to make sure of this.