MELSA

Handle

Cluster stats

Netblocks	8
All fragments	56 blocks across 2 clusters
Cluster ID	207725025
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

Attribution	RIR handle
Shared handles	clustered on 1 shared RIR contact/maintainer handle
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON

8 0 netblocks since 2026-07-05

2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
103.19.77.14/32	MELSA	PEERINGDB	ASSIGNED	● high
119.11.184.75/32	MELSA	PEERINGDB	ASSIGNED	● high
123.108.12.47/32	MELSA	PEERINGDB	ASSIGNED	● high
218.100.27.143/32	MELSA	PEERINGDB	ASSIGNED	● high
2001:7fa:2:5::43d/128	MELSA	PEERINGDB	ASSIGNED	● high
2001:7fa:f::f/128	MELSA	PEERINGDB	ASSIGNED	● high
2001:df7:3400::196/128	MELSA	PEERINGDB	ASSIGNED	● high
2404:c8:0:a::9657:1/128	MELSA	PEERINGDB	ASSIGNED	● high

Possibly related to this organisation

what's this?

Same name family

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

Melsa-i-net AS 48 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.

DIGAMELSA via VODAFONE ESPANA S.A.U. sub-allocation
HARRYVENTURESSNCDIACHEAMPONGHARRYBOAKYEEMARSHALLANFOMELSA sub-allocation
ARIMELSASDIGIUFFRIDASEMORELLINIG sub-allocation
COMELSASDIMOLTENIELIOEC sub-allocation
ELSEWISYISLAMELSAYEDKAMEL sub-allocation

Network trust

what's this?

RPKI hygiene: D how networks compare →

37.5% of checked blocks have valid RPKI ROA coverage (3 of 8)

No discrepancies found among checked blocks.

NIC Handles

AS9657