Arelion’s AS1299: Tier-1 reach still needs constant renewal

Summary

• Arelion is the private carrier formerly called Telia Carrier; Twelve99 remains a technical and legacy identity, while AS1299 is its global routing identity.
• AS1299 reaches the full Internet through customer routes and settlement-free peers, but Tier-1 status does not guarantee shortest paths, superior support or immunity from incidents.
• IP transit and dedicated Internet access sit beside Ethernet, wavelengths, managed optical networks, cloud and exchange connectivity, DDoS mitigation, mobile, voice and AI Direct.
• Accumulated routes, fibre, points of presence, peers and operating knowledge create advantage; continuous spending on capacity, security and expansion remains the burden, without standalone public finances.

Four names describe four different layers

The business began inside the Telia group and operated for years as Telia International Carrier and later Telia Carrier. Polhem Infra completed its acquisition of Telia Carrier on 1 June 2021, transferring control out of Telia Company. The carrier adopted the Arelion name in January 2022. These dates divide corporate history: references to Telia ownership are accurate before the completion and inaccurate when used as a description of the current company.

Twelve99 did not disappear with the rebrand. The name remains visible in the technical domain twelve99.net, including the public looking glass, and continues to be associated with AS1299. That persistence is useful to engineers because autonomous-system numbers, hostnames, route filters, customer configurations and operational references often need more stability than a corporate brand. It does not create a second company. Twelve99 is technical continuity; Arelion is the current commercial and corporate identity.

AS1299 is another layer again. It is the autonomous-system identity through which the backbone originates, receives, selects and advertises routes. An ASN is neither a legal person nor a physical cable. It names a routing domain whose policy is expressed across routers, points of presence and interconnections. Arelion operates that domain, while the underlying paths may use infrastructure under different ownership and contractual arrangements.

The four-part distinction—former brand, current company, technical hostname and routing system—prevents several common errors. It stops historical continuity from becoming a false ownership claim; it stops a technical identifier from being treated as a subsidiary; and it forces network-scale statements to be attributed to the company that publishes them. It also exposes the central theme of Arelion’s history: corporate control changed faster than the backbone’s operational identity.

A Tier-1 network is a relationship, not a medal

The phrase “Tier-1 backbone” compresses several facts into one label. At the routing layer, a Tier-1 autonomous system can reach the full Internet through routes learned from customers and through settlement-free peering with other large networks. It does not need to purchase an upstream transit service for general global reach. That position matters because it removes one class of supplier dependence and lets the network sell full-route transit to others.

It is also maintained rather than granted: peers can change policy, traffic can move, and the carrier must keep enough capacity and direct relationships for settlement-free exchange to remain mutually acceptable.

Nothing in that definition certifies latency, support quality, DDoS performance, enterprise access or financial strength. BGP chooses paths according to policy and attributes, not a universal shortest-distance rule. A network can be Tier-1 and still depend on colocation operators, subsea systems, access carriers, router vendors, optical suppliers and customers whose traffic gives the network economic relevance. The label describes routing independence under a particular set of interconnection relationships. It should begin the analysis, not conclude it.

Arelion’s current profile makes the distinction unusually clear. The company’s commercial claim is not simply that AS1299 has global reach. It says that this reach can be converted into IP transit, private packet transport, optical services, cloud and exchange access, network-layer security and operational support. Buyers therefore encounter Tier-1 status through a service contract whose value depends on demarcation, geography, capacity, route policy and the ability to repair failures.

From a national incumbent lineage to an international carrier

Arelion dates the organic development of its backbone to 1993. The network grew within the Telia lineage, but its operating logic was international. A domestic telecom serves retail, mobile and enterprise customers inside a national market. An international carrier must connect other networks across borders, place routers in neutral facilities, acquire long-haul paths, maintain optical capacity and negotiate interconnection with organisations that may also be competitors.

That distinction helped Telia Carrier become separable from its former parent. By 2020, the carrier had customers and infrastructure relationships well beyond Telia’s national business. Telia Company agreed to sell it to Polhem Infra in October 2020; the acquisition completed the following June. The completed transaction, rather than the announcement, marks the transfer of control. Polhem Infra’s account also noted a continuing strategic network relationship with Telia, showing that corporate independence did not erase commercial interdependence.

The rebrand in 2022 gave the independent carrier a name not tied to its former parent. The underlying asset was not a newly assembled network. It was a mature backbone whose fibre routes, points of presence, customer links and peering relationships had accumulated over decades. This matters because connectedness cannot be reproduced simply by installing a software control plane. A new entrant can lease capacity and open ports quickly in selected markets, but it cannot instantly create the history of direct routes, operating trust and fault-recovery practice embedded in a long-running global network.

Independence also altered the investment question. Inside Telia, the carrier competed for capital within a diversified telecom group. Under Polhem Infra, it became a focused infrastructure holding backed by Swedish pension capital. That structure can favour long-duration investment, but it does not remove return targets or make capital unlimited. It changes who decides, how the asset is framed and what evidence outsiders can see.

The backbone is a chain of control, not one homogeneous asset

Arelion reports more than 80,000 kilometres of its own fibre, more than 350 points of presence and service in 129 countries. It also reports more than 2,000 customers and roughly 450 access partners. These figures describe different layers and should remain company-attributed. Fibre kilometres concern physical reach; PoPs concern interconnection and service locations; countries describe commercial service availability; access partners extend delivery beyond direct facilities. Adding the figures together would produce no meaningful measure.

The service chain can include Arelion-owned fibre, optical systems placed on those routes, router and switching equipment, colocation space and power, cross-connects to customers and peers, capacity on subsea systems, cloud on-ramps and local access circuits provided by other carriers. Arelion can control the service and route policy while sharing some physical failure domains with suppliers and facilities. “Global backbone” describes an operational system assembled through several forms of control, not proof that one company owns every trench, cable, landing station and building used by every delivered service.

This distinction is operational rather than semantic. Two logical routes can appear diverse on a network diagram while crossing the same conduit or submarine cable. Two services can be sold separately while sharing a router, optical line system or facility power feed. Conversely, leased or partner infrastructure can be highly resilient when the contract, monitoring and physical diversity are well designed. Ownership alone does not answer the reliability question; the relevant evidence is the failure boundary and the provider’s ability to observe and restore it.

Arelion’s commercial platform therefore begins with control of a chain. It must know which segment belongs to its own backbone, which depends on a facility, which is supplied by an access partner, which endpoint is controlled by a cloud provider and where the contractual SLA changes. A customer sees one order and support relationship, but the underlying incident may cross several organisations. The carrier’s value lies partly in making that chain manageable without pretending it is singular.

Fibre supplies path; optics supply usable capacity

Fibre length is a geographic measure, not a capacity number. A strand can carry different numbers of wavelengths, and each wavelength can be upgraded through new coherent optics and line systems. The same physical route can therefore support much more traffic after an equipment refresh without a new trench. Arelion’s continuing 400G and higher-capacity programme belongs to this optical layer, where transponders, coherent pluggables, amplifiers and spectrum engineering turn glass into active transport.

Wavelength service gives a customer a dedicated optical channel across a qualified route. It is suited to predictable, high-volume movement such as data-centre interconnection, replication or carrier aggregation. The customer receives a service with a clearer capacity boundary than public IP transit, although the wavelength still depends on physical fibre, optical equipment and route protection. The word “dedicated” refers to the channel; it should not be expanded into a claim that the customer owns a physically isolated cable.

Arelion also sells optical fibre and a Managed Optical Fiber Network. The managed offer shifts more design, equipment and operational responsibility to the carrier. For a large enterprise, cloud operator or service provider, that can avoid building an optical engineering organisation for every route. The trade-off is dependence on Arelion’s supported geography, supplier choices, restoration process and lifecycle decisions.

