AS250.net
Cluster stats
Netblocks15
All fragments 24 blocks across 2 clusters
Cluster ID191838870
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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 (15)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.194.102/32 AS250.net PEERINGDB ASSIGNED ● high
91.198.176.52/32 AS250.net PEERINGDB ASSIGNED ● high
185.1.170.75/32 AS250.net PEERINGDB ASSIGNED ● high
185.1.208.58/32 AS250.net PEERINGDB ASSIGNED ● high
185.1.210.140/32 AS250.net PEERINGDB ASSIGNED ● high
193.110.13.139/32 AS250.net PEERINGDB ASSIGNED ● high
193.178.185.23/32 AS250.net PEERINGDB ASSIGNED ● high
193.239.118.38/32 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8::fa:0:1/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:13::a500:250:1/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:19:1::fa:1/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:21:9::139/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:3d::fa:0:2/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:44::fa:0:2/128 AS250.net PEERINGDB ASSIGNED ● high
2001:7f8:9e::fa:0:2/128 AS250.net PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (12 of 15)
No discrepancies found among checked blocks.

NIC Handles

AS250