Network · data from 2026-11-12
AS13645 365 Data Centers (Host.net)
Registry name: BROADBANDONE - BroadbandONE, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13645, 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.
| 64.139.220.0/22 | No ROA | None | 666 99% |
| 75.119.176.0/22 | No ROA | Other origin onlycovered by 75.119.128.0/18 | 666 99% |
| 75.119.184.0/24 | No ROA | Other origin onlycovered by 75.119.128.0/18 | 666 99% |
| 75.119.190.0/23 | No ROA | Other origin onlycovered by 75.119.128.0/18 | 666 99% |
| 66.115.0.0/18 | No ROA | Other IRR onlyBBOI | 668 99% |
| 216.242.0.0/16 | No ROA | Other IRR onlyBBOI | 668 99% |
| 2001:5b8::/32 | No ROA | Other IRR onlyBBOI | 631 99% |
AS-SET
AS13645's PeeringDB record names no 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 31 are in fix.csv.
- ROA: none7
- Route object: none4
- Route object: RIR3
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.139.220.0/22 | No ROA covers it. Add a ROA for AS13645, maxLength 22. |
| Route object: none | 64.139.220.0/22 | No route object for it. Add a route object with origin AS13645 in the RIR database for the space. |
| ROA: none | 75.119.176.0/22 | No ROA covers it. Add a ROA for AS13645, maxLength 22. |
| Route object: none | 75.119.176.0/22 | Route objects for it name AS19151. A route object for 75.119.128.0/18 with origin AS13645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13645 in the RIR database for the space. |
| ROA: none | 75.119.184.0/24 | No ROA covers it. Add a ROA for AS13645, maxLength 24. |
| Route object: none | 75.119.184.0/24 | Route objects for it name AS19151. A route object for 75.119.128.0/18 with origin AS13645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13645 in the RIR database for the space. |
| ROA: none | 75.119.190.0/23 | No ROA covers it. Add a ROA for AS13645, maxLength 23. |
| Route object: none | 75.119.190.0/23 | Route objects for it name AS19151. A route object for 75.119.128.0/18 with origin AS13645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13645 in the RIR database for the space. |
| ROA: none | 66.115.0.0/18 | No ROA covers it. Add a ROA for AS13645, maxLength 18. |
| Route object: RIR | 66.115.0.0/18 | Route object only in BBOI. Add it in the RIR database for the space. |
| ROA: none | 216.242.0.0/16 | No ROA covers it. Add a ROA for AS13645, maxLength 16. |
| Route object: RIR | 216.242.0.0/16 | Route object only in BBOI. Add it in the RIR database for the space. |
| ROA: none | 2001:5b8::/32 | No ROA covers it. Add a ROA for AS13645, maxLength 32. |
| Route object: RIR | 2001:5b8::/32 | Route object only in BBOI. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13645 whose prefix no peer sees AS13645 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.34.247.0/24 | RADB | No ROA |
| 64.135.0.0/17 | BBOI | No ROA |
| 64.135.24.0/24 | BBOI | No ROA |
| 64.139.128.0/18 | BBOI | No ROA |
| 66.154.100.0/22 | RADB | No ROA |
| 66.179.220.0/24 | BBOI | No ROA |
| 66.216.51.0/24 | BBOI | No ROA |
| 66.231.184.0/22 | RADB | No ROA |
| 66.231.187.0/24 | RADB | No ROA |
| 72.51.20.0/23 | RADB | No ROA |
| 72.51.22.0/23 | RADB | No ROA |
| 75.119.128.0/18 | BBOI | No ROA |
| 168.245.192.0/24 | BBOI | No ROA |
| 190.114.10.0/24 | BBOI | No ROA |
| 192.92.140.0/24 | BBOI | No ROA |
| 204.16.208.0/22 | RADB | No ROA |
| 204.235.96.0/21 | BBOI | No ROA |
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.