Home Prefix Lookup2a04:81c0::/29

2a04:81c0::/29 - TANGO PROXIMUS NXT Proximus Luxembourg S.A (AS56665)

IPv6RIPE NCCallocatedAS56665TANGO-PROXIMUS_NXT Proximus Luxembourg S.A. RPKI Valid

CIDR

2a04:81c0::/29

IP Version

IPv6

Addresses

633825.3Y

Mask

/29

Country

🇱🇺 Luxembourg

City

Bertrange

RIR

RIPE NCC

Status

allocated

Allocated

2013-11-11

Announced BGP Routes

1 of 1 route

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
2a04:81c0::/29	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Valid	RIPE	2026-10-11

More-Specific Announcements

6 more-specific announcements

Prefix	Origin AS	RPKI	IRR	Last Seen
2a04:81c4::/44	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Valid	-	2026-10-11
2a04:81c4:10::/44	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Valid	-	2026-10-11
2a04:81c4:1000::/40	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Valid	-	2026-10-11
2a04:81c4:1100::/40	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Valid	-	2026-10-11
2a04:81c4:aa00::/40	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Invalid	-	2026-10-11
2a04:81c4:cc00::/40	AS56665 TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.	Invalid	-	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
2a04:81c0::/29	AS56665	/29	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS56665	RIPE	TANGO-MNT	2019-04-11

More Specific Prefixes

Prefix	Country	Status
2a04:81c0::/32	🇱🇺LU	assigned
2a04:81c4::/36	🇱🇺LU	assigned
2a04:81c4:1000::/36	🇱🇺LU	assigned

Transfer History

Registry transfers of 2a04:81c0::/29, blocks inside it, or blocks containing it.

2a04:81c0::/29M&A · 2019-02-07
Tango S.A.
RIPE NCC
→
Proximus Luxembourg S.A.
RIPE NCC

Date	Resource	From	To	Type
2019-02-07	2a04:81c0::/29	Tango S.A. RIPE NCC	Proximus Luxembourg S.A. RIPE NCC	M&A

Origin ASN

AS56665

TANGO-PROXIMUS_NXT Proximus Luxembourg S.A.

Related Prefixes

More prefixes of AS56665

All prefixes of AS56665 →

Geolocation

Country🇱🇺LuxembourgLU

RegionLuxembourg

CityBertrange

Coordinates49.6076, 6.0699 ↗

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

GEThttps://api.ipctl.io/v1/prefix/2a04:81c0::/29

Returns prefix allocation, BGP routes, and more-specific subnets.

curl -s "https://api.ipctl.io/v1/prefix/2a04:81c0::/29" | jq

External Links

RIPEstat