Skip to main content

AS212386

cdctelco

ROUTE64-VERIFY: R64-780c955339c662360eb5918b1eb063ed739fa43611c88d0ed9f2f93a5cfb1233

Registry

Authoritative registration data

AS number
212386
Name
cdctelco
Organisation
ROUTE64-VERIFY: R64-780c955339c662360eb5918b1eb063ed739fa43611c88d0ed9f2f93a5cfb1233
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS212386
176.119.199.0/24 IPv4 /24 not checked
2a01:ac0:40::/42 IPv6 /42 not checked
2a01:ac0:80::/42 IPv6 /42 not checked
2a01:ac0::/42 IPv6 /42 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS212386
Address families
INTERIX 10,000 Mbps IPv4 · IPv6
Protocol 7 IX - Hong Kong 1,000 Mbps IPv6
ixFabric - Frankfurt 1,000 Mbps IPv6
ixFabric - London 1,000 Mbps IPv6

No rows match “”.

Showing – of

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 AS212386 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS212386 in AS paths

Observed upstreams
Families
AS11967 HOP179 103 361
v4 v6
AS20473 AS-VULTR 44 166
v4 v6
AS16302 SUOMICOMMUNICATIONS 131 149
v4
AS212895 ROUTE64_ORG 17 28
v4
AS215467 Skhron 5 16
v4 v6
AS211358 AS-IPV6GO 1 6
v6
AS401753 BIXCE 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS212386 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS25091 IP-Max 1 3
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.