Optical services also reveal why the carrier cannot treat an old backbone as a finished asset. Traffic grows, interfaces move to higher rates, and customers expect new paths to clouds and data centres. Each upgrade consumes capital before demand is certain. Underbuild can create congestion and weak service; overbuild can strand optics, ports and contractual commitments. The financial discipline of a carrier is therefore hidden inside capacity planning long before a customer notices a speed change.

Points of presence turn long-haul capacity into a market

A point of presence is where backbone capacity becomes available for interconnection. It may contain routers, optical systems, switches, customer ports and cross-connects inside a data centre or carrier hotel. A dense PoP map can shorten the distance between Arelion and customers, peers, clouds and exchanges. It also creates operating exposure to facility power, cooling, building access and cross-connect processes.

Arelion’s reported total of more than 350 PoPs is a scale claim, not a statement that every product and port speed is present at every site. A location may support IP transit but not a particular wavelength route; Ethernet at 400 Gb/s requires technical validation; a cloud connection depends on the provider’s on-ramp; and a remote enterprise site may need a partner tail. A useful procurement question is therefore “Which service is available at this demarcation?” rather than “Is Arelion in this country?”

PoP density also affects connectedness. Direct interconnection reduces the number of intermediate networks a route may cross, and more direct customers and peers can improve path choice. Arelion says 95% of end users in the United States and European Union are within one network hop of AS1299 and describes AS1299 as the world’s most connected backbone by its selected metric. Those statements should stay attributed because the result depends on dataset, definition and date. One-hop reach is not the same as lowest latency for every flow, and connectedness is not traffic market share.

The packet layer carries several products over shared infrastructure

Above the optical layer, routers and packet systems turn capacity into routable and private services. AS1299’s BGP control plane exchanges Internet routes. MPLS and segment-routing functions support traffic engineering and private packet transport. Ethernet services present Layer 2 connectivity; Smart IP-VPN presents a managed routed WAN; Cloud Connect and IX Connect extend those paths into specific ecosystems. These products share parts of the underlay while exposing different service boundaries.

Arelion’s Ethernet portfolio includes point-to-point EVPL and multipoint ELAN arrangements at rates from 10 Mb/s to 400 Gb/s, subject to route and technical availability. The carrier’s documentation describes segment-routing and Flex-Algo mechanisms for selected low-latency paths inside its MPLS backbone. Such controls can improve determinism within the provider domain, but they do not erase an access tail or external endpoint that lies outside Arelion’s full control.

The service-level figures make this boundary visible. Arelion publishes a 99.999% availability claim for MPLS backbone services, 99.99% for basic PoP-to-PoP Ethernet and 99.5% for an end-to-end service that includes a managed network-interface device and access tail. The numbers are not interchangeable. The lower commitment for the wider service reflects additional equipment and third-party dependencies. Actual terms remain contract- and route-specific.

A customer can also place multiple services over one port through logical separation. That can reduce cross-connect and interface cost. It concentrates those services on one physical failure domain, however. A port failure can affect several logically distinct circuits at once. Efficient multiplexing and concentrated risk belong in the same explanation.

IP transit is the defining commercial expression of Tier-1 status

An IP-transit customer normally operates an autonomous system, announces prefixes through BGP and receives routes to the Internet from Arelion. The carrier carries outbound traffic toward other networks and returns traffic toward the customer prefixes. The product is priced and contracted as reach, capacity and service, while the underlying value comes from AS1299’s customer and peer relationships.

The transaction sounds simple because BGP hides the physical path behind route advertisements. In operation, Arelion must maintain full routing tables, filter invalid or unauthorised announcements, balance traffic across links, provision capacity, protect sessions, manage communities and recover from failures across many PoPs. A customer that multi-homes to another carrier gains redundancy and path choice, but also acquires a more complicated routing problem. It must understand preferences, inbound traffic engineering and how failures propagate through each provider.

Tier-1 economics do not mean every interconnection is free. Settlement-free peering removes payments for a defined exchange with qualifying networks. Arelion still pays for fibre, facilities, equipment, power, access, labour, maintenance and other commercial relationships. It may also buy local services or partner access where that is more efficient than building directly. The absence of upstream transit expense is one element of the cost structure, not a zero-cost network.

The carrier’s route position must also be preserved. If traffic balance, geographic reach or commercial policy changes materially, a peer may seek different terms or end a relationship. The practical moat is therefore accumulated and continuously defended. The network needs enough customers, direct reach, capacity and operational credibility for other large backbones to keep exchanging traffic on settlement-free terms.

Dedicated Internet access shifts more routing responsibility to the provider

Dedicated Internet access serves enterprises that want managed connectivity without operating a full BGP relationship and global route table. The customer may receive a default route or a managed edge, while Arelion takes more responsibility for the Internet-facing design. The physical access and service quality may resemble transit in some locations, but the operational contract is different.

The distinction matters during failure and change. A transit customer can use its own ASN, prefixes, communities and multi-homing policy. A DIA customer often has less control and depends more heavily on the provider’s routing and edge support. Neither model is intrinsically superior. Transit suits organisations with routing expertise and a need for policy control; DIA suits buyers that prefer a managed demarcation.

SecureConnect combines Internet access or transit with automated DDoS protection. This packaging reduces procurement and configuration boundaries for customers that would otherwise contract transport and mitigation separately. The protection still has a defined scope. It does not secure credentials, endpoints, application logic or attacks that fall outside the selected network-layer service.

BGP communities make route policy part of the product

BGP communities are tags attached to route advertisements. Arelion can interpret a customer’s tags and apply provider-defined actions such as changing preference, limiting propagation, prepending AS paths or triggering blackholing. They give the customer influence over the provider network without direct access to its routers.

This is a powerful form of delegated control. An operator can make one prefix less attractive in a region, limit where it is advertised or sacrifice reachability to protect the rest of the network during an attack. The semantics are specific to AS1299; a community value used by another carrier may mean something else. Customers need current documentation, controlled changes and a way to verify the outcome through routing tools.

Communities also carry failure risk. A misplaced tag can withdraw reachability or send traffic over an unintended path. A remote-triggered black hole deliberately discards traffic to a destination so that an attack does not congest wider links. That action is useful in an emergency because it trades the availability of one target for the stability of the network. It is not mitigation without cost.

Looking glasses expose a slice of routing reality

Arelion’s Twelve99 looking glass lets users inspect routes, pings and traceroutes from selected network locations. The tool can answer practical questions: how does AS1299 see a prefix, which path is selected from a given vantage point, and where does latency appear along that view? It also preserves the Twelve99 name as a technical identity after the corporate rebrand.

A looking glass is evidence from a vantage point, not an audit of the entire network. It does not show every alternative path, historical incident, internal preference or physical fibre route. BGP policy can differ by location, and a traceroute may hide devices or respond differently under load. The tool is most valuable when combined with customer measurements, route collectors, service tickets and provider performance data.

Arelion also publishes monthly IP-network performance metrics. Those reports can help buyers track provider-selected measures over time, but the methodology and scope remain the company’s. Transparency improves when a provider exposes operational data; independent assurance still requires clear definitions and external observation.

RPKI reduces one routing risk without repairing BGP as a whole

Route Origin Authorisation allows a prefix holder to state which autonomous system may originate the route. Route-origin validation can then classify an announcement as valid, invalid or not found. Filtering invalid origins reduces some hijacks and configuration mistakes. Arelion’s educational material presents RPKI as one part of routing security.

