Skip to main content

AS398041

XCD-TELECOM

XCD Telecom

Registry

Authoritative registration data

AS number
398041
Name
XCD-TELECOM
Organisation
XCD Telecom
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS398041
169.128.216.0/22 IPv4 /22 not checked
67.226.212.0/22 IPv4 /22 not checked
23.146.136.0/24 IPv4 /24 not checked
23.156.16.0/24 IPv4 /24 not checked
2605:6840::/32 IPv6 /32 RPKI valid
2607:20c0::/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 AS398041 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS398041 in AS paths

Observed upstreams
Families
AS33185 HIVE-DATA-CENTER 370 1,247
v4 v6
AS6939 HURRICANE 32 80
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS398041 in AS paths

Observed downstreams
Families
AS397896 TAIGA-ASN-01 144 334
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS1403 EBOX 2 9
v4 v6
AS49544 i3Dnet 2 7
v4 v6
AS35280 F5 2 5
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.