Skip to main content

AS212066

Y-COM-TR

-------------------------------------------------

Registry

Authoritative registration data

AS number
212066
Name
Y-COM-TR
Organisation
-------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS212066
45.148.65.0/24 IPv4 /24 not checked
5.45.215.0/24 IPv4 /24 not checked
2a02:6b8:215::/48 IPv6 /48 not checked
2a14:48c6::/48 IPv6 /48 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 AS212066 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS212066 in AS paths

Observed upstreams
Families
AS208398 TELETECH 241 464
v4 v6
AS6939 HURRICANE 111 179
v4 v6
AS25091 IP-Max 10 43
v4 v6
AS6663 TTI-NET 2 6
v4 v6
AS12735 ASTurkNet 1 2
v6
AS51095 E1-EMEA 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212066 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS25145 AS-TEKNOTEL 1 4
v4 v6
AS208972 1 4
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.