2a0e:4001:2000::/36 - PFCLOUD UG (Haftungsbeschrankt) (AS51396)
CIDR
2a0e:4001:2000::/36
IP Version
IPv6
Addresses
4951.7Y
Mask
/36
Country
🇩🇪 Germany
City
Hanover (Bothfeld-Vahrenheide)
RIR
RIPE
Status
assigned
Allocated
-
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
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a0e:4001:2000::/36 | AS51396 PFCLOUD Pfcloud UG (haftungsbeschrankt) | Invalid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a0e:4001:2000::/36 | AS0 | /36 | ripe |
Transfer History
Registry transfers of 2a0e:4001:2000::/36, blocks inside it, or blocks containing it.
- 2a0e:4000::/29Transfer ·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 2a0e:4000::/29 | DGTL Technologies LLC | DGTL TECH UK LLP | Transfer |
Related Prefixes
More prefixes of AS51396
All prefixes of AS51396 →Geolocation
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 transfer marketTransfers published by all five RIRs
API
Open https://api.ipctl.io/v1/prefix/2a0e:4001:2000::/36Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a0e:4001:2000::/36" | jq
External Links