MAX_BET-NET

BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 2 clusters
Cluster ID211225175
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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.46.150.121/32 MAX_BET-NET RIPE ASSIGNED PA ● low
77.46.163.18/32 MAX_BET-NET RIPE ASSIGNED PA ● low
79.101.35.229/32 MAX_BET RIPE ASSIGNED PA ● low
79.101.55.129/32 MAX_BET-NET RIPE ASSIGNED PA ● low
93.87.9.128/32 MAX_BET-NET RIPE ASSIGNED PA ● low
93.87.45.87/32 MAX_BET-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MAX BET” — 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.

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE TELEKOM-MNT Telekom-mnt