bgpreport

Network · data from 2026-11-12

AS47901 Meeza

Registry name: Meeza MEEZA QSTP-LLC, QA · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS47901, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47901, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
94.125.224.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.225.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.226.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.227.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.228.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.229.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.230.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
94.125.231.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67

AS-SET

AS47901's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 16 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR94.125.224.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.228.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.229.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.230.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR94.125.231.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS47901 whose prefix no peer sees AS47901 announce. Many are kept on purpose (backup routes, space announced only in some places).

86.36.128.0/24RADBNo ROA
94.125.224.0/21NTTCOM, RADB, RIPENo ROA
94.125.224.0/22NTTCOMNo ROA
94.125.224.0/23NTTCOMNo ROA
94.125.226.0/23NTTCOMNo ROA
94.125.228.0/22NTTCOMNo ROA
94.125.228.0/23NTTCOMNo ROA
94.125.230.0/23NTTCOMNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.