The mechanism verifies origin authority for covered prefixes. It does not validate the complete AS path, guarantee that a peer exports routes correctly or prevent every route leak. A valid origin can still be propagated through an unintended path, and operational mistakes can occur in filters, route objects or customer configuration. RPKI narrows the trust problem; it does not replace BGP policy, monitoring and incident response.

For a Tier-1 carrier, this boundary is important because route security and route availability can conflict. Aggressive filtering can block legitimate traffic when records are wrong; weak filtering can spread invalid announcements. The operator needs staged policy, customer communication, exception handling and current data. Public statements that “RPKI secures BGP” hide the operational judgement that remains.

IX Connect sells access to interconnection rather than full Internet reach

Internet exchanges provide venues where networks can establish peering. Arelion’s IX Connect carries a customer from an eligible Arelion location to an exchange port, allowing remote participation without building a separate local network presence. The product can reduce the cost and lead time of reaching several peers, especially for a network expanding into a new market.

The transport does not create peering policy. The customer still needs exchange participation where required, compatible ports, bilateral or route-server arrangements and its own route filters. A remote path can also introduce another dependency compared with a router physically placed at the exchange. IX Connect is therefore an access service to a market of routes, not a substitute for the customer’s interconnection strategy.

This product shows why a Tier-1 carrier competes and cooperates with exchanges at the same time. Arelion peers at exchange venues while selling transport to them. A customer may replace some paid transit with direct peering, yet still buy Arelion capacity to reach the exchange or cover the rest of the Internet. The boundaries among transit, peering and transport are commercial choices built on the same physical network.

Cloud Connect brings the backbone to a provider-controlled demarcation

Arelion lists private connectivity to AWS, Microsoft Azure, Google Cloud, Oracle and IBM. Cloud Connect transports customer traffic to supported cloud on-ramps, reducing dependence on public-Internet paths for that segment. This can provide more predictable routing, capacity and security than sending all cloud traffic through general Internet transit.

The service ends at a shared boundary. The cloud provider controls its virtual interface, regional availability, quotas and internal network. The customer controls its account, routes and workloads. Arelion controls the carrier path it sells. A fault can sit on any side, and the parties need aligned configuration. Calling the whole route “private” can be misleading if it suggests that one provider owns every component or that no shared infrastructure exists.

Cloud connectivity also changes the carrier’s competitive position. Hyperscalers operate large private backbones and increasingly carry traffic between their own regions. Arelion’s opportunity lies in joining enterprises, data centres, multiple clouds and networks that do not share one administrative domain. Its limitation is the same: it cannot dictate what happens inside a cloud or replace the cloud provider’s own fabric.

DDoS defence has become part of backbone capacity planning

Volumetric attacks consume links, router resources and scrubbing capacity. A global carrier sees enough traffic to detect shifts and can divert attacked flows before congestion reaches a customer access circuit. Arelion’s DDoS service combines detection, route steering and scrubbing, then returns permitted traffic toward the destination.

In its report published on 15 July 2026, Arelion said the Aisuru botnet accounted for roughly one-third of attack traffic observed in its dataset and that the largest attack reached 6.1 Tb/s. These are provider observations from Arelion’s network and methodology. They are useful because they show the attack scale visible to a major backbone; they are not a universal census of global DDoS activity.

The 6.1 Tb/s observation should not be converted into a guaranteed mitigation figure. An attack may be observed across the backbone without one customer receiving the full volume, and service commitments depend on architecture and contract. Effective mitigation also depends on detection time, BGP convergence, scrubbing placement, clean-path capacity and false-positive control. Application-layer attacks can pass through volumetric filters because the packets themselves appear legitimate.

Remote-triggered blackholing is the emergency edge of the design. A community can cause traffic to an attacked prefix to be discarded upstream. This protects shared capacity but makes the target unavailable. Scrubbing aims to preserve service; blackholing accepts an outage to contain damage. A mature DDoS product needs both mechanisms, clear triggers and customer authority over when the harsher response is used.

SecureConnect brings mitigation into the connectivity purchase rather than treating it as an optional system assembled later. That can improve adoption because protection is active before an incident. The strategic test is not the name of the bundle but the attach rate, response evidence, scope of protected services and ability to scale as attack peaks rise.

AI Direct packages wide-area transport for distributed AI systems

AI Direct is Arelion’s connectivity portfolio for data movement among AI clusters, data centres and clouds. It combines services already familiar to carriers—Ethernet, wavelengths, Internet access, managed optical networks and security—under an AI-infrastructure proposition. The suite does not provide GPUs, storage systems or model-training software. Its role begins where data must leave one facility or administrative domain.

That boundary is economically important. Training inside one campus depends on a local high-performance fabric whose latency and collective behaviour a wide-area carrier cannot replace. Wide-area demand appears when datasets, checkpoints, replicas, inference traffic or entire workloads move among facilities. Arelion’s advantage is reach across those locations; its service must connect to, rather than become, the internal AI fabric.

In May 2026 the company added 400G EVPL to AI Direct. The announcement established a high-capacity packet option on qualified routes, not universal 400G availability. Arelion had also announced Danish network and cable-landing-station upgrades in April, describing them as part of a Nordic AI corridor. Earlier additions included North American expansion such as an Oklahoma City PoP, while its 2026 channel programme in Mexico broadened distribution. These events show an active route and product strategy, although the company did not disclose activated utilisation, customer concentration or investment amounts for every project.

The strongest evidence that AI Direct is more than a label would be named high-capacity customers, activated ports, recurring traffic and route-specific service commitments. Announcements about an “AI superhighway” express strategic intent. They do not reveal how much revenue, utilisation or new capacity comes from AI workloads. Arelion’s current evidence supports a credible transport portfolio and a direction of investment; it does not support a claim that AI has already transformed the company’s economics.

Enterprise services monetise the backbone beyond transit

Transit prices tend to face long-term pressure as capacity improves and buyers gain alternatives. Arelion can respond by selling services that combine the same routes with more control, demarcation and support. Ethernet, Smart IP-VPN, Cloud Connect, IX Connect, managed optical networks and DDoS protection increase the number of problems the carrier can solve for one customer.

This portfolio does not mean every service has the same margin or buyer. A wholesale carrier may buy transit and wavelengths; a multinational enterprise may buy managed access and IP-VPN; a cloud operator may buy optical capacity; a regional ISP may buy transit and exchange access. The commercial organisation has to sell common infrastructure through different contracts and support models.

The broad offer also creates internal operating complexity. Capacity reserved for private services, public transit and mitigation must be planned together. A change in an optical path can affect several packet products. A local access delay can hold up an otherwise automated global order. Asset reuse improves economics only when service isolation, change control and capacity accounting remain accurate.

Arelion’s mobile-data, IoT, voice and messaging services widen the portfolio further. The research evidence is strongest for the backbone and connectivity products, so these adjacent services should be treated as part of the current catalogue rather than analysed with unsupported market-share claims. Their strategic relevance is that Arelion is not a pure IP-transit wholesaler even though AS1299 remains its defining technical identity.

Access partners extend reach while changing the SLA boundary

Arelion reports about 450 access partners. These carriers can connect a customer building to an Arelion PoP where the backbone has no direct local fibre. The model expands service coverage without requiring Arelion to build every last mile. It also gives customers one commercial relationship for a path assembled from several providers.

The access tail is often the least standardised part of the service. Lead time, repair process, available bandwidth, jumbo-frame support, demarcation equipment and local regulation can vary. Arelion may monitor and manage the tail, but the physical repair may belong to another carrier. The lower published availability for an end-to-end Ethernet service compared with PoP-to-PoP service captures this added exposure.

