bgpreport

Network · data from 2026-11-12

AS269946 BOOM SOLUTIONS C.A.

Registry name: AS269946 - BOOM SOLUTIONS C.A., VE · PeeringDB

28IPv4 routes 100.0% RPKI valid · 96.4% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS269946, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269946, 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.159.48.0/21 Valid Nonecovered by 38.159.48.0/20 673 100% 67
2803:3850:9f00::/48 Valid Nonecovered by 2803:3850::/32 603 95% 67
38.68.176.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.177.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.179.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.180.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.181.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.182.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.183.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.184.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.185.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.48.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.49.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.53.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.56.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.60.0/24 Valid Other IRR onlyRADB 672 100% 67
38.159.61.0/24 Valid Other IRR onlyRADB 672 100% 67
74.123.48.0/24 Valid Other IRR onlyRADB 672 100% 67
74.123.49.0/24 Valid Other IRR onlyRADB 672 100% 67
74.123.51.0/24 Valid Other IRR onlyRADB 672 100% 67
38.68.178.0/24 Valid Other IRR onlyRADB 671 100% 67
38.159.57.0/24 Valid Other IRR onlyRADB 671 100% 67
38.159.59.0/24 Valid Other IRR onlyRADB 671 100% 67
38.159.62.0/24 Valid Other IRR onlyRADB 671 100% 67
74.123.50.0/24 Valid Other IRR onlyRADB 671 100% 67
38.159.58.0/24 Valid Other IRR onlyRADB 665 99% 67
38.159.63.0/24 Valid Other IRR onlyRADB 665 99% 67
38.159.54.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
45.189.234.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
2803:3850::/32 Valid RIR databaseLACNIC, RADB 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS269946: AS269946:AS-BOOMSOLUTIONS. 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 (AS269946 isn't in the set, or no route object for AS269946 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.

NameDatabaseASNsSets Route objectsAS269946 in itNot covered
AS269946:AS-BOOMSOLUTIONS LACNIC 11861 No 30

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 43 are in fix.csv.

  • Route object: none2
  • Route object: RIR26
  • AS-SET: own ASN1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none38.159.48.0/21No route object for it. A route object for 38.159.48.0/20 with origin AS269946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269946 in the RIR database for the space.673 of 673
Route object: none2803:3850:9f00::/48No route object for it. A route object for 2803:3850::/32 with origin AS269946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269946 in the RIR database for the space.603 of 636
Route object: RIR38.68.176.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.177.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.179.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.180.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.181.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.182.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.183.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.184.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.185.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.48.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.49.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.53.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.56.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.60.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.159.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.123.48.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.123.49.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.123.51.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.68.178.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.159.57.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.159.59.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.159.62.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR74.123.50.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.159.58.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR38.159.63.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR38.159.54.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: own ASNAS269946:AS-BOOMSOLUTIONSAS269946 isn't in AS269946:AS-BOOMSOLUTIONS (LACNIC) once expanded. Add AS269946 to it.

Route objects not announced

Route objects with origin AS269946 whose prefix no peer sees AS269946 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.68.176.0/20ARINValid
38.68.186.0/24RADBValid
38.68.187.0/24RADBValid
38.68.188.0/24RADBValid
38.68.189.0/24RADBValid
38.68.190.0/24RADBValid
38.68.191.0/24RADBValid
38.159.48.0/20ARINValid
38.159.50.0/24RADBValid
38.159.51.0/24RADBValid
38.159.52.0/24RADBValid
38.159.55.0/24RADBValid
74.123.48.0/22LACNIC, RADBValid
2801:1b:c800::/48RADBNo 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.