Betasoft
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 6 · 2,050 IPv4 addresses |
| IPv6 | 3 prefixes (largest 2a00:2381:d0d7::/48) |
| All fragments | 11 blocks across 4 clusters |
| Cluster ID | 213578444 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
4 weekly snapshots · JSON
6
-1 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-26
IP Ranges (6)
⬇ 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 |
| 2a00:2381:d0d7::/48 | BETASOFT-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
83.3%
of checked blocks have valid RPKI ROA coverage
(5 of 6)
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