bgpreport

Network · data from 2026-11-12

AS265010 AS265010 - ZAP NET LTDA

Registry name: AS265010 - ZAP NET LTDA, BR · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
20IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS265010, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265010, 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.84.100.0/22 Valid Other IRR onlyALTDB, RADB 669 99% 67
170.84.100.0/24 Valid Other IRR onlyRADB 669 99% 67
170.84.101.0/24 Valid Other IRR onlyRADB 669 99% 67
170.84.102.0/24 Valid Other IRR onlyRADB 669 99% 67
170.84.103.0/24 Valid Other IRR onlyRADB 669 99% 67
2804:3160::/32 Valid Other IRR onlyALTDB, RADB 635 100% 69
2804:3160::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160::/46 Valid Other IRR onlyRADB 635 100% 69
2804:3160::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:1::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:2::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:3::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:1000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:2000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:3000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:4000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:5000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:6000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7000::/46 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7000::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7001::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7002::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7003::/48 Valid Other IRR onlyRADB 635 100% 69
2804:3160:7004::/46 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS265010 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 25 are in fix.csv.

  • Route object: RIR25
ChangePrefix or setDetailFull-table peers
Route object: RIR170.84.100.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.84.100.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.84.101.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.84.102.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.84.103.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:3160::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160::/46Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:3::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:1000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:3000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:5000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:6000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7000::/46Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7001::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7002::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7003::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3160:7004::/46Route 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 AS265010 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.