A global service footprint should therefore be read as the ability to deliver, not as a map of owned facilities. For enterprise buyers, the relevant diligence includes naming the local supplier, identifying route diversity, understanding escalation rights and checking whether a second access path shares the same conduit. A single global contract can simplify governance while leaving local physics unchanged.

Operations turn network assets into a service customers can use

A backbone is valuable only when it can be provisioned, observed and repaired. Arelion’s customer model includes the MyArelion portal, service management and network-operations support. These systems translate ports, routes, tickets, planned maintenance and performance into a customer experience.

Automation can shorten provisioning and expose status, but a global carrier cannot reduce every event to an API call. Fibre repairs require field teams; a cloud endpoint may reject a configuration; a peer may change policy; a colocation facility may need a cross-connect; and a local carrier may miss a delivery date. The quality of carrier automation includes how clearly it represents exceptions and responsibility, not only how quickly it accepts a normal order.

Arelion reports customer-experience recognition and a high net-promoter score. Those claims can indicate a deliberate service culture, but the methodology and response population are not independently audited in the supplied evidence. Awards and surveys belong alongside operational detail, not in place of it.

The business model reuses one infrastructure base through several demarcations

Arelion earns by selling access to capacity, routes, service assurance and operational responsibility. IP transit monetises global route reach. Ethernet and IP-VPN monetise private packet paths. Wavelengths and managed optical networks monetise optical capacity and engineering. Cloud and IX products monetise ecosystem access. DDoS services monetise visibility and protection. Each product begins at a different demarcation even when several share the same backbone.

This reuse can improve asset utilisation. A fibre route and PoP support more revenue when they serve multiple products and customer groups. The carrier still needs separation and headroom. If every service is planned against the same optimistic utilisation, an attack or traffic shift can expose hidden contention. Capacity accounting must distinguish booked ports, typical traffic, protected traffic and failure scenarios.

Commercial leverage comes from reducing coordination work for the customer. A multinational buyer could assemble local carriers, exchange ports, cloud links, transit, optical paths and security separately. Arelion offers to integrate more of that chain. The customer pays not only for bits but for fewer contracts, a defined support path and the ability to shift responsibility. The provider earns that premium only when the integrated service behaves better than the fragmented alternative.

Pension-backed ownership changes the time horizon, not the laws of economics

Polhem Infra owns Arelion. Polhem Infra’s current company description says it is jointly owned by Sweden’s Third AP Fund and Fourth AP Fund. Historical Polhem material from the 2021 Telia Carrier acquisition described the investment company as having been founded by AP1, AP3 and AP4; the current ownership description should therefore be used for the present-day profile rather than assuming the founding ownership structure remained unchanged.

Long-duration capital can tolerate investments whose payback spans several years, such as fibre rights, optical upgrades and new PoPs. It can also favour stable cash generation over short-term public-market signalling. The owner still has fiduciary and return requirements. Pension affiliation does not mean routes will be funded regardless of demand, and it does not disclose how much debt, operating cash or owner capital supports Arelion.

The governance change after 2021 was more visible than the technical change. AS1299 continued routing while board control, financing and strategic priorities moved from Telia to Polhem Infra. Daniel Kurgan became CEO in October 2023, and Charles Gill joined as CFO in March 2024. The current management page identifies a wider team across strategy, commercial, legal, people, technology and operations, although it is not a complete statutory board register.

Management cannot be credited personally with every architecture decision. The backbone is the accumulated work of engineering, operations, procurement, sales and partner teams over decades. Leadership sets capital allocation, risk tolerance, product direction and disclosure. The network’s day-to-day quality depends on distributed expertise and institutional memory.

Private ownership leaves the central financial questions unanswered

The supplied evidence does not establish current standalone revenue, profit, debt, capital expenditure, valuation, traffic volume, contract duration or customer concentration for Arelion. The absence is material because a global carrier must keep financing equipment, route rights, colocation, access and security capacity. Product announcements reveal activity; they do not reveal returns.

Historical transaction information would describe the 2020–2021 sale, not the company’s 2026 value. Carrying an old transaction figure forward would ignore changes in traffic, assets, capital structure and market conditions. Likewise, a connectedness ranking cannot serve as a proxy for revenue or margin. A network can be highly connected while operating in a market where price per bit falls.

This opacity changes how performance should be judged. Public routing data and looking glasses can show reachability and path behaviour. News releases can show route and product activity. Customer announcements can show selected deployments. None of those sources reveals whether capital is being deployed at an adequate return, whether one customer dominates revenue or whether leverage constrains the next upgrade.

The correct conclusion is limited: Arelion appears to be an active global carrier with a broad product portfolio and continuing investment. The supplied evidence cannot support a profitability estimate or claim that pension ownership guarantees the next capital cycle.

Renewal economics sit between physical ownership and contractual control

The investment problem is more complex than deciding whether Arelion should own or lease a particular path. A Tier-1 carrier has to preserve several forms of control at once. Fibre ownership provides direct authority over a physical route but still leaves dependencies on permits, power, repair teams, landing stations and equipment suppliers. Long-term fibre rights can approximate ownership for operational planning while fixing contractual obligations for years. Shorter-term capacity purchases preserve flexibility but can expose the carrier to repricing and supplier availability.

The correct structure depends on the route, the market and the consequence of failure.

This matters because network economics are shaped before a service is sold. Arelion may need to install line systems, router capacity, cross-connects and reserve headroom before a new customer commits traffic. Expansion into a new PoP can require facility contracts and equipment even when the commercial case depends on future demand. A high-capacity AI corridor can look compelling at the market level while individual customers remain uncertain about where their workloads will sit. Capital therefore arrives before some of the revenue evidence that is supposed to justify it.

The same timing problem applies to resilience. A backup route has value precisely when the primary route fails, which means part of its capacity may appear underutilised during normal operation. Finance teams can see idle headroom where operations teams see protection. The network has to decide how much apparently unused capacity is economically justified by the customer commitments and failure scenarios it protects. Too little reserve can turn one fibre cut or equipment failure into customer loss; too much reserve can depress returns if pricing does not recognise the reliability benefit.

Arelion’s broad portfolio makes the calculation more difficult because the same physical and packet infrastructure supports products with different demand patterns. Transit traffic can be bursty and price-sensitive. Ethernet and wavelengths can carry contracted high-capacity flows. DDoS mitigation needs capacity that may be lightly used until an attack. Cloud links depend on the location and growth of external platforms. A capacity planner cannot simply add average traffic and buy the result.

The carrier has to model correlated peaks, protection switching, maintenance windows and the possibility that one incident moves several services onto the same surviving path.

The 2026 expansion of AI Direct adds another layer of uncertainty. The company has a credible reason to position high-capacity Ethernet and optical services around distributed AI infrastructure because data movement between facilities is a genuine wide-area requirement. Yet AI demand does not remove the ordinary discipline of carrier investment. The route still has to connect actual facilities, the ports have to be activated, the customer has to pay for the capacity and the traffic has to persist long enough to justify the equipment and rights committed to it. A fashionable workload does not change the accounting of unused capacity.

Supplier strategy also affects the renewal cycle. Router and optical platforms are not infinitely interchangeable. A major upgrade can create years of operational familiarity, spare-parts planning, software dependencies and vendor support. Open line systems and coherent pluggables can reduce some lock-in by separating elements of the optical stack, but interoperability still has to be engineered and tested. The carrier gains optionality only when it maintains the skills and operational processes needed to exercise it.

