Skip to main content

AS212630

AS_LUXAIRPORT

Aeroport de Luxembourg

Registry

Authoritative registration data

AS number
212630
Name
AS_LUXAIRPORT
Organisation
Aeroport de Luxembourg
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS212630
82.117.241.0/24 IPv4 /24 not checked
91.209.220.0/24 IPv4 /24 not checked
2a0b:53c0::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS212630 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS212630 in AS paths

Observed upstreams
Families
AS6661 146 457
v4 v6
AS56665 TANGO-PROXIMUS_NXT 146 453
v4 v6
AS29467 77 217
v4 v6
AS34019 HIVANE 4 16
v4 v6
AS20766 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212630 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS25091 IP-Max 1 9
v4 v6
AS24482 SGGS-AS-AP 1 6
v4 v6
AS2027 MilkyWan 1 3
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS56987 AS-ABACLOUDA 1 3
v4 v6
AS209823 1 3
v4 v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.