Network · data from 2026-11-12
AS46718 BTCONF-SON - BT Conferencing
Registry name: BTCONF-SON - BT Conferencing, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46718, 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.
| 216.98.188.0/24 | No ROA | Other origin only | 672 100% |
| 216.98.191.0/24 | No ROA | Other origin only | 672 100% |
| 63.170.232.0/24 | No ROA | RIR databaseARIN | 672 100% |
AS-SET
AS46718 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 5 are in fix.csv.
- ROA: none3
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.98.188.0/24 | No ROA covers it. Add a ROA for AS46718, maxLength 24. |
| Route object: none | 216.98.188.0/24 | Route objects for it name AS18548. Add a route object with origin AS46718 in the RIR database for the space. |
| ROA: none | 216.98.191.0/24 | No ROA covers it. Add a ROA for AS46718, maxLength 24. |
| Route object: none | 216.98.191.0/24 | Route objects for it name AS14039. Add a route object with origin AS46718 in the RIR database for the space. |
| ROA: none | 63.170.232.0/24 | No ROA covers it. Add a ROA for AS46718, maxLength 24. |
Route objects not announced
Every route object with origin AS46718 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.