IDNIC-MMNET-AS-ID

Data as of 2026-10-25
BGP inherited
This organisation
Netblocks5 · 514 IPv4 addresses
IPv6 2 prefixes (largest 2001:df3:d240::/48)
Record ID256995710
RegistryAPNIC
Customerssee who runs inside 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 · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
123.108.12.130/32 IDNIC-MMNET-AS-ID PEERINGDB ASSIGNED ● high
157.10.16.98/32 IDNIC-MMNET-AS-ID PEERINGDB ASSIGNED ● high
157.66.16.0/23 IDNIC-MMNET-ID APNIC ASSIGNED PORTABLE ● high
2001:7fa:2:5::490/128 IDNIC-MMNET-AS-ID PEERINGDB ASSIGNED ● high
2001:df3:d240::/48 IDNIC-MMNET-ID APNIC ASSIGNED PORTABLE ● high

IPv6 ranges (2)

Network trust

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

These blocks are registered to IDNIC-MMNET-AS-ID 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.

2001:df3:d240::/48 /48 authorized for AS136089 — PT Mitra Mandiri Network
157.66.16.0/23 /23 authorized for AS136089 — PT Mitra Mandiri Network

NIC Handles

AS136089 MNT-APJII-ID NAH7-AP NAH7-AP