bgpreport

Network · data from 2026-11-12

AS265920 AS265920 - Network Internet

Registry name: AS265920 - Network Internet, BR · not in PeeringDB

7IPv4 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
10No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS265920, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265920, 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.
131.196.204.0/22 No ROA Other IRR onlyRADB 672 100% 66
131.196.204.0/23 No ROA Other IRR onlyRADB 672 100% 66
131.196.204.0/24 No ROA Other IRR onlyRADB 672 100% 66
131.196.205.0/24 No ROA Other IRR onlyRADB 672 100% 66
131.196.206.0/23 No ROA Other IRR onlyRADB 672 100% 66
131.196.206.0/24 No ROA Other IRR onlyRADB 672 100% 66
131.196.207.0/24 No ROA Other IRR onlyRADB 671 100% 66
2804:3fdc::/32 No ROA Other IRR onlyRADB 635 100% 70
2804:3fdc:4000::/35 No ROA Other IRR onlyRADB 635 100% 70
2804:3fdc:6000::/35 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

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

  • ROA: none10
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none131.196.204.0/22No ROA covers it. Add a ROA for AS265920, maxLength 22.672 of 673
Route object: RIR131.196.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.204.0/23No ROA covers it. Add a ROA for AS265920, maxLength 23.672 of 673
Route object: RIR131.196.204.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.204.0/24No ROA covers it. Add a ROA for AS265920, maxLength 24.672 of 673
Route object: RIR131.196.204.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.205.0/24No ROA covers it. Add a ROA for AS265920, maxLength 24.672 of 673
Route object: RIR131.196.205.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.206.0/23No ROA covers it. Add a ROA for AS265920, maxLength 23.672 of 673
Route object: RIR131.196.206.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.206.0/24No ROA covers it. Add a ROA for AS265920, maxLength 24.672 of 673
Route object: RIR131.196.206.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.196.207.0/24No ROA covers it. Add a ROA for AS265920, maxLength 24.671 of 673
Route object: RIR131.196.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:3fdc::/32No ROA covers it. Add a ROA for AS265920, maxLength 32.635 of 636
Route object: RIR2804:3fdc::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3fdc:4000::/35No ROA covers it. Add a ROA for AS265920, maxLength 35.635 of 636
Route object: RIR2804:3fdc:4000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3fdc:6000::/35No ROA covers it. Add a ROA for AS265920, maxLength 35.635 of 636
Route object: RIR2804:3fdc:6000::/35Route 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 AS265920 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.