bgpreport

Network · data from 2026-11-12

AS265104 AS265104 - Gelson Pancheski Kavalkieviz Informatica

Registry name: AS265104 - Gelson Pancheski Kavalkieviz Informatica, BR · not in PeeringDB

7IPv4 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
8No 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 AS265104, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265104, 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.
170.254.104.0/23 No ROA Other IRR onlyRADB 668 99% 67
170.254.104.0/24 No ROA Other IRR onlyRADB 668 99% 67
170.254.105.0/24 No ROA Other IRR onlyRADB 668 99% 67
170.254.104.0/22 No ROA Other IRR onlyRADB 667 99% 67
170.254.106.0/23 No ROA Other IRR onlyRADB 667 99% 67
170.254.106.0/24 No ROA Other IRR onlyRADB 667 99% 67
170.254.107.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:32e8::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS265104 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none170.254.104.0/23No ROA covers it. Add a ROA for AS265104, maxLength 23.668 of 673
Route object: RIR170.254.104.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.254.104.0/24No ROA covers it. Add a ROA for AS265104, maxLength 24.668 of 673
Route object: RIR170.254.104.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.254.105.0/24No ROA covers it. Add a ROA for AS265104, maxLength 24.668 of 673
Route object: RIR170.254.105.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.254.104.0/22No ROA covers it. Add a ROA for AS265104, maxLength 22.667 of 673
Route object: RIR170.254.104.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none170.254.106.0/23No ROA covers it. Add a ROA for AS265104, maxLength 23.667 of 673
Route object: RIR170.254.106.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none170.254.106.0/24No ROA covers it. Add a ROA for AS265104, maxLength 24.667 of 673
Route object: RIR170.254.106.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none170.254.107.0/24No ROA covers it. Add a ROA for AS265104, maxLength 24.666 of 673
Route object: RIR170.254.107.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:32e8::/32No ROA covers it. Add a ROA for AS265104, maxLength 32.636 of 636
Route object: RIR2804:32e8::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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