Arelion’s AS1299: Tier-1 reach requires continuous renewal

Summary

• Arelion is the private carrier formerly called Telia Carrier; Twelve99 remains the technical and historical identity, AS1299 is the global routing identity.
• AS1299 reaches the entire Internet via customer routes and settlement-free peering, yet Tier-1 does not guarantee the shortest paths, better support or protection against disruptions.
• IP transit and dedicated Internet access sit alongside Ethernet, wavelengths, managed optical networks, cloud and exchange connectivity, DDoS mitigation, mobile, voice and AI Direct.
• Accumulated routes, fibre, PoPs, peers and operational knowledge create advantages; ongoing expenditure for capacity, security and expansion remains the burden, without published separate financials.

Four names describe four different layers

The business originated within the Telia group and for years operated as Telia International Carrier and later Telia Carrier. Polhem Infra completed the acquisition of Telia Carrier on 1 June 2021, taking control from Telia Company. In January 2022 the carrier adopted the name Arelion. These dates separate the corporate history: references to Telia ownership are correct before the transaction closed and incorrect as a description of the company today.

Twelve99 did not disappear with the rebranding. The name remains visible in the technical domain twelve99.net, including the public Looking Glass, and is still associated with AS1299. This persistence is useful for engineers because autonomous-system numbers, hostnames, route filters, customer configurations and operational references often need to be more stable than a company brand. It does not, however, create a second company. Twelve99 stands for technical continuity; Arelion is today's commercial and legal identity.

AS1299 is, in turn, another layer. It is the autonomous-system identity through which the backbone originates, receives, selects and propagates routes. An ASN is neither a legal entity nor a physical cable. It denotes a routing domain whose policy is expressed through routers, points of presence and interconnections. Arelion operates this domain, while the underlying paths may use fibre with different ownership and contractual arrangements.

The four-part distinction—former brand, current company, technical hostname and routing system—prevents several common mistakes. It prevents historical continuity from becoming a false ownership claim; it prevents a technical identifier from being treated as a subsidiary; and it forces statements about network size to be attributed to the company publishing them. At the same time it reveals the central theme of Arelion's story: legal control changed faster than the backbone's operational identity.

A Tier-1 network is a relationship, not an award

The phrase "Tier-1 backbone" condenses several facts into a label. At the routing level, a Tier-1 autonomous system can reach the entire Internet through customer-learned routes and settlement-free peering with other large networks. For general global reachability it does not need to buy upstream transit. This position matters because it removes one class of supplier dependency and allows the network to sell full-route transit to others.

It is also maintained, not permanently granted: peers can change their policy, traffic can shift, and the carrier must maintain sufficient capacity and direct relationships so that cost-neutral exchange remains acceptable to both sides.

Nothing in this definition certifies latency, support quality, DDoS performance, enterprise access or financial strength. BGP chooses paths by policy and attributes, not by a universal shortest-distance rule. A network can be Tier-1 and still depend on colocation operators, submarine systems, access carriers, router vendors, optics suppliers and customers whose traffic gives the network economic significance. The label describes routing independence within a particular set of interconnection relationships. It should open analysis, not close it.

Arelion's profile today makes this distinction especially clear. The company's commercial statement is not merely that AS1299 has global reach. It is 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 in a service contract whose value depends on demarcation, geography, capacity, routing policy and repair capability.

From national-incumbent origins to an international carrier

Arelion dates the organic development of its backbone to 1993. The network grew in the Telia line, yet its operational logic was international. A national telecommunications provider serves consumer, mobile and enterprise customers within a single country. An international carrier must connect other networks across borders, place routers in neutral facilities, acquire long-haul capacity, maintain optical capacity and negotiate interconnection with organisations that may also be competitors.

This distinction helped make Telia Carrier separable from its former parent. By 2020 the carrier had customer and infrastructure relationships far beyond Telia's domestic business. Telia Company agreed in October 2020 to sell to Polhem Infra; the acquisition closed the following June. The closing, not the announcement, marks the transfer of control. Polhem Infra also noted a continuing strategic network relationship with Telia. Legal independence thus did not remove commercial interdependence.

The 2022 rebranding gave the independent carrier a name unlinked to its former parent. The underlying asset was not a newly assembled network but a mature backbone whose fibre spans, PoPs, customer connections and peering relationships had grown over decades. This matters because interconnection cannot be reproduced merely by installing a software control plane. A new entrant can quickly lease capacity and open ports in selected markets, but cannot instantly create the history of direct routes, operational trust and troubleshooting practice of a long-operating global network.

Independence also changed the investment question. Inside Telia, the carrier competed for capital within a diversified telecommunications group. Under Polhem Infra it became a focused infrastructure investment backed by Swedish pension capital. This structure can favour long-term investment but neither removes return targets nor makes capital unlimited. It changes who decides, how the asset is classified and what evidence outsiders can see.

The backbone is a control chain, not a homogenous asset

Arelion claims more than 80,000 km of fibre, more than 350 points of presence and service in 129 countries. The company also cites more than 2,000 customers and around 450 access partners. These figures describe different layers and must remain attributed to the company. Fibre kilometres concern physical reach; PoPs concern interconnection and service locations; countries describe commercial availability; access partners extend delivery beyond direct locations. Adding the numbers together yields no meaningful measure.

The physical chain may include fibre that Arelion owns, controls long-term or leases as capacity; optical systems on those fibres; routers and switches; colocation space and power; cross-connects to customers and peers; capacity on submarine systems; cloud on-ramps; and local access circuits from other carriers. Arelion can control service and routing policy while sharing physical failure domains with suppliers. "Global backbone" describes an operating system assembled through multiple forms of control, not proof that one company owns every duct, cable and building.

This distinction is operational, not just semantic. Two logical paths can look diverse on a network map yet share the same duct or submarine cable. Two services can be sold separately yet share a router, an optical line system or a site's power feed. Conversely, leased infrastructure can be very robust if contract, monitoring and physical diversity are well designed. Ownership alone does not answer the reliability question; what matters is the failure boundary and the provider's ability to detect and recover from it.

Arelion's commercial platform therefore starts with control of a chain. The company must know which segment belongs to its own backbone, which depends on a facility, which is supplied by an access partner, which endpoint is under a cloud provider's control and where the contractual SLA changes. A customer sees one order and one support relationship, yet the underlying incident can cross several organisations. Part of the carrier's value lies in making this chain manageable without pretending it is uniform.

Fibre provides the path; optics provide usable capacity

Fibre length is a geographic measure, not a capacity number. One fibre can carry varying numbers of wavelengths, and each wavelength can be upgraded through new coherent optics and line systems. The same physical span can therefore carry much more traffic after an equipment swap without new trenching. Arelion's ongoing programme for 400G and higher capacities belongs to this optical layer, where transponders, coherent pluggables, amplifiers and spectrum planning turn glass into active transport.

