JINX Operations/Route Collector

Data as of 2026-09-27
BGP inherited
This organisation
Netblocks6
IPv6 3 prefixes (largest 2001:43f8:1f0::101/128)
Record ID246698774
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.60.96.3/32 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high
196.60.96.101/32 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high
196.60.96.102/32 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high
2001:43f8:1f0::3/128 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high
2001:43f8:1f0::101/128 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high
2001:43f8:1f0::102/128 JINX Operations/Route Collector PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Footprint over time

12 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-09-27

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS37474