FRONTNET
Data as of 2026-10-18
BGP inherited
This organisation
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2001:200:141::/48) |
| Also registered under this name | 4 netblocks across 2 separate records |
| Record ID | 252208028 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 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 |
|---|---|---|---|---|
| 2001:200:141::/48 | FRONTNET | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 2001:200:142::/48 | STARBED-NET | APNIC | ASSIGNED NON-PORTABLE | ● medium |
| 2001:df0:2ed::/48 | FRONTNET | APNIC | ASSIGNED PORTABLE | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
RPKI-inferred operator
WIDE Project
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
JNIC1-AP
JNIC1-AP
MAINT-JP-WIDE
MAINT-JPNIC
SU19-AP
TM382-AP
YS413-AP
YS413-AP