A wavelength service gives the customer a dedicated optical channel over a qualified route. It suits predictable, high-volume data flows such as data-centre interconnects, replication or carrier aggregation. The customer obtains a service with a clearer capacity limit than with public IP transit, though the wavelength still depends on physical fibre, optical equipment and path protection. "Dedicated" refers to the channel and must not be extended to claim the customer owns a physically isolated cable.

Arelion also sells fibre and a Managed Optical Fiber Network. In the managed offering, the carrier takes more responsibility for design, equipment and operation. For a large enterprise, cloud operator or service provider, this can avoid building a separate optics-engineering organisation for every route. The trade-off is dependence on Arelion's supported geography, supplier selection, restoration procedures and lifecycle decisions.

Optical services also show why a carrier cannot treat an old backbone as a finished asset. Traffic grows, interfaces shift to higher rates, and customers expect new paths to clouds and data centres. Every upgrade ties up capital before demand is certain. Under-investment can create congestion and weak service; over-investment can leave optics, ports and contractual commitments idle. A carrier's financial discipline therefore lies in capacity planning long before a speed change becomes visible to customers.

Points of Presence turn long-haul capacity into a market

A point of presence is where backbone capacity becomes available for interconnection. It can 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 operational dependency on the site's power, cooling, building access and cross-connect processes.

The stated figure of more than 350 PoPs is a scale indicator, not a promise that every product and port speed is available at every location. A site may support IP transit but not a certain wavelength route; Ethernet at 400 Gb/s requires technical checking; a cloud connection depends on the provider's on-ramp; and a remote enterprise site may need partner access. The useful procurement question is therefore "Which service is available at this demarcation?" rather than "Is Arelion in this country?".

PoP density also influences interconnection. Direct interconnection reduces the number of intermediate networks a route may traverse, and more direct customers and peers can improve path selection. Arelion states it reaches 95% of end users in the United States and Europe within one network hop, and calls AS1299 the world's most connected backbone by the chosen measure. These claims must remain attributed because the result depends on dataset, definition and date. One hop does not mean the lowest latency for every flow, and connectedness is not traffic market share.

The packet layer carries multiple 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 capabilities support traffic engineering and private packet transport. Ethernet services provide Layer-2 connectivity; Smart IP-VPN offers a managed routed WAN; Cloud Connect and IX Connect extend these paths into specific ecosystems. The products share parts of the underlay but show the customer different service boundaries.

Arelion's Ethernet portfolio includes point-to-point EVPL and multipoint ELAN with rates from 10 Mb/s to 400 Gb/s, depending on route and technical availability. Documentation describes Segment Routing and Flex-Algo for selected low-latency paths in the MPLS backbone. Such controls can improve predictability within the provider domain but neither remove an access tail nor an external endpoint outside Arelion's full control.

The service-level figures make this boundary visible. Arelion publishes an availability statement of 99.999% for MPLS backbone services, 99.99% for simple PoP-to-PoP Ethernet and 99.5% for an end-to-end service including managed Network Interface Device and access tail. The values are not interchangeable. The lower commitment for the more comprehensive service reflects additional equipment and third-party dependencies. Actual terms remain contract- and route-specific.

A customer can also use logical separation to run several services over a single port. This can reduce cross-connect and interface costs. It concentrates those services, however, on one physical failure domain. A port failure can hit several logically separate circuits simultaneously. 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 typically operates an autonomous system, announces prefixes via BGP and receives routes from Arelion to the Internet. The carrier carries outbound traffic to other networks and inbound traffic to the customer's prefixes. The product is priced and contracted as reach, capacity and service; the underlying value comes from AS1299's customer and peering relationships.

The transaction looks simple because BGP hides the physical path behind route announcements. In operation, Arelion must maintain full routing tables, filter invalid or unauthorised announcements, distribute traffic across links, provision capacity, protect sessions, manage communities and troubleshoot faults across many PoPs. A customer who also connects to another carrier gains redundancy and path choice but also takes on a more complex routing problem. They must understand preferences, inbound traffic engineering and fault propagation across each provider.

Tier-1 economics do not mean every interconnection is free. Settlement-free peering removes payment for a defined exchange with qualified networks. Arelion still pays for fibre, sites, equipment, power, access, staff, maintenance and other business relationships. Where it is more efficient than building itself, the company may also buy local services or partner access. The absence of upstream transit cost is one element of the cost structure, not a zero-cost network.

The carrier's route position must also be maintained. If traffic ratios, geographic reach or business policy change materially, a peer may demand different terms or end the 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 settlement-free.

Dedicated Internet Access shifts more routing responsibility to the provider

Dedicated Internet Access targets enterprises that want managed connectivity without running a full BGP relationship and global routing table themselves. The customer can obtain a default route or a managed edge, while Arelion takes more responsibility for the Internet-side design. Physical access and service quality may resemble transit at some locations, yet the operational contract is different.

The difference matters during faults and changes. A transit customer can use their own ASN, prefixes, communities and multihoming policy. A DIA customer often has less control and depends more on the provider's routing and edge support. Neither model is inherently superior. Transit suits organisations with routing expertise and policy-control needs; DIA suits buyers who prefer a managed demarcation.

SecureConnect combines Internet access or transit with automated DDoS protection. This bundling reduces procurement and configuration boundaries for customers who would otherwise contract transport and mitigation separately. The protection none the less has a defined scope. It does not protect credentials, endpoints or application logic, nor attacks outside the chosen network-layer service.

BGP communities make routing policy part of the product

BGP communities are tags on route announcements. Arelion can interpret a customer's tags and perform provider-defined actions, such as changing preferences, limiting propagation, lengthening AS paths or triggering blackholing. They give the customer influence over the provider network without direct router access.

This is a powerful form of delegated control. An operator can make a prefix less attractive in one region, limit its announcement or sacrifice reachability to protect the rest of the network during an attack. The semantics are specific to AS1299; the same community value may mean something different on another carrier. Customers need up‑to‑date documentation, controlled changes and a way to verify the result with routing tools.

Communities also carry error risk. A misapplied tag can withdraw reachability or steer traffic over an unintended path. Remote Triggered Blackholing deliberately drops traffic to a destination upstream so that an attack does not overwhelm wider links. In an emergency this is useful because one target's availability is traded for network stability. It is not a consequence‑free mitigation.

Looking Glasses show a slice of routing reality

Arelion's Twelve99 Looking Glass allows checking routes, pings and traceroutes from selected network locations. The tool answers practical questions: how does AS1299 see a prefix, what path is chosen from a particular observation point, and where does latency appear in that view? At the same time it preserves Twelve99 as a technical identity after the rebrand.