Facilities create a similar form of embedded commitment. A PoP becomes more valuable as customers, peers and clouds connect to it, but that density also makes moving the PoP harder. Cross-connects, customer equipment, maintenance procedures and commercial relationships accumulate around the location. A facility can therefore gain bargaining power over a carrier even when the carrier owns the routers inside it. The practical question is whether Arelion has enough alternative sites, route diversity and commercial leverage to prevent one building or supplier from becoming a hidden strategic constraint.

This is why private financial opacity matters to an infrastructure profile. Without current capex, debt, lease commitments and cash flow, outsiders cannot see whether network renewal is being funded from operating cash, owner capital or borrowing, nor how much flexibility remains for the next hardware cycle. Technical announcements show that spending is occurring. They do not show whether the company can sustain the same pace through weaker pricing, a demand slowdown or a larger-than-expected resilience requirement.

The strongest external evidence is therefore cumulative. New routes that are completed rather than only announced, new PoPs that attract customers, modern interfaces that become orderable, direct routes that remain stable, and security systems that absorb larger attack peaks all indicate an owner continuing to fund the network. None proves profitability alone. Together they show whether capital is being converted into an operating system that preserves the economic relevance of AS1299.

For Arelion, the renewal obligation is inseparable from the moat. The company’s advantage comes partly from a network position accumulated over three decades. That position saves customers the work of assembling the same reach themselves. It also creates a large installed base that must be refreshed continuously. The more valuable AS1299 becomes as a neutral global path, the more damaging deferred investment would be. Tier-1 status therefore creates both bargaining power and a permanent capital obligation.

Geography is a service map, a route map and a dependency map

Arelion’s roots and ownership base are Nordic, while its backbone spans Europe, North America and Asia. The company reports service in 129 countries. That figure is commercial reach, not a count of owned fibre systems or direct PoPs. A buyer needs three maps: where Arelion has backbone and facilities, where it can deliver through partners, and where a particular service is technically available.

Europe remains a dense part of the network lineage. North America is a major transit and enterprise market, and recent additions such as Oklahoma City were positioned around cloud and AI data-centre demand. Arelion’s 2026 Danish investment concerned routes and a cable-landing-station environment important to Nordic and subsea connectivity. In Mexico, route development and a channel programme broadened access to a growth market. The supplied evidence provides less route-level public detail for Asia than for Europe and North America.

Subsea connectivity deserves separate treatment. Arelion can buy spectrum or capacity, install equipment at landing stations and operate an end-to-end service without owning an entire submarine system. Cable faults, landing-station incidents and shared terrestrial backhaul can affect multiple carriers. Logical route diversity must therefore be tested against cable and conduit diversity.

Geopolitics can also reshape route economics. Cross-border regulation, sanctions, permitting, cable security and national-resilience policy influence where carriers can build and how customers assess risk. The supplied evidence does not establish a specific current dispute involving Arelion, so these factors belong as structural constraints rather than allegations.

Competition occurs at several layers at once

At the Tier-1 and global-transit layer, Arelion competes with networks such as NTT, Lumen’s Level 3 lineage, GTT, Tata Communications, Cogent and Sparkle. Direct comparison requires dated evidence for route relationships, geography, latency, capacity, security, support and price. A single connectedness ranking cannot settle the choice.

At the physical and optical layer, firms such as Zayo compete for fibre and wavelength demand. At the cloud-connectivity layer, Megaport and Equinix Fabric offer software-driven interconnection through partner and facility ecosystems. At the enterprise layer, regional carriers, SD-WAN providers and managed-service companies can assemble alternatives around Internet underlays. These are overlapping rather than identical categories.

Hyperscaler private backbones present a different challenge. A cloud provider can internalise traffic among its regions and combine transport with compute. Arelion remains useful where a customer needs connectivity among clouds, enterprises, data centres and networks outside one provider’s control. The more traffic stays inside hyperscaler domains, the smaller some wholesale opportunities become; the more workloads distribute across providers, the more valuable neutral wide-area reach becomes.

Internet exchanges can both complement and substitute for transit. A network with enough traffic can peer directly for major destinations and buy less transit. It still needs reach to the rest of the Internet, transport to exchange sites and operational support. Arelion’s IX Connect and transit products place it on both sides of that decision.

Arelion’s durable advantage is not that any one component is impossible to copy. Fibre can be leased, routers can be bought, cloud on-ramps can be joined and DDoS systems can be deployed. The combined system—routes, peer relationships, customer prefixes, PoPs, optical paths, support and reputation—takes years to build and continuous investment to keep relevant.

Connectedness creates resilience and contagion at the same time

A highly connected backbone offers more path options and direct reach. It can help traffic avoid intermediate networks and can absorb failures by shifting flows. The same position increases the number of downstream organisations exposed to its mistakes. A route leak, filter error or capacity incident can propagate beyond direct customers because other networks depend on routes learned through AS1299.

Physical concentration can create a similar dual effect. Dense PoPs improve interconnection, yet a facility outage can affect many services. A diverse logical topology may share one fibre conduit. A DDoS platform can protect customers, yet an error in diversion policy can move a large volume of legitimate traffic. Scale magnifies both capability and blast radius.

Resilience therefore depends on controls that are less visible than network maps: maintenance discipline, staged configuration, route filters, RPKI validation, community governance, optical protection, capacity reserves, scrubbing placement, out-of-band access, incident communications and tested rollback. Arelion’s public tools and product pages establish elements of this system, but the supplied evidence does not contain a complete incident history or independent audit.

Customers also have responsibilities. Multi-homing, prefix design, route policy, test plans and local access diversity determine how much of the provider’s resilience becomes effective at the customer edge. Buying from a Tier-1 does not remove the need for an architecture that can survive loss of that carrier.

Sustainability claims need denominator discipline

Backbone growth consumes equipment, power, colocation, construction and maintenance. New coherent optics can increase capacity per watt and per unit of rack space. That efficiency can coexist with higher total energy use if traffic and the network footprint expand faster. Arelion publishes a sustainability framework, but the supplied evidence does not provide a complete independently audited footprint for the full network and supply chain.

The responsible editorial treatment is to separate efficiency from absolute impact. A route upgrade may reduce energy per transported bit; a new route may increase total equipment and power. Leasing infrastructure also moves some emissions and energy use into suppliers rather than eliminating them. Without consistent scope, baseline and traffic data, broad claims of net environmental improvement would be unsupported.

Sustainability matters strategically because customers and pension-backed owners may ask for credible evidence on energy, procurement and resilience. It also matters operationally: denser optics, cooling and power availability affect where capacity can be deployed. The monitoring question is whether reporting becomes granular enough to connect network expansion with measured resource use.

What the public evidence cannot show

The network-scale figures in this profile are primarily Arelion’s own current claims. The supplied evidence does not contain an independent route-by-route audit of more than 80,000 kilometres, a uniform definition for every PoP or a complete inventory of owned versus partner-supplied infrastructure across every delivered service. It also does not contain a comparable traffic series across competitors.

The connectedness claim is metric-dependent. The one-hop statement describes Arelion’s reported reach in the United States and European Union, not a guarantee for every destination, protocol or moment. Monthly performance reporting is useful but provider-selected. A procurement decision still needs route-specific tests and contract terms.

Product availability is also conditional. Ethernet supports rates up to 400 Gb/s; that does not mean every site, tail or route can deliver 400G. AI Direct is a connectivity suite, not proof of AI customer revenue. A 6.1 Tb/s observed attack does not reveal contracted scrubbing capacity. MEF/Mplify certification supports service-definition confidence but does not certify every access tail or incident outcome.

The financial gap is wider. Current revenue, margin, debt, capex, valuation and customer concentration remain undisclosed in the supplied materials. That gap prevents a full economic model. It should remain visible rather than being filled with assumptions derived from route rank, customer count or owner identity.

