bgpreport

Network · data from 2026-11-12

AS269665 LEKST TELECOM

Registry name: AS269665 - LEKST TELECOM, BR · PeeringDB

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

Announced routes

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

2804:6804::/33 Valid Nonecovered by 2804:6804::/32 353 56% 65
2804:6804::/34 Valid Nonecovered by 2804:6804::/32 353 56% 65
2804:6804:4000::/34 Valid Nonecovered by 2804:6804::/32 353 56% 65
2804:6804:8000::/33 Valid Nonecovered by 2804:6804::/32 353 56% 65
2804:6804:8000::/34 Valid Nonecovered by 2804:6804::/32 353 56% 65
2804:6804:c000::/34 Valid Nonecovered by 2804:6804::/32 353 56% 65
45.191.32.0/22 Valid Other IRR onlyALTDB, TC 671 100% 66
45.191.32.0/23 Valid Other IRR onlyRADB 671 100% 66
45.191.34.0/23 Valid Other IRR onlyRADB 671 100% 66
45.191.34.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 66
45.191.32.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 66
45.191.33.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 66
45.191.35.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 66
2804:6804::/32 Valid Other IRR onlyALTDB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS269665: AS269665. 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 (AS269665 isn't in the set, or no route object for AS269665 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 objectsAS269665 in itNot covered
AS269665 A single AS number, not a set: AS269665 (this network), 8 route objects.

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.

  • Route object: none6
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:6804::/33No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: none2804:6804::/34No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: none2804:6804:4000::/34No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: none2804:6804:8000::/33No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: none2804:6804:8000::/34No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: none2804:6804:c000::/34No route object for it. A route object for 2804:6804::/32 with origin AS269665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269665 in the RIR database for the space.353 of 636
Route object: RIR45.191.32.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.191.32.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.191.34.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.191.34.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.191.32.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.191.33.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.191.35.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:6804::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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