MCT Japan
Data as of 2026-08-09
BGP inherited
Cluster stats
| Netblocks | 5 |
| IPv6 | 2 prefixes (largest 2001:de8:8:6:0:4:5687:1/128) |
| Registered in | Japan (2) · Australia (1) |
| Cluster ID | 220877178 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 |
|---|---|---|---|---|
| 101.203.89.45/32 | MCT Japan | PEERINGDB | ASSIGNED | ● high |
| 103.246.232.99/32 | MCT Japan | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:8:6:0:4:5687:1/128 | MCT Japan | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::4:5687:1/128 | MCT Japan | PEERINGDB | ASSIGNED | ● high |
| 210.193.244.96/27 | MCT-AP | APNIC | ASSIGNED NON-PORTABLE | ● low |
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)
No discrepancies found among checked blocks.
NIC Handles
AM2341-AP
AS45687
MAINT-AU-MCT
MCT2-AP
MCT2-AP