A Looking Glass provides evidence from one observation point, not an audit of the entire network. It does not show every alternative path, historical incident, internal preference or physical fibre span. BGP policy can vary by location, and a traceroute can hide devices or behave differently under load. The tool is most valuable alongside customer measurements, route collectors, service tickets and provider performance data.

Arelion also publishes monthly IP network performance metrics. Buyers can use these to track provider‑selected measures over time; methodology and scope remain the company's own. Transparency increases when a provider discloses operational data. Independent verification still requires clear definitions and external observation.

RPKI reduces one routing risk without fixing BGP as a whole

A Route Origin Authorisation allows a prefix holder to specify 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 certain hijacks and configuration mistakes. Arelion's materials present RPKI as one component of routing security.

The mechanism confirms origin authorisation for covered prefixes. It does not validate the full AS path, does not guarantee correct export by a peer and does not prevent every route leak. A valid origin can still be propagated over an unintended path, and operational errors can occur in filters, route objects or customer configurations. RPKI narrows the trust problem; it does not replace BGP policy, monitoring or incident response.

For a Tier-1 carrier this boundary matters because route security and reachability can conflict. Aggressive filtering may block legitimate traffic if entries are wrong; weak filtering can propagate invalid announcements. The operator needs graduated policies, customer communication, exception handling and current data. The statement "RPKI makes BGP secure" hides the continuing operational judgement.

IX Connect sells access to interconnection, not full Internet reach

Internet exchanges provide places where networks can establish peering. Arelion's IX Connect transports a customer from a suitable Arelion location to an exchange port, enabling remote participation without a separate local network presence. The product can lower cost and lead time for connecting to multiple peers, especially when a network expands into a new market.

The transport does not create peering policy. The customer still needs exchange membership where required, compatible ports, bilateral or route‑server agreements and their own route filters. A remote path can also introduce an additional 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.

The product shows why a Tier-1 carrier simultaneously competes and cooperates with exchanges. Arelion peers at exchange locations and also sells transport to them. A customer can replace some paid transit with direct peering and still buy Arelion capacity for the path to the exchange or for the rest of the Internet. The boundaries between transit, peering and transport are commercial choices on the same physical network.

Cloud Connect extends the backbone to a provider‑controlled demarcation

Arelion lists private connectivity to AWS, Microsoft Azure, Google Cloud, Oracle and IBM. Cloud Connect carries customer traffic to supported cloud on‑ramps, reducing dependence on public Internet paths for that segment. This can make routing, capacity and security more predictable than carrying all cloud traffic over 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 account, routes and workloads. Arelion controls the sold carrier path. A fault can lie on any side, and configurations must be coordinated. Calling the whole path "private" can mislead if it suggests one provider owns every component or that no shared infrastructure exists.

Cloud connectivity also changes the carrier's competitive position. Hyperscalers run large private backbones and increasingly carry traffic between their own regions. Arelion's opportunity lies in connecting enterprises, data centres, multiple clouds and networks that are not in the same administrative domain. The boundary is the same: the company can neither govern operations inside a cloud nor replace the cloud provider's fabric.

DDoS mitigation has become part of backbone capacity planning

Volumetric attacks consume link, router and scrubbing capacity. A global carrier sees enough traffic to detect shifts and can redirect attacked flows before congestion reaches the customer connection. Arelion's DDoS service combines detection, routing control and scrubbing, returning permitted traffic to the destination afterwards.

In its report published on 15 July 2026, Arelion stated that the Aisuru botnet accounted for roughly one third of the attack traffic observed in its dataset, and the largest attack reached 6.1 Tb/s. These are provider observations from Arelion's network and methodology. They are valuable because they show the attack dimension seen by a large backbone; they are not a universal survey of worldwide DDoS activity.

The 6.1 Tb/s observation must not be converted into a guaranteed mitigation capacity. An attack can appear distributed over the backbone without a single customer receiving the full volume, and service commitments depend on architecture and contract. Effective mitigation also depends on detection time, BGP convergence, scrubbing‑system placement, clean‑path capacity and control of false positives. Application‑layer attacks can pass volumetric filters because individual packets look legitimate.

Remote Triggered Blackholing is the emergency edge of the design. A community can cause traffic to a targeted prefix to be discarded upstream. This protects shared capacity but makes the destination unreachable. Scrubbing tries to preserve the service; blackholing accepts an outage to contain damage. A mature DDoS service needs both mechanisms, clear triggers and customer control over when the harder response is used.

SecureConnect integrates mitigation into the connectivity purchase instead of treating it as a later‑assembled option. This can increase uptake because protection is already active before an incident. The strategic test is not the bundle's name but the attach rate, response evidence, the scope of protected services and the ability to scale with rising attack peaks.

AI Direct bundles wide‑area transport for distributed AI systems

AI Direct is Arelion's connectivity portfolio for data movement between AI clusters, data centres and clouds. It bundles carrier‑familiar services—Ethernet, wavelengths, Internet access, managed optical networks and security—under an offering for AI infrastructure. The suite does not provide GPUs, storage systems or model‑training software. Its role begins where data must leave a facility or administrative domain.

This boundary is economically important. Training inside a campus depends on a local high‑performance fabric whose latency and collective behaviour a wide‑area carrier cannot replace. WAN demand arises when datasets, checkpoints, replicas, inference traffic or entire workloads move between facilities. Arelion's advantage is reach between those places; the service must connect to the internal AI fabric, not become it.

In May 2026 the company added AI Direct 400G EVPL. The announcement evidenced 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 expansions included North America, such as a PoP in Oklahoma City; the 2026 Channel Programme in Mexico extended distribution. The events show an active route and product strategy, though Arelion disclosed neither activated utilisation nor customer concentration or investment sums for each undertaking.

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 of an "AI superhighway" express strategic intent. They do not show how much revenue, utilisation or new capacity flows from AI workloads. Today's evidence supports a credible transport portfolio and an investment direction; it does not support a claim that AI has already changed the company's economics.

Enterprise services monetise the backbone beyond transit

Transit prices often face long‑term pressure as capacity improves and buyers gain alternatives. Arelion can respond with services that combine the same spans 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 a customer.

The portfolio does not mean every service carries the same margin or the same 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 sales organisation must sell shared infrastructure across different contracts and support models.

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

Arelion's mobile data, IoT, voice and messaging services further broaden the portfolio. Research evidence is strongest for backbone and connectivity products. These adjacent services should therefore be treated as part of the current catalogue and not analysed with unsubstantiated market‑share claims. Strategically they show that Arelion is not a pure IP‑transit wholesaler, even though AS1299 remains the defining technical identity.

Access partners extend reach and shift the SLA boundary

Arelion mentions around 450 access partners. These carriers can connect a customer building to an Arelion PoP where the backbone has no direct local fibre. The model extends service coverage without Arelion having to build every last mile. At the same time the customer gets one business relationship for a path composed of several providers.