Renewal is continuous even when the routing identity looks stable

AS1299 can appear remarkably stable from the outside. The autonomous-system number persists, familiar peers remain visible, the Twelve99 hostname still resolves operational continuity and customers continue to see a global route table. That stability is useful, but it can obscure how much change has to occur underneath it. A backbone can preserve the same public routing identity while replacing routers, optical platforms, line cards, software trains, power arrangements, fibre routes and facility connections. The product is continuity created through managed change.

Hardware generations create one renewal clock. Router capacity has to keep pace with larger interface speeds, route-table growth, telemetry and security functions. A chassis or line card that was adequate when 100G dominated may become a constraint as 400G ports and higher aggregate traffic become normal. The timing is not determined only by whether a device still forwards packets. Spares, vendor support, power density, software compatibility and the cost of keeping two generations in operation can make a technically functioning platform economically obsolete.

Optical systems create another clock. Coherent technology can increase the amount of usable capacity on an existing fibre pair, but the upgrade is not a universal software switch. Distance, fibre characteristics, spectrum, amplifiers, ROADMs, open-line-system design and operational certification determine what can be carried on a route. Arelion’s ability to advertise higher-capacity services therefore depends on route-by-route engineering, not only on the nominal capability of a transponder or pluggable optic.

Software adds a third clock. Routing platforms receive security patches, protocol changes, feature releases and operational fixes. A stable network may deliberately avoid the newest release until it is proven, but staying too long on an ageing train can increase support and security risk. Operators have to stage upgrades so that a software correction does not create a larger availability problem than the defect it fixes. For a Tier-1 backbone, the quality of change management is as important as the quality of the code itself because one policy or control-plane error can affect traffic far beyond a single customer.

Internet routing standards and operational practice create a fourth clock. RPKI adoption, filtering expectations, peering policies, BGP community conventions and routing-security practices evolve without changing the AS number. A network that was considered well operated a decade ago cannot assume that old controls remain sufficient. Customers and peers increasingly expect better validation, more transparent route policy and stronger response to leaks and hijacks. Maintaining trust therefore requires procedural renewal as well as capacity renewal.

Facilities create a slower but consequential renewal cycle. A PoP may remain in the same building while power density, cooling, cross-connect economics or the mix of peers around it changes. A carrier can discover that a historically important site is no longer the best place for new high-capacity equipment, while moving existing customer and peer connections would be expensive. New data-centre campuses can pull traffic away from traditional carrier hotels. The network must add reach to emerging hubs without weakening the dense interconnection that made older sites valuable.

Customer geography creates another source of movement. Enterprise applications migrate to cloud regions; content platforms add edge locations; AI clusters appear around power-rich data-centre markets; wholesale customers open new national networks. Arelion can retain the same number of PoPs and still become less relevant if those PoPs are no longer close to the demand that matters. Conversely, selective route additions can strengthen the value of the existing backbone without changing the overall public footprint dramatically.

Security capacity follows an especially uneven demand curve. Normal traffic can be planned around ordinary peaks, but DDoS systems have to withstand events that are rare by definition. The largest attacks observed in one year can become ordinary several years later as botnets, access speeds and attack techniques evolve. A carrier that sizes scrubbing only for average utilisation is underprepared; a carrier that builds unlimited unused capacity destroys economics.

The renewal problem is to maintain enough distributed headroom and diversion flexibility for plausible attacks while using the same infrastructure efficiently during normal conditions.

Access partners have their own lifecycle. A local carrier can improve, consolidate, change ownership, withdraw a product or become less competitive. A path that was the best enterprise access option three years ago may no longer be the best. Global service quality therefore depends on continuous supplier qualification and the ability to move new orders or, when practical, existing customers to better alternatives. Arelion’s partner count measures breadth; the renewal burden is deciding which relationships still deserve traffic.

Contracts can age even when infrastructure does not. Long-term capacity rights may have attractive economics when signed and become expensive relative to market prices later. Short agreements can preserve flexibility but expose the carrier to repricing. Facility, fibre and supplier contracts also contain renewal dates that may not align with customer terms. A network operator has to manage these contractual clocks alongside the physical ones so that a route does not become financially unattractive simply because several obligations renew at the wrong time.

People create a less visible renewal requirement. Global backbones depend on operational knowledge about route policy, optical characteristics, historic incidents, supplier behaviour and customer exceptions. Some of that knowledge can be encoded in inventory systems and automation; some remains institutional. Retirements, reorganisations and outsourcing can remove context that becomes important only during an unusual failure. A stable network therefore needs succession, documentation and training as surely as it needs spare optics.

Automation does not eliminate these clocks. It can improve inventory accuracy, accelerate configuration and expose dependencies, but it also increases the need for trustworthy data. A wrong facility identifier, stale route record or incorrect supplier demarcation can be propagated more quickly through an automated workflow than through a manual one. The more Arelion standardises provisioning and operations, the more important it becomes to validate the data model beneath the automation.

The commercial consequence is that renewal spending cannot be judged only by visible expansion. Replacing a line card before failure, adding spare capacity to an existing route, moving a customer away from a correlated path or upgrading a security platform may not add a new country or PoP. Those investments protect revenue already on the network. A private owner that evaluates only headline growth could underweight them; an operator that treats every protective upgrade as mandatory could overcapitalise the network.

The useful discipline is to connect each renewal decision to a failure mode, a capacity constraint, a customer commitment or a measurable operating improvement.

This makes the apparently simple question “Is AS1299 still Tier-1?” too narrow. The routing relationship can remain intact while other aspects of the service improve or deteriorate. A more complete test asks whether the network is keeping up with traffic growth, whether physical diversity remains genuine, whether peers and customers retain confidence, whether security capacity tracks the threat environment and whether capital arrives before technical debt becomes visible as outages.

Arelion’s long history is therefore both evidence and burden. More than three decades of operation show that the system has survived multiple hardware, traffic and ownership cycles. They also mean that the network contains decisions made under many generations of technology and demand. Renewal is the process of preserving what still creates value while replacing what no longer fits. The autonomous-system number can remain constant precisely because so much beneath it does not.

Buyers should validate the service boundary rather than the Tier-1 label

For a customer, the most useful diligence begins after confirming that AS1299 is a Tier-1 network. The next question is where Arelion’s direct control begins and ends for the service being purchased. A transit port at an Arelion PoP, a managed enterprise circuit delivered through a local partner, a wavelength across an Arelion fibre route and a Cloud Connect service all expose different failure domains. The same brand and backbone can sit behind materially different operational contracts.

The physical demarcation should be explicit. A customer needs to know whether the handoff is in an Arelion PoP, a third-party data centre, its own site or a partner facility. If the service includes a local access tail, the customer should know who owns that tail, where it enters the building and whether a second circuit truly uses a different physical route. Two circuit identifiers do not prove diversity. The relevant evidence is conduit, entrance, facility, power and upstream path separation.

The routing demarcation matters separately. A transit customer controls its own ASN and can use communities, preferences and multi-homing. A DIA customer delegates more of the edge policy. An Ethernet customer may receive a Layer 2 service whose internal routing is invisible. A Cloud Connect customer reaches a provider on-ramp where a second administrative domain begins. Procurement should record these differences because they determine who can act during a failure.

Capacity should be tested at the exact boundary purchased. A backbone may support 400G while a local port, exchange, cloud on-ramp or access carrier does not. A customer planning high-capacity AI or data-centre traffic should distinguish the core network’s capability from the orderable service at the two endpoints. Route qualification, port availability and protection options are more useful than a generic statement that the provider supports a particular speed.

