1-IX's exchange-port account prices Ukrainian route locality

Summary

• 1-IX matters if its Ukrainian exchange-port, route-server, local data-centre and Europe-facing interconnection account lets Ukrainian networks hold more traffic close to users, reduce paid transit exposure, and buy useful routing optionality under wartime fibre, power and cross-border uncertainty.
• The public case is commercially credible but bounded. 1-IX has direct evidence for legal identity, Ukrainian telecom registration, published port prices, 30-plus connection data centres, more than 150 claimed participants, PeeringDB and Internet Society exchange records, and visible content or carrier members; it does not publish audited real traffic by Ukrainian city, port utilisation, customer retention, outage history, power autonomy or gross margin by service line.

The purchase begins with a traffic bill under pressure

The customer that makes 1-IX economically interesting is a Ukrainian ISP, hosting operator, content platform, corporate network, public-sector contractor or carrier aggregation business that has reached the point where upstream transit alone is too blunt a tool. It may have customers in Kyiv and Lviv watching video, reaching cloud services, using banking platforms, gaming, backing up files, or moving traffic between local networks. It may also be trying to keep routes usable while electricity is unreliable, fibre paths are exposed, engineers are scarce, and foreign transit routes carry more strategic weight than they did before 2022.

The paid unit is a Ukrainian exchange-port, route-locality and peering account. The buyer pays for a port or transport path that lets its autonomous system meet other networks at 1-IX, exchange selected traffic through route servers or private sessions, and avoid sending every packet through a paid upstream transit provider. That unit is valuable only if it changes the customer's total operating cost. It has to save enough on transit, latency, troubleshooting and routing exposure to justify port fees, data-centre cross-connects, optical modules, router capacity, staff time, contract work and the risk of depending on another shared switching fabric.

The substitute list is explicit in the first procurement meeting. The buyer can keep buying paid upstream transit. It can take a remote foreign IX port in Warsaw, Frankfurt, Amsterdam or another European market and haul traffic there. It can pay for a private cross-connect to one high-volume partner if one partner drives most demand. It can seek a CDN cache or direct content arrangement to remove a large content category from the bill. It can also do nothing until traffic grows, accepting higher unit transit cost because the port, cross-connect and engineering work are not yet worth the effort. 1-IX matters if its local account beats enough of those alternatives at once.

