Network · data from 2026-11-12
AS272102 Besser Solutions
Registry name: AS272102 - BESSER SOLUTIONS C.A., VE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272102, 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.51.123.0/24 | No ROA | Other IRR onlyRADB | 664 99% |
| 38.51.120.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 38.51.121.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 38.51.122.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 149.18.28.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 149.18.29.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 149.18.30.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 149.18.31.0/24 | No ROA | Other IRR onlyRADB | 663 99% |
| 2803:e710::/32 | Valid | RIR databaseLACNIC, RADB | 632 99% |
| 2803:e710:1400::/42 | Valid | RIR databaseLACNIC | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS272102: RADB::AS272102:AS-CONE. 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 (AS272102 isn't in the set, or no route object for AS272102 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 | AS272102 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS272102:AS-CONE | RADB | 9 | 2 | 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: none8
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.51.123.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 38.51.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.51.120.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 38.51.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.51.121.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 38.51.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.51.122.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 38.51.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.18.28.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 149.18.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.18.29.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 149.18.29.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.18.30.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 149.18.30.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.18.31.0/24 | No ROA covers it. Add a ROA for AS272102, maxLength 24. |
| Route object: RIR | 149.18.31.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS272102 whose prefix no peer sees AS272102 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.51.120.0/22 | RADB | No ROA |
| 149.18.28.0/22 | RADB | 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.