Latency claims also require a route-specific definition. Arelion’s connectedness can reduce intermediaries, but the lowest-AS-hop path is not automatically the lowest-latency physical path. BGP policy, fibre distance, metro access and the location of the destination all matter. Customers with latency-sensitive applications should measure from relevant sites and understand whether the contracted service uses traffic engineering, protected paths or ordinary Internet routing.

Availability commitments need the same discipline. The difference between backbone, PoP-to-PoP and end-to-end service levels shows why one headline SLA is insufficient. A customer should ask which components are inside the commitment, how planned maintenance is treated, what exclusions apply, how measurement is performed and what remedy follows a breach. A high percentage can still allow a material outage if the measurement window and remedy do not match the application’s business cost.

DDoS procurement should separate detection, diversion, scrubbing and emergency blackholing. The carrier’s ability to observe multi-terabit attacks is useful evidence of network visibility, but the customer needs to know its own protection mode, activation policy, protected prefixes, clean-traffic return path and escalation process. It should also understand which attacks are outside the service, particularly application-layer events that require different controls.

Cloud connectivity needs a three-party operating model. Arelion can deliver the carrier path, the cloud provider controls its interface and internal fabric, and the customer controls its account and routing configuration. Troubleshooting works best when identifiers and contacts across those domains are recorded before an incident. A “private connection” is operationally valuable because it narrows the path and improves control; it does not collapse the three parties into one.

Partner-delivered access deserves special attention because it is where a global carrier’s consistency is most difficult to preserve. The buyer should ask whether Arelion monitors the local circuit, receives proactive alarms, controls the supplier escalation and can obtain route information. It should also know what happens when the local provider repeatedly misses repair targets. A global contract is most valuable when the prime carrier has enough data and commercial leverage to change the outcome, not merely to forward tickets.

Operational transparency should be evaluated before purchase, not only during an outage. Looking glasses, performance reports and the MyArelion portal provide useful views, but a customer should determine which metrics are available for its own service, how frequently they update and whether raw evidence can be exported. When performance becomes disputed, shared timestamps, route observations and incident records are more valuable than a generic service-status message.

Change control is another service boundary. Customers should know which changes they can make through a portal or BGP community, which require provider approval and which can be initiated by Arelion during maintenance or security response. Delegated control is useful only when the action, blast radius and rollback path are understood. This is particularly important when multiple logical services share one physical port.

A multi-homed customer should also test the failure case rather than assume redundancy from buying two providers. Route preferences can keep traffic on a failed or degraded path longer than expected; customer prefixes can be filtered incorrectly; inbound traffic can behave differently from outbound traffic. Regular failover exercises reveal whether the architecture actually uses AS1299 and the alternative carrier as intended.

The same principle applies to optical diversity. A protected wavelength may use two fibre paths, but buyers should confirm how those paths are defined and where they reconverge. A dual-link service with diverse endpoints can offer a stronger boundary than two channels that share a site. The application architecture may need to span data centres as well as network routes if a facility itself is a critical failure domain.

Contract renewal should revisit these assumptions. The service purchased three years earlier may now be delivered through a different access supplier, facility or network architecture. New clouds and data centres may offer better endpoints. A provider may have added direct routes that change the optimal design. Treating renewal as an administrative price negotiation misses the chance to update the resilience model.

For BTW readers, this diligence illustrates the practical meaning of Tier-1 status. AS1299 gives Arelion a powerful routing position, but customers buy services at specific demarcations. The value of the backbone is realised only when route policy, physical infrastructure, partner access, security and operations work together at those boundaries. The label reduces one type of dependency; it does not remove the need to understand the others.

The central judgement

Arelion shows what a Tier-1 carrier has become. AS1299’s settlement-free reach is still the defining network position, but the commercial product is a layered service platform. Fibre and optics provide path and capacity. PoPs provide market access. BGP, communities and route security provide policy. Ethernet, cloud, exchange and managed services create different demarcations. DDoS systems use backbone visibility as a security function. Operations and customer support turn all of these layers into something an enterprise or carrier can buy.

The moat is historical accumulation. Arelion inherited decades of routes, facilities, peer relationships and operating knowledge from the Telia Carrier lineage. Polhem Infra’s ownership gave that system a focused infrastructure investor and a new brand without replacing its technical identity. Twelve99 remains visible because the network has a memory longer than corporate marketing.

The same history creates an obligation. Tier-1 status does not freeze the network at the moment it is achieved. Traffic prices change, attack peaks grow, clouds internalise transport, AI creates new corridor demand, optics move to higher rates and customers expect more automation. Arelion has to renew the platform while protecting the routing trust that makes AS1299 valuable.

The evidence supports confidence that Arelion is active, globally relevant and technically broad. It does not support confidence about current profitability, leverage or the pace at which AI-related announcements become durable revenue. The most useful conclusion is therefore concrete: a Tier-1 today is a routing relationship wrapped in capital-intensive fibre, optical, packet, security and operational systems, and its quality is proved repeatedly at the service boundary rather than granted once by the label.

The indicators that will show whether the backbone is strengthening

Arelion’s next phase should be judged by conversions rather than slogans. The company already has a mature routing identity, global scale claims and a broad product catalogue. The unresolved questions are whether new routes become activated demand, whether higher-value services offset price pressure in transit, and whether resilience keeps pace with connectedness. The following indicators link technical activity to commercial and operational outcomes.

Peer and route stability

Tier-1 status depends on maintained settlement-free relationships. Material changes in AS1299’s visible adjacencies, path lengths or route propagation would be an early signal that interconnection economics had shifted. Looking-glass results and external BGP observations can reveal change, although they cannot explain the commercial terms behind it.

Activated capacity rather than announced capacity

New 400G products, optical upgrades and route announcements matter when ports are lit, traffic grows and customers commit. Monitor qualified 400G availability, completed Nordic and North American routes, new PoPs and named customer deployments. Announcement cadence without activation evidence would weaken the AI and capacity narrative.

Product mix beyond transit

Traffic volume can rise while price per bit falls. Evidence that SecureConnect, Cloud Connect, IX Connect, managed optical networks and Ethernet are attaching to existing accounts would indicate that Arelion is monetising integration rather than relying on commodity transit alone. The company does not currently disclose product-level revenue, so customer and service announcements are the available proxies.

Access-partner performance

Growth through roughly 450 access partners expands reach but can introduce variable delivery and repair. Monitor the difference between direct-PoP and end-to-end service outcomes, local-loop lead times, repeated regional incidents and whether Arelion discloses stronger partner qualification. The published SLA gap already shows that the last mile changes the risk profile.

DDoS scale and mitigation evidence

The 2026 report establishes the attack environment observed by Arelion. Future reports should be read for peak growth, botnet composition, mitigation time, customer impact and scrubbing distribution rather than one headline number. A larger observed attack is not itself proof of stronger protection.

Capital and governance signals

Private ownership limits direct financial analysis. Monitor leadership changes, completed route projects, hiring, supplier commitments, any disclosed financing and changes in Polhem Infra’s investment posture. Slower deployment or heavier partner reliance could reflect capital discipline, demand uncertainty or both.

Five evidence-supported scenarios

Wide-area AI demand becomes a durable growth engine

Neoclouds, enterprises and research users distribute data and workloads across facilities. Arelion activates 400G EVPL and wavelength services on named corridors, and AI Direct becomes a measurable source of traffic and customer expansion.

Traffic grows while economics tighten

AS1299 carries more bits, but transit prices fall faster than utilisation rises. Arelion remains technically important while returns depend increasingly on cloud, security, Ethernet and managed optical services.

