Block_4

BGP inherited

Limited data: only 2 ranges found registered under this exact name. This may not reflect the organisation's full internet footprint — many companies' web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.

Cluster stats

Netblocks	2
Cluster ID	205465728
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

IP Ranges (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.10.247.0/24	Block_4	RIPE	ASSIGNED PA	● low
185.15.115.0/24	Block_4	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

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.

Fiber P2P Block 4 sub-allocation
Virtual1 Link via Virtual1 Limited sub-allocation
Splitblock142 via Slovak Telekom, a.s. sub-allocation
Block 4 via Bechtle Managed Service GmbH sub-allocation
Networks-BHS-Block-4 via Bechtle Managed Service GmbH sub-allocation
IRANHOST-IPBLOCK-4 via Roshangar Rayaneh Tehran Co. Ltd. sub-allocation
SIMAH-IP-BLOCK-4 sub-allocation
DH-185-192-BLOCK-4 via The Constant Company, LLC sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

Possible discrepancies (1)

These blocks are registered to Block_4 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

185.10.247.0/24 /24

authorized for AS61266 — Jehovas Zeugen in Deutschland, K.d.O.R.

NIC Handles

DUMY-RIPE DUMY-RIPE JW-MNT Tugushi