Skip to main content

AS204025

CMD

Centre de Telecommunications et Teleinformatiques Luxembourgeois s.a.

Registry

Authoritative registration data

AS number
204025
Name
CMD
Organisation
Centre de Telecommunications et Teleinformatiques Luxembourgeois s.a.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS204025
185.71.56.0/22 IPv4 /22 not checked
185.71.56.0/23 IPv4 /23 not checked
185.71.58.0/23 IPv4 /23 not checked
185.71.58.0/24 IPv4 /24 not checked
185.71.59.0/24 IPv4 /24 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 AS204025 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS204025 in AS paths

Observed upstreams
Families
AS29467 LuxNetwork 310 1,015
v4
AS174 COGENT-174 208 608
v4
AS6939 HURRICANE 18 19
v4
AS25091 IP-Max 3 15
v4
AS34019 HIVANE 3 15
v4
AS20766 GITOYEN-MAIN-AS 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204025 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 21
v4
AS2027 MilkyWan 1 3
v4
AS36236 NETACTUATE 1 3
v4
AS56987 AS-ABACLOUDA 1 3
v4
AS209823 ENKI-AS 1 3
v4

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.