IDNIC-MMNET-ID

Data as of 2026-10-11
BGP inherited
Limited data: only 3 ranges found registered under this exact name. This may not reflect the organisation's full internet footprint — many companies' web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
Netblocks3 · 513 IPv4 addresses
IPv6 1 prefix (largest 2001:df3:d240::/48)
Record ID245658341
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 (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
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:df3:d240::/48 IDNIC-MMNET-ID APNIC ASSIGNED PORTABLE ● high

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (3 of 3)
Possible discrepancies (2)

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