The access tail is often the least standardised part of the service. Lead time, repair procedures, available bandwidth, jumbo‑frame support, demarcation device and local regulation can vary. Arelion can monitor and manage the tail, but physical repair may rest with another carrier. The lower published availability of an end‑to‑end Ethernet service compared with PoP‑to‑PoP reflects this additional risk.

A global service footprint should therefore be read as delivery capability, not a map of owned facilities. For enterprise buyers, the relevant check includes the local supplier, actual route diversity, escalation rights and whether a second access uses the same duct. A global contract can simplify governance without changing local physics.

Operations turn network assets into a usable service

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 customer experience.

Automation can shorten provision and make status visible, but a global carrier cannot reduce every event to an API call. Fibre repairs need outside teams; a cloud endpoint may reject a configuration; a peer can change its policy; a colocation facility can require a cross‑connect; and a local carrier can miss a delivery date. Carrier‑automation quality also shows in how clearly exceptions and responsibilities are presented, not just in the speed of a standard order.

Arelion points to customer‑experience awards and a high Net Promoter Score. Such claims can hint at a deliberately maintained service culture, yet methodology and response population are not independently verified in the available evidence. Awards and surveys belong alongside operational detail, not in its place.

The business model leverages an infrastructure base across several demarcations

Arelion earns money 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 starts at a different demarcation, even when several share the same backbone.

This reuse can improve asset utilisation. A fibre span and a PoP carry more revenue when they serve multiple products and customer groups. The carrier still needs isolation and headroom. If every service is planned against the same optimistic utilisation, an attack or a traffic shift can reveal hidden competition for capacity. Capacity accounting must distinguish reserved ports, typical traffic, protected traffic and failure scenarios.

Commercial leverage arises because the customer's coordination burden falls. A multinational buyer could separately assemble local carriers, exchange ports, cloud links, transit, optical paths and security. Arelion proposes to integrate a larger part of that chain. The customer pays not just for bits, but for fewer contracts, a defined support path and the transfer of responsibility. The provider earns that premium only if the integrated service works better than the fragmented alternative.

Pension‑backed ownership changes the time horizon, not economic laws

Polhem Infra owns Arelion. According to current presentation, Polhem Infra is jointly owned by the Swedish Third AP Fund and Fourth AP Fund. This links the carrier, through an infrastructure investment vehicle, to national pension capital. The structure suits an asset whose routes and interconnection position have been built over long periods.

Long‑term capital can support investments whose payback takes several years, such as fibre rights, optics upgrades and new PoPs. It can also weight stable cash flow more heavily than short‑term market communication. The owner none the less has fiduciary and return obligations. The pension‑fund connection does not mean spans are financed regardless of demand, and it does not show how much debt, operating cash flow or owner equity Arelion carries.

The governance change after 2021 was more visible than the technical one. AS1299 kept routing while board control, funding and strategic priorities shifted 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 names a wider team for strategy, sales, legal, people, technology and operations, but is not a complete statutory board register.

Not every architecture decision can be personally attributed to individual executives. The backbone is the accumulated work of engineering, operations, procurement, sales and partner teams over decades. Leadership decides capital allocation, risk tolerance, product direction and disclosure. Day‑to‑day network quality depends on distributed expertise and institutional memory.

Private ownership leaves the central financial questions unanswered

The provided evidence shows no current standalone disclosures from Arelion on revenue, profit, debt, capital expenditure, valuation, traffic volume, contract duration or customer concentration. This gap matters because a global carrier must continually fund equipment, span rights, colocation, access and security capacity. Product announcements show activity; they do not show returns.

Historical transaction data would describe the 2020–2021 sale, not the 2026 enterprise value. Extrapolating an old deal figure into the present would ignore changes in traffic, assets, capital structure and market conditions. Likewise, a connectedness ranking cannot substitute for revenue or margin. A network can be very highly connected and operate in a market where the price per bit falls.

This opacity changes the performance assessment. Public routing data and Looking Glasses can show reachability and path behaviour. Press releases can show route and product activity. Customer announcements can evidence selected implementations. None of those sources show whether capital is deployed at an adequate return, whether one customer dominates revenue or whether debt constrains the next upgrade.

The permissible conclusion is limited: Arelion appears to be an active global carrier with a broad portfolio and ongoing investment. The available evidence supports neither a profitability estimate nor a claim that pension‑fund ownership guarantees the next capital cycle.

Renewal economics lies between physical ownership and contractual control

The investment question is more complex than whether Arelion should own or lease a given span. A Tier‑1 carrier must maintain several forms of control simultaneously. Fibre ownership creates direct authority over a physical path but leaves dependencies on permits, power, repair crews, landing stations and equipment suppliers. Long‑term fibre rights can resemble ownership for operational planning while locking in contractual obligations for years. Shorter capacity contracts preserve flexibility but expose the carrier to renegotiation, price changes and supplier availability.

The right structure depends on route, market and the consequences of failure.

This matters because network economics arise before a service is sold. Arelion may have to deploy line systems, router capacity, cross‑connects and headroom before a new customer commits traffic. Expansion into a new PoP can require site contracts and equipment even though the business case rests on future demand. A high‑capacity corridor for AI can look compelling at the market level while individual customers do not yet know where their workloads will settle long term. Capital therefore arrives ahead of some of the revenue evidence it is meant to justify.

The same timing problem applies to resilience. A backup path is valuable precisely when the primary fails. This can make some of its capacity appear under‑utilised during normal operations. Finance teams may see unused headroom where operations teams see protection. The network must decide how much apparently spare capacity is economically justified by customer commitments and the failure scenarios it must survive. Too little reserve can turn a fibre cut or equipment failure into customer loss; too much reserve can depress returns if reliability is not priced accordingly.

Arelion's broad portfolio complicates the arithmetic because the same physical and packet infrastructure carries products with differing load profiles. Transit traffic can fluctuate and be price‑sensitive. Ethernet and wavelengths can carry contracted high‑capacity flows. DDoS mitigation needs capacity that sees little use until an attack. Cloud connections depend on the location and growth of external platforms. A capacity planner cannot simply add average traffic and buy the result.

They must model correlated peaks, protection switching, maintenance windows and the possibility that several services shift onto the same remaining path during a failure.

The AI Direct positioning expanded in 2026 adds a further uncertainty. Arelion has a credible basis to position high‑capacity Ethernet and optical services around distributed AI infrastructure, because data movement between facilities creates real WAN demand. AI demand does not, however, remove a carrier's normal investment discipline. The route must connect real facilities, ports must be activated, customers must pay for capacity and traffic must persist long enough to justify equipment and contractual rights. A popular workload does not change the arithmetic of unused capacity.

