Betasoft

Registry
Cluster stats
Netblocks7 · 2,047 IPv4 addresses
All fragments 11 blocks across 3 clusters
Cluster ID209569628
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-12

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.216.42.50/32 Betasoft PEERINGDB ASSIGNED ● high
212.91.1.89/32 Betasoft PEERINGDB ASSIGNED ● high
2001:7f8:5b::600/128 Betasoft PEERINGDB ASSIGNED ● high
2001:7f8:60::19:6858:1/128 Betasoft PEERINGDB ASSIGNED ● high
213.5.200.0/21 Betasoft RIPE ASSIGNED PI ● medium
2001:67c:188c::/48 Betasoft-IPv6 RIPE ASSIGNED PI ● medium
2a00:2381:d0d7::/48 BETASOFT-LTD RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Betasoft” — 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: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
Possible discrepancies (1)

These blocks are registered to Betasoft but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:2381:d0d7::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS196858 BTNET-MNT DUMY-RIPE DUMY-RIPE ORG-BSzo10-RIPE PL-CKPOLSL-MNT RIPE-NCC-END-MNT atman-mnt