201.25.168.0/23 - BGP Prefix (MOAS)
IPv4RIPE NCCannouncedMOAS RPKI Invalid
CIDR
201.25.168.0/23
IP Version
IPv4
Addresses
512
Mask
/23 (255.255.254.0)
Country
🇯🇵 Japan
City
Tokyo
RIR
RIPE NCC
Status
announced
Allocated
-
Announced BGP Routes
2 of 2 routesMOAS - 2 origin ASNs
RPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 201.25.168.0/23 | AS9009 M247 M247 Europe SRL | Invalid | - | 2026-10-12 |
| 201.25.168.0/23 | AS212238 CDNEXT Datacamp Limited | Valid | RIPE | 2026-10-12 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 201.25.168.0/23 | AS212238 | /24 | ripe |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS212238 | RIPE | lir-us-acedatacenter-1-MNT | 2026-08-03 |
Transfer History
Registry transfers of 201.25.168.0/23, blocks inside it, or blocks containing it.
- 201.25.160.0/19inter-RIRTransfer ·
- 201.25.160.0/19inter-RIRTransfer ·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 201.25.160.0/19inter-RIR | Transfer | |||
| 201.25.160.0/19inter-RIR | Transfer |
Geolocation
Country🇯🇵JapanJP
CityTokyo
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/201.25.168.0/23Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/201.25.168.0/23" | jq
External Links