Supplier strategy also shapes the renewal cycle. Router and optics platforms are not limitlessly interchangeable. A major upgrade can create years of operational familiarity, spares planning, software dependencies and vendor support. Open‑line systems and coherent pluggables can reduce some lock‑in by decoupling elements of the optical stack. Interoperability still has to be developed and tested. Optionality only materialises if the carrier maintains the capabilities and operational processes to actually use it.

Locations create a similar form of embedded stickiness. A PoP becomes more valuable when customers, peers and clouds join it; the same density makes a move harder. Cross‑connects, customer equipment, maintenance processes and business relationships accumulate around the site. A data centre can thereby gain negotiating leverage over the carrier, even though Arelion owns the routers inside. The practical question is whether enough alternative sites, route diversity and commercial leverage exist so that one building or operator does not become a hidden strategic choke point.

This is why private financial opacity matters for an infrastructure profile. Without current figures on capex, debt, lease obligations and cash flow, outsiders cannot see whether network renewal is paid from operating cash, owner equity or debt, and how much headroom remains for the next hardware generation. Technical announcements show that investment is occurring. They do not show whether Arelion can sustain the same pace if prices weaken, demand grows more slowly or resilience requirements increase unexpectedly.

The strongest external evidence is therefore cumulative. New routes that are actually completed, not just announced; new PoPs with customer demand; modern interfaces that become orderable; direct routes that stay stable; and security systems that handle larger attack peaks—these show an owner that continues to fund the network. None of these points alone proves profitability. Together they show whether capital is being converted into an operating system that sustains the economic significance of AS1299.

For Arelion, the renewal obligation is inseparable from the moat. Part of the advantage comes from a network position built over more than three decades. That position saves customers the effort of assembling the same reach themselves. At the same time it creates a large installed base that must be modernised 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 commitment.

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

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

Europe remains a dense part of the network's history. North America is a key transit and enterprise market, and new sites like Oklahoma City were justified with cloud and AI data‑centre demand. Arelion's 2026 Danish investment involved routes and a cable landing‑station environment important for Nordic and submarine connectivity. In Mexico, route development and a channel programme widened access to a growth market. For Asia the research pack contains fewer public route details than for Europe and North America.

Submarine connectivity deserves separate consideration. 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 cuts, landing‑station incidents and shared terrestrial backhaul can affect multiple carriers. Logical route diversity must therefore be checked against cable and duct diversity.

Geopolitics can also change route economics. Cross‑border regulation, sanctions, permits, cable security and national resilience policy affect where carriers can build and how customers assess risk. The present pack does not evidence any concrete current dispute involving Arelion; these factors therefore enter the analysis as structural constraints, not as allegations.

Competition occurs on several levels simultaneously

At the Tier‑1 and global‑transit level, Arelion competes with networks such as NTT, Lumen's Level‑3 lineage, GTT, Tata Communications, Cogent and Sparkle. A direct comparison needs dated evidence on route relationships, geography, latency, capacity, security, support and price. A single connectedness ranking does not decide selection.

At the physical and optical level, companies like Zayo compete for fibre and wavelength demand. At the cloud‑connectivity level, Megaport and Equinix Fabric offer software‑defined interconnection over partner and facility ecosystems. At the enterprise level, regional carriers, SD‑WAN providers and managed‑service companies can build alternatives on Internet underlays. These are overlapping, not identical categories.

Hyperscalers' private backbones present another challenge. A cloud provider can internalise traffic between its regions and bundle transport with compute. Arelion remains relevant where customers need connectivity between clouds, enterprises, data centres and networks outside any single provider's control. The more traffic stays inside hyperscaler domains, the smaller some wholesale opportunities become; the more workloads are distributed across providers, the more valuable neutral WAN reach becomes.

Internet exchanges can complement and partially replace transit. A network with enough traffic can peer directly for important destinations and buy less transit. It still needs reach to the rest of the Internet, transport to exchange locations and operational support. Arelion's IX Connect and transit position the company on both sides of that decision.

Arelion's durable advantage is not that any single component is impossible to copy. Fibre can be leased, routers can be bought, cloud on‑ramps can be used and DDoS systems can be installed. The combined system—routes, peering relationships, customer prefixes, PoPs, optical paths, support and reputation—takes years to build and ongoing investment to stay relevant.

Connectedness creates both resilience and contagion

A highly connected backbone offers more path options and direct reach. It can help traffic bypass intermediate networks and absorb failures by rerouting flows. The same position increases the number of downstream organisations exposed to its faults. A route leak, filter error or capacity incident can spread beyond direct customers because other networks use routes learned from AS1299.

Physical concentration can create the same double effect. Dense PoPs improve interconnection, but a site failure can hit many services. A logically diverse topology can share the same fibre duct. A DDoS platform can protect customers, but a misdirected redirection policy can move large amounts of legitimate traffic. Scale amplifies 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 headroom, scrubbing placement, out‑of‑band access, incident communication and tested rollback. Arelion's public tools and product pages attest to parts of this system, but the pack contains neither a full incident history nor an independent audit.

Customers also bear responsibility. Multihoming, prefix design, routing policy, test plans and local access diversity determine how much provider resilience becomes effective at the customer edge. Buying from a Tier‑1 carrier does not remove the need for architecture that survives the loss of that carrier.

Sustainability claims need discipline around the denominator

Backbone growth consumes equipment, power, colocation, construction and maintenance. New coherent optics can increase capacity per watt and per rack unit. That efficiency can coincide with higher total energy use if traffic and network footprint grow faster. Arelion publishes a sustainability framework, but the available evidence does not include a full, independently assured footprint of the entire network and supply chain.

Responsible editorial treatment separates efficiency from absolute impact. A route upgrade may lower energy per bit carried; a new route may add total equipment and power. Leased infrastructure shifts some emissions and energy use to suppliers rather than eliminating them. Without consistent scope, baseline and traffic data, broad statements about a net environmental improvement would be unsupported.

Sustainability is strategically relevant because customers and pension‑backed owners may demand credible evidence on energy, procurement and resilience. It is also operationally relevant: denser optics, cooling and power availability determine where capacity can be built. The thing to watch is whether reporting becomes granular enough to link network expansion to measured resource consumption.

What the public evidence cannot show

The scale figures in this profile are primarily Arelion's own current statements. The research pack contains neither an independent route‑by‑route audit of the more than 80,000 km, nor a uniform definition of each PoP or a complete register of owned versus leased infrastructure. It also contains no comparable traffic series across competitors.

The connectedness claim is metric‑dependent. The statement of 95% within one hop describes Arelion's reported reach in the United States and Europe, not a guarantee for every destination, protocol or moment. Monthly performance reports are 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, access tail or route can deliver 400G. AI Direct is a connectivity suite, not proof of revenue from AI customers. An observed 6.1 Tb/s attack does not show contractually assured scrubbing capacity. MEF/Mplify certification supports confidence in service definitions but does not certify every access tail or incident outcome.

