ATOSS_NET

BGP inherited
Cluster stats
Netblocks8
All fragments 10 blocks across 2 clusters
Cluster ID210018584
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
176.94.3.216/29 ATOSS-NET RIPE ASSIGNED PA ● low
212.75.47.160/27 ATOSS_NET RIPE ASSIGNED PA ● low
212.75.56.208/29 ATOSS_NET RIPE ASSIGNED PA ● low
212.75.58.208/29 ATOSS_NET RIPE ASSIGNED PA ● low
212.75.60.104/29 ATOSS_NET RIPE ASSIGNED PA ● low
212.75.60.112/29 ATOSS_NET RIPE ASSIGNED PA ● low
212.75.60.120/29 ATOSS_NET RIPE ASSIGNED PA ● low
212.211.168.8/29 ATOSS_NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ATOSS” — 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.
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

ARCOR-MNT DUMY-RIPE DUMY-RIPE SCAN-PLUS-MNT