bgpreport

Network · data from 2026-11-12

AS394828 ValTech Communications

Registry name: VALTECH-ENTERPRISES - VALTECH ENTERPRISES, LLC, US · PeeringDB

10IPv4 routes 10.0% RPKI valid · 90.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS394828, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS394828, 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.

147.136.254.0/24 No ROA Other origin only 671 100% 69
2602:2a2::/36 No ROA Other IRR onlyRADB 635 100% 69
23.145.200.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
23.153.120.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
50.58.108.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
50.58.112.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
50.59.146.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
174.46.65.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
174.47.192.0/24 No ROA RIR databaseARIN 671 100% 68
8.8.94.0/24 No ROA RIR databaseARIN, RADB 664 99% 68
2602:fa7f::/36 No ROA RIR databaseARIN, RADB 635 100% 69
2607:1ac0::/32 No ROA RIR databaseARIN 635 100% 69
66.11.18.0/24 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS394828: ARIN::RS-VE. 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 (AS394828 isn't in the set, or no route object for AS394828 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 objectsAS394828 in itNot covered
ARIN::RS-VE A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none12
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none147.136.254.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.671 of 673
Route object: none147.136.254.0/24Route objects for it name AS397673. Add a route object with origin AS394828 in the RIR database for the space.671 of 673
ROA: none2602:2a2::/36No ROA covers it. Add a ROA for AS394828, maxLength 36.635 of 636
Route object: RIR2602:2a2::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none23.145.200.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.671 of 673
ROA: none23.153.120.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.671 of 673
ROA: none50.58.108.0/22No ROA covers it. Add a ROA for AS394828, maxLength 22.671 of 673
ROA: none50.58.112.0/23No ROA covers it. Add a ROA for AS394828, maxLength 23.671 of 673
ROA: none50.59.146.0/23No ROA covers it. Add a ROA for AS394828, maxLength 23.671 of 673
ROA: none174.46.65.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.671 of 673
ROA: none174.47.192.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.671 of 673
ROA: none8.8.94.0/24No ROA covers it. Add a ROA for AS394828, maxLength 24.664 of 673
ROA: none2602:fa7f::/36No ROA covers it. Add a ROA for AS394828, maxLength 36.635 of 636
ROA: none2607:1ac0::/32No ROA covers it. Add a ROA for AS394828, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS394828 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.