Network · data from 2026-11-12

AS268056 LEXCOM TELECOM

Registry name: AS268056 - LEXCOM TELECOM, BR · PeeringDB

9IPv4 routes 77.8% RPKI valid · 55.6% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 4 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS268056, seen from no peer

Announced routes

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


186.194.84.0/24	No ROA	Other origin only	668 99%	67
186.194.85.0/24	No ROA	Other origin only	668 99%	67
45.168.88.0/24	Valid	Nonecovered by 45.168.88.0/23	202 30%	54
45.168.90.0/24	Valid	Nonecovered by 45.168.90.0/23	202 30%	54
45.168.88.0/22	Valid	Other IRR onlyALTDB, RADB, TC	671 100%	66
2804:5748::/32	Valid	Other IRR onlyRADB, TC	634 100%	67
2804:5748::/33	Valid	Other IRR onlyRADB	355 56%	64
2804:5748:8000::/33	Valid	Other IRR onlyRADB	355 56%	64
45.168.88.0/23	Valid	Other IRR onlyALTDB, RADB	202 30%	54
45.168.89.0/24	Valid	Other IRR onlyRADB	202 30%	54
45.168.90.0/23	Valid	Other IRR onlyRADB	202 30%	54
45.168.91.0/24	Valid	Other IRR onlyRADB	201 30%	54

AS-SET

PeeringDB's irr_as_set for AS268056: AS-LEXCOM-268056. 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 (AS268056 isn't in the set, or no route object for AS268056 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.

Name	Database	ASNs	Sets	Route objects	AS268056 in it	Not covered
AS-LEXCOM-268056	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS268056 in it

Not covered

AS-LEXCOM-268056

In no IRR database read today.

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

ROA: none2
Route object: none4
Route object: RIR8
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
ROA: none	186.194.84.0/24	No ROA covers it. Add a ROA for AS268056, maxLength 24.	668 of 673
Route object: none	186.194.84.0/24	Route objects for it name AS28249. Add a route object with origin AS268056 in the RIR database for the space.	668 of 673
ROA: none	186.194.85.0/24	No ROA covers it. Add a ROA for AS268056, maxLength 24.	668 of 673
Route object: none	186.194.85.0/24	Route objects for it name AS28249. Add a route object with origin AS268056 in the RIR database for the space.	668 of 673
Route object: none	45.168.88.0/24	No route object for it. A route object for 45.168.88.0/23 with origin AS268056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268056 in the RIR database for the space.	202 of 673
Route object: none	45.168.90.0/24	No route object for it. A route object for 45.168.90.0/23 with origin AS268056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268056 in the RIR database for the space.	202 of 673
Route object: RIR	45.168.88.0/22	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:5748::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:5748::/33	Route object only in RADB. Add it in the RIR database for the space.	355 of 636
Route object: RIR	2804:5748:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	355 of 636
Route object: RIR	45.168.88.0/23	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	202 of 673
Route object: RIR	45.168.89.0/24	Route object only in RADB. Add it in the RIR database for the space.	202 of 673
Route object: RIR	45.168.90.0/23	Route object only in RADB. Add it in the RIR database for the space.	202 of 673
Route object: RIR	45.168.91.0/24	Route object only in RADB. Add it in the RIR database for the space.	201 of 673
AS-SET: not found	AS-LEXCOM-268056	PeeringDB names AS-LEXCOM-268056; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

186.194.84.0/24

No ROA covers it. Add a ROA for AS268056, maxLength 24.

668 of 673

Route object: none

186.194.84.0/24

Route objects for it name AS28249. Add a route object with origin AS268056 in the RIR database for the space.

668 of 673

ROA: none

186.194.85.0/24

No ROA covers it. Add a ROA for AS268056, maxLength 24.

668 of 673

Route object: none

186.194.85.0/24

Route objects for it name AS28249. Add a route object with origin AS268056 in the RIR database for the space.

668 of 673

Route object: none

45.168.88.0/24

No route object for it. A route object for 45.168.88.0/23 with origin AS268056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268056 in the RIR database for the space.

202 of 673

Route object: none

45.168.90.0/24

No route object for it. A route object for 45.168.90.0/23 with origin AS268056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268056 in the RIR database for the space.

202 of 673

Route object: RIR

45.168.88.0/22

Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.

671 of 673

Route object: RIR

2804:5748::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

634 of 636

Route object: RIR

2804:5748::/33

Route object only in RADB. Add it in the RIR database for the space.

355 of 636

Route object: RIR

2804:5748:8000::/33

Route object only in RADB. Add it in the RIR database for the space.

355 of 636

Route object: RIR

45.168.88.0/23

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

202 of 673

Route object: RIR

45.168.89.0/24

Route object only in RADB. Add it in the RIR database for the space.

202 of 673

Route object: RIR

45.168.90.0/23

Route object only in RADB. Add it in the RIR database for the space.

202 of 673

Route object: RIR

45.168.91.0/24

Route object only in RADB. Add it in the RIR database for the space.

201 of 673

AS-SET: not found

AS-LEXCOM-268056

PeeringDB names AS-LEXCOM-268056; no IRR database read has it.

Route objects not announced

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