Skip to main content

AS39560

KT-NET

KT-NET Communications GmbH

Registry

Authoritative registration data

AS number
39560
Name
KT-NET
Organisation
KT-NET Communications GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS39560
85.233.96.0/19 IPv4 /19 not checked
46.20.16.0/20 IPv4 /20 not checked
185.190.220.0/22 IPv4 /22 not checked
185.90.92.0/22 IPv4 /22 not checked
2.56.208.0/22 IPv4 /22 not checked
45.10.144.0/22 IPv4 /22 not checked
45.144.84.0/22 IPv4 /22 not checked
45.149.32.0/22 IPv4 /22 not checked
45.95.124.0/22 IPv4 /22 not checked
85.209.20.0/22 IPv4 /22 not checked
193.254.204.0/23 IPv4 /23 not checked
193.254.218.0/23 IPv4 /23 not checked
2a00:dc0::/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

Internet Exchange memberships listed for AS39560
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 2,000 Mbps IPv4 · IPv6
VIX 3,000 Mbps IPv4 · 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 AS39560 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS39560 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39560 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

40 adjacencies that may be an artefact of collector peering

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.