2a00:4180::/32 - BGP Prefix
IPv6RIPE NCCallocated RPKI Valid
CIDR
2a00:4180::/32
IP Version
IPv6
Addresses
79228.1Y
Mask
/32
Country
🇱🇺 Luxembourg
City
Bertrange
RIR
RIPE NCC
Status
allocated
Allocated
2011-04-21
Announced BGP Routes
0 of 0 routesRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below. | ||||
More-Specific Announcements
4 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a00:4180:1::/48 | AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A. | Valid | - | 2026-10-11 |
| 2a00:4180:2::/48 | AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A. | Valid | - | 2026-10-11 |
| 2a00:4180:3::/48 | AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A. | Valid | - | 2026-10-11 |
| 2a00:4180:1000::/36 | AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A. | Valid | - | 2026-10-11 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a00:4180::/34 | 🇱🇺LU | assigned |
Transfer History
Registry transfers of 2a00:4180::/32, blocks inside it, or blocks containing it.
- 2a00:4180::/32M&A ·
- 2a00:4180::/32Transfer ·
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/2a00:4180::/32Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a00:4180::/32" | jq
External Links