bgpreport

Network · data from 2026-11-12

AS269699 LINAX SERVICOS DE INTERNET LTDA

Registry name: AS269699 - LINAX SERVICOS DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269699, 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:6888::/33 No ROA Nonecovered by 2804:6888::/32 631 99% 67
2804:6888:8000::/33 No ROA Nonecovered by 2804:6888::/32 631 99% 67
45.191.252.0/22 No ROA Other IRR onlyRADB, TC 667 99% 67
45.191.252.0/23 No ROA Other IRR onlyRADB 667 99% 67
45.191.254.0/23 No ROA Other IRR onlyRADB 667 99% 67
2804:6888::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
45.191.252.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
45.191.253.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
45.191.254.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
45.191.255.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS269699'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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2804:6888::/33No ROA covers it. Add a ROA for AS269699, maxLength 33.631 of 636
Route object: none2804:6888::/33No route object for it. A route object for 2804:6888::/32 with origin AS269699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269699 in the RIR database for the space.631 of 636
ROA: none2804:6888:8000::/33No ROA covers it. Add a ROA for AS269699, maxLength 33.631 of 636
Route object: none2804:6888:8000::/33No route object for it. A route object for 2804:6888::/32 with origin AS269699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269699 in the RIR database for the space.631 of 636
ROA: none45.191.252.0/22No ROA covers it. Add a ROA for AS269699, maxLength 22.667 of 673
Route object: RIR45.191.252.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none45.191.252.0/23No ROA covers it. Add a ROA for AS269699, maxLength 23.667 of 673
Route object: RIR45.191.252.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.191.254.0/23No ROA covers it. Add a ROA for AS269699, maxLength 23.667 of 673
Route object: RIR45.191.254.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:6888::/32No ROA covers it. Add a ROA for AS269699, maxLength 32.631 of 636
Route object: RIR2804:6888::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none45.191.252.0/24No ROA covers it. Add a ROA for AS269699, maxLength 24.2 of 673
Route object: RIR45.191.252.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none45.191.253.0/24No ROA covers it. Add a ROA for AS269699, maxLength 24.2 of 673
Route object: RIR45.191.253.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none45.191.254.0/24No ROA covers it. Add a ROA for AS269699, maxLength 24.2 of 673
Route object: RIR45.191.254.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none45.191.255.0/24No ROA covers it. Add a ROA for AS269699, maxLength 24.2 of 673
Route object: RIR45.191.255.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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