The economic test is not whether an Internet exchange point is useful in theory. Internet Society describes peering and IXPs as a way for networks to keep traffic local, make connections faster, lower the cost of expensive international links and improve resilience (https://www.internetsociety.org/our-work/connectivity/peering/). That is the general rule. The specific question is whether "1-IX" LLC turns that rule into a Ukrainian service account with enough member liquidity, operating trust and route control to be worth paying for during a period when network managers also have to budget for batteries, generators, spare optics, remote hands, cyber defence and emergency rerouting.

The company's own pages make the commercial promise in direct language. Its Ukrainian site says 1-IX unites operators to increase efficiency, reliability and availability of Internet resources by providing direct connection between networks (https://1-ix.net/en/). The same page positions the product as an "Internet accelerator" with lower-latency direct connections, more traffic-routing control, backup for current ISP uplinks, standard 24/7 support and SLA language. The page also says more than 150 participants trust the exchange and lists a mix of Ukrainian networks, carriers, content platforms and global names (https://1-ix.net/en/uchasnyky-en-translation/).

That does not prove that every buyer should connect. A local port is a monthly commitment, and it adds another failure domain. A small ISP with little off-net traffic may be better off buying a blended transit service and waiting. A network whose traffic is dominated by one content platform may get more from a cache or private interconnect. A company whose sites are not in 1-IX data centres must still buy a path into the exchange. A foreign-focused hosting business may prefer a remote European fabric. 1-IX's strategic value begins only when Ukrainian locality, member liquidity and routing optionality have enough weight to beat those alternatives.

The legal and financial record shows a young operating company

The public corporate record identifies the directory subject as a recent Ukrainian legal company, not a long-established incumbent carrier. Opendatabot lists EDRPOU code 45177866 for TOV "1-IX", gives the English name as LIMITED LIABILITY COMPANY "1-IX", shows a Kyiv address at Prakhovykh Simyi Street 50, records 6 September 2023 as the foundation date, names Denys Yashchenko as director, and lists wired telecommunications activity as the main business classification (https://opendatabot.ua/c/45177866). Hosting Ukraine's registry page repeats the same legal identity, registration date, main activity and address, and records the company as registered in the Ukrainian state register (https://www.ukraine.com.ua/egrpou/45177866/).

That matters because the exchange brand appears to have a longer operating story than the current Ukrainian legal vehicle. The 1-IX site describes design in 2021, a project start in 2022, 45 participants, own channels, two cross-border transitions and seven PoPs in Kyiv, Odesa, Lviv and Warsaw; then 150 members, 2 Tbit/s of own channels, four cross-border transitions and more than 30 PoPs in 10 cities in 2023; then a 2024 plan of 250-plus members and European expansion (https://1-ix.net/en/about-us-english-edition/). The corporate registration in September 2023 therefore should not be read as the first date of the exchange concept. It is the legal wrapper visible in the Ukrainian registry for the assigned company.

Opendatabot's financial presentation is also useful, but it should be treated as a registry-derived and platform-processed signal rather than a full audited investor pack. It shows revenue of 2.6 million hryvnias in 2023, 28.7 million hryvnias in 2024 and 43.0 million hryvnias in 2025; net profit of about 91,300 hryvnias in 2023, 2.1 million hryvnias in 2024 and 2.9 million hryvnias in 2025; assets of 842,200 hryvnias in 2023, 3.9 million hryvnias in 2024 and 6.5 million hryvnias in 2025; and staff rising from 1 to 10 to 14 across those years (https://opendatabot.ua/c/45177866). Hosting Ukraine's registry presentation shows similar rounded 2023-2025 figures (https://www.ukraine.com.ua/egrpou/45177866/).

The scale is consistent with a young exchange and interconnection service business that has started to monetise ports, engineering and related services, not with a national fibre incumbent. The 2025 revenue figure is meaningful in local operating terms, but it is small beside the capital and labour burden of a large carrier network. That is why the economic unit should remain the account and not an imagined national infrastructure monopoly. 1-IX can be strategically useful without being financially large.

The regulator-adjacent evidence supports the telecom status. Opendatabot states that the company is in the register of providers of electronic communications networks and services (https://opendatabot.ua/c/45177866). A public NKEK PDF listing providers includes TOV "1-IX" among entities in the electronic communications provider list, alongside many Ukrainian telecom operators (https://nkek.gov.ua/static-objects/nkek/uploads/public/68f/78b/5bc/68f78b5bcba6a097766150.pdf). That proves recognition as a telecom-sector participant. It does not reveal port churn, service quality, customer concentration or the economics of the switching fabric.

The boundary is important. A buyer can verify that "1-IX" LLC exists, is registered, operates in the telecom field and reports growing financial activity. The public record does not show whether the company earns high margin on exchange ports, whether it cross-subsidises Ukrainian resilience from European services, whether a small group of large accounts drives revenue, or whether staffing is enough for simultaneous incidents. Those are contract-diligence questions, not questions answered by a registry entry.

Published prices turn locality into a measurable option

The strongest direct commercial evidence is that 1-IX publishes tariff bands. The Ukrainian service page lists connection cities Kyiv, Lviv, Kharkiv, Odesa, Dnipro and Uzhhorod, then gives a "Port price / UAH with VAT" table with 1G at 6,000 UAH, 10G at 60,000 UAH, 40G at 220,000 UAH and 100G at 450,000 UAH (https://1-ix.net/en/poslugy-en-translation/ua-exchange-2/). The same service page also contains separate blocks for Kyiv data-centre connections, another Ukrainian connection block, consulting and outsourcing services, and L2/VLAN transport. Because the page combines several product sections and has visible translation and formatting issues, a buyer should treat it as a starting tariff sheet rather than a final invoice.

Even with that caveat, the price logic is visible. A port is not free just because settlement-free peering can reduce transit bills. The customer has to rent the port, bring fibre or a cross-connect into the right data centre, configure BGP, update PeeringDB, keep route objects and RPKI clean, monitor sessions, and decide which peers should receive which prefixes. The step-by-step connection guide says the customer must be a legal entity with an AS number and IP block, choose a data centre based on 1-IX's PeeringDB presence, select speed from 1G to 400G, agree VLAN and router details, receive a draft agreement, receive an LOA with the demarcation point, order the cross from the data-centre operator, then enter a two-week free trial before monthly billing (https://1-ix.net/1-ixknowhow/instructions/).

That sequence is the practical economics of a route-locality account. The monthly port fee is only one line. A network outside the same facility pays backhaul to a 1-IX location. A customer inside the facility still pays for cross-connect work and may need optics, router ports, hands-and-eyes support and staff time. The more ports and sessions it manages, the more the NOC must understand BGP policy. The exchange account becomes cheaper than upstream transit only after the reachable traffic base is large enough and stable enough.

1-IX's Europe-facing pricing makes the same comparison sharper. The 1-ix.eu site describes a carrier-grade distributed IXP, lists 238 networks, 92 10G ports, 35 40G ports, 155 100G ports, a 4.75 Tb/s traffic peak, and says a single connection can exchange traffic and L2 transports with all members (https://1-ix.eu/). Its Internet Peering table lists monthly euro prices of 99 for 1G, 400 for 10G, 900 for 40G, 1,800 for 100G and 4,600 for 400G, with discounts where partial port use is planned. Its L2 Transport table lists 99 euro for 1G, 700 euro for 10G and 2,000 euro for 40G, with 100G and 400G on request (https://1-ix.eu/).

The EU pricing does not directly price a Ukrainian port from "1-IX" LLC, because the European site is associated with A-Systems Sp. z o.o. in PeeringDB. It still matters to the Ukrainian thesis because 1-IX sells a platform story that spans Ukrainian and European interconnection. The buyer's choice is not just "local port or no port". It can be "local port plus foreign reach", "remote foreign IX port plus Ukrainian backhaul", "foreign transit only", or "private cross-connect to one partner". The published price bands let the buyer compare those choices as an account.

The 1-ix.eu page also lists IP Transit 1Gbit/s on a 100G port at 95th percentile pricing at 50 euro in its other-services table, while cloud services such as Microsoft Azure access, Google cloud and AWS Direct Connect are on request (https://1-ix.eu/). That is a useful reminder that 1-IX is not only selling pure public peering. It is selling a bundle of peering, transport, transit and cloud-adjacent access. The exchange-port account can therefore be a sales entry point into several services.

The buyer should price all of this against the substitutes. Paid upstream transit is simpler and can be cheaper at low volume, but it keeps more traffic in paid upstream paths. A remote foreign IX port may offer deeper global liquidity, but it requires transport and may increase latency for domestic Ukrainian traffic. A private cross-connect can be ideal for one heavy partner, but it does not create broad route-server liquidity. A CDN cache can remove traffic from the bill but only for the cache owner's content. Doing nothing until traffic grows avoids immediate spending, but it can leave the network paying more per useful bit and accepting weaker local route control.

Member liquidity is the product, not decoration

An exchange port has no value without other useful networks on the fabric. 1-IX's public member list is therefore not a marketing sidebar; it is core product evidence. The Ukrainian site says the list is according to PeeringDB and includes more than 150 participants. It lists content networks, Ukrainian ISPs, carriers, route servers and global platforms, including Amazon.com, Apple Edge Cache, ByteDance, CDN77, Cloudflare, Datagroup, Facebook Inc, Google, Google Global Cache, Hetzner Online, Hurricane Electric, Kyivstar, Microsoft, Netflix, OVHcloud, Telegram Messenger, Twitch, UA-IX, UARNet, Ukrtelecom, Valve Corporation and Vodafone-adjacent entries elsewhere in the technical records (https://1-ix.net/en/uchasnyky-en-translation/).

Those names should not be overread. A member list does not prove every pair exchanges material traffic, that all members are physically in the same Ukrainian data centre, or that a buyer's routes will be accepted by selective peers. Still, the mix is commercially meaningful. A regional ISP benefits when local access networks, national carriers, content platforms and route-server peers are reachable through one account. The value of the first 10G port grows when it can touch many useful counterparties rather than one bilateral session.

PeeringDB gives a more structured external view. The 1-IX UA record identifies "1-IX Internet Exchange Ukraine" with organization "1-IX UA LLC", cities Kyiv, Odesa, Kharkiv, Dnipro, Poltava, Lviv, Uzhgorod and Uman, country Ukraine, 12 facilities, 107 listed networks and a last update on 29 August 2024 (https://www.peeringdb.com/ix/3562). The PeeringDB API snapshot pulled for this review showed 140 public netixlan entries for 1-IX UA, representing 107 unique ASNs and about 5.61 Tbps of listed member port capacity. PeeringDB is self-reported and not a real-time traffic meter, but it is one of the industry's standard interconnection directories.

The Internet Society Pulse IXP Tracker gives the same evidence in reader-friendly form. Its 1-IX Ukraine page, based on PeeringDB data last updated in May 2026, lists 107 member ASNs, 95 registered in Ukraine, 56 Cable/DSL/ISP networks, 19 NSPs, 8 content networks and 5 enterprise networks. It also reports that 85 of 107 members peer at the route server and 89 of 107 use RPKI (https://pulse.internetsociety.org/en/ixp-tracker/ixp/1007/). Those figures describe exactly the kind of liquidity a small or regional network wants: local access networks, content, transit-like networks and route-server convenience.

The comparison set matters. Internet Society's UA-IX page lists Ukrainian Internet Exchange - UA-IX at 152 members and 4,157 Gbps of cumulative port speeds in May 2026, with 122 of 152 members at the route server and 134 using RPKI (https://pulse.internetsociety.org/en/ixp-tracker/ixp/114/). The same page's country selector lists many Ukrainian IXP options, including 1-IX UA, DTEL-IX, Giganet IXN, GNM-IX UA, LVIV-IX, Mesh.IX, UA-IX and others. That is healthy for customers, and it disciplines 1-IX pricing. If another exchange gives a better member mix in the buyer's city, 1-IX cannot rely on the generic value of peering alone.

Member liquidity also shapes trust. Route servers make it easier to peer without negotiating dozens of bilateral sessions. 1-IX's connection guide asks customers to allow BGP sessions for rs1, rs2 and rs3 on the international exchange and says this is necessary to fully reserve services (https://1-ix.net/1-ixknowhow/instructions/). Its peering policy requires a registered AS number, at least one IP prefix, a current PeeringDB profile, routing policy in RIPE, ARIN or RADB, complete AS-SET objects and ROA objects for RPKI, correct next-hop behaviour and restrictions on leaking peering LAN networks (https://1-ix.net/en/peering-policy-en/). Those rules are not just technical etiquette. They are how the exchange protects the economic value of the shared fabric.

The member evidence supports a positive but conditional judgement. A buyer with real Ukrainian traffic can see enough peers, content names and route-server adoption to justify a serious trial. The same buyer still needs to ask which members are reachable in the exact city, which peers are open or selective, which ports are active, and what traffic volume will actually move off paid transit.

Ukrainian geography is the operating surface

The geography of 1-IX's Ukrainian footprint matters because route locality is physical before it is economic. The PeeringDB record lists Kyiv, Odesa, Kharkiv, Dnipro, Poltava, Lviv, Uzhgorod and Uman for 1-IX UA (https://www.peeringdb.com/ix/3562). Internet Society Pulse repeats those cities for 1-IX Ukraine (https://pulse.internetsociety.org/en/ixp-tracker/ixp/1007/). The 1-IX network-map page says that during the war it publishes only the number of data centres where participants can join and that addresses are provided by request or specialist contact. It lists 12 connection points in Kyiv, 3 in Lviv, 3 in Odesa, and 1 each in Dnipro, Kharkiv and Uzhhorod, with European points in Amsterdam, Warsaw, Frankfurt, London and Bratislava (https://1-ix.net/en/karta-merezhi-en-translation/).

That disclosure choice is itself a wartime signal. In peacetime, public facility addresses can help customers and peers plan. In wartime, too much facility detail can be sensitive. For the buyer, the tradeoff is practical. Less public detail may be understandable, but it increases pre-sales diligence work. The buyer needs to know whether its router is already in a 1-IX facility, whether a local metro cross-connect is possible, whether it needs third-party backhaul, whether there are two physically separated paths, and whether a second city improves continuity enough to justify cost.

Kyiv is the natural centre of gravity, but the route-locality thesis is not Kyiv alone. Odesa, Kharkiv, Dnipro, Lviv and Uzhhorod are all commercially relevant in different ways. Odesa and Dnipro matter for large regional demand and southern or eastern business routes. Kharkiv matters because an eastern industrial and academic region under wartime stress may still need resilient connectivity. Lviv and Uzhhorod matter because western Ukraine has become more important for displaced activity, logistics, European handoffs and continuity planning. A port in the wrong city can be cheap and still not solve the buyer's risk.

Cloudflare's analysis of the first year of the war in Ukraine showed how traffic patterns changed under invasion and power stress, with shifts away from heavily attacked regions and increases in western regions during the early displacement period, and sharp national traffic drops after energy-infrastructure strikes (https://blog.cloudflare.com/one-year-of-war-in-ukraine/). RIPE Labs' analysis of Ukraine's internet after one year of war also tied late-2022 instability to attacks on electrical power and stressed the importance of electricity for Internet availability (https://labs.ripe.net/author/emileaben/the-resilience-of-the-internet-in-ukraine-one-year-on/). Those are national observations, not 1-IX audits, but they explain why city-level exchange access is not an abstract map exercise.

The paid unit is valuable when it maps to the buyer's real failure scenario. If the buyer needs lower latency to Kyiv-hosted services, a Kyiv port matters. If the buyer needs a western failover path, Lviv, Uzhhorod or a Europe-linked transport option may matter more. If it needs to keep video and cloud traffic away from expensive transit links, content-member reach matters. If it needs a second Ukrainian routing community because one exchange or carrier has operational trouble, multi-IX strategy matters. A 1-IX account can contribute to each case, but only if the physical and logical route match the problem.

The public record does not provide a full route map, switch inventory, power-backup table or availability report by location. It tells us that 1-IX has a distributed Ukrainian and European service surface and that it deliberately limits public address detail during the war. The buyer therefore has to turn public geography into contract evidence: facility name, demarcation, LOA, cross-connect price, optical budget, power autonomy, remote-hands process, maintenance window, escalation list and route-server redundancy.

The European extension changes the substitute equation

1-IX is not only a Ukrainian exchange story. The European side is commercially important because wartime Ukrainian networks often need foreign reach without abandoning local control. The PeeringDB record for 1-IX EU identifies "1-IX Internet Exchange Europe" in cities including New York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Lviv, Kyiv and Hong Kong, with country Poland, 25 facilities and 171 networks (https://www.peeringdb.com/ix/3958). The 1-ix.eu site lists a distributed IXP, 238 networks, high counts of 10G, 40G and 100G ports, and a 4.75 Tb/s peak (https://1-ix.eu/).

The Internet Society Pulse page for 1-IX EU reports 171 member ASNs, with 84 registered in Ukraine, 13 in Poland, 10 in the United States, 9 in Germany, 9 in the Netherlands, and smaller counts across multiple countries. It lists 64 Cable/DSL/ISP networks, 41 NSPs, 28 content networks and 8 enterprise networks, with 151 of 171 members peering at the route server and 154 using RPKI (https://pulse.internetsociety.org/en/ixp-tracker/ixp/1181/). This is not simply a local Ukrainian IX exported to Europe. It is a bridge between Ukrainian member demand and broader European interconnection.

The AS evidence supports that reading. RIPEstat WHOIS data identifies AS60812 as IXP-1-IX-UA with description "1-IX UA Internet Exchange", created 11 May 2023 and last modified 2 May 2024 (https://stat.ripe.net/data/whois/data.json?resource=AS60812). It identifies AS50263 as IXP-1-IX-EU with description "1-IX Internet Exchange", created 2 July 2021 and last modified 30 April 2024 (https://stat.ripe.net/data/whois/data.json?resource=AS50263). BGP.tools lists AS50263 as A-Systems Sp. z o.o., a carrier network registered in RIPE with upstreams including GTT, Euroline Ukraine, Lumen, Liberty Global and Euro Crypt, and shows 513 peers plus 153 downstreams in its observed model at the time of access (https://bgp.tools/as/50263). BGP.HE lists AS50263 with 20 Internet exchanges, 3,018 announced prefixes and 408 observed BGP peers (https://bgp.he.net/AS50263).

Those records should be treated as technical and market evidence, not as proof that the Ukrainian legal company owns every European resource. PeeringDB places 1-IX EU under A-Systems Sp. z o.o.; the Ukrainian directory subject is "1-IX" LLC. The relevant economic point is that the public 1-IX service set offers Ukrainian customers a platform path into foreign peering and transport. In practice, a Ukrainian network can compare a local 1-IX account plus European reach with a remote foreign IX port bought from a different exchange, a foreign carrier's transit product, or a direct cross-border transport route.

The 1-ix.eu page's wartime statement is unusually direct. It says that for the duration of the war in Ukraine, all funds of the project are invested in alternative data transmission channels to Ukraine, telecom equipment and remuneration of highly qualified network engineers maintaining links, communication nodes and equipment (https://1-ix.eu/). That is company language, not audited capital allocation. But it fits the thesis: the product is being sold as route locality and resilience, not only as cheap switching.

The European extension also changes the role of cloud and content. The 1-ix.eu site presents Microsoft Azure ExpressRoute and Google Cloud Connect links and lists Microsoft Azure access, Google cloud and AWS Direct Connect in its services table (https://1-ix.eu/). The 1-IX LinkedIn page described Azure ExpressRoute delivery for operators and ISPs, with pricing from 99 euro per month and corporate-customer use cases including enterprise, financial and public-sector procurement (https://pl.linkedin.com/company/1-ix-eu). That social post is a promotional signal, not contract evidence, but it shows how 1-IX tries to turn exchange membership into a broader B2B channel.

For the buyer, the comparison becomes sharper. A remote foreign IX port can be excellent for reaching global peers, but if Ukrainian traffic must be hauled abroad before meeting Ukrainian or regional networks, the buyer may lose locality. A local 1-IX port with European extension can be attractive if it keeps domestic traffic close and gives a controlled path outward. A private cross-connect may still win for one high-volume partner. A CDN cache may still win for one content class. Paid upstream transit may still win for simplicity. The European extension is valuable when it helps the buyer avoid choosing between local traffic and foreign resilience.

Routing control is part of the service

The economic case for 1-IX depends on more than ports and member names. It depends on whether the buyer gets enough routing control to make the account useful under stress. The peering policy sets baseline obligations: a registered AS number, at least one prefix, a complete and current PeeringDB profile, valid routing-policy entries and route-origin authorisation, correct next-hop, no leaking peering LANs outside the member router, and limits on unsuitable protocols such as STP, CDP, DHCP and several routing protocols on the exchange interface (https://1-ix.net/en/peering-policy-en/). Those requirements reduce the chance that one careless participant damages the shared switching environment.

The BGP traffic-engineering page shows how members can steer announcements. It lists traditional communities for the Ukrainian exchange, including not announcing a prefix to a certain peer, announcing to a specific peer, not advertising to any peer, announcing to all nodes, prepending one to three times, and blackholing traffic to a /32 with community 60812:666. It lists matching large-community controls and then repeats similar options for the international exchange (https://1-ix.net/1-ixknowhow/1-ix-bgp-traffic-engineering/). This is a real operating feature. Without traffic engineering, the buyer has less ability to tune cost, latency, congestion and attack response.

Blackholing and DDoS language are also commercially relevant. The 1-ix.eu page lists DDoS Protection, blackholing and Advanced Blackholing among technical information links (https://1-ix.eu/). The 1-IX LinkedIn page has recent public posts describing DDoS protection inside the carrier-grade network, discussion of large-scale DDoS attacks, sFlow and NetFlow telemetry, anomaly detection, advanced blackholing and attack mitigation around IXP fabric operations (https://pl.linkedin.com/company/1-ix-eu). Social posts are not service-level evidence, but they identify a market problem 1-IX wants buyers to associate with the account.

For a Ukrainian network, that matters because the exchange-port account is partly an insurance product. A buyer does not know in advance whether the next expensive incident will be upstream congestion, a route leak, an attack, power disruption, a fibre cut, a peer outage, a remote data-centre fault or a customer-growth spike. The value of route servers, BGP communities, blackhole signalling and support is that the buyer can react without rebuilding the whole interconnection plan.

There is a cost side to that control. More routing options require better staff discipline. A small ISP cannot simply connect and forget. It needs maintained PeeringDB records, routing filters, route-object hygiene, RPKI monitoring, session alerts, traffic graphs, peer-by-peer policy, and an understanding of what not to announce. The port may lower transit spend, but it can increase engineering responsibility. If the buyer lacks that capability, paid upstream transit remains attractive because it outsources much of the route-management burden.

The strongest evidence for 1-IX's routing credibility is not any one feature. It is the alignment between written policy, connection instructions, route-server adoption in Pulse data, and BGP records showing many peers. BGP.HE lists AS60812 with the 1-ix.net website, a looking glass at lg.1-ix.net, Ukraine as country of origin, one Internet exchange, 89 announced prefixes and 58 observed BGP peers at the time of access (https://bgp.he.net/AS60812). BGP.tools' AS60812 WHOIS-style policy output lists import and export relationships to networks including Netflix, UARNet, Datagroup, Infocom, Ukrtelecom, TENET, Hurricane Electric and others (https://bgp.tools/as/60812). These are technical records, not revenue proof. They still support the existence of a functioning route-policy surface.

The buyer should verify route control during the trial. Does traffic move as expected through route servers? Which important peers are open, selective or not reachable? Are blackhole communities accepted? Are support responses fast enough during route instability? Is the exchange's looking glass useful? Does the traffic mix justify the port after the first month? A route-locality account that cannot be observed and tuned becomes a faith purchase, and sophisticated network buyers do not renew faith purchases for long.

The cost stack reaches beyond the port fee

1-IX's service account has a visible price card, but the hidden cost stack decides margin for both sides. The customer pays for the exchange port, a cross-connect or transport path into the data centre, router interfaces, optics, rack power, maintenance windows, staff time and monitoring. The exchange operator pays for switches, optics, backhaul between PoPs, route servers, monitoring, data-centre fees, power resilience, network engineers, billing, sales, remote hands, replacement cycles and support coverage.

The connection guide makes the customer-side version concrete. It tells the customer to choose a facility based on 1-IX's PeeringDB presence, choose the physical speed, agree technical details, receive an LOA, order the cross from the data-centre operator, test physical levels and then enter commercial operation with monthly billing by the 25th day of the following month (https://1-ix.net/1-ixknowhow/instructions/). Those steps carry time and money even if the port fee looks low. A remote site that needs metro transport into the facility has a very different payback period from a router already in the same rack row.

The exchange-side cost is visible through 1-IX's published footprint and hiring language. The about page says the team has spent professional lives in telecommunications and lists network-engineering vacancies (https://1-ix.net/en/about-us-english-edition/). The 1-ix.eu wartime statement says funds go to alternative data transmission channels to Ukraine, telecom equipment and network engineers maintaining links, nodes and equipment (https://1-ix.eu/). The network-map page lists many connection points but withholds exact addresses during the war (https://1-ix.net/en/karta-merezhi-en-translation/). Together, those pages point to an operating model where engineering labour and distributed facility costs are central.

Power cost is the hardest public element to price. A shared switching fabric fails commercially if the ports are cheap but the site or transport loses power too often. Ukraine's wartime power stress has made that a core telecom input. The International Energy Agency's Ukraine energy-security report described extensive damage to power generation and the need to manage rolling blackouts and winter stress (https://www.iea.org/reports/ukraines-energy-security-and-the-coming-winter/executive-summary). RIPE Labs and Cloudflare both linked Ukrainian Internet instability to electricity attacks and outages, and the UN Human Rights Monitoring Mission reported that attacks on electricity infrastructure affected civilian life, including communications (https://ukraine.ohchr.org/en/Attacks-On-Ukraines-Electricity-Infrastructure).

For 1-IX, power resilience is not just a moral or national issue. It is an account-retention cost. Batteries, generators, fuel, remote-hands coordination and spare equipment all consume margin. If the exchange or its facilities can keep route servers and switching stable while other paths fail, it can justify price. If customers lose service because their own premises, the data centre or the backhaul path lacks power, they may blame the account even when the exchange fabric is not the root cause. The contract has to allocate that risk clearly.

The buyer also has to price the cost of not connecting. Paid upstream transit can look cheap if the route table is simple and demand is low. It can become expensive when video, cloud and gaming traffic grows. A private cross-connect can look efficient if one partner dominates traffic, but it leaves the buyer exposed to all other off-net traffic. A CDN cache can reduce content cost, but it does not create broad peer reach. A remote foreign IX port can deepen global liquidity, but it can add transport cost and latency for Ukrainian-to-Ukrainian traffic. Doing nothing until traffic grows can be prudent, but it can leave congestion and routing exposure unpriced until customers complain.

The cost paragraph leads to a practical conclusion: 1-IX is attractive when one account can replace several separate expenditures. If the port displaces enough paid transit, reduces support tickets, gives access to important content networks, provides a cleaner foreign path and adds attack or route-failure tools, the total cost can be lower than a transit-only model. If it merely adds a port while traffic still exits through the same upstreams, it becomes an extra bill.

Wartime resilience raises the proof standard

Ukraine has become a stress test for decentralised Internet operations. RIPE Labs' 2026 essay on Ukraine as a laboratory of Internet resilience argues that resilient networks are not only networks with good hardware; they are embedded in diverse markets, supported by local and international cooperation, separated from hostile dependencies and sustained by the people maintaining them (https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-internet-resilience/). That frame fits an exchange-port account. The product is part switch, part routing community, part trust network and part operations bench.

The war has also changed what buyers ask. A pre-war exchange sale might emphasise lower latency, reduced transit bills and access to content. A wartime exchange sale has to answer harder questions. What happens when power is cut in one city? What if a fibre route into the data centre is damaged? What if a member is under DDoS attack? What if a foreign transit path becomes congested? What if the customer's own technical team is unavailable? What if the safest public disclosure policy leaves the customer with less visible facility information before signing?

1-IX has several positive signals against that standard. It has Ukrainian and European connection points, route-server adoption, RPKI-related policy requirements, public BGP community controls, route-server and blackhole language, content and carrier members, and public statements about investing wartime funds in alternative data channels and engineers. Its legal and financial records show revenue growth and a small but real staff base. Its PeeringDB and Pulse records show enough member liquidity to matter.

It also has gaps. The public record does not show exchange uptime by city, route-server incident history, aggregate Ukrainian-only traffic during blackout periods, repair-time distribution, data-centre power autonomy, cross-border capacity utilisation, failover tests, member churn or paid customer concentration. The 1-ix.eu page shows 24-hour traffic figures and a 4.75 Tb/s peak, but those are platform figures, not audited Ukrainian route-locality results (https://1-ix.eu/). The 1-IX UA PeeringDB capacity snapshot is listed port capacity, not real traffic (https://www.peeringdb.com/ix/3562).

This boundary does not make the thesis weak. Wholesale interconnection businesses rarely disclose contract-level economics. It means the public case is strong enough for a buyer to run a trial and not strong enough to skip diligence. A serious buyer should ask for route-server uptime, maintenance communication samples, facility list under NDA if needed, escalation contacts, power backup details, cross-connect process, support availability, policy for route leaks, blackhole response, and expected peers for the buyer's own traffic mix.

The public social evidence should be handled the same way. 1-IX's LinkedIn page shows current messaging around DDoS protection, advanced blackholing, cyber resilience and participation in peering events (https://pl.linkedin.com/company/1-ix-eu). It also claims a OneTeraBitClub milestone and repeats CAIDA ASRank figures for AS50263 in a social update. Those posts show what the market is being told, not what contracts guarantee. They are useful because they reveal strategic emphasis: resilience, DDoS, cloud access, and international interconnection.

The final wartime point is that resilience can be local and foreign at the same time. A Ukrainian network may need a local exchange for domestic traffic and a foreign route for continuity. It may need content caches inside the country and backup reach outside it. It may need route diversity but also battery autonomy at its own sites. 1-IX's best case is not that it solves all wartime risk. It is that one account gives the buyer more routing and peering options while the buyer assembles the rest of the continuity stack.

Competition disciplines the account price

1-IX competes in a crowded and multi-layer market. At the narrowest level, it competes with other Ukrainian IXPs. Internet Society Pulse's Ukraine selector lists UA-IX, DTEL-IX, Giganet IXN, GNM-IX UA, LVIV-IX, Mesh.IX and other exchanges alongside 1-IX (https://pulse.internetsociety.org/en/ixp-tracker/ixp/114/). UA-IX itself has a larger Pulse member count than 1-IX UA. A buyer can connect to more than one exchange, but budget and router capacity still force prioritisation.

At the next level, 1-IX competes with paid upstream transit. Transit remains the default because it is simple: buy capacity, announce prefixes, receive full routes, and let the upstream carry traffic. It is not always cheapest per delivered bit, but it is operationally clean. 1-IX beats transit when enough traffic shifts to settlement-free or lower-cost exchange paths and when the buyer values route control. Transit beats 1-IX when volume is small, engineering capacity is weak, or the desired peers are not reachable through the fabric.

Remote foreign IX ports are a second major substitute. Warsaw, Frankfurt, Amsterdam and London offer deep content and carrier ecosystems. 1-IX itself sells European access, which makes this both a competitor and a complement. A Ukrainian network may decide that a direct port at a large foreign exchange plus leased transport is better than a local account. It may also decide that 1-IX gives a cheaper bridge into enough European liquidity while preserving Ukrainian locality. The decision turns on traffic geography and backhaul price, not on brand.

Private cross-connects are a third substitute. If the customer's traffic is dominated by one counterparty, a private interconnect can beat public peering. It can offer predictable capacity, direct accountability and reduced dependence on a route server. But it does not create broad discovery or many-to-many peering. 1-IX is stronger when the buyer's traffic is distributed across many networks, content providers and Ukrainian access peers.

CDN caches are a fourth substitute. If Google Global Cache, Netflix, Cloudflare, Apple Edge Cache or another content arrangement can remove a large share of traffic from paid transit, it may delay the need for a bigger IX port. But caches are content-specific. They do not solve routing to every Ukrainian ISP, carrier, enterprise or cloud path. 1-IX's member list includes content networks, which means the exchange account and cache strategy can reinforce each other rather than fully substitute for each other (https://1-ix.net/en/uchasnyky-en-translation/).

Doing nothing until traffic grows is the fifth and often most rational substitute. Wartime budgets are constrained. Engineering teams are busy. Customers may tolerate modest latency or transit cost if the alternative is another deployment project. A network manager may decide to wait for a clear traffic threshold before signing a new port. 1-IX has to make the cost of waiting concrete: higher transit spend, higher latency, fewer local failover paths, weaker DDoS options, poorer content reach or lost customer quality.

The competition story is therefore not "1-IX versus no peering". It is 1-IX against a stack of alternatives that can be combined. A sophisticated buyer might use paid upstream transit for default reachability, 1-IX for local and regional peering, a remote foreign IX port for global liquidity, a private cross-connect for one heavy partner, a CDN cache for video or cloud traffic, and a deliberate wait-and-see policy on additional capacity. 1-IX wins share of wallet when it becomes the account through which several of those needs can be managed.

What the public evidence proves and what it only implies

The public evidence proves that "1-IX" LLC is a Ukrainian legal company with telecom activity, a Kyiv registration, a Ukrainian electronic-communications-provider signal, and growing reported revenue. It proves that the 1-IX service publishes port and transport prices, connection instructions, peering policy, BGP communities and a network map. It proves that PeeringDB and Internet Society Pulse recognise 1-IX UA and 1-IX EU as exchange records with material member counts. It proves that content networks, carriers and Ukrainian access networks appear in the public member and PeeringDB ecosystem.

The evidence also proves that the company markets route locality, backup for uplinks, low-latency direct connections, flexible technical conditions, route control, 24/7 support language and wartime alternative data-channel investment. It shows that the European side of the 1-IX platform is large enough to be visible in BGP records, PeeringDB, Pulse and public social posts. It shows that 1-IX understands the current buyer anxieties around DDoS, cyber resilience, cloud access and wartime survivability.

The evidence only implies current customer economics. It does not prove that a typical Ukrainian ISP saves more on transit than it pays in port, cross-connect, transport and staff costs. It does not prove that every listed content network exchanges meaningful traffic with every buyer. It does not prove that the exchange fabric stayed available during major power disruptions. It does not prove that the Ukrainian legal company captures the economics of every European platform service. It does not prove that public tariff tables are the actual signed prices for large accounts.

The evidence only implies resilience. A distributed map implies route options, but not physical separation. A wartime statement implies investment intent, but not spare inventory. A route-server count implies easier peering, but not packet quality. RPKI use implies better routing hygiene, but not immunity from route leaks. BGP blackhole communities imply attack-response tools, but not the outcome of a live incident. Member names imply potential reach, but not traffic volumes.

The private metric that would most change the judgement is paid traffic conversion. How much customer traffic moves from paid transit to settlement-free or lower-cost peering after a 1-IX connection, and how stable is that shift over six months? The second metric is retention after incidents. Do customers renew after power cuts, DDoS events, fibre faults and route instability? The third is facility-level availability. Which cities and data centres kept switching and route-server service available during stress periods? The fourth is margin by service. Are port, L2, transit, cloud-access and support products covering power and labour costs?

The public evidence is therefore good enough for a conditional positive view and too incomplete for certainty. A buyer should enter a trial with a traffic baseline, a substitute cost model and explicit success criteria. If the port reduces paid transit, improves latency to important peers, gives workable route control, and avoids new support burdens, the account is valuable. If it becomes another underused interface, the buyer should stop.

Watchpoints for 1-IX's market position

The first watchpoint is member quality. The raw count matters less than the members a Ukrainian buyer can actually use. Additions by Ukrainian regional ISPs, national carriers, cloud platforms, CDN networks, banks, hosting providers and public-service networks would strengthen the account. Departures by major content or access networks would weaken it. Route-server participation and RPKI adoption should remain high because they protect the trust value of the shared fabric.

The second watchpoint is city-level usefulness. Kyiv can support a large exchange ecosystem, but the route-locality thesis depends on Ukrainian route locality beyond one capital facility. Evidence of active growth in Lviv, Odesa, Dnipro, Kharkiv and Uzhhorod would matter. So would clearer proof that the European handoff does not simply turn every route into a remote foreign path. The strongest outcome is a distributed fabric where local Ukrainian traffic stays local and European traffic exits efficiently.

The third watchpoint is power and transport resilience. Public data-centre counts are not enough. Customers need proof of backup power, route diversity, recovery procedures and escalation. If 1-IX can document uptime through blackout periods, its pricing power improves. If public incidents show repeated failures at key sites, buyers will shift to larger carriers, foreign ports, private cross-connects or delay.

The fourth watchpoint is product bundling. Peering alone can be price-competitive but limited. Peering plus L2 transport, IP transit, cloud connectivity, DDoS tools, remote hands and consulting can become a broader account. That helps revenue but can also blur the economics. A buyer should not pay for a broad bundle unless each piece replaces a real cost or risk.

The fifth watchpoint is governance and transparency. The current Ukrainian company is young. Its public records show growth, but not deep reserves. The European platform involves a separate Polish-associated entity in PeeringDB. This may be commercially normal, but customers with continuity requirements should understand contracting party, support responsibility, billing, facility agreements and liability. Ambiguity in the account structure can weaken trust even when the network works.

The final watchpoint is market discipline. Other Ukrainian IXPs, paid transit providers, foreign exchanges, CDN caches and private interconnect options keep 1-IX honest. If its prices rise faster than delivered traffic value, buyers can shift. If its member liquidity grows and support proves strong, the same competition can validate 1-IX: customers will choose it not because they lack alternatives, but because the account reduces the total cost of Ukrainian connectivity.

Final judgement

1-IX should be understood as a route-locality and peering-account business, not as a generic regional ISP. Its value is created when a Ukrainian network can use one account to bring more traffic into local or regionally efficient paths, reduce paid upstream transit exposure, reach useful content and access networks, control BGP announcements, and preserve foreign optionality during wartime uncertainty.

The public evidence supports taking that thesis seriously. The company has a visible Ukrainian legal identity, telecom-provider signals, growing reported revenue, published port prices, connection instructions, peering-policy controls, traffic-engineering communities, a distributed Ukrainian and European service map, more than 150 claimed participants, PeeringDB and Pulse records, route-server adoption, RPKI evidence and social-market messaging around resilience, DDoS and cloud access. Those are the right kinds of evidence for an exchange-port account.

The thesis remains conditional because the most important operating and financial proofs are not public. We cannot see Ukrainian city-by-city traffic, paid port revenue, customer retention, facility uptime, power autonomy, margin by product, private discounting, repair capacity or the real traffic exchanged with each marquee member. We can see the ingredients of a useful local exchange account. We cannot see every outcome.

The procurement comparison returns to the substitutes. 1-IX is attractive when its local port and European extension are cheaper and more controllable than relying only on paid upstream transit, lower-latency for Ukrainian traffic than a remote foreign IX port, broader than a private cross-connect, more general than a CDN cache, and more valuable than doing nothing until traffic grows. It is less attractive when the buyer has too little traffic, lacks BGP operations capacity, needs only one content cache, can get better economics at another Ukrainian exchange, or must first spend scarce budget on premises power and access redundancy.

The most defensible judgement is positive but bounded. 1-IX matters if it converts Ukrainian member liquidity, route-server convenience, published port economics and Europe-facing reach into a lower-cost, lower-latency and more controllable routing account for networks operating under wartime uncertainty. The company has enough public proof to justify buyer diligence and a measured trial. The facts that would change the view are not branding facts; they are traffic conversion, uptime, power, retention and route-separation facts.