bgpreport

Network · data from 2026-11-12

AS27172 3Com Net Router - AS27172

Registry name: 3COM-NET-ROUTER-AS27172 - 3Com Net Router, US · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
12IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS27172, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27172, 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.

2602:f635::/40 Valid Other IRR onlyRADB 634 100% 67
2602:f635::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:1::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:11::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:21::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:34::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:61::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:66::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:92::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:99::/48 Valid Other IRR onlyRADB 634 100% 67
2602:f635:ff::/48 Valid Other IRR onlyRADB 634 100% 67
23.139.140.0/24 Valid RIR databaseARIN 669 99% 67
2602:f635::/32 Valid RIR databaseARIN 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS27172: AS-3COM27172. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS27172 isn't in the set, or no route object for AS27172 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS27172 in itNot covered
AS-3COM27172 ARINlists itself further down 5459 Yes 0

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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR2602:f635::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:1::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:11::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:21::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:34::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:61::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:66::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:92::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:99::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:f635:ff::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS27172 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.