195.208.208.0/21 - BGP Prefix (MOAS)
IPv4RIPE NCCallocatedMOAS RPKI Invalid
CIDR
195.208.208.0/21
IP Version
IPv4
Addresses
2K
Mask
/21 (255.255.248.0)
Country
🇷🇺 Russia
City
Moscow
RIR
RIPE NCC
Status
allocated
Allocated
1996-04-19
AS0 discard ROA - upstream RPKI inconsistency
The only ROA covering this prefix names AS0, which means the issuing RIR has published the prefix as “not routable by any AS” (RFC 6483). If the RIR’s allocation records still point to a live operator, the ROA and the RDAP registration disagree - this is an upstream inconsistency in the issuing RIR’s own publications, not necessarily a hijack.
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 |
|---|---|---|---|---|
| 195.208.208.0/21 | AS7713 telkomnet-as-ap - PT Telekomunikasi Indonesia | Invalid | - | 2026-10-12 |
| 195.208.208.0/21 | AS35168 TNS-Plus-Core TNS-Plus LLP | Invalid | - | 2026-10-12 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 195.208.208.0/21 | AS0 | /32 | ripe |
Transfer History
Registry transfers of 195.208.208.0/21, blocks inside it, or blocks containing it.
- 195.208.208.0/21Transfer ·
Origin ASNs (2)
AS7713MOAS
telkomnet-as-ap - PT Telekomunikasi Indonesia
AS35168MOAS
TNS-Plus-Core TNS-Plus LLP
Geolocation
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/195.208.208.0/21Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/195.208.208.0/21" | jq
External Links