bgpreport

Network · data from 2026-11-12

AS269749 NETCOM PLUS

Registry name: AS269749 - NETCOM PLUS, C.A, VE · PeeringDB

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

Announced routes

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

45.182.140.0/24 Valid Nonecovered by 45.182.140.0/23 667 99% 67
45.182.141.0/24 Valid Nonecovered by 45.182.140.0/23 667 99% 67
2803:f960::/36 Valid Nonecovered by 2803:f960::/32 631 99% 68
38.183.112.0/24 Valid Other IRR onlyRADB 669 99% 67
38.183.113.0/24 Valid Other IRR onlyRADB 669 99% 67
38.183.114.0/24 Valid Other IRR onlyRADB 669 99% 67
38.183.115.0/24 Valid Other IRR onlyRADB 669 99% 67
38.183.119.0/24 Valid Other IRR onlyRADB 669 99% 67
206.1.88.0/24 Valid Other IRR onlyRADB 669 99% 67
206.1.89.0/24 Valid Other IRR onlyRADB 669 99% 67
206.1.90.0/24 Valid Other IRR onlyRADB 669 99% 67
206.1.91.0/24 Valid Other IRR onlyRADB 669 99% 67
38.183.112.0/21 Valid RIR databaseARIN 669 99% 67
45.182.140.0/23 Valid RIR databaseLACNIC, RADB 669 99% 67
206.1.88.0/22 Valid RIR databaseARIN 669 99% 67
2803:f960::/32 Valid RIR databaseLACNIC, RADB 631 99% 68

AS-SET

PeeringDB's irr_as_set for AS269749: LACNIC::AS269749:AS-CLIENTES. 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 (AS269749 isn't in the set, or no route object for AS269749 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 objectsAS269749 in itNot covered
LACNIC::AS269749:AS-CLIENTES LACNIC 4133 No 16

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

  • Route object: none3
  • Route object: RIR9
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none45.182.140.0/24No route object for it. A route object for 45.182.140.0/23 with origin AS269749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269749 in the RIR database for the space.667 of 673
Route object: none45.182.141.0/24No route object for it. A route object for 45.182.140.0/23 with origin AS269749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269749 in the RIR database for the space.667 of 673
Route object: none2803:f960::/36No route object for it. A route object for 2803:f960::/32 with origin AS269749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269749 in the RIR database for the space.631 of 636
Route object: RIR38.183.112.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.183.113.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.183.114.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.183.115.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.183.119.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.1.88.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.1.89.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.1.90.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.1.91.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
AS-SET: own ASNLACNIC::AS269749:AS-CLIENTESAS269749 isn't in AS269749:AS-CLIENTES (LACNIC) once expanded. Add AS269749 to it.

Route objects not announced

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

38.183.116.0/24RADBValid
38.183.117.0/24RADBValid
38.183.118.0/24RADBValid

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.