bgpreport

Network · data from 2026-11-12

AS60432 4ISP

Registry name: ASN-forisp NetJoin Srl, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60432, 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.

2a00:8c60:2::/48 No ROA None 1 0%low visibility 1
2a00:8c60:3::/48 No ROA None 1 0%low visibility 1

AS-SET

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a00:8c60:2::/48No ROA covers it. Add a ROA for AS60432, maxLength 48.1 of 636
Route object: none2a00:8c60:2::/48No route object for it. Add a route object with origin AS60432 in the RIR database for the space.1 of 636
ROA: none2a00:8c60:3::/48No ROA covers it. Add a ROA for AS60432, maxLength 48.1 of 636
Route object: none2a00:8c60:3::/48No route object for it. Add a route object with origin AS60432 in the RIR database for the space.1 of 636

Route objects not announced

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

185.26.198.0/23RIPEInvalid: origin
185.26.198.0/24RIPEInvalid: origin
185.26.199.0/24RIPEInvalid: origin

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.