bgpreport

Network · data from 2026-11-12

AS269460 NEW NET LG SOLUCOES TELECOMUNICACOES E INFORMATICA

Registry name: AS269460 - NEW NET LG SOLUCOES TELECOMUNICACOES E INFORMATICA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269460, 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.187.9.0/24 Invalid: maxLength Nonecovered by 45.187.8.0/23 67 10%low visibility 30
45.187.8.0/22 Valid Other IRR onlyRADB 672 100% 66
45.187.11.0/24 Valid Other IRR onlyRADB 672 100% 67
45.187.8.0/23 Valid Other IRR onlyRADB 671 100% 67
45.187.10.0/24 Valid Other IRR onlyRADB 671 100% 67
2804:64f8::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS269460's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.187.9.0/24ROA 45.187.8.0/22 AS269460 has maxLength 22; ROA 45.187.8.0/23 AS269460 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 45.187.9.0/24.67 of 673
Route object: none45.187.9.0/24No route object for it. A route object for 45.187.8.0/23 with origin AS269460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269460 in the RIR database for the space.67 of 673
Route object: RIR45.187.8.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.187.11.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.187.8.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.187.10.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:64f8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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