Melbicom

Data as of 2026-07-26
Registry
Cluster stats
Netblocks33 · 1,038 IPv4 addresses
IPv6 15 prefixes (largest 2a06:f903:4000::/36)
Registered in LT (4) · India (2) · Japan (2) · United States (2) · Sweden (2) · Singapore (2)
All fragments 54 blocks across 6 clusters
Cluster ID214584535
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 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

6 weekly snapshots · JSON
33 0 netblocks since 2026-07-05
2026-07-05 peak 33 2026-07-26

IP Ranges (33)

⬇ export CSV
CIDR Org name Registry Status Confidence
27.111.230.75/32 Melbicom PEERINGDB ASSIGNED ● high
103.16.102.212/32 Melbicom PEERINGDB ASSIGNED ● high
103.27.170.121/32 Melbicom PEERINGDB ASSIGNED ● high
103.77.108.156/32 Melbicom PEERINGDB ASSIGNED ● high
185.1.8.28/32 Melbicom PEERINGDB ASSIGNED ● high
185.1.15.52/32 Melbicom PEERINGDB ASSIGNED ● high
194.68.123.209/32 Melbicom PEERINGDB ASSIGNED ● high
194.68.128.209/32 Melbicom PEERINGDB ASSIGNED ● high
196.60.58.226/32 Melbicom PEERINGDB ASSIGNED ● high
196.216.148.80/32 Melbicom PEERINGDB ASSIGNED ● high
206.71.12.54/32 Melbicom PEERINGDB ASSIGNED ● high
206.72.211.117/32 Melbicom PEERINGDB ASSIGNED ● high
210.171.225.18/32 Melbicom PEERINGDB ASSIGNED ● high
210.173.177.190/32 Melbicom PEERINGDB ASSIGNED ● high
2001:504:13::211:117/128 Melbicom PEERINGDB ASSIGNED ● high
2001:504:40:12::1:54/128 Melbicom PEERINGDB ASSIGNED ● high
2001:7f8:d:fe::209/128 Melbicom PEERINGDB ASSIGNED ● high
2001:7f8:d:ff::209/128 Melbicom PEERINGDB ASSIGNED ● high
2001:7f8:73::2291:0:1/128 Melbicom PEERINGDB ASSIGNED ● high
2001:7f8:7a::8849:1/128 Melbicom PEERINGDB ASSIGNED ● high
2001:7fa:7:1::8849:1/128 Melbicom PEERINGDB ASSIGNED ● high
2001:de8:4::8849:1/128 Melbicom PEERINGDB ASSIGNED ● high
2001:de8:8::8849:1/128 Melbicom PEERINGDB ASSIGNED ● high
2001:de8:12:100::212/128 Melbicom PEERINGDB ASSIGNED ● high
2001:df2:1900:2::156/128 Melbicom PEERINGDB ASSIGNED ● high
2001:43f8:bb1::80/128 Melbicom PEERINGDB ASSIGNED ● high
2001:43f8:11f0::a500:8849:1/128 Melbicom PEERINGDB ASSIGNED ● high
2401:7500:fff6::26e/128 Melbicom PEERINGDB ASSIGNED ● high
95.174.68.0/24 MELBICOM RIPE ASSIGNED PA ● low
95.174.69.0/24 MELBICOM RIPE ASSIGNED PA ● low
95.174.70.0/24 MELBICOM RIPE ASSIGNED PA ● low
95.174.71.0/24 MELBICOM RIPE ASSIGNED PA ● low
2a06:f903:4000::/36 SE-MELBICOM RIPE ASSIGNED ● low

IPv6 ranges (15)

CIDR
2a06:f903:4000::/36
2001:43f8:11f0::a500:8849:1/128
2001:43f8:bb1::80/128
2001:504:13::211:117/128
2001:504:40:12::1:54/128
2001:7f8:73::2291:0:1/128
2001:7f8:7a::8849:1/128
2001:7f8:d:fe::209/128
2001:7f8:d:ff::209/128
2001:7fa:7:1::8849:1/128
2001:de8:12:100::212/128
2001:de8:4::8849:1/128
2001:de8:8::8849:1/128
2001:df2:1900:2::156/128
2401:7500:fff6::26e/128

Network trust

what's this?
RPKI hygiene: B how networks compare →
81.8% of checked blocks have valid RPKI ROA coverage (27 of 33)
Possible discrepancies (5)

These blocks are registered to Melbicom 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.

2a06:f903:4000::/36 /36 authorized for AS8849 — Melbikomas UAB
95.174.68.0/24 /24 authorized for AS8849 — Melbikomas UAB
95.174.69.0/24 /24 authorized for AS8849 — Melbikomas UAB
95.174.70.0/24 /24 authorized for AS8849 — Melbikomas UAB
95.174.71.0/24 /24 authorized for AS8849 — Melbikomas UAB

NIC Handles

AS8849 DUMY-RIPE DUMY-RIPE MELBICOM-MNT