Atomic Access
Cluster stats
Netblocks12
All fragments 108 blocks across 29 clusters
Cluster ID193385127
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 (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.60.9.120/32 Atomic Access PEERINGDB ASSIGNED ● high
196.60.9.124/32 Atomic Access PEERINGDB ASSIGNED ● high
196.60.70.149/32 Atomic Access PEERINGDB ASSIGNED ● high
196.60.70.224/32 Atomic Access PEERINGDB ASSIGNED ● high
196.223.22.166/32 Atomic Access PEERINGDB ASSIGNED ● high
196.223.23.49/32 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:1f1::166/128 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:1f1::1:49/128 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:120/128 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:124/128 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:6d1::149/128 Atomic Access PEERINGDB ASSIGNED ● high
2001:43f8:6d1::224/128 Atomic Access 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

AS328266