Network · data from 2026-11-12
AS15100 BEVCOMM-AS1
Registry name: BEVCOMM-AS1 - Bevcomm, US · PeeringDB
21IPv4 routes
19.0% RPKI valid · 76.2% with a route object
1IPv6 routes
0.0% RPKI valid · 0.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
17No ROA
6 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS15100, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS15100, 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.38.46.0/23 | Invalid: maxLength | RIR databaseARIN | 28 4%low visibility |
| 69.163.0.0/21 | No ROA | Nonecovered by 69.163.0.0/19 | 671 100% |
| 69.163.8.0/21 | No ROA | Nonecovered by 69.163.0.0/19 | 671 100% |
| 69.163.16.0/20 | No ROA | Nonecovered by 69.163.0.0/19 | 671 100% |
| 69.163.28.0/24 | No ROA | Nonecovered by 69.163.0.0/19 | 671 100% |
| 69.163.31.0/24 | No ROA | Nonecovered by 69.163.0.0/19 | 671 100% |
| 2606:e700::/35 | No ROA | Nonecovered by 2606:e700::/32 | 632 99% |
| 76.164.128.0/19 | No ROA | RIR databaseARIN | 671 100% |
| 192.40.192.0/21 | No ROA | RIR databaseARIN | 671 100% |
| 199.199.240.0/21 | No ROA | RIR databaseARIN | 670 100% |
| 206.146.64.0/20 | No ROA | RIR databaseARIN | 670 100% |
| 206.146.64.0/21 | No ROA | RIR databaseARIN | 670 100% |
| 206.146.72.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 206.146.76.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 206.146.80.0/20 | No ROA | RIR databaseARIN | 670 100% |
| 69.163.0.0/19 | No ROA | RIR databaseARIN | 669 99% |
| 206.145.24.0/22 | No ROA | RIR databaseARIN | 669 99% |
| 168.151.96.0/19 | No ROA | RIR databaseARIN | 665 99% |
| 216.38.32.0/22 | Valid | RIR databaseARIN | 671 100% |
| 216.38.32.0/20 | Valid | RIR databaseARIN | 670 100% |
| 216.38.36.0/22 | Valid | RIR databaseARIN | 670 100% |
| 216.38.40.0/21 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS15100'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 30 are in fix.csv.
- ROA: maxLength1
- ROA: none17
- Route object: none6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 216.38.46.0/23 | ROA 216.38.32.0/20 AS15100 has maxLength 20; ROA 216.38.40.0/21 AS15100 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 216.38.46.0/23. |
| ROA: none | 69.163.0.0/21 | No ROA covers it. Add a ROA for AS15100, maxLength 21. |
| Route object: none | 69.163.0.0/21 | No route object for it. A route object for 69.163.0.0/19 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 69.163.8.0/21 | No ROA covers it. Add a ROA for AS15100, maxLength 21. |
| Route object: none | 69.163.8.0/21 | No route object for it. A route object for 69.163.0.0/19 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 69.163.16.0/20 | No ROA covers it. Add a ROA for AS15100, maxLength 20. |
| Route object: none | 69.163.16.0/20 | No route object for it. A route object for 69.163.0.0/19 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 69.163.28.0/24 | No ROA covers it. Add a ROA for AS15100, maxLength 24. |
| Route object: none | 69.163.28.0/24 | No route object for it. A route object for 69.163.0.0/19 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 69.163.31.0/24 | No ROA covers it. Add a ROA for AS15100, maxLength 24. |
| Route object: none | 69.163.31.0/24 | No route object for it. A route object for 69.163.0.0/19 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 2606:e700::/35 | No ROA covers it. Add a ROA for AS15100, maxLength 35. |
| Route object: none | 2606:e700::/35 | No route object for it. A route object for 2606:e700::/32 with origin AS15100 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15100 in the RIR database for the space. |
| ROA: none | 76.164.128.0/19 | No ROA covers it. Add a ROA for AS15100, maxLength 19. |
| ROA: none | 192.40.192.0/21 | No ROA covers it. Add a ROA for AS15100, maxLength 21. |
| ROA: none | 199.199.240.0/21 | No ROA covers it. Add a ROA for AS15100, maxLength 21. |
| ROA: none | 206.146.64.0/20 | No ROA covers it. Add a ROA for AS15100, maxLength 20. |
| ROA: none | 206.146.64.0/21 | No ROA covers it. Add a ROA for AS15100, maxLength 21. |
| ROA: none | 206.146.72.0/22 | No ROA covers it. Add a ROA for AS15100, maxLength 22. |
| ROA: none | 206.146.76.0/22 | No ROA covers it. Add a ROA for AS15100, maxLength 22. |
| ROA: none | 206.146.80.0/20 | No ROA covers it. Add a ROA for AS15100, maxLength 20. |
| ROA: none | 69.163.0.0/19 | No ROA covers it. Add a ROA for AS15100, maxLength 19. |
| ROA: none | 206.145.24.0/22 | No ROA covers it. Add a ROA for AS15100, maxLength 22. |
| ROA: none | 168.151.96.0/19 | No ROA covers it. Add a ROA for AS15100, maxLength 19. |
Route objects not announced
Route objects with origin AS15100 whose prefix no peer sees AS15100 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.40.192.0/22 | ARIN | No ROA |
| 192.40.196.0/22 | ARIN | No ROA |
| 206.146.64.0/19 | ARIN | No ROA |
| 2001:470:38f::/48 | ARIN | Valid |
| 2001:470:63e::/48 | ARIN | Valid |
| 2606:e700::/32 | ARIN | 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.