Next-Access-2 — IP ranges & network footprint

IP Ranges (3)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
77.73.227.40 – 77.73.227.63	Next-Access-2	RIPE	ASSIGNED PA	● low
212.57.58.0/24	Next-access-2	RIPE	ASSIGNED PA	● low
212.57.60.0/24	Next-Access-2	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Next Access” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Next-Access-3 2 blocks
Next-Access-1 2 blocks
Next-Access-7 1 blocks
Next-Access-8 1 blocks
Next-Access-4 1 blocks
Next-Access-5 1 blocks
Next-Access-6 1 blocks

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.

Next-Accessories via MetroNet Bangladesh Limited sub-allocation
Next-Access-7 via Nextpertise B.V. sub-allocation
Next-Access-8 via Nextpertise B.V. sub-allocation
Next-Access-4 via Nextpertise B.V. sub-allocation
Next-Access-5 via Nextpertise B.V. sub-allocation
Next-Access-6 via Nextpertise B.V. sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE NEXTPERTISE-MNT

Netblocks	3 · 536 IPv4 addresses
All fragments	12 blocks across 8 clusters
Cluster ID	215790520
Registry	RIPE
Customers	find customers using this network →

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue