bgpreport

Network · data from 2026-11-12

AS46303 POPP-COM - POPP.com, Inc.

Registry name: POPP-COM - POPP.com, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46303, 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.
63.86.120.0/22 No ROA Other IRR onlyRADB 673 100% 67
63.87.112.0/20 No ROA Other IRR onlyRADB 673 100% 67
65.240.28.0/22 No ROA Other IRR onlyRADB 673 100% 67
65.248.208.0/20 No ROA Other IRR onlyRADB 673 100% 67
65.255.240.0/20 No ROA Other IRR onlyRADB 673 100% 67
76.76.48.0/20 No ROA Other IRR onlyRADB 673 100% 67
173.240.16.0/20 No ROA Other IRR onlyRADB 673 100% 67
208.254.148.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.14.176.0/20 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS46303 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none63.86.120.0/22No ROA covers it. Add a ROA for AS46303, maxLength 22.673 of 673
Route object: RIR63.86.120.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none63.87.112.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR63.87.112.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.240.28.0/22No ROA covers it. Add a ROA for AS46303, maxLength 22.673 of 673
Route object: RIR65.240.28.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.248.208.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR65.248.208.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.255.240.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR65.255.240.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none76.76.48.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR76.76.48.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.240.16.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR173.240.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.254.148.0/24No ROA covers it. Add a ROA for AS46303, maxLength 24.673 of 673
Route object: RIR208.254.148.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.14.176.0/20No ROA covers it. Add a ROA for AS46303, maxLength 20.673 of 673
Route object: RIR216.14.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS46303 is announced.

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.