The financial gap is larger. Current revenue, margin, debt, capex, valuation and customer concentration remain unpublished in the documents provided. This prevents a full economic model. The gap should remain visible rather than being filled with assumptions from route ranking, customer count or owner identity.

Renewal remains 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 continues to convey technical continuity, and customers still see a global routing table. This stability is useful but can mask how much change must occur underneath. A backbone can retain the same public routing identity while replacing routers, optical platforms, line cards, software versions, power arrangements, fibre spans and facility connections. The real product is continuity through controlled change.

Hardware generations create one renewal tempo. Router capacity must keep pace with higher interface speeds, growing routing tables, telemetry and security functions. A chassis or line card that was adequate in a phase dominated by 100G can become a bottleneck when 400G ports and higher aggregate load become normal. The timing is not only about whether a device still forwards packets. Spares, vendor support, power density, software compatibility and the cost of running parallel generations can make a technically functional platform economically obsolete.

Optical systems create a second tempo. Coherent technology can greatly increase usable capacity on an existing fibre pair, but an upgrade is not a universal software switch. Distance, fibre characteristics, spectrum, amplifiers, ROADMs, open‑line‑system design and operational certification determine what is actually possible on a route. Arelion's ability to offer higher‑rate services therefore depends on route‑specific engineering, not just on a transponder's or pluggable's nominal capability.

Software creates a third tempo. Routing platforms receive security patches, protocol changes, new features and operational fixes. A stable network may deliberately delay the newest version until it is sufficiently proven; staying on an ageing release for too long, however, increases support and security risks. Operators must stage upgrades so that a fix does not itself become a larger availability problem. For a Tier‑1 backbone, the quality of change management is as important as code quality, because a single policy or control‑plane failure can affect traffic far beyond one customer.

Routing standards and operational practice create a fourth tempo. RPKI adoption, filter expectations, peering policies, BGP community conventions and routing‑security practices evolve without the AS number changing. A network that was considered well‑run a decade ago cannot assume its then‑controls suffice today. Customers and peers increasingly expect better validation, more transparent routing policy and stronger response to leaks and hijacks. Maintaining trust therefore demands process renewal as much as capacity renewal.

Locations have a slower but consequential renewal cycle. A PoP can stay in the same building while power density, cooling, cross‑connect economics or the peer mix around it change. A historically important site can become less attractive 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 build reach into new centres without weakening the dense interconnection that makes older sites valuable.

Customer geography also changes. Enterprise applications migrate to cloud regions; content platforms open edge locations; AI clusters arise in power‑rich data‑centre markets; wholesale customers build new national networks. Arelion can keep the same PoP count and still lose relevance if those PoPs are no longer close to the deciding demand. Conversely, targeted route additions can significantly enhance the existing backbone without changing the total site count much.

Security capacity follows a particularly uneven demand curve. Normal traffic can be planned around typical peaks, but DDoS systems must cope with rare events. The largest attacks of one year can look ordinary a few years later as botnets, access speeds and attack methods grow. Sizing scrubbing only for average load leaves one under‑prepared; building unlimited unused capacity destroys economics. The renewal task is to hold enough distributed headroom and redirection flexibility for plausible attacks while using the same infrastructure efficiently in normal operation.

Access partners have a lifecycle too. A local carrier can improve, consolidate, change hands, withdraw a product or become less competitive. The best enterprise‑access option of three years ago may not be the best today. Global service quality therefore depends on ongoing supplier qualification and the ability to steer new orders and, where practical, existing customers to better alternatives. The partner count measures breadth; the renewal work is deciding which relationships still deserve traffic.

Contracts also age. Long‑term capacity rights can look attractive when signed and later appear expensive against market prices. Short‑term agreements preserve flexibility but raise renegotiation and price‑increase risk. Facility, fibre and supplier contracts also expire at times that may not align with customer terms. The operator must manage these contractual clocks alongside the physical ones so that a route does not become uneconomic solely through misaligned commitments.

Staff create a less visible renewal requirement. Global backbones depend on knowledge of routing policy, optical characteristics, past disruptions, supplier behaviour and customer exceptions. Some can be transferred into inventory systems and automation; some remains institutional. Retirements, reorganisations and outsourcing can remove context that becomes important only in an unusual failure. A stable network therefore needs succession, documentation and training as much as replacement optics.

Automation does not eliminate these cycles. It can improve inventory accuracy, speed provisioning and make dependencies visible, but it raises the importance of trustworthy data. A wrong site ID, an outdated route entry or an incorrect supplier demarcation can propagate faster through an automated workflow than through a manual process. The more Arelion standardises provision and operations, the more critical the validation of the data model underneath the automation becomes.

The commercial consequence is that renewal spending must not be measured only by visible expansion. Replacing a line card before it fails, adding headroom on an existing route, moving a customer away from a correlated path or updating a security platform may not create a new country or PoP. Those investments protect existing revenue. A private owner that only measures visible growth could underweight them; an operator that treats every protection as mandatory could over‑invest. The sensible discipline is to tie every renewal decision to a failure mode, capacity bottleneck, customer contract or measurable operational gain.

With this, the simple question "Is AS1299 still Tier‑1?" is too narrow. The routing relationship can stay intact while other parts of the service improve or deteriorate. The broader test asks whether the network keeps pace with traffic growth, whether physical diversity remains real, whether peers and customers retain trust, whether security capacity follows the threat, and whether capital arrives before technical debt becomes visible as disruption.

Arelion's long history is both evidence and burden. More than three decades of operation show the system has survived several hardware, traffic and ownership cycles. They also mean the network contains decisions from different generations of technology and demand. Renewal means keeping what is valuable and replacing what no longer fits. The autonomous-system number can remain constant precisely because much beneath it does not.

Buyers should check the service boundary, not just the Tier‑1 label

For customers, the useful check begins after confirming that AS1299 is Tier‑1. The next question is where Arelion's direct control starts and ends in the purchased service. A transit port in an Arelion PoP, a managed enterprise circuit via a local partner, a wavelength on an Arelion route and a Cloud Connect service have different failure domains. The same brand and the same backbone can sit behind distinctly different operational contracts.

The physical demarcation should be explicit. The customer needs to know whether the handoff is in an Arelion PoP, in a third‑party data centre, at the customer's own site or in a partner facility. If the service includes a local access tail, it should be known who owns it, where it enters the building and whether a second circuit genuinely uses a different physical route. Two circuit IDs do not prove diversity. The key factors are duct, building entry, site, power and upstream path.

