NetOne NL

BGP inherited
Cluster stats
Netblocks24
Registered in Netherlands (8) · Belgium (1) · Canada (1) · Switzerland (1) · France (1)
Cluster ID208801495
RegistryPEERINGDB
Customersfind customers using 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

IP Ranges (24)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.211.17/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.14.102/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.32.101/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.138.22/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.147.202/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.160.13/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.160.88/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.160.239/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.184.47/32 NetOne NL PEERINGDB ASSIGNED ● high
185.1.223.8/32 NetOne NL PEERINGDB ASSIGNED ● high
193.239.119.76/32 NetOne NL PEERINGDB ASSIGNED ● high
206.81.104.61/32 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:20:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:13::a520:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:8f::a520:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:b7::a020:123:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:20:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:10f::3:dc4:13/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:10f::3:dc4:88/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:10f::3:dc4:239/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:12e::20:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high
2001:7f8:134::47/128 NetOne NL PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff::61/128 NetOne NL PEERINGDB ASSIGNED ● high
2a0c:b641:700:0:a5:20:132:1/128 NetOne NL PEERINGDB ASSIGNED ● high

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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (16 of 24)
No discrepancies found among checked blocks.

NIC Handles

AS200132