MELBICOM-JP

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks7 · 1,536 IPv4 addresses
IPv6 1 prefix (largest 2407:d140:1000::/36)
Cluster ID213713901
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
110.44.110.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
110.44.111.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
203.190.0.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
203.190.1.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
203.190.2.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
203.190.3.0/24 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low
2407:d140:1000::/36 MELBICOM-JP APNIC ASSIGNED NON-PORTABLE ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
RPKI-inferred operator Melbikomas UAB
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AM3175-AP MAINT-MELBIKOMASUAB-AP MUA4-AP MUA4-AP