Network · data from 2026-11-12
AS46890 3Com Net Router - AS46890
Registry name: 3COM-NET-ROUTER-AS46890 - 3Com Net Router, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46890, 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.
| 177.124.158.0/24 | Valid | Nonecovered by 177.124.156.0/22 | 671 100% |
| 177.124.158.0/23 | Valid | Nonecovered by 177.124.156.0/22 | 670 100% |
| 177.124.159.0/24 | Valid | Nonecovered by 177.124.156.0/22 | 670 100% |
| 164.163.108.0/23 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 164.163.108.0/24 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 164.163.109.0/24 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 164.163.110.0/23 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 164.163.110.0/24 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 164.163.111.0/24 | Valid | Nonecovered by 164.163.108.0/22 | 669 99% |
| 177.124.156.0/23 | Valid | Nonecovered by 177.124.156.0/22 | 669 99% |
| 177.124.157.0/24 | Valid | Nonecovered by 177.124.156.0/22 | 669 99% |
| 177.124.156.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 164.163.108.0/22 | Valid | RIR databaseARIN | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS46890: AS-3COM46890. 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 (AS46890 isn't in the set, or no route object for AS46890 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.
| Name | Database | ASNs | Sets | AS46890 in it | Not covered |
|---|---|---|---|---|---|
| AS-3COM46890 | ARINlists itself further down | 5 | 4 | 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 13 are in fix.csv.
- Route object: none11
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.124.158.0/24 | No route object for it. A route object for 177.124.156.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 177.124.158.0/23 | No route object for it. A route object for 177.124.156.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 177.124.159.0/24 | No route object for it. A route object for 177.124.156.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.108.0/23 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.108.0/24 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.109.0/24 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.110.0/23 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.110.0/24 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 164.163.111.0/24 | No route object for it. A route object for 164.163.108.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 177.124.156.0/23 | No route object for it. A route object for 177.124.156.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: none | 177.124.157.0/24 | No route object for it. A route object for 177.124.156.0/22 with origin AS46890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46890 in the RIR database for the space. |
| Route object: RIR | 177.124.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46890 whose prefix no peer sees AS46890 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.124.156.0/22 | ARIN | Valid |
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.