Security convergence improves retention

Customers buy transit or DIA together with automated mitigation, giving SecureConnect a larger role in renewals and incident response. Success would be visible in attachment, customer references and evidence of preserved availability during large attacks.

Hyperscalers internalise more transport

Cloud providers carry more traffic inside private backbones and reduce some wholesale demand. Arelion retains relevance where enterprises need neutral multi-cloud and inter-data-centre paths, but corridor economics become more selective.

A correlated route, facility or capital shock exposes concentration

A peering change, fibre event, facility outage or delayed upgrade affects several services at once. The strategic consequence would depend on physical diversity, capacity reserves, incident transparency and the owner’s willingness to fund remediation.

Professional implications by stakeholder

Network operators should test route policy, community behaviour and multi-homing rather than treating Tier-1 status as redundancy. Enterprise buyers should map the direct and partner-served segments of every service. Cloud teams should define the boundary between Arelion and the provider on-ramp. Security teams should separate observed attack volume from contracted mitigation. Investors and owners should connect route expansion to utilisation and returns. Regulators and resilience planners should examine concentration at facilities, cables and autonomous systems without assuming that ownership is the only form of control.

Control, incentives and decisions that shape AS1299’s next decade

Arelion’s leadership problem is not choosing between “network” and “business.” The network is the business, and each technical choice fixes capital, supplier and customer obligations for years. The company’s control map is distributed: Polhem Infra controls ownership and investment; management allocates capital and sets product priorities; engineering and operations control route and capacity changes; peers determine settlement-free relationships; facilities and access partners control parts of the physical path; customers control prefixes, demand and multi-homing; cloud providers control the far side of on-ramps.

Strategy succeeds only when these authorities are aligned.

Decision one: fund physical diversity before marketing reach

Arelion should measure route diversity at cable, conduit, landing-station, facility and power levels, not only by logical topology. A new PoP or path can increase apparent reach while sharing a hidden failure domain with existing capacity. The irreversible risk is long-term commitment to infrastructure that cannot provide the resilience sold above it.

The leadership choice is to make physical-diversity evidence part of capital approval and customer design. That may increase cost or slow some launches. It also reduces the chance that several revenue products fail in one incident and protects the credibility of the global map. A carrier with mixed forms of physical control can still be trusted when it can demonstrate control of failure boundaries.

Decision two: preserve interconnection neutrality while monetising direct reach

AS1299’s moat depends on peers and customers continuing to view the network as a reliable exchange partner. Product growth must not distort route policy in ways that weaken that trust. Commercial pressure can encourage aggressive preferences, concentration on large accounts or insufficient investment in routes that appear less profitable but preserve topology.

Leadership should protect a clear separation between settlement-free peer policy, customer transit policy, security interventions and product traffic engineering. The second-order benefit is easier incident diagnosis and stronger counterpart confidence. The third-order risk of failure is loss of direct relationships that cannot be restored simply by buying more fibre.

Decision three: require activation proof for the AI portfolio

AI Direct gives Arelion a credible language for high-capacity inter-data-centre demand. It can also become a container for ordinary circuits relabelled without new economics. Management should govern the portfolio through route-level availability, activated ports, named use cases, utilisation, protection requirements and renewal behaviour.

This discipline prevents capital from following market enthusiasm without customer evidence. It also improves product design because training data, inference traffic, replication and cloud access have different latency and security requirements. The irreversible risk is overbuilding corridors or optical capacity whose demand depends on forecasts that do not materialise.

Decision four: turn security evidence into an operating feedback loop

The DDoS report gives Arelion a valuable view of attack traffic. Leadership should connect that publication to capacity planning, customer architecture, scrubbing placement, false-positive review and post-incident learning. Reporting peak volume alone rewards spectacle; reporting mechanisms and outcomes improves the service.

A stronger feedback loop would distinguish attacks observed, attacks mitigated, customer impact and the role of blackholing. This would help customers size risk and help the owner evaluate whether security capital is protecting revenue. The long-term consequence of weak evidence is commoditisation: SecureConnect becomes a label rather than a trusted operational capability.

Decision five: make partner reach governable

Access partners are necessary for global enterprise delivery, but responsibility can fragment across contracts. Arelion should treat partner selection, service inventory, incident data, diversity and exit rights as part of the product architecture. The customer should know which segments are direct, which are managed and which are merely coordinated.

The second-order effect of strong governance is a larger addressable market without equivalent owned build. The third-order effect of weak governance is that one local supplier degrades the reputation of the global backbone. Some failures will remain outside Arelion’s physical control; they need not remain outside its evidence and escalation control.

Decision six: disclose enough economics to sustain institutional trust

Private ownership gives Arelion flexibility but leaves customers, partners and infrastructure stakeholders unable to assess leverage, capex or customer concentration. Full public-company reporting is not required to improve trust. Management and the owner could disclose consistent operational investment, capacity activation, resilience and sustainability measures without revealing contract-sensitive detail.

Better disclosure would make route announcements more meaningful and reduce the temptation to treat connectedness as a proxy for financial health. It could also discipline internal capital allocation by tying strategy to comparable outcomes. The risk of continued opacity is that counterparties apply their own, often harsher assumptions during market stress.

Second-order effects of successful execution

If Arelion converts long-duration capital into physically diverse capacity, preserves peer trust and attaches higher-value services, AS1299 becomes more than a commodity transit path. It becomes a neutral wide-area platform for clouds, enterprises, carriers and distributed AI infrastructure. That position can improve customer retention, support better capacity forecasting and make security investment more economically defensible.

Success also affects the surrounding ecosystem. Access partners gain traffic and standards pressure; data centres gain interconnection value; cloud providers gain enterprise reach; exchanges gain remote participants; and customers gain an alternative to concentrating all transport inside a hyperscaler. The benefit is distributed, which is why no single participant controls the entire result.

Third-order effects of failure

A severe route-policy mistake or hidden physical concentration could damage more than one product. Customers may reroute traffic, peers may reassess trust, security services may lose credibility and the owner may face a larger capital requirement at the same time revenue is at risk. Highly connected infrastructure can transmit reputation loss as quickly as packets.

A prolonged capital constraint would have slower but durable effects. Delayed optics and PoP upgrades can lengthen paths, increase partner dependence and make the network less attractive to high-capacity customers. Once direct relationships and anchor accounts migrate, rebuilding them may require years.

Irreversible risks

The hardest risks to reverse are loss of settlement-free peer relationships, commitment to physically correlated routes, underinvestment through a hardware generation, dependence on one large customer segment, and a security incident that reveals weak operational control. Brand damage can be repaired; a lost route position or stranded long-term infrastructure contract may persist.

Leadership should therefore distinguish reversible product experiments from irreversible network commitments. A portal feature can be changed; a fibre right, landing-station dependency or optical architecture can bind the company for years. A pricing promotion can end; a peer relationship damaged by policy abuse may not return on demand.

The leadership judgement

Arelion’s strategic asset is neither the Arelion brand nor the Twelve99 hostname in isolation. It is the coordinated system behind AS1299: interconnection relationships, physical routes, optical capacity, packet policy, security, operations and the confidence of customers and peers. Polhem Infra and management inherit that system rather than starting with a blank sheet. Their task is to renew it without breaking the trust accumulated under its previous identity.

The decisive test is disciplined conversion. New routes must become diverse usable paths. New ports must become customer traffic. AI positioning must become activated services. DDoS visibility must become preserved availability. Partner reach must become governable delivery. Private capital must become timely upgrades without hiding risk. When those conversions hold, Tier-1 status remains economically meaningful. When they fail, the label survives longer than the advantage it once described.