bgpreport

Network · data from 2026-11-12

AS269205 AS269205 - lider telecom

Registry name: AS269205 - lider telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269205, 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.181.239.0/24 No ROA Other IRR onlyRADB 669 99% 67
45.181.236.0/23 No ROA Other IRR onlyRADB 667 99% 67
45.181.238.0/24 No ROA Other IRR onlyRADB 667 99% 67
45.181.236.0/24 No ROA Other IRR onlyRADB 665 99% 67
45.181.237.0/24 No ROA Other IRR onlyRADB 665 99% 67
2804:6100:100::/48 No ROA Other IRR onlyRADB 634 100% 69
2804:6100:1800::/40 No ROA Other IRR onlyRADB 634 100% 69
2804:6100::/32 No ROA Other IRR onlyALTDB, RADB 630 99% 69

AS-SET

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

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.181.239.0/24No ROA covers it. Add a ROA for AS269205, maxLength 24.669 of 673
Route object: RIR45.181.239.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.181.236.0/23No ROA covers it. Add a ROA for AS269205, maxLength 23.667 of 673
Route object: RIR45.181.236.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.181.238.0/24No ROA covers it. Add a ROA for AS269205, maxLength 24.667 of 673
Route object: RIR45.181.238.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.181.236.0/24No ROA covers it. Add a ROA for AS269205, maxLength 24.665 of 673
Route object: RIR45.181.236.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none45.181.237.0/24No ROA covers it. Add a ROA for AS269205, maxLength 24.665 of 673
Route object: RIR45.181.237.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:6100:100::/48No ROA covers it. Add a ROA for AS269205, maxLength 48.634 of 636
Route object: RIR2804:6100:100::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6100:1800::/40No ROA covers it. Add a ROA for AS269205, maxLength 40.634 of 636
Route object: RIR2804:6100:1800::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:6100::/32No ROA covers it. Add a ROA for AS269205, maxLength 32.630 of 636
Route object: RIR2804:6100::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

45.181.236.0/22ALTDB, RADBNo ROA
45.181.238.0/23RADBNo ROA
2804:6100:f000::/36RADBNo ROA

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.