The Console is part of the TTN provided backend service - flakey though it sometimes is it doesn’t directly impact the key provision of packet/message routing.
The TTN Mapper is ‘nothing to do with TTN/TTi’ and is a 3rd party system kindly provided & maintained as a benefit to all users and communities on an opt in basis and isnt run or managed by TTN (Think of it as an Integration a la e.g. Cayenne/MyDevices) - if that goes down or doesnt show data correctly as long as TTN is passing messages through there isnt much they can do to fix. Not sure but TTN Mapper may well scrape data from the NOC or under TTNCTL and have a direct data dependency on what comes through from there but if that is unreliable in the same way that the Console can sometimes be that is not going to get fixed in this version of V2Stack/Console pairing.
Users should not judge TTN soley on the performance of 3rd party provisions/providers. Ultimately the best view of available GW’s is provided by the overall TTN Map and the local Community maps (assuming one covers the area where the GW is deployed, which isnt always the case). Also remember (if not aware) that on registering a GW the owners have the option (tick box) to declare it as public or private. If set to private it wont show on the map…but AFIK it does still carry all TNN registered traffic through to the back end and provides coverage 