bgpreport

Network · data from 2026-11-12

AS265999 R N DE CASTRO PROVEDOR DE INTERNET

Registry name: AS265999 - Cianet Provedor de Internet EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265999, 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.
164.163.100.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
164.163.102.0/24 No ROA Other IRR onlyRADB, TC 668 99% 66
164.163.101.0/24 No ROA Other IRR onlyALTDB, RADB, TC 666 99% 66
138.94.99.0/24 No ROA Other IRR onlyRADB 665 99% 67
2804:4108::/32 No ROA Other IRR onlyRADB, TC 628 99% 67
164.163.103.0/24 No ROA Other IRR onlyALTDB, RADB, TC 25 4%low visibility 12

AS-SET

AS265999'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 46 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none164.163.100.0/24No ROA covers it. Add a ROA for AS265999, maxLength 24.672 of 673
Route object: RIR164.163.100.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none164.163.102.0/24No ROA covers it. Add a ROA for AS265999, maxLength 24.668 of 673
Route object: RIR164.163.102.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none164.163.101.0/24No ROA covers it. Add a ROA for AS265999, maxLength 24.666 of 673
Route object: RIR164.163.101.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none138.94.99.0/24No ROA covers it. Add a ROA for AS265999, maxLength 24.665 of 673
Route object: RIR138.94.99.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:4108::/32No ROA covers it. Add a ROA for AS265999, maxLength 32.628 of 636
Route object: RIR2804:4108::/32Route object only in RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none164.163.103.0/24No ROA covers it. Add a ROA for AS265999, maxLength 24.25 of 673
Route object: RIR164.163.103.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.25 of 673

Route objects not announced

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

138.94.96.0/24RADBNo ROA
164.163.100.0/22RADB, TCNo ROA
164.163.100.0/23RADB, TCNo ROA
164.163.102.0/23RADB, TCNo ROA
2804:4108::/33RADB, TCNo ROA
2804:4108::/34RADB, TCNo ROA
2804:4108::/35RADBNo ROA
2804:4108::/36RADBNo ROA
2804:4108:1000::/36RADBNo ROA
2804:4108:2000::/35RADBNo ROA
2804:4108:2000::/36RADBNo ROA
2804:4108:3000::/36RADBNo ROA
2804:4108:4000::/34RADB, TCNo ROA
2804:4108:4000::/35RADBNo ROA
2804:4108:4000::/36RADBNo ROA
2804:4108:5000::/36RADBNo ROA
2804:4108:6000::/35RADBNo ROA
2804:4108:6000::/36RADBNo ROA
2804:4108:7000::/36RADBNo ROA
2804:4108:8000::/33RADB, TCNo ROA
2804:4108:8000::/34RADB, TCNo ROA
2804:4108:8000::/35RADBNo ROA
2804:4108:8000::/36RADBNo ROA
2804:4108:9000::/36RADBNo ROA
2804:4108:a000::/35RADBNo ROA
2804:4108:a000::/36RADBNo ROA
2804:4108:b000::/36RADBNo ROA
2804:4108:c000::/34RADB, TCNo ROA
2804:4108:c000::/35RADBNo ROA
2804:4108:c000::/36RADBNo ROA
2804:4108:d000::/36RADBNo ROA
2804:4108:e000::/35RADBNo ROA
2804:4108:e000::/36RADBNo ROA
2804:4108: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.