The routing demarcation is separately relevant. A transit customer controls its ASN and can use communities, preferences and multihoming. A DIA customer delegates more edge policy. An Ethernet customer may get a Layer‑2 service whose internal routing is not visible. A Cloud Connect customer reaches an on‑ramp where a second administrative domain begins. Procurement should capture these differences because they determine who can act when something fails.

Capacity should be checked at the exact boundary that is bought. A backbone can support 400G while a local port, exchange, cloud on‑ramp or access carrier does not. Buyers with AI or data‑centre traffic must distinguish core‑network capability from the orderable performance at both endpoints. Route qualification, port availability and protection options are more helpful than a generic statement that a provider supports a certain speed.

Latency claims also need route‑specific definition. Arelion's connectedness can reduce intermediate stops, but the path with the fewest AS hops is not automatically the physically shortest or lowest‑latency. BGP policy, fibre length, metro access and destination location are just as important. Customers with latency‑sensitive applications should measure from relevant locations and understand whether the contracted service uses traffic engineering, protected paths or normal Internet routing.

Availability commitments need the same discipline. The gap between backbone, PoP‑to‑PoP and end‑to‑end SLAs shows why a headline number is not enough. The customer should ask which components are included, how planned maintenance is treated, what exclusions apply, how it is measured and what follows a breach. A high percentage can still allow a material outage if the measurement window and remedy do not match the application's cost.

For DDoS procurement, detection, redirection, scrubbing and emergency blackholing should be examined separately. That a carrier observes multi‑terabit attacks is useful evidence of network visibility. The customer still needs to know their own protection type, activation rule, protected prefixes, clean‑traffic return and escalation. Equally important is knowing which attacks are not in scope, particularly application‑layer events that need other controls.

Cloud connectivity needs a three‑party operating model. Arelion supplies the carrier path, the cloud provider controls the interface and internal fabric, the customer controls the account and routing. Troubleshooting works better when the identifiers and contacts of these domains are documented before an incident. A "private connection" is valuable because it improves path and control; it does not turn three parties into a single operator.

Partner‑based access demands special attention because this is where a global carrier's consistency is hardest to deliver. Buyers should ask whether Arelion monitors the local circuit, receives proactive alerts, controls supplier escalation and can obtain route information. Also important is what happens when the local provider repeatedly misses repair targets. A global contract is especially valuable when the prime carrier has enough data and commercial influence to change the outcome, not just forward tickets.

Operational transparency should be assessed before purchase, not only during an outage. Looking Glasses, performance reports and MyArelion offer helpful visibility, but the customer should clarify which metrics are available for their specific service, how often they are updated and whether raw data can be exported. When performance becomes disputed, shared timestamps, route observations and incident records are more valuable than a generic status message.

Change control is another service boundary. Customers should know which changes they can trigger themselves through the portal or BGP community, which need provider approval and which Arelion may initiate during maintenance or security response. Delegated control is only useful when the action, blast radius and rollback are understood. This is especially true when several logical services share a physical port.

A multihomed customer should also test the failure case instead of assuming redundancy across two providers. Routing 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. Regular failover tests show whether the architecture actually uses AS1299 and the alternative carrier as planned.

The same applies to optical diversity. A protected wavelength may use two fibre paths, but buyers should check how those paths are defined and where they converge again. A dual‑link service with diverse endpoints can provide a stronger boundary than two channels sharing the same site. Application architecture may need to span multiple data centres if the site itself is a critical failure domain.

At contract renewal, these assumptions should be revisited. A service bought three years ago may today be delivered over a different access supplier, site 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 only as a price negotiation misses the chance to update the resilience model.

For BTW readers, this check shows the practical meaning of Tier‑1. AS1299 gives Arelion a strong routing position, but customers buy services at concrete demarcations. The backbone's value materialises only when routing policy, physical infrastructure, partner access, security and operations work together at those boundaries. The label removes one kind of dependency; it does not remove the others.

The central judgement

Arelion shows what a Tier‑1 carrier has become. The settlement‑free reach of AS1299 remains the defining network position, yet the commercial product is a multi‑layer service platform. Fibre and optics deliver path and capacity. PoPs deliver market access. BGP, communities and route security deliver policy. Ethernet, cloud, exchange and managed services create different demarcations. DDoS systems turn backbone visibility into a security function. Operations and customer support make every layer something an enterprise or carrier can buy.

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

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

The evidence supports an assessment that Arelion is active, globally relevant and technically broad. It does not support an assessment of current profitability, debt or the speed at which AI‑related announcements generate durable revenue. The most useful conclusion is therefore concrete: a Tier‑1 today is a routing relationship surrounded by capital‑intensive fibre, optics, packet, security and operational systems. Its quality is proved again and again at the service boundary, not awarded once by the label.

Indicators of whether the backbone is getting stronger

Arelion's next phase should be judged by implementations rather than by slogans. The company already possesses a mature routing identity, global scale figures and a broad product catalogue. The open question is whether new routes turn into activated demand, whether higher‑value services offset transit price pressure, and whether resilience keeps pace with connectedness. The following indicators connect 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 of shifting interconnection economics. Looking Glass results and external BGP observations can show changes but cannot explain the underlying business terms.

Activated rather than just announced capacity

New 400G products, optical upgrades and route announcements count when ports are lit, traffic grows and customers commit. Watch for qualified 400G availability, completed Nordic and North American routes, new PoPs and named customer implementations. A high announcement frequency without activation evidence would weaken the AI and capacity narrative.

Product mix beyond transit

Traffic volume can rise while the price per bit falls. Evidence that SecureConnect, Cloud Connect, IX Connect, managed optical networks and Ethernet are being attached to existing customer contracts would show that Arelion is monetising integration, not merely dependent on commodity transit. The company does not currently publish product revenue; customer and service announcements are therefore the available proxies.

Access‑partner performance

Growth through around 450 access partners widens reach but can introduce uneven delivery and repair. Watch for divergence between direct PoP and end‑to‑end results, local circuit lead times, recurring regional disruptions and possibly tighter disclosure of partner qualification. The published SLA gap already shows the last mile changes the risk profile.

DDoS scale and mitigation evidence

The 2026 report documents the attack environment seen by Arelion. Future reports should be checked for peak growth, botnet composition, mitigation time, customer impact and scrubbing distribution, not just a headline number. A larger observed attack is not, by itself, proof of stronger protection.

Capital and governance signals

Private ownership limits direct financial analysis. Watch for leadership changes, completed route projects, hiring, supplier commitments, disclosed financing and shifts in Polhem Infra's investment posture. Slower deployment or greater partner reliance may reflect capital discipline, demand uncertainty or both.

Five evidence‑based scenarios

WAN demand for AI becomes a durable growth driver

Neoclouds, enterprises and research bodies distribute data and workloads across sites. 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 stays technically important while returns increasingly depend on cloud, security, Ethernet and managed optical services.

