Network · data from 2026-11-12
AS396350 Boom Communications
Registry name: BOOMCOMMUNICATIONS-US - Boom Communications, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396350, 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.
| 38.191.112.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.41.214.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.41.213.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 154.41.215.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 165.254.132.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 2001:418:1416::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2602:f950::/36 | Valid | Other IRR onlyRADB | 635 100% |
| 144.225.40.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 144.225.9.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS396350: AS-SET-BOOMCOMMUNICATIONS. 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 (AS396350 isn't in the set, or no route object for AS396350 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 | AS396350 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET-BOOMCOMMUNICATIONS | RADB | 3 | 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 18 are in fix.csv.
- ROA: none4
- Route object: RIR7
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.191.112.0/22 | No ROA covers it. Add a ROA for AS396350, maxLength 22. |
| Route object: RIR | 38.191.112.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.41.214.0/24 | No ROA covers it. Add a ROA for AS396350, maxLength 24. |
| Route object: RIR | 154.41.214.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.41.213.0/24 | No ROA covers it. Add a ROA for AS396350, maxLength 24. |
| Route object: RIR | 154.41.213.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.41.215.0/24 | No ROA covers it. Add a ROA for AS396350, maxLength 24. |
| Route object: RIR | 154.41.215.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 165.254.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:418:1416::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:f950::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS396350 whose prefix no peer sees AS396350 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.191.112.0/24 | RADB | No ROA |
| 38.191.113.0/24 | RADB | No ROA |
| 38.191.114.0/24 | RADB | No ROA |
| 38.191.115.0/24 | RADB | No ROA |
| 154.41.212.0/22 | RADB | No ROA |
| 2001:470:4a9::/48 | ARIN | Valid |
| 2a13:9500:193::/48 | RIPE | 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.