Mongolia Telecom
MTC-NETWORK
Cluster stats
| Netblocks | 32 |
| All fragments | 300 blocks across 19 clusters |
| Cluster ID | 193326801 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (32)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.242.44.0/23 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 103.242.46.0/23 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.2.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.3.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.4.0/24 | MTC-Network | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.6.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.7.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.8.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.10.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.11.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.12.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.13.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.14.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.15.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.16.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.17.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.18.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.19.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.20.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.21.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.22.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.23.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.24.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.25.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.26.0/24 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 202.179.27.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.28.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.29.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.30.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.179.31.0/24 | MTC-NETWORK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2400:7480:1000::/36 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 2400:7480:2000::/36 | MTC-NETWORK | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(32 of 32)
RPKI-inferred operator
Mongolia Telecom
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
AT960-AP
MAINT-MN-MICOM
UB36-AP
UB36-AP