bgpreport

Network · data from 2026-11-12

AS269799 GENOVEZ TOBAR CARLOS ANDRES (NOCTELECOM)

Registry name: AS269799 - GENOVEZ TOBAR CARLOS ANDRES (NOCTELECOM), EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269799, 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:a0a0:905::/48 Valid Nonecovered by 2803:a0a0:900::/40 634 100% 67
2803:a0a0:906::/48 Valid Nonecovered by 2803:a0a0:900::/40 634 100% 67
2803:a0a0:907::/48 Valid Nonecovered by 2803:a0a0:900::/40 634 100% 67
2803:a0a0:908::/48 Valid Nonecovered by 2803:a0a0:900::/40 634 100% 67
2803:a0a0:901::/48 Valid Nonecovered by 2803:a0a0:900::/40 3 0%low visibility 3
2803:a0a0:904::/48 Valid Other IRR onlyRADB 633 100% 67
2803:8420:ff00::/48 Valid Other IRR onlyRADB 630 99% 68
2803:a0a0:903::/48 Valid Other IRR onlyRADB 630 99% 68
45.233.103.0/24 Valid RIR databaseALTDB, LACNIC, RADB 666 99% 67

AS-SET

PeeringDB's irr_as_set for AS269799: AS269799:AS-UPSTREAM. 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 (AS269799 isn't in the set, or no route object for AS269799 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 objectsAS269799 in itNot covered
AS269799:AS-UPSTREAM LACNIC 614,808 No 9

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

  • Route object: none5
  • Route object: RIR3
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2803:a0a0:905::/48No route object for it. A route object for 2803:a0a0:900::/40 with origin AS269799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269799 in the RIR database for the space.634 of 636
Route object: none2803:a0a0:906::/48No route object for it. A route object for 2803:a0a0:900::/40 with origin AS269799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269799 in the RIR database for the space.634 of 636
Route object: none2803:a0a0:907::/48No route object for it. A route object for 2803:a0a0:900::/40 with origin AS269799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269799 in the RIR database for the space.634 of 636
Route object: none2803:a0a0:908::/48No route object for it. A route object for 2803:a0a0:900::/40 with origin AS269799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269799 in the RIR database for the space.634 of 636
Route object: none2803:a0a0:901::/48No route object for it. A route object for 2803:a0a0:900::/40 with origin AS269799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269799 in the RIR database for the space.3 of 636
Route object: RIR2803:a0a0:904::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:8420:ff00::/48Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2803:a0a0:903::/48Route object only in RADB. Add it in the RIR database for the space.630 of 636
AS-SET: own ASNAS269799:AS-UPSTREAMAS269799 isn't in AS269799:AS-UPSTREAM (LACNIC) once expanded. Add AS269799 to it.

Route objects not announced

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

2803:8420:ff00::/40LACNIC, RADBValid
2803:a0a0:900::/40LACNIC, RADBValid

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.