bgpreport

Network · data from 2026-11-12

AS268506 AS268506 - LEON TELECOM LTDA

Registry name: AS268506 - LEON TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268506, 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.162.96.0/24 No ROA Nonecovered by 45.162.96.0/22 672 100% 67
2804:5244::/32 No ROA None 636 100% 67
45.162.97.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.162.98.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.162.96.0/22 No ROA Other IRR onlyRADB 671 100% 66
45.162.99.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS268506 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none45.162.96.0/24No ROA covers it. Add a ROA for AS268506, maxLength 24.672 of 673
Route object: none45.162.96.0/24No route object for it. A route object for 45.162.96.0/22 with origin AS268506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268506 in the RIR database for the space.672 of 673
ROA: none2804:5244::/32No ROA covers it. Add a ROA for AS268506, maxLength 32.636 of 636
Route object: none2804:5244::/32No route object for it. Add a route object with origin AS268506 in the RIR database for the space.636 of 636
ROA: none45.162.97.0/24No ROA covers it. Add a ROA for AS268506, maxLength 24.672 of 673
Route object: RIR45.162.97.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.162.98.0/24No ROA covers it. Add a ROA for AS268506, maxLength 24.672 of 673
Route object: RIR45.162.98.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.162.96.0/22No ROA covers it. Add a ROA for AS268506, maxLength 22.671 of 673
Route object: RIR45.162.96.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.162.99.0/24No ROA covers it. Add a ROA for AS268506, maxLength 24.671 of 673
Route object: RIR45.162.99.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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