2a10:77c0::/29 - BGP Prefix (MOAS)
IPv6RIPE NCCallocatedMOAS RPKI Invalid
CIDR
2a10:77c0::/29
IP Version
IPv6
Addresses
633825.3Y
Mask
/29
Country
🇺🇸 United States
City
Ashburn
RIR
RIPE NCC
Status
allocated
Allocated
2020-10-05
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
3 of 3 routesMOAS - 3 origin ASNs
RPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a10:77c0::/29 | AS6079 RCN-AS - RCN | Invalid | - | 2026-10-11 |
| 2a10:77c0::/29 | AS212144 FUTURE-NETWORK-01 trafficforce, UAB | Invalid | - | 2026-10-11 |
| 2a10:77c0::/29 | AS402933 VOSMET - Vosmet | Invalid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a10:77c0::/29 | AS0 | /29 | ripe |
Origin ASNs (3)
AS6079MOAS
RCN-AS - RCN
AS212144MOAS
FUTURE-NETWORK-01 trafficforce, UAB
AS402933MOAS
VOSMET - Vosmet
Geolocation
Country🇺🇸United StatesUS
CityAshburn
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/2a10:77c0::/29Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a10:77c0::/29" | jq
External Links