Monsternett AS

BGP inherited

Cluster stats

Netblocks	10 · 16,728 IPv4 addresses
All fragments	11 blocks across 2 clusters
Cluster ID	209557580
Registry	BGP
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
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

Footprint over time

5 weekly snapshots · JSON

10 0 netblocks since 2026-07-05

2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.20.168.0/22	Monsternett AS	BGP	ANNOUNCED	● high
217.171.192.0/20	Monsternett AS	BGP	ANNOUNCED	● high
2a00:15a0::/32	Monsternett AS	BGP	ANNOUNCED	● high
160.5.224.0/20	Monsternett AS	RIPE	LEGACY	● low
185.20.168.0/24	Monsternett AS	RIPE	ASSIGNED PA	● low
185.20.168.0/22	Monsternett AS	RIPE	ALLOCATED PA	● low
185.20.169.0/24	Monsternett AS	RIPE	ASSIGNED PA	● low
217.171.192.0/20	Monsternett AS	RIPE	ALLOCATED PA	● low
217.171.192.0 – 217.171.199.95	MONSTERNETT	RIPE	ASSIGNED PA	● low
2a00:15a0::/29	Monsternett AS	RIPE	ALLOCATED-BY-RIR	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Monsternett” — 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.

MONSTERNETT-COLO 1 blocks

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.

MONSTERNETTCOLO-NET via GLOBALCONNECT AS sub-allocation
Monsternett Cn sub-allocation
MONSTERNETT-COLO sub-allocation

NIC Handles

AS201577 DUMY-RIPE DUMY-RIPE MNT-MONSTERNETT MNT-MONSTERNETT ORG-MA388-RIPE RIPE-NCC-HM-MNT RIPE-NCC-LEGACY-MNT