Security convergence strengthens customer stickiness

Customers buy transit or DIA together with automated mitigation, making SecureConnect more important at renewal and during incident response. Success would show in attach rate, customer references and evidence of maintained availability under large attacks.

Hyperscalers internalise more transport

Cloud providers carry more traffic on private backbones, reducing some wholesale demand. Arelion stays relevant where enterprises need neutral multi‑cloud and data‑centre connectivity, but corridor economics become more selective.

A correlated route, site or capital shock exposes concentration

A peering change, fibre event, site failure or delayed upgrade hits several services simultaneously. The strategic consequence depends on physical diversity, capacity reserves, incident transparency and the owner's willingness to fund remediation.

Professional implications by stakeholder

Network operators should test routing policy, community behaviour and multihoming rather than treat Tier‑1 status as redundancy. Enterprise buyers should map direct and partner‑served segments of each service. Cloud teams should define the boundary between Arelion and the provider on‑ramp. Security teams should separate observed attack volume from contractual mitigation. Investors and owners should link route expansion to utilisation and return. Regulators and resilience planners should examine concentration at sites, cables and autonomous systems without assuming ownership is the only form of control.

Control, incentives and decisions for AS1299's next decade

Arelion's leadership problem is not a choice between "network" and "business". The network is the business, and every technical decision ties up capital, suppliers and customers for years. The 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; sites and access partners control parts of the physical path; customers control prefixes, demand and multihoming; cloud providers control the other side of the on‑ramps.

Strategy succeeds only when these authorities are aligned.

Decision one: fund physical diversity before marketing reach

Arelion should measure route diversity at the cable, duct, landing‑station, site and power level, not just by logical topology. A new PoP or path can increase apparent reach while sharing a hidden failure domain with existing capacity. The hard‑to‑reverse risk is long‑term commitment to infrastructure that cannot deliver the resilience sold over it.

The leadership decision is to embed evidence of physical diversity into capital approval and customer design. This may raise cost or delay some launches. It also reduces the risk that multiple revenue products fail in a single incident and protects the credibility of the global map. A carrier with mixed forms of physical control can still be trusted if it demonstrates control over failure boundaries.

Decision two: preserve interconnection neutrality and monetise direct reach

AS1299's moat depends on peers and customers continuing to see the network as a reliable exchange partner. Product growth must not distort routing policy in ways that weaken this trust. Commercial pressure can favour aggressive preferences, concentration on large customers or under‑investment in routes that look less profitable but maintain topology.

Leadership should protect clear separation between settlement‑free peer policy, customer transit policy, security interventions and product traffic engineering. The second‑order effect is simpler incident diagnosis and stronger counterparty trust. The third‑order risk is loss of direct relationships that cannot easily be bought back with more fibre.

Decision three: demand activation evidence for the AI portfolio

AI Direct gives Arelion a credible language for high‑capacity demand between data centres. It can also become a container into which ordinary circuits are relabelled without new economics. Management should steer the portfolio by route‑specific availability, activated ports, named use cases, utilisation, protection requirements and renewal behaviour.

This discipline prevents capital from following market excitement without customer proof. It also improves product design, because training data, inference traffic, replication and cloud access have different latency and security requirements. The hard‑to‑reverse risk is overbuilding corridors or optical capacity based on forecasts that do not materialise.

Decision four: turn security evidence into an operational feedback loop

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

A stronger loop would distinguish observed attacks, mitigated attacks, customer impact and the role of blackholing. This would help customers size risk and show the owner whether security capital protects 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 manageable

Access partners are necessary for global enterprise delivery, yet responsibility can diffuse across contracts. Arelion should treat partner selection, service inventory, incident data, diversity and exit rights as part of 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 self‑build. The third‑order effect of weak governance is that a local supplier damages the global backbone's reputation. Some failures remain outside Arelion's physical control; they need not remain outside its evidence and escalation control.

Decision six: disclose enough economics to keep institutional trust

Private ownership gives Arelion flexibility but leaves customers, partners and infrastructure stakeholders unable to assess debt, capex and customer concentration. Full public‑company disclosure is not needed to improve trust. Management and owners could disclose consistent metrics on operational investment, capacity activation, resilience and sustainability without revealing sensitive contract details.

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 continuing opacity is that counterparties, during market stress, apply their own, often stricter, assumptions.

Second‑order effects of successful execution

If Arelion converts long‑term capital into physically diverse capacity, maintains peer trust and attaches higher‑value services, AS1299 becomes more than a commodity transit path. It can become a neutral WAN platform for clouds, enterprises, carriers and distributed AI infrastructure. That position can improve customer stickiness, enable more precise capacity forecasting and make security investment more economically justifiable.

Success also radiates into the surrounding ecosystem. Access partners gain traffic and standardisation pressure; data centres gain interconnection value; cloud providers gain enterprise reach; exchanges gain remote entities; customers gain an alternative to concentrating all transport inside one hyperscaler. The benefit is distributed, which is why no single stakeholder controls the whole outcome.

Third‑order effects of failure

A severe routing‑policy error or hidden physical concentration can harm more than one product. Customers may redirect traffic, peers may reassess trust, security services may lose credibility, and the owner may face a larger capital call just when revenue is at risk. Highly connected infrastructure can transmit reputational damage as fast as packets.

A prolonged capital constraint would have slower but durable effects. Delayed optic and PoP upgrades can lengthen paths, increase partner reliance and make the network less attractive to high‑capacity customers. If direct relationships and anchor customers drift away, rebuilding them can take years.

Irreversible risks

The hardest to reverse are loss of settlement‑free peering relationships, commitment to physically correlated routes, under‑investment across a hardware generation, dependency on a large customer segment and a security incident that exposes weak operational controls. Brand damage can be repaired; a lost route position or a stranded long‑term infrastructure contract can persist.

Leadership should therefore distinguish reversible product experiments from hard‑to‑reverse network commitments. A portal feature can be changed; a fibre right, a landing‑station dependency or an optical architecture can bind the company for years. A pricing action can end; a peering relationship damaged by policy misuse may not return on demand.

The leadership judgement

Arelion's strategic asset is neither the Arelion brand nor the Twelve99 hostname alone. It is the coordinated system behind AS1299: interconnection relationships, physical paths, optical capacity, packet policy, security, operations and the trust of customers and peers. Polhem Infra and management inherit this system, rather than starting from a blank sheet. Their task is to renew it without destroying the trust accumulated under the previous identity.

The decisive test is disciplined execution. New routes must become diverse, usable paths. New ports must carry customer traffic. AI positioning must become activated services. DDoS visibility must become maintained availability. Partner reach must become manageable delivery. Private capital must become timely upgrades without hiding risk. If these conversions succeed, Tier‑1 status remains economically meaningful. If they fail, the label outlasts the advantage it once described.