Network · data from 2026-11-12
AS329062 Baremetal Computer Traders
Registry name: Baremetal Computer Traders - Baremetal Computer Traders, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS329062, 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.
| 102.216.0.0/23 | Valid | Nonecovered by 102.216.0.0/22 | 126 19% |
| 102.216.2.0/23 | Valid | Nonecovered by 102.216.0.0/22 | 126 19% |
| 102.216.0.0/24 | Valid | Nonecovered by 102.216.0.0/22 | 26 4%low visibility |
| 102.216.1.0/24 | Valid | Nonecovered by 102.216.0.0/22 | 26 4%low visibility |
| 102.216.2.0/24 | Valid | Nonecovered by 102.216.0.0/22 | 26 4%low visibility |
| 102.216.3.0/24 | Valid | Nonecovered by 102.216.0.0/22 | 26 4%low visibility |
| 102.216.0.0/22 | Valid | RIR databaseAFRINIC | 668 99% |
| 2c0f:1880::/32 | Valid | RIR databaseAFRINIC | 340 53% |
AS-SET
PeeringDB's irr_as_set for AS329062: AS-BAREMETAL. 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 (AS329062 isn't in the set, or no route object for AS329062 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 | AS329062 in it | Not covered |
|---|---|---|---|---|---|
| AS-BAREMETAL | AFRINIC | 1 | 1 | 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 6 are in fix.csv.
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.216.0.0/23 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
| Route object: none | 102.216.2.0/23 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
| Route object: none | 102.216.0.0/24 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
| Route object: none | 102.216.1.0/24 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
| Route object: none | 102.216.2.0/24 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
| Route object: none | 102.216.3.0/24 | No route object for it. A route object for 102.216.0.0/22 with origin AS329062 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329062 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS329062 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.