bgpreport

Network · data from 2026-11-12

AS273890 NAP VE - Transit

Registry name: AS273890 - SERVICIOS NAP VEN, C.A., VE · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
18IPv6 routes 100.0% RPKI valid · 72.2% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 5 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS273890, seen from no peer

Announced routes

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

2803:7760:1010::/48 Valid Nonecovered by 2803:7760:1000::/42 634 100% 67
2803:7760:1020::/48 Valid Nonecovered by 2803:7760:1000::/42 634 100% 67
2801:18d:d::/48 Valid Nonecovered by 2801:18d:c::/46 1 0%low visibility 1
2801:18d:e::/48 Valid Nonecovered by 2801:18d:c::/46 1 0%low visibility 1
2801:18d:f::/48 Valid Nonecovered by 2801:18d:c::/46 1 0%low visibility 1
45.68.90.0/23 Valid Other IRR onlyRADB 671 100% 68
38.9.176.0/24 Valid Other IRR onlyRADB 670 100% 68
45.68.102.0/24 Valid Other IRR onlyRADB 670 100% 68
45.68.103.0/24 Valid Other IRR onlyRADB 670 100% 68
45.68.102.0/23 Valid Other IRR onlyRADB 666 99% 67
45.68.90.0/24 Valid Other IRR onlyRADB 665 99% 67
45.68.91.0/24 Valid Other IRR onlyRADB 665 99% 67
2801:18d:c::/46 Valid Other IRR onlyRADB 634 100% 69
2801:18d:10::/45 Valid Other IRR onlyRADB 634 100% 69
2801:18d:11::/48 Valid Other IRR onlyRADB 634 100% 69
2801:18d:13::/48 Valid Other IRR onlyRADB 634 100% 69
2801:18d:1::/48 Valid Other IRR onlyRADB 631 99% 68
2801:18d:2::/47 Valid Other IRR onlyRADB 631 99% 68
2801:18d:4::/46 Valid Other IRR onlyRADB 631 99% 70
2801:18d:8::/45 Valid Other IRR onlyRADB 631 99% 70
2801:18d:a::/48 Valid Other IRR onlyRADB 631 99% 68
2801:18d:b::/48 Valid Other IRR onlyRADB 631 99% 68
2803:7760:1000::/48 Valid Other IRR onlyRADB 631 99% 68
38.9.177.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
2801:18d:3::/48 Valid Other IRR onlyRADB 1 0%low visibility 1
2801:18d:10::/46 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS273890: AS273890:AS-CUSTOMERS. 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 (AS273890 isn't in the set, or no route object for AS273890 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 objectsAS273890 in itNot covered
AS273890:AS-CUSTOMERS RADB 9587,586 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 40 are in fix.csv.

  • Route object: none5
  • Route object: RIR21
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none2803:7760:1010::/48No route object for it. A route object for 2803:7760:1000::/42 with origin AS273890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273890 in the RIR database for the space.634 of 636
Route object: none2803:7760:1020::/48No route object for it. A route object for 2803:7760:1000::/42 with origin AS273890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273890 in the RIR database for the space.634 of 636
Route object: none2801:18d:d::/48No route object for it. A route object for 2801:18d:c::/46 with origin AS273890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273890 in the RIR database for the space.1 of 636
Route object: none2801:18d:e::/48No route object for it. A route object for 2801:18d:c::/46 with origin AS273890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273890 in the RIR database for the space.1 of 636
Route object: none2801:18d:f::/48No route object for it. A route object for 2801:18d:c::/46 with origin AS273890 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273890 in the RIR database for the space.1 of 636
Route object: RIR45.68.90.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.9.176.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.68.102.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.68.103.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.68.102.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.68.90.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR45.68.91.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2801:18d:c::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2801:18d:10::/45Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2801:18d:11::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2801:18d:13::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2801:18d:1::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2801:18d:2::/47Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2801:18d:4::/46Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2801:18d:8::/45Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2801:18d:a::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2801:18d:b::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2803:7760:1000::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR38.9.177.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR2801:18d:3::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2801:18d:10::/46Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

38.9.176.0/23ARIN, RADBValid
38.13.184.0/23ARINValid
45.68.88.0/22LACNIC, RADBValid
45.68.88.0/24RADBValid
45.68.89.0/24RADBValid
45.68.100.0/22LACNIC, RADBValid
2801:18d::/44LACNIC, RADBValid
2801:18d:2::/48RADBValid
2801:18d:c::/48RADBValid
2801:18d:10::/44LACNIC, RADBValid
2801:18d:18::/45RADBValid
2803:7760:1000::/42LACNIC, RADBValid
2803:7760:1001::/48RADBValid
2803:7760:1002::/48RADBValid

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.