What we do

Internet Exchange Point

Public peering with route servers and
peer-to-peer connections between any counterparties
at speeds of 1/10/100/400 GBps

What we do


DDoS protection. Up to 100Gbit/s


Public peering with route-servers
No need to negotiate a private interface with all participating providers: it is enough to establish BGP sessions with our route servers.
Price for Kyiv:
Port 2 Gbps – 2800 UAH including VAT
Port 10 GbE - 8 400 UAH including VAT
Port 40 GbE - 18 000 UAH including VAT
Port 100 GbE - 28 800 UAH including VAT
Port 400 GbE - on request
International Exchange - 4000 UAH including VAT for 1Gbps
Price (NRC) - 1200 UAH including VAT ( without crossconnect cost)
Price for Odesa, Kharkiv, Lviv:
1 Gbps – 2 800 UAH including VAT
10 GbE - 20 000 UAH including VAT
40 GbE - 60 000 UAH including VAT
International Exchange - 5000 UAH including VAT for 1Gbps
Price for Amsterdam, Frankfurt and Warsaw:
Port 1 Gbps – 99 €
Port 10 GbE - 400 €
Port 40 GbE - 1200 €
Port 100 GbE - 1800 €
Port 400 GbE - 4800 €

Price (NRC) - 120 €
*We have a system of discounts
Traffic encryption through L1 / L2 / L3 channels of any ISP with guaranteed availability
Private transport
The traffic exchange network provides its members with the ability to use private transports (VLAN)/ between participants of any of the points of presence using the 802.1Q standard. Both Point-To-Point and Point-To-Multipoint Ethernet transports (between three or more ports) are supported.
Available ports: 1Gbps, 10Gbps, 40Gbps, 100Gbps
10Mbps - 10 Gbps – 500 UAH including VAT
100 Mbps - 1000 UAH including VAT
1 Gbps - 2 000 UAH including VAT
1 Gbps - 250€
10 Gbps - 700 €
Price (NRC) - 120 UAH including VAT ( without crossconnect cost on both sides)
* We have a system of discounts
Peer-to-peer connections between any counterparties, ISP, B2C (1/10/100/400 GBps)
Private cloud solutions of any complexity
DDoS protection (levels 1-7)

Connection at Ukraine

Kyiv, Odesa, Lviv, Kharkiv (all addresses)

If you are in the region, build L2 to Kiev, and then we'll redirect you to the desired point and to the desired service.

Connection at Netherlands

AM5 Schepenbergweg 42, Amsterdam, 1105 AT

Connection at Poland

EQUINIX Alejo Jerozolimskie 65/79, Warsaw

Atman WAW-2 Konstruktorska Street 5, Warsaw

Work with us

a partner

1IX doesn't compete with ISPs, IT integrators, equipment and service providers. We only supplement them.

We invite telecom operators to partnership in order to increase the mutual connectivity of networks and the introduction of additional services on the partner's networks.

These technical requirements are mandatory for participants of the 1IX Network:

The maximum transmitted frame size (MTU) is 9216 bytes.
Ethernet frames pointing towards other member ports must have one fixed MAC address in the source field.
Ethernet frames of the IEEE-802.3 standard are allowed, having one of three Ethertypes: 0 × 0800 - IPv4, 0 × 0806 - ARP, 0x86dd - IPv6.
It is not allowed to use proxy ARP on the interfaces of routers connected to the traffic exchange point.
Only two types of broadcast frames are allowed: broadcast ARP, multicast ICMPv6 Neighbor Discovery (ICPMv6 Router Solicitation and Advertisement are not included in this list).
Link-local protocols are not allowed. (A far from complete list of such protocols: IRDP, ICMP redirects, IEEE 802 Spanning Tree, CDP, EDP, ELRP, VTP, DTP, OSPF, ISIS, IGRP, EIGRP, BOOTP / DHCP, PIM-SM, PIM-DM, DVMRP, ICMPv6 ND-RA, UDLD, L2 Keepalives). The exceptions are protocols: ARP and IPv6 ND.
Redirection of IP packets to Network addresses is not allowed - No IP directed broadcast.
On the router interface, the Participant must use only those IP addresses and netmasks that are allocated to him when establishing a connection. Only these addresses can be used as the next-hop parameter for all the Participant's announcements.
The participant must have an Autonomous System (AS) number registered with one of the Regional Internet Registry (RIR).
The participant should not announce private networks, private ASs, default route, full view towards route servers 1-IX.
It is the Member's responsibility to keep the information regarding the routing policy of their autonomous system up to date in the Internet Routing Registry (IRR) of RIPE, ARIN or RADB.