jac john

BGP inherited

Cluster stats

Netblocks	8
Cluster ID	210210327
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

8 0 netblocks since 2026-07-05

2026-07-05 peak 8 2026-07-19

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
5.39.32.224/27	jac john	RIPE	ASSIGNED PA	● high
5.39.34.192/27	jac john	RIPE	ASSIGNED PA	● high
5.135.7.160/27	jac john	RIPE	ASSIGNED PA	● high
5.135.28.160/27	jac john	RIPE	ASSIGNED PA	● high
5.135.82.224/27	jac john	RIPE	ASSIGNED PA	● high
5.135.209.176/28	jac john	RIPE	ASSIGNED PA	● high
51.75.35.160/27	jac john	RIPE	LEGACY	● high
51.75.37.160/27	jac john	RIPE	LEGACY	● high

what's this?

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

john_elechukwu sub-allocation
john_osajele sub-allocation
JOHNNY-NIEMANN-NET via TDC Holding A/S sub-allocation
John-MCINTYRE-000000008687245 via British Telecommunications Limited sub-allocation
Pipex John Kennedy via Wavenet Limited sub-allocation
John-FITZPATRICK-000000008392925 via British Telecommunications Limited sub-allocation
John-MASON-000000009074172 via British Telecommunications Limited sub-allocation
John-PINHORN-000000008623243 via British Telecommunications Limited sub-allocation

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)

No discrepancies found among checked blocks.

DUMY-RIPE DUMY-RIPE ORG-JJ162-RIPE OVH-MNT