Oxymium
Cluster stats
Netblocks12
All fragments 25 blocks across 6 clusters
Cluster ID193382070
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

Footprint over time

2 weekly snapshots · JSON
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-06

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.49.236.97/32 Oxymium PEERINGDB ASSIGNED ● high
77.95.71.28/32 Oxymium PEERINGDB ASSIGNED ● high
188.93.170.84/32 Oxymium PEERINGDB ASSIGNED ● high
193.34.197.244/32 Oxymium PEERINGDB ASSIGNED ● high
194.116.96.242/32 Oxymium PEERINGDB ASSIGNED ● high
195.42.144.33/32 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:23:ffff::242/128 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:43::4:1157:1/128 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:47:47::1c/128 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:4c::a0c5:1/128 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:54::97/128 Oxymium PEERINGDB ASSIGNED ● high
2001:7f8:6d::4:1157:1/128 Oxymium PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS41157