Arelion’s AS1299: Tier-1 Reach Still Demands Constant Renewal

• Arelion is the private operator formerly known as Telia Carrier; Twelve99 retains a technical and historical identity, while AS1299 is its global routing identifier.
• AS1299 reaches the entire internet through customer routes and settlement-free peering, but Tier-1 status does not guarantee the shortest paths, better support, or immunity from routing incidents.
• Beyond IP Transit and Dedicated Internet Access, the company also sells Ethernet, wavelengths, managed optical networks, cloud and exchange connections, DDoS mitigation, mobile, voice and AI Direct.
• Accumulated routes, fibre, nodes, peering relationships and operational knowledge form a moat; without independent public financials, continuous investment in capacity, security and expansion remains the primary burden.

Four Names, Four Different Layers

The business started within the Telia group, operating first as Telia International Carrier and then as Telia Carrier. Polhem Infra completed the acquisition of Telia Carrier on 1 June 2021, moving corporate control away from Telia Company. The operator adopted the Arelion brand in January 2022. These dates form a corporate timeline: referring to Telia ownership before the deal closed is accurate; using it to describe the company today is not.

Twelve99 did not vanish with the rebranding. The name continues to appear in the twelve99.net technical domain, including the public looking glass, and remains tightly linked to AS1299. For engineers, this continuity is valuable because ASNs, hostnames, route filters, customer configurations and operational references often need more stability than commercial brands. It does not represent another company. Twelve99 is technical continuity; Arelion is the current commercial and corporate identity.

AS1299 is another layer. It is the autonomous-system identity used by this backbone to originate, receive, select and advertise routes. An ASN is not a legal entity nor a physical cable; it is a routing domain that enforces a unified policy across routers, PoPs and interconnection points. Arelion operates this domain, but the underlying paths can use fibre under different ownership and contractual arrangements.

Separating the historical brand, the current company, the technical hostname and the routing system avoids several common mistakes: it prevents treating technical continuity as ownership continuity, mistaking a technical identifier for a subsidiary, and it forces all network-scale numbers to be attributed clearly to the company that publishes them. This separation also reveals a core feature of Arelion's history: corporate control changes faster than the operational identity of the backbone.

Tier-1 Is a Relationship, Not a Badge

The label “Tier-1 backbone” compresses several layers of reality into a single phrase. At the routing layer, a Tier-1 autonomous system can reach the entire internet through customer routes and settlement-free peering with other large networks. It does not need to purchase upstream transit for general global reachability. This matters because it removes one class of supplier dependency and allows the network to sell full-route transit to other ASes.

At the same time, this status must be continuously maintained: peers may adjust policies, traffic patterns can shift, and the operator must keep enough capacity and direct interconnections for settlement-free exchange to remain mutually beneficial.

This definition does not certify latency, customer-support quality, DDoS protection, enterprise access or financial strength. BGP selects routes based on policy and path attributes, not a uniform geographical shortest-path principle. A Tier-1 network may still depend on data-centre operators, submarine systems, local access carriers, router and optical equipment vendors, and the customers that provide its economic value. The label merely indicates routing independence under specific interconnection relationships. It should be the starting point of analysis, not the conclusion.

Arelion’s current position demonstrates this clearly. Its commercial proposition is not merely that AS1299 has global reachability; it is that this reachability can be turned into IP Transit, dedicated packet transport, optical services, cloud and exchange connectivity, network-layer security and operational support. Buyers are not purchasing an abstract Tier-1 label; they are buying a contract constrained by service demarcation, geography, capacity, routing policy and fault-recovery capability.

From National Telco to International Operator

Arelion traces the organic development of its backbone to 1993. The network grew within the Telia family, but its operating logic was international from the start. A domestic telecom operator primarily serves its home-country retail, mobile and business customers; an international operator needs to connect across borders to other networks, deploy routers in neutral data centres, acquire long-haul circuits, maintain optical transmission capacity and negotiate interconnection with organisations that may also be competitors.

This difference prepared Telia Carrier for a separation from its former parent. By 2020 its customer and infrastructure relationships had clearly outgrown Telia’s domestic business. Telia Company agreed to sell it to Polhem Infra in October 2020, and the deal closed in June the following year. The closing, not the earlier announcement, marks the real transfer of control. Polhem Infra simultaneously noted that Arelion maintains a strategic network relationship with Telia, showing that equity independence does not eliminate commercial interdependence.

The 2022 rebranding gave the independent operator a corporate identity no longer tied to the former shareholder, but the underlying asset is not a greenfield network; it is a mature backbone with decades of accumulated fibre paths, PoPs, customer connections and peering. Direct interconnection capability cannot be instantly replicated by deploying a software control plane. A new entrant can quickly lease capacity and light ports in several markets, but it cannot immediately copy the long-established direct routes, operational reputation and outage-recovery experience.

Independent ownership also changes the investment logic. Inside Telia, the Carrier business had to compete for capital within a diversified telecoms group; under Polhem Infra it became a dedicated infrastructure investment backed by Swedish pension capital. Such a structure may be better suited to long-cycle deployment, but it does not mean there is no return requirement or that capital is unlimited. What changes is who makes the decisions, how assets are understood and what evidence is visible to the outside.

The Backbone Is a Chain of Control, Not a Single Homogeneous Asset

Arelion claims more than 80,000 km of fibre, over 350 PoPs, service in 129 countries, together with more than 2,000 customers and about 450 access partners. These numbers describe different layers and must stay attributed to the company. Fibre kilometres describe physical coverage; PoPs describe service and interconnection locations; the country count describes commercial delivery reach; and partners extend service beyond direct PoPs. Adding them together yields no meaningful scale metric.

The underlying chain may include fibre owned, controlled under long-term rights or leased by Arelion; optical systems deployed on it; routers and switches; data-centre space and power; cross-connects linking customers and peers; submarine system capacity; cloud on-ramps; and local tail circuits from other carriers. Arelion can control the end-to-end service and routing policy while sharing physical failure domains with suppliers. “Global backbone” describes an operating system assembled from multiple forms of control; it does not mean a single company owns every trench, fibre and data centre.

This is not wordplay; it is the core of failure analysis. Two logical routes that appear independent on a map may in fact share the same duct or submarine cable. Two separately sold services may share routers, optical line systems or power. Conversely, leased infrastructure can be highly resilient if the contract, monitoring and physical diversity design are sound. Ownership alone cannot answer the reliability question; what matters are the failure boundaries and whether the operator can observe and recover from them.

Arelion’s commercial capability rests first on its command of this chain. It must know which segments are its own backbone, which depend on data centres, which are provided by access partners, which endpoints are controlled by cloud providers, and where the contractual SLA changes. The customer sees one order and one support window, but an incident may cross multiple organisations. Part of the operator’s value is making that chain manageable, not pretending it is composed only of itself.

Fibre Provides the Path; Optical Systems Provide Usable Capacity

Fibre length is a geographical metric, not a capacity metric. A single fibre can carry a varying number of wavelengths, and each wavelength can be upgraded with new coherent optics and line systems. Consequently, the same physical route can carry more traffic after equipment refresh without new trenching. Arelion’s 400G and higher-capacity plans sit in this optical-transmission layer: transceivers, coherent modules, amplifiers and spectrum engineering turn glass into usable transport.

Wavelength services offer customers dedicated optical paths on proven routes, suited to large-scale, predictable data movement such as data-centre interconnect, replication or carrier aggregation. They provide clearer capacity boundaries than public IP Transit, but still depend on physical fibre, optical equipment and path protection. “Dedicated” refers to a logical or optical channel; it should not be stretched to imply the customer owns a fully physically separate fibre cable.

Arelion also sells fibre and Managed Optical Fiber Network services. The managed option shifts more design, equipment and operational responsibility to the carrier. Large enterprises, cloud operators or service providers can avoid building their own optical network teams for every route, but become more dependent on Arelion’s serviceable geography, supplier selection, restoration processes and lifecycle decisions.

The optical business also illustrates why a mature backbone cannot be considered a “build once and done” asset. Traffic keeps growing, interface speeds increase, and customers continuously demand new cloud and data-centre paths. Each upgrade requires capital before demand is fully firm. Under-building leads to congestion and service degradation; over-building results in idle optics, ports and long-term commitments. An operator’s financial discipline often shows up in capacity planning before customers notice any speed change.

PoPs Turn Long-Haul Capacity into Tradable Market Access

PoPs are where backbone capacity actually enters the interconnection market. A PoP may house routers, optical equipment, switches, customer ports and cross-connects inside a data centre or carrier hotel. Denser PoP coverage shortens the distance between Arelion and customers, peers, clouds and IXs, but also exposes operations to data-centre power, cooling, building access and cross-connect processes.

“Over 350 PoPs” is a scale claim; it does not mean every product and port speed is available at every location. A site may support IP Transit but not a particular wavelength; 400 Gb/s Ethernet requires technical verification; cloud connectivity depends on the provider’s on-ramp; remote enterprise sites may still need partner tail circuits. The more meaningful procurement question is not “Is Arelion in this country?” but “Is this service available at this demarcation point?”

PoP density also affects network directness. Direct interconnection reduces the number of intermediate networks a path must traverse; more direct customers and peers can also improve route selection. Arelion claims that 95% of end users in the United States and Europe are reachable within one network hop, and on its chosen metrics calls AS1299 the world’s most interconnected backbone. These claims must stay attributed, because the conclusions depend on the dataset, definitions and date. One network hop is not the same as least latency for every flow, and “interconnectedness” is not the same as traffic market share.

The Packet Layer Runs Multiple Products on a Shared Underlay

Above the optical layer, routers and packet systems turn capacity into public and private services. AS1299’s BGP control plane exchanges internet routes; MPLS and Segment Routing underpin traffic engineering and private packet transport; Ethernet provides Layer-2 connectivity; Smart IP-VPN delivers a managed routed WAN; Cloud Connect and IX Connect extend paths into specific ecosystems. They share some of the same underlying infrastructure but have different service boundaries.

Arelion’s Ethernet portfolio includes point-to-point EVPL and multipoint ELAN, with speeds from 10 Mb/s to 400 Gb/s, depending on path and technology availability. Its documentation also describes using Segment Routing and Flex-Algo to create specific low-latency paths inside the MPLS backbone. This can improve predictability within the operator’s domain, but cannot eliminate the local access tail or external endpoints outside its control.

Publicly stated availability figures reveal the service boundaries clearly. Arelion quotes 99.999% for its MPLS backbone service, 99.99% for basic PoP-to-PoP Ethernet, and 99.5% for end-to-end service that includes a managed NID and access tail. These numbers are not interchangeable. The wider the scope, the more equipment and third-party dependencies are added. The final commitment remains specific to the contract and path.

Customers can also use logical isolation to let several services share a single port, reducing cross-connect and interface costs. Those services are then concentrated in the same physical failure domain, however; a single port failure can affect multiple logically independent services at once. Efficient multiplexing and concentration risk must be described together.

IP Transit Is the Most Central Commercial Expression of Tier-1 Status

IP Transit customers typically run their own autonomous systems, advertise prefixes over BGP and receive a full internet routing table from Arelion. The operator delivers outbound traffic toward other networks and returns inbound traffic to the customer’s prefixes. On the surface the contract buys reachability, capacity and a service; the underlying value flows from AS1299’s relationships with customers and peers.

BGP wraps physical paths in route advertisements, so the transaction looks simple. In daily operation Arelion must maintain a full routing table, filter invalid or unauthorised advertisements, balance traffic, provision capacity, protect sessions, enforce community-based policies and recover from failures across multiple PoPs. A customer that connects to multiple operators obtains redundancy and path choice, but routing design and incident diagnosis become more complex. It must understand preferences, inbound traffic engineering and the fault-propagation behaviour of different operators.

Tier-1 economics do not mean that all interconnection is free. Settlement-free peering only removes the charge for one type of exchange with qualifying networks. Arelion still bears the costs of fibre, data centres, equipment, power, access, staff, maintenance and other commercial relationships; in some locations buying local service or partner access is more efficient than building. Not needing upstream transit is just one element of the cost structure; it does not make the network costless.

This routing status must also be continuously defended. If traffic balance, geographic coverage or commercial policy changes significantly, peers may demand new terms or terminate the relationship. The real moat is therefore accumulated over time and actively maintained. The network must retain enough customers, direct coverage, capacity and operational credibility for other large backbones to keep accepting settlement-free exchange.

Dedicated Internet Access Gives More Routing Responsibility to the Operator

Dedicated Internet Access targets enterprises that want a managed connection but do not wish to run full BGP relationships and a global routing table themselves. The customer may receive only a default route or a managed edge, with Arelion taking on greater internet-side design responsibility. The physical access in some locations resembles Transit, but the operational responsibilities and contract boundaries differ.

The difference is most visible during faults and changes. A Transit customer can use its own ASN, prefixes, communities and multi-homing policies; a DIA customer has less control and relies more on the carrier’s edge routing and support. Neither model is universally better. Transit suits organisations with in-house routing capability that need policy control; DIA suits buyers who want a managed demarcation.

SecureConnect packages Transit or DIA with automated DDoS mitigation, reducing the boundary between separately procured transport and protection services. The protection scope remains limited, however: it does not defend account credentials, endpoints, application logic, or attacks outside the chosen network-layer service envelope.

BGP Communities Make Routing Policy Part of the Product

BGP Communities are tags attached to route advertisements. Arelion can execute carrier-defined actions based on a customer’s tags, such as changing local preference, limiting propagation, adding AS-path prepends or triggering blackholing. This lets customers influence routing treatment inside AS1299 without directly logging into the carrier’s routers.

This delegated control is powerful. A carrier customer can make a prefix less preferred in a region, restrict the directions to which it is advertised, or sacrifice reachability under attack to protect the wider network. The community semantics are proprietary to AS1299; the same numeric values at other operators may trigger different actions. Customers must verify outcomes with up-to-date documentation, controlled changes and routing tools.

Communities can also cause incidents. A misapplied tag can withdraw reachability or steer traffic onto an unintended path. Remote Triggered Black Hole deliberately discards traffic toward a target upstream, protecting shared infrastructure from congestion but rendering the target unreachable. It is an emergency tool that trades local availability for overall stability, not a cost-free mitigation.

Looking glass only shows part of routing reality

Arelion’s Twelve99 looking glass lets users view routes, ping and traceroute from selected network nodes. It can answer practical questions: how AS1299 sees a prefix, what path is chosen from a node and where latency may occur; it also keeps Twelve99 alive as a technical identity after the rebranding.

A looking glass is evidence from one observation point, not a whole-network audit. It cannot see all alternative paths, historical incidents, internal preferences or physical fibre. BGP policies may differ by location; traceroute may hide devices or behave differently under load. It is best used together with customer measurements, public route collectors, trouble tickets and provider performance data.

Arelion also publishes monthly IP network performance metrics. These materials help observe how the operator’s chosen indicators evolve over time, but methodology and scope are still defined by the company. Publishing operational data adds transparency; independent validation still needs a clear methodology and external observation.

RPKI narrows one routing risk but cannot fix all of BGP

Route Origin Authorisation lets a prefix holder declare which AS is authorised to originate a route. Route Origin Validation then classifies announcements as valid, invalid or not found. Filtering invalid origins can reduce some hijacks and misconfigurations. Arelion’s educational materials treat RPKI as one part of routing security.

It validates the origination authority of a covered prefix, not the full AS-path; it does not guarantee that peers export routes correctly, nor does it prevent all route leaks. A route with a valid origin can still propagate along an unintended path; filters, route objects and customer configurations can also be wrong. RPKI narrows the trust problem but cannot replace BGP policy, monitoring and incident response.

For a Tier-1 this boundary is especially important because security and availability can conflict. Aggressive filtering can block legitimate traffic when records are wrong; filtering too loosely propagates invalid announcements. Operators need phased policies, customer communication, exception handling and current data. Simply saying “RPKI makes BGP safe” hides the operational judgements that still have to be made.

IX Connect Sells an Interconnection Port, Not Full Internet Reachability

Internet exchanges provide venues for networks to establish peering. Arelion’s IX Connect transports customers from an available Arelion location to an exchange port, enabling remote participation without building local network presence. For networks entering new markets, this can lower the cost and lead time to reach multiple peers.

The transport service itself does not create a peering strategy. Customers still need the required membership, a compatible port, bilateral or route-server relationships and their own route filtering. The remote path also adds extra dependencies compared with deploying a router directly at the IX. IX Connect is therefore an access service into the routing market, not a substitute for a customer’s interconnection strategy.

This also explains why a Tier-1 both cooperates with and forms an alternative to IXs. Arelion peers on IXs while selling transport to them. Customers can reduce some paid transit through direct peering, but still need Arelion to reach the IX or cover the rest of the internet. The boundaries between transit, peering and transport are commercial choices built on the same physical network.

Cloud Connect Delivers the Backbone to a Cloud-Provider-Controlled Demarcation Point

Arelion lists private cloud connections to AWS, Microsoft Azure, Google Cloud, Oracle and IBM. Cloud Connect delivers customer traffic to a supported cloud on-ramp, reducing that segment’s reliance on the public internet and potentially offering more predictable routing, capacity and security than generic Transit.

The service terminates at a shared boundary. The cloud provider controls the virtual interface, regional availability, quotas and internal network; the customer controls accounts, routes and workloads; Arelion controls the carrier path it sells. Failures can happen on any side, and configuration requires coordination. It would be misleading if “private” were understood as one company owning all components or as a complete absence of shared infrastructure.

Cloud connectivity also shifts the operator’s competitive position. Hyperscalers run large private backbones and increasingly carry traffic internally between regions. Arelion’s opportunity lies in connecting enterprises, data centres, multi-cloud environments and other networks that do not belong to the same administrative domain; its limits are equally clear: it cannot control inside the cloud, nor can it replace the cloud provider’s own network fabric.

DDoS Mitigation Has Become Part of Backbone Capacity Planning

High-volume attacks consume link, router and scrubbing capacity. A global operator can detect anomalies in aggregate traffic and divert attack traffic toward scrubbing systems before congestion reaches the customer tail. Arelion’s DDoS service combines detection, BGP diversion and scrubbing, then returns clean traffic to the destination.

In a report published on 15 July 2026, Arelion stated that the Aisuru botnet accounted for roughly one-third of attack traffic it observed, with the largest attack reaching 6.1 Tb/s. This is a provider observation based on Arelion’s network and methodology; it illustrates the attack volumes a large backbone sees but is not a census of global DDoS activity.

The 6.1 Tb/s observation cannot be written as guaranteed mitigation capacity. Attacks may be observed distributed across the backbone rather than fully hitting a single customer; service commitments also depend on architecture and contract. Effective mitigation is influenced by detection time, BGP convergence, scrubbing location, clean-path capacity and false-positive control. Application-layer attack packets may look normal and can slip through purely volumetric filtering.

Remote blackholing is an extreme emergency measure. A BGP Community can cause traffic towards an attacked prefix to be dropped upstream, protecting the shared network while making the target unreachable. Scrubbing tries to preserve service; blackholing accepts interruption to contain damage. A mature service needs both, clear trigger conditions, and customer authorisation for the more drastic action.

SecureConnect procures mitigation capability together with connectivity, rather than assembling it after an incident. This should improve the rate of pre-enablement. What should really be monitored are the attach rate, response evidence, protected service scope, and the ability to scale when attack peaks grow, not the product name.

AI Direct Packages Wide-Area Transport for Distributed AI Systems

AI Direct is Arelion’s connectivity bundle aimed at moving data between AI clusters, data centres and clouds. It combines traditional carrier services—Ethernet, wavelengths, internet access, managed optical networks and security—into an AI-infrastructure connectivity package. It does not supply GPUs, storage systems or model-training software; its role begins after data leaves a single facility or administrative domain.

This boundary matters. Training within a single campus relies on low-latency, high-bandwidth local fabric that a wide-area operator cannot replace. Wide-area transport demand appears only when datasets, checkpoints, replication traffic, inference traffic or entire workloads need to move between facilities. Arelion’s strength is cross-site coverage; it connects internal AI fabrics, rather than becoming one.

In May 2026 the company added 400G EVPL to AI Direct. This indicates that high-capacity packet options exist on qualified routes, not that they are universally available everywhere. The previous April, Arelion announced Danish network and cable-landing-station investments, describing them as part of a Nordic AI corridor; earlier North American expansion included an Oklahoma City PoP, while a Mexican channel programme widened commercial distribution. These events show active route and product strategy, but the company has not disclosed actual utilisation, customer concentration or investment amounts for each project.

Proving that AI Direct is more than repackaging requires named high-capacity customers, lit ports, sustained traffic and route-level commitments. “AI superhighway” signals direction; it does not show how much revenue, utilisation or fresh capacity AI is contributing. The available evidence supports a credible transport bundle and an investment direction, but is limited public evidence to prove that AI is already reshaping the company’s economics.

Enterprise Services Monetise the Backbone Beyond Transit

As capacity grows and alternatives multiply, Transit unit prices face long-term pressure. Arelion can use the same network to offer more control, demarcation and support, selling higher-value services. Ethernet, Smart IP-VPN, Cloud Connect, IX Connect, managed optical networks and DDoS protection widen the solutions a single customer can buy.

Product breadth does not mean all services carry the same margin or customer type. Wholesale carriers may buy Transit and wavelengths; multinational enterprises buy managed access and IP-VPN; cloud operators buy optical capacity; regional ISPs buy transit and IX access. Commercial teams must sell the common infrastructure through different contracts and support models.

A broad portfolio also creates internal complexity. Capacity reserved for private services, public Transit and DDoS mitigation must be planned together. An optical-path change can affect multiple packet products simultaneously; local-access delays can stall what looks like a global automated order. Asset reuse improves economics only when isolation, change control and capacity accounting are accurate.

Mobile data, IoT, voice and messaging further broaden the portfolio. The research material has the strongest evidence for the backbone and connectivity products, so these adjacent offerings should be treated as current service categories without inferring market share. They show that Arelion is not a pure IP Transit wholesaler, even though AS1299 remains its most significant technical identity.

Access Partners Extend Coverage and Shift SLA Boundaries

Arelion claims about 450 access partners. They can connect a customer building to an Arelion PoP, enabling the operator to extend enterprise service coverage without building fibre for every last kilometre. A customer can thereby buy a path stitched across multiple carriers through a single commercial relationship.

The tail circuit is often the least standardised segment. Lead times, repair processes, bandwidth, jumbo frame support, NID capabilities and local regulation can vary. Arelion can monitor and manage the tail, but physical repair may belong to another carrier. The lower end-to-end Ethernet commitment compared with the public PoP-to-PoP SLA reflects this extra risk.

Global coverage should therefore be understood as deliverable, not as fully owned. Enterprise due diligence needs to confirm the local supplier, physical diversity, upgrade and fault-escalation rights, and whether a second circuit shares the same duct. A global contract simplifies governance but does not change local physical conditions.

Operations Turn Network Assets into a Service Customers Can Use

A backbone only has value when it is provisionable, observable and repairable. Arelion’s customer-facing systems include the MyArelion portal, service management and network-operations support. These systems turn ports, routes, trouble tickets, planned maintenance and performance information into customer experience.

Automation can shorten provisioning and surface status, but a global operator cannot simplify every event to an API call. Fibre repair needs a field team; a cloud endpoint may reject a configuration; a peer may change its policy; a data centre may wait for a cross-connect; a local carrier may delay delivery. The quality of carrier automation is also shown in how it represents exceptions and responsibility, not just the speed of normal orders.

Arelion reports winning customer-experience awards and a high NPS. This may speak to a service culture, but the research material contains no independent audit of its methodology or sample. Awards and surveys can supplement operational evidence; they cannot replace it.

The Business Model Multiplexes the Same Infrastructure Across Multiple Service Demarcations

Arelion sells capacity, routing, service guarantees and operational responsibility. IP Transit monetises global reachability; Ethernet and IP-VPN monetise private packet paths; wavelengths and managed optical networks monetise optical capacity and engineering capability; cloud and IX connections monetise ecosystem access; DDoS monetises visibility and protection. Even when they share the same backbone, the demarcation point differs for each product.

Multiplexing can increase asset utilisation. A fibre route and a PoP that carry several products at the same time can generate more revenue. But the operator still needs to maintain isolation and headroom. If all products are planned on the same optimistic utilisation figure, a single attack or traffic shift can expose hidden contention. Capacity accounting must distinguish sold ports, day-to-day traffic, protected traffic and failure scenarios.

Commercial value also comes from reducing customer coordination. A multinational enterprise could separately procure local carriers, IX ports, cloud connections, Transit, optical paths and security services; Arelion tries to consolidate more of these pieces. What the customer pays for is not just bits; it is fewer contracts, clearer support paths and a transfer of responsibility. The carrier earns a premium only when the integrated service outperforms the fragmented alternative.

Pension Capital Changes the Time Horizon but Not the Economics

Polhem Infra owns Arelion, and Polhem Infra is jointly owned by the Swedish Third AP Fund and Fourth AP Fund. This ties the operator to national pension capital through an infrastructure-investment platform. The structure has logic for an asset that requires years to accumulate routes and interconnection positions.

Patient capital can sustain investments like fibre rights, optical-system upgrades and new PoP builds that pay back over many years, and may value stable cash flows over short-term public-market signals. But the owners still have return and fiduciary obligations. Pension backing does not mean unlimited capital injected regardless of demand, nor does it reveal how much debt, operating cash flow or shareholder capital Arelion uses.

The governance shift after 2021 is more visible than any technology change. AS1299 continues to route, while board control, financing and strategic priorities moved from Telia to Polhem Infra. Daniel Kurgan became CEO in October 2023; Charles Gill became CFO in March 2024. The company’s current management page covers strategy, sales, legal, HR, technology and operations, but is not a complete statutory board list.

Nor should every network-architecture decision be attributed to individual executives. The backbone is the cumulative output of decades of effort by engineering, operations, procurement, sales and partner teams. Leadership decides capital allocation, risk tolerance, product direction and disclosure; day-to-day network quality rests on distributed expertise and institutional memory.

Private Ownership Keeps Key Financial Questions Out of Sight

Available materials do not disclose Arelion’s current standalone revenue, profit, debt, capital expenditure, valuation, traffic volumes, contract durations or customer concentration. This matters because a global operator must continuously finance equipment, circuit rights, data centres, access and security capacity. Product announcements show activity; they do not prove returns.

The historical deal value describes the 2020–2021 sale, not the company’s worth in 2026. Extrapolating from it ignores traffic, asset, capital-structure and market changes. An interconnection ranking is no substitute for revenue or profit. A network can be highly interconnected yet operate in a market where unit bandwidth prices are falling.

This opacity changes how outsiders assess the company. Public BGP and looking glass show reachability; news shows route and product activity; customer announcements show selected deployments. But they cannot show whether returns on capital are adequate, whether a single large customer exists, or whether leverage constrains the next upgrade cycle.

The supportable conclusion is only that Arelion appears to be an active, global, continuously investing operator. The available evidence cannot support an earnings estimate, nor can it prove that pension ownership automatically guarantees the next round of capital deployment.

Geographic Coverage Is a Service Map, a Routing Map and a Dependency Map at the Same Time

Arelion’s historical and ownership roots lie in the Nordics; the backbone spans Europe, North America and Asia. The 129-country figure represents the commercial service footprint, not the extent of wholly owned fibre systems or PoPs. Buyers need three maps: the backbone and facilities Arelion directly owns or controls; the locations partners can deliver; and the locations where a specific product is technically available.

Europe remains the most historically dense region. North America is the primary Transit and enterprise market; expansions such as Oklahoma City are positioned for cloud and AI data-centre demand. The 2026 Danish investment involves fibre routes and a cable-landing-station environment, important for Nordic and submarine connectivity. Mexico is being extended through route and channel programmes. The research material has fewer route details for Asia than for Europe and North America.

Submarine connectivity needs separate treatment. Arelion can buy spectrum or capacity, deploy equipment at landing stations and run end-to-end services without owning an entire submarine cable. Cable faults, landing-station incidents and shared terrestrial backhaul can affect multiple operators simultaneously. Logical diversity must be verified down to the level of submarine cables and duct routes.

Geopolitics also changes route economics. Cross-border regulation, sanctions, licensing, submarine-cable security and national resilience policies all affect build decisions and customer risk assessment. The research material does not record specific disputes currently involving Arelion, so these should be treated as structural constraints, not allegations.

Competition Occurs at Multiple Levels Simultaneously

At the Tier-1 and global Transit layer, Arelion faces NTT, Lumen’s Level 3 network, GTT, Tata Communications, Cogent, Sparkle and others. Meaningful comparison requires time-stamped routing relationships, geographic coverage, latency, capacity, security, support and pricing data; a single interconnection ranking cannot determine the outcome.

At the physical and optical layer, companies such as Zayo compete for fibre and wavelength demand; at the cloud-interconnection layer Megaport and Equinix Fabric offer software-defined connectivity through data-centre and partner ecosystems; at the enterprise layer, regional carriers, SD-WAN and managed-service providers can assemble alternatives atop internet underlays. These categories overlap but are not the same.

Hyperscaler private backbones are another challenge. Cloud providers can internalise inter-region traffic and bundle transport with compute. Arelion’s value lies in connecting enterprises, data centres, multi-cloud environments and networks that do not belong to the same cloud administrative domain. More traffic staying inside clouds shrinks some wholesale opportunities; more workloads distributed across locations raises the value of neutral wide-area connectivity.

IXs both complement and partly substitute for Transit. A network with sufficient traffic can peer directly with major destinations, reducing Transit purchases, but still needs coverage for the rest of the internet, transport to the IX and operational support. Arelion’s IX Connect and Transit products let it participate in both choices.

Arelion’s durable advantage is not that any single component is absolutely un-copyable. Fibre can be leased, routers bought, cloud on-ramps joined and DDoS systems deployed. What genuinely takes years is the combined system: routes, peering relationships, customer prefixes, PoPs, optical paths, support and reputation, together with the continuing investment to maintain them.

High Interconnection Brings Both Resilience and Contagion Risk

A highly interconnected backbone provides more path options and direct reach; it can also shift traffic during failures. At the same time, more downstream organisations can be affected by its mistakes. Route leaks, filter errors or capacity incidents can propagate beyond direct customers because other networks rely on routes learned from AS1299.

Physical concentration has the same dual effect. Dense PoPs improve interconnection, but a data-centre failure can affect multiple services; a logically distributed topology may share ducts; a DDoS platform can protect customers, but a misdirected diversion can also move large volumes of legitimate traffic. Scale amplifies both capability and blast radius.

Resilience therefore depends on controls that are invisible on a map: maintenance discipline, staged configuration, route filtering, RPKI, community governance, optical protection, capacity headroom, scrubbing distribution, out-of-band access, incident communication and tested rollback. Arelion’s public tools and product materials demonstrate that some of these mechanisms exist, but the material contains no complete incident history or independent audit.

Customers also carry responsibility. Multihoming, prefix design, routing policy, test plans and local-access diversity determine how much of the carrier’s resilience actually reaches the customer edge. Buying Tier-1 does not mean the architecture can ignore the possibility of that carrier failing as a whole.

Sustainability Claims Need a Rigorous Denominator

Backbone expansion consumes equipment, electricity, data centres, construction and maintenance. New coherent optics can increase the capacity per watt and per rack unit, but if traffic and network footprint grow faster, an improvement in unit efficiency can still come with a rise in total energy use. Arelion publishes a sustainability framework, but the available material lacks a complete, independently audited whole-network and supply-chain footprint.

A reasoned approach separates efficiency from absolute impact. An upgrade may lower energy per bit; a new route adds equipment and power. Leased infrastructure merely shifts some energy use and emissions to the supplier; it does not make them disappear. Without consistent scope, baseline and traffic data, a broad net-improvement conclusion cannot be supported.

Sustainability is strategically relevant because customers and pension shareholders may demand credible evidence on energy, procurement and resilience; it also affects operations because optical density, cooling and power availability determine where capacity can be deployed. The watchpoint should be whether disclosures gradually become granular enough to link network expansion to real resource consumption.

What the Public Evidence Cannot Show

The network-scale numbers in this article are mainly from Arelion’s own representations. The research material contains no route-by-route audit of the more than 80,000 km; no uniform definition for every PoP; no complete list of owned versus leased assets; and no comparable competitor traffic series.

Interconnection rankings depend on specific metrics. The 95%-one-hop claim is Arelion’s statement about the United States and Europe, not a guarantee for every destination, protocol and moment. Monthly performance reports are informative but still provider-chosen. Procurement still requires path-level testing and contractual terms.

Product availability is also conditional. Ethernet supports up to 400 Gb/s, but that does not mean it is deliverable at every location, tail and route. AI Direct is a connectivity bundle, not evidence of AI revenue. The 6.1 Tb/s observation is not the same as contractual scrubbing capacity. MEF/Mplify certification supports consistency of service definitions, not the outcome on every tail or incident.

The financial gap is larger. The available material has no current revenue, margins, debt, capex, valuation or customer concentration, so a complete economic model cannot be built. This gap must be maintained, not filled with routing rankings, customer counts or shareholder background.

Core Judgement

Arelion shows what a Tier-1 operator looks like today. AS1299’s settlement-free full reachability remains the defining network position, but the commercial product is already a layered service platform. Fibre and optical systems provide the path and capacity; PoPs provide market access; BGP, communities and routing security provide policy; Ethernet, cloud, IX and managed services create different demarcations; DDoS systems convert backbone visibility into a security function; and operations and support turn all these layers into services clients can buy.

The moat comes from historical accumulation. Arelion inherited decades of Telia Carrier’s routes, facilities, peering relationships and operational knowledge. Polhem Infra’s ownership brought a dedicated infrastructure investor and a new brand to this system, but did not replace its technical identity. Twelve99 persists because network memory often outlasts market brands.

That history also brings obligations. Tier-1 status does not freeze the network after it is earned. Prices change, attack peaks grow, clouds internalise transport, AI creates new corridors, optical rates rise and customers demand more automation. Arelion has to renew the platform while protecting the routing trust that makes AS1299 valuable.

The evidence is sufficient to describe Arelion as active, globally significant and technically broad, but limited public evidence to judge current profitability, leverage or the speed at which AI announcements turn into steady revenue. The most useful conclusion is therefore highly specific: a Tier-1 today is a routing relationship wrapped inside capital-intensive fibre, optical transmission, packet, security and operational systems; its quality must be demonstrated repeatedly at every service boundary, not conferred once by a label.

Indicators of Whether the Backbone Is Still Strengthening

Arelion’s next phase should be judged by conversion, not slogans. It already has a mature routing identity, a global scale claim and a broad product set. The open questions are whether new routes convert into actual demand, whether higher-value services can offset Transit pricing pressure, and whether resilience is improving at the same pace as interconnectedness. The indicators below link technical activity to commercial and operational outcomes.

Peering relationships and routing stability

Tier-1 status depends on sustained settlement-free relationships. Significant changes in AS1299’s visible adjacencies, path lengths or propagation patterns could be early signals of shifting interconnection economics. Looking glass and external BGP observation can see the change but cannot explain the commercial terms.

Watch activated capacity, not just announcements

400G products, optical upgrades and new routes matter only when ports are lit, traffic grows and customers sign. Watch for qualified 400G availability, Nordic and North American route completions, new PoPs and named customers. Frequent announcements without activation evidence weaken the AI and capacity narratives.

Product mix beyond Transit

Traffic can grow while unit prices fall. Whether SecureConnect, Cloud Connect, IX Connect, managed optical networks and Ethernet attach to existing customers is a signal of whether Arelion is monetising its integration capability. The company does not disclose revenue by product, so customer and service announcements are the available proxy.

Access-partner performance

About 450 partners expand coverage but may also increase delivery and repair variability. Watch for direct PoP versus end-to-end outcomes, tail delivery times, regional repeat faults and partner selection disclosures. The public SLA differences already show how the last kilometre changes the risk.

DDoS scale and mitigation evidence

The 2026 report describes the attack environment Arelion sees. Future reports should be tracked for peak growth, botnet structure, mitigation time, customer impact and scrubbing distribution, not just a single number. Observing larger attacks does not automatically prove stronger protection.

Capital and governance signals

Private ownership limits direct analysis. Watch management changes, completed routes, hiring, supplier commitments, financing disclosures and Polhem Infra’s posture toward investment. Slower deployment or greater reliance on partners could stem from capital discipline, demand uncertainty, or both.

Five Scenarios with Evidentiary Support

Wide-area AI demand becomes a durable growth engine

Neoclouds, enterprises and research institutions distribute data and workloads across multiple facilities. Arelion activates 400G EVPL and wavelengths on named corridors, and AI Direct becomes a measurable source of traffic and customer growth.

Traffic grows but economic headroom tightens

AS1299 carries more bits while Transit unit prices fall faster. Arelion remains technically important, but returns depend more on cloud, security, Ethernet and managed optical business.

Security integration lifts customer retention

Customers buy Transit or DIA together with automatic mitigation; SecureConnect plays a growing role in renewals and incident response. Success would show up in attach rates, customer case studies and availability during large attacks.

Hyperscalers internalise more transport

Cloud providers carry more traffic on private backbones, reducing some wholesale demand. Arelion retains value in neutral connectivity between enterprises, data centres and multiple clouds, but corridor economics become more selective.

Correlated shocks in routing, data centres or capital expose concentration risk

Peering changes, fibre incidents, data-centre outages or upgrade delays affect multiple services simultaneously. The consequences depend on physical diversity, capacity headroom, incident transparency and the owner’s willingness to commit repair capital.

Implications for Different Professional Roles

Network operations teams should test routing policy, communities and multihoming, not treat Tier-1 as redundancy. Enterprise buyers should label every direct and partner segment. Cloud teams should define the boundary between Arelion and the cloud on-ramp. Security teams should distinguish observed attack volumes from contractual mitigation. Investors and owners should link route expansion to utilisation and returns. Regulators and resilience planners should examine data-centre, submarine-cable and autonomous-system concentration, without treating ownership as the only form of control.

Controls, Incentives and Decisions Shaping AS1299’s Next Decade

Arelion’s leadership challenge is not a choice between “network” and “business.” The network is the business; every technical decision locks in years of capital, supplier and customer obligations. The control structure is highly distributed: Polhem Infra controls ownership and investment; management allocates capital and product priorities; engineering and operations control routing and capacity changes; peers decide settlement-free relationships; data centres and access partners control portions of the physical path; customers control prefixes, demand and multihoming; cloud providers control the far side of the on-ramp.

The strategy works only when these powers align.

Decision one: invest in physical diversity before marketing coverage

Arelion should measure diversity at the submarine-cable, duct, landing-station, data-centre and power layers, not just in the logical topology. A new PoP or new route may improve apparent coverage while sharing hidden failure domains with older paths. The irreversible risk is long-term investment in infrastructure that cannot deliver on higher-layer resilience promises.

Leadership should embed physical-diversity evidence into capital approval and customer design. This may raise costs or slow some rollouts, but it lowers the risk of a single incident hitting multiple products and protects the credibility of the global map. Even when asset ownership is opaque, trust can be built if the operator can demonstrate failure-domain control.

Decision two: protect interconnection neutrality while monetising direct reach

AS1299’s moat depends on customers and peers continuing to see it as a trusted exchange partner. Product growth must not distort routing policy to the point of damaging that trust. Commercial pressure could push toward aggressive preference, excessive reliance on large accounts, or neglect of routes that look low-margin but are topologically important.

Management should cleanly separate settlement-free peering policy, customer transit policy, security intervention and product traffic engineering. The second-order benefit is easier incident diagnosis and stronger counterparty trust; the third-order failure risk is losing direct relationships that cannot be recovered merely by buying more fibre.

Decision three: demand activation evidence for the AI portfolio

AI Direct provides credible language for high-capacity inter-data-centre demand, but it could also become a container for relabelling ordinary routes. Management should govern the portfolio by route availability, lit ports, named use cases, utilisation, protection demand and renewal behaviour.

This prevents capital from chasing market heat without customer evidence, and allows a sharper distinction between training data, inference traffic, replication and cloud-access demand. The irreversible risk is overbuilding corridors and optical capacity on the back of forecasts that do not materialise.

Decision four: turn security evidence into a closed operational feedback loop

DDoS reports give Arelion a valuable attack vantage point. Leadership should connect them to capacity planning, customer architecture, scrubbing placement, false-positive review and post-incident learning. Publishing only peaks rewards “biggest number”; publishing mechanism and outcome enables service improvement.

A stronger feedback loop would separate observed attacks, mitigated attacks, customer impact and the role of blackholing. This helps both customers measure risk and owners judge whether security capital is protecting revenue. The long-term outcome of limited public evidence evidence is that SecureConnect becomes commoditised into a label.

Decision five: make partner coverage governable

Access partners are indispensable for global enterprise delivery, but responsibility can be scattered across multiple contracts. Arelion should embed partner selection, service inventory, incident data, physical diversity and exit rights into the product architecture. Customers need to know which segments are direct, managed or merely coordinated.

Well-governed, the second-order effect is market expansion without equivalent self-build; poorly governed, the third-order effect is one local supplier damaging a global backbone’s reputation. Some failures may lie outside Arelion’s physical control, but they should not be outside its evidence and escalation control.

Decision six: disclose enough economic information to maintain institutional trust

Private ownership gives Arelion flexibility, but makes it harder for customers, partners and infrastructure stakeholders to assess leverage, capex and customer concentration. Improving trust does not require full public-company reporting. Management and shareholders can disclose consistent operational investment, capacity activation, resilience and sustainability metrics while protecting contract-sensitive information.

Better disclosure would make route announcements more meaningful and reduce the temptation to treat interconnection rankings as a proxy for financial health. It would also discipline internal capital allocation through comparable results. The risk of sustained opacity is that, under market stress, counterparties will adopt their own—often harsher—assumptions.

Second-Order Effects of Successful Execution

If Arelion converts patient capital into physically diverse capacity, keeps peering trust and lifts high-value service attach rates, AS1299 becomes more than a commoditised Transit path; it turns into a neutral wide-area platform for clouds, enterprises, carriers and distributed AI. That would improve customer retention, capacity forecasting and the economic logic of security investment.

Success would also affect the surrounding ecosystem: access partners gain traffic and pressure toward higher standards, data centres see increased interconnection value, cloud providers obtain enterprise reach, IXs gain remote entities, and customers get an alternative to concentrating all transport in a single hyperscaler. The benefits are distributed, so no single actor controls the entire outcome.

Third-Order Effects of Failure

A severe routing-policy error or hidden physical concentration could hurt multiple products at the same time. Customers would move traffic, peers would reassess trust, security services would lose credibility, and owners could face greater capital needs when revenue is threatened. A highly interconnected infrastructure can propagate reputational loss as fast as it propagates packets.

Long-term capital constraints act more slowly but more persistently. Delayed optical-system and PoP upgrades lengthen paths, increase partner reliance and reduce attractiveness to high-capacity customers. Once direct relationships and anchor customers drift, rebuilding can take years.

Irreversible Risks

The hardest-to-reverse risks include losing settlement-free peering relationships, locking into physically correlated routes for the long term, missing a generation of hardware upgrades, becoming over-reliant on a single customer segment, and a security incident that exposes weak operational control. A brand can be repaired; lost routing positions and long-term infrastructure contracts can persist.

Leadership should distinguish between reversible product experiments and irreversible network commitments. A portal feature can be changed; fibre rights, landing-station dependencies and optical architecture lock in for years. A promotion can be ended; peering relationships damaged by policy abuse may not recover on demand.

The Renewal Economy Sits Between Physical Ownership and Contractual Control

Arelion’s renewal burden does not fall only on assets it directly owns. The reality of a global backbone is that physical ownership, long-term rights-of-use, leased capacity, data-centre contracts, cross-connects, submarine-system shares and local-access agreements together make up the service chain. Even when a piece of fibre is not owned by Arelion, once it is included in a commercial service under AS1299, the operator still has to manage contract duration, capacity upgrades, supplier replacement, fault escalation and redundancy design.

Renewal is therefore not simply “replacing equipment”; it means renewing technology, contracts and control rights at the same time. If the equipment on a route still has headroom but the site contract is about to expire, or a supplier no longer supports the needed port speed, the operator may still be forced to migrate. Conversely, a long-term contract may still be valid but become unsuitable for next-generation capacity because of optical-layer efficiency, power consumption, protection method or changed customer demand.

This structure explains why network capex and opex cannot be fully understood in isolation. Building new optical paths, refreshing routers or expanding PoPs are clear capital decisions, but maintaining a global Tier-1 also involves ongoing data-centre charges, power, cross-connects, maintenance, staff, licences and third-party access. A segment that looks “asset-light” does not automatically become low-risk; it merely converts part of the capital obligation into a contractual one.

For a buyer, the real question is not whether a particular asset sits on Arelion’s balance sheet, but whether Arelion has enough contractual rights, operational control, monitoring capability and fallback options to maintain service when something breaks or needs upgrading.

This also makes supplier selection part of the network architecture. Router platforms, coherent optics, line systems, data centres and local-access suppliers all have different lifecycles. A vendor exiting a product line, software going end-of-support, a generational change in optics, power constraints or tight data-centre power can force a network redesign without any brand change. AS1299’s routing identity can stay stable, but the equipment and contract mix that supports it will keep changing.

Arelion’s competitiveness therefore depends on carrying out those replacements with minimal customer friction, while avoiding the creation of new shared failure domains that concentrate multiple services.

Stable Routing Identity Does Not Mean Renewal Cycles Stop

The stability of an ASN can create an illusion: as long as AS1299 exists and retains Tier-1 status, the underlying network appears to be a piece of permanent infrastructure. In reality, the routing identity is only the outermost continuity. Inside the backbone, multiple renewal cycles run at different speeds.

Customer traffic and business mix can change month by month or quarter by quarter; router software and security policies are continuously updated; ports and optics are upgraded as capacity needs dictate; major router platforms may be replaced on multi-year cycles; data-centre, power and long-haul circuit contracts have their own renewal dates. Submarine routes, duct rights and long-term fibre arrangements can last even longer. Arelion has to mesh these cycles together so that ageing in any single layer does not become the bottleneck for the whole service.

The difficulty of this continuous renewal is that customers want a stable service, not a sense of every internal migration. The operator needs to shift traffic and equipment without disrupting BGP sessions, radically altering paths, or creating capacity congestion. Bringing up a new router is not just a hardware installation; it involves routing-policy replication, filter validation, community behaviour, RPKI handling, telemetry, traffic engineering, failure fallback and customer maintenance windows. Optical-layer renewal likewise requires handling spectrum, amplification, protection and cross-equipment compatibility.

The more frequent the renewal, the more critical change-management capability becomes; renew too little, and technical debt and concentrated-upgrade risk build up.

Therefore, Arelion’s long-term value cannot be judged only by a network-scale snapshot. The 80,000 km, 350+ PoPs or an interconnection ranking describe only a point in time. The more meaningful questions are: how much of these assets has already been upgraded to target capacity; do critical paths have next-generation headroom; are equipment and contracts being renewed within a manageable timeframe; is capacity addition keeping pace with customer consumption; and does the upgrade process preserve routing and security stability?

For a long-term infrastructure investor, renewal capability is itself part of asset quality, because a backbone that is not renewed does not stand still—it gradually falls behind relative to customer demand and competing networks.

Buyers Should Verify the Service Demarcation, Not Just the Tier-1 Label

The easiest mistake for an enterprise or network buyer evaluating Arelion is to treat AS1299’s Tier-1 status as a uniform quality certificate for the whole service. Tier-1 only describes part of the core routing relationship. A real order may start at the customer building, pass through a local access partner, a data-centre cross-connect, an Arelion PoP, the AS1299 core, a submarine or long-haul optical path, and then into another carrier, an IX or a cloud on-ramp. Each boundary may be controlled by a different party, with different SLAs, repair processes, visibility and change windows.

The service’s final performance depends on the weakest or slowest link, not just on the core backbone’s status.

Procurement should therefore capture “who controls what” into a verifiable design. Buyers need to confirm the local tail supplier, physical route diversity, data-centre power and cross-connect dependencies, whether protection paths genuinely use separate ducts, where the DDoS scrubbing inlet sits, how a cloud-side fault is escalated, and who has the right to switch during planned maintenance. For multi-homed customers, they should also check how AS1299’s path policy interacts with another transit operator, and whether there are shared submarine cables, shared data centres or common local access that create apparent redundancy.

Only when these boundaries are clearly described can the core Tier-1 advantage translate into end-to-end resilience.

Contracts also need to align with technical boundaries. A customer may buy a single global master agreement, but the service commitment is not identical across countries, PoPs and access methods. A 400G port on a direct Arelion PoP and an enterprise-access circuit delivered via a local partner do not have the same failure modes, even if they sit under the same commercial account. Writing those differences into the design, acceptance and monitoring upfront reduces the risk of discovering unclear responsibility boundaries only after an incident.

For a large customer, this kind of due diligence is a better predictor of real-world operational experience than simply asking “Are you Tier-1?”

Renewal Must Preserve Capacity, Policy and Operational Memory at the Same Time

Network renewal has a frequently overlooked dimension: knowledge continuity. A global backbone is not just hardware and contracts; it also depends on the engineering team’s understanding of historical routing choices, exception configurations, facility constraints, bespoke customer requirements and failure patterns. The brand change from Telia Carrier to Arelion did not automatically reset that knowledge; the continued existence of the Twelve99 name itself reflects that technical systems often outlive corporate brands.

As people move, platforms are replaced and automation grows, the operator needs to convert knowledge that once lived in individual experience into repeatable configuration, documentation, telemetry and change processes.

Automation can reduce manual errors, but it also speeds up their propagation. If a policy template, community handling or configuration-generation logic is flawed, automation can rapidly replicate it across many nodes. Renewal therefore cannot only pursue faster provisioning; it must also build staged roll-out, rollback, independent validation and anomaly detection. For a global network like AS1299, controlling the change radius is as important as increasing the change velocity. The hallmark of mature operations is not “no mistakes ever,” but that mistakes can be contained, detected, explained and rapidly recovered.

This operational memory also affects capital efficiency. If the engineering team can accurately identify which paths are truly congested, which devices are risk-concentration points and which customers need high-availability designs, upgrades can be targeted more effectively. Conversely, if assets, dependencies and failure history lack a unified record, capital may be directed toward segments that look important but are not the real constraint, while the true bottleneck stays in the tail, the data-centre power or the shared optical path.

Continuous renewal is therefore also continuous learning: every incident, capacity expansion and customer deployment should improve the next round of investment and design judgement.

The Commercial Value of Network Renewal Comes from Deliverable Outcomes, Not the Volume of Announcements

Arelion’s route expansions, 400G products, AI Direct, DDoS reports and regional investments all show that the company is active, but commercial value is only created when customers actually gain new capabilities. A new PoP becomes a saleable service only after cross-connects, ports, backhaul capacity and support processes are connected; 400G becomes revenue-generating only after the end-to-end path meets technical conditions and customers light it; AI Direct moves beyond marketing positioning only when data is actually moving between facilities at scale and generating paid demand.

Public announcements can be a leading indicator of renewal, but they cannot substitute for delivery evidence.

This distinction is especially important for a privately owned Arelion, because outsiders lack detailed revenue by product, capital expenditure and utilisation data. Without those figures, it is tempting to substitute announcement counts, network rankings or customer totals for economic analysis.

A more reliable approach is to track verifiable operational transitions: whether new routes open on schedule, whether ports are lit, whether customers deploy publicly, whether service scope widens, whether performance metrics improve, whether security events are effectively contained, and whether upgrades reduce shared failure domains rather than increase them. These signals still do not replace financial statements, but they are closer to actual asset quality than marketing cadence.

From a long-term capital perspective, the most important thing is not how many projects are announced each year, but whether the renewal pace matches demand and risk. Too slow, and competing networks gain capacity, route and automation advantages; too fast, and idle ports, excessive optical capacity or complex supply-chain commitments may build up. Arelion’s task is to convert capital deployment into saleable, monitorable, recoverable services, and to make that conversion repeatable across multiple technology generations.

Only then will AS1299’s historical accumulation continue to produce future value, rather than merely retaining a technically respected label.

Capacity Planning Must Distinguish Nominal Speed, Saleable Capacity and Failure Headroom

For a global backbone like Arelion’s, a port’s nominal speed and genuinely deliverable capacity are not the same thing. A 400G interface means the equipment or a particular service path supports that rate; it does not mean the same route can unconditionally deliver 400G under normal, maintenance and failure conditions. The operator must simultaneously consider link utilisation, protection paths, traffic bursts, DDoS scrubbing demand, planned maintenance, optical-layer headroom and shared equipment capacity.

Even if the primary path has plenty of idle capacity in normal times, if the backup path cannot absorb the shifted traffic during a single fault, the service still carries capacity risk. Mature capacity planning is therefore not a simple subtraction of sold bandwidth from port speed; it judges, by failure scenario, whether the network can still meet its contractual commitments under abnormal conditions.

The same distinction applies to PoP and regional expansion. A new PoP may have routers and customer interfaces, but it can be temporarily constrained by back-end long-haul capacity, wavelength availability, data-centre power or local cross-connect delivery. Announcing “we are in a market” is only the first step; true commercial maturity depends on whether that location can sustainably carry customer growth and maintain service when a neighbouring path or piece of equipment fails.

For AI Direct or other high-capacity services, this issue is even sharper, because a small number of large customers can quickly change the load profile of a corridor. High-bandwidth customer growth does not add a little traffic linearly; it can demand new wavelengths, router ports, data-centre power and protection capacity in one large step.

Operators also have to manage the gap between “sold capacity” and “actual traffic.” Many services are sold on a committed bandwidth or a port capability, but customer utilisation may stay well below the ceiling for long periods. Shared infrastructure can therefore improve economics through statistical multiplexing, but multiplexing cannot assume that all customers will never peak at the same time. DDoS, cloud migrations, software releases, major live-streaming events or failovers can all cause multiple customers to increase traffic simultaneously.

Capacity models need to be continuously updated using real telemetry, customer growth trends and failure exercises, not static over-subscription ratios. Whether Arelion can turn a large network into stable commercial service depends heavily on this invisible capacity discipline.

Buyers should also understand the hierarchy of capacity commitments. A 100G or 400G interface can represent a physical port capability, a contractual ceiling, a guaranteed bandwidth or a burstable upper limit; different products mean different things. Capacity boundaries also differ for wavelength, Ethernet, Transit, Cloud Connect and DDoS services. If a procurement document only records “speed” without noting congestion policy, protection mode, failure conditions and measurement method, it cannot accurately assess risk.

For a highly interconnected network like AS1299, the real advantage is not having a lot of high numbers; it is the ability to turn those numbers into stable, interpretable, recoverable services under both normal and abnormal conditions.

Contract Renewal, Supply Chain and Technology Generations Together Determine the Next Round of Renewal

The renewal rhythm of a global backbone is also shaped by contracts and supply chains. Routers, optics, line systems, data centres, cross-connects, submarine capacity and local access often come from different suppliers, each with its own procurement cycle, lead time and replacement risk. A generation of equipment may be performant enough, but that does not mean its supply chain is stable; a vendor may still offer support, but that does not guarantee new capacity can be delivered on time in the places it is needed.

Delivery delays for chips, optics, chassis, power hardware or on-site construction can push a well-planned network project behind market demand. For Arelion, renewal capability is therefore not only “willingness to invest”; it also includes the ability to lock in equipment, sites and construction resources ahead of time, while avoiding excessive reliance on a single supplier.

Technology generational transitions amplify this challenge further. A router-platform refresh may change power consumption, rack density, port architecture and software regime; an optical-system upgrade may alter available spectrum, amplifier design and coherent-module requirements; new security capabilities may need stronger telemetry and processing resources. Old and new equipment typically coexist for long periods; operations teams must maintain interoperability, not flip everything in a single big-bang replacement.

Mixed generations bring extra complexity: different devices may support different features, automation interfaces and fault-diagnosis methods, and network policy needs to stay consistent across multiple platforms. Renewing too fast raises change risk; renewing too slowly turns legacy platforms into capacity and security bottlenecks.

Contract duration also affects technology freedom. Long-term fibre rights, data-centre space, submarine capacity or local access agreements can reduce short-term uncertainty, but they can also lock the operator into certain geographical paths and cost structures. If demand moves to new cities, cloud regions or AI data-centre clusters, legacy contracts may still tie up capital. Conversely, over-reliance on short-term leases increases renewal-price and supply-stability risk.

Arelion needs to balance long-term control with flexibility so that critical backbone paths have enough certainty, while the ability to adjust service boundaries and supplier mix is preserved when demand shifts.

For a long-term owner, this supply-chain and contract management is just as important as fibre kilometres. A company can have a mature network yet be unable to renew on time because of equipment delivery, data-centre power, contractual lock-in or supplier concentration. Conversely, an operator that does not own all its assets can still remain agile if it has a multi-vendor strategy, clear alternative paths and strong procurement capability.

Judging whether Arelion is truly “continuously renewing” therefore requires looking beyond the number of announced projects to whether renewal forms a stable execution chain across supply, contracts, installation, testing and customer turn-up.

Assessing Arelion Requires Putting Routing Data, Service Data and Capital Signals Together

A peculiarity of AS1299 is that outside observers can see a fair amount of technical behaviour through public BGP data, looking-glass tools, route collectors and interconnection directories, yet see nowhere near the same granularity of commercial and financial outcomes. This can tempt analysts to mistake “observable” for “most important.” Route counts, adjacencies, path lengths and one-hop coverage do describe a network position, but they cannot directly show customer satisfaction, contract renewal, port utilisation, return on capital or whether the next upgrade cycle is already funded.

Assessing Arelion therefore requires combining different layers of evidence; technical data cannot be allowed to substitute for commercial data.

The first layer is routing and interconnection evidence. It can help judge whether AS1299 continues to hold broad direct relationships, whether unusual path changes appear, whether there have been clear routing incidents, and whether directness improves in certain markets. The second layer is service and delivery evidence: new PoPs, 400G routes, customer deployments, Cloud Connect, IX Connect, DDoS protection and actual AI Direct turn-ups. The third layer is capital and governance signals: management changes, supplier commitments, long-term investment projects, public financing and Polhem Infra’s ongoing support for the asset.

No single layer is complete on its own, but together they form a more reliable judgement framework than any single ranking.

This combined approach also guards against mistaking “the network is still large” for “the network is getting stronger.” A large network can keep an absolute scale lead while falling behind in certain critical cities, cloud on-ramps, submarine corridors or high-capacity customer segments. Conversely, a network can improve its real competitiveness without dramatically adding total kilometres, through higher spectral efficiency, more powerful routing platforms, better security systems and more direct interconnections.

The outcome of renewal must be judged by whether control capability and service quality are improving, not just whether the map is bigger.

This judgement fits Arelion’s historical structure especially well. AS1299, Twelve99 and Arelion represent, respectively, the routing identity, the technical continuity and the current corporate vehicle. The stability of the technical identity allows long-term comparison of routing data, while changes in corporate ownership require a fresh understanding of capital and governance. The most valuable analysis does not conflate the three; it watches how the same AS1299 is being invested in, expanded and operated under different corporate-governance phases.

Only then can one judge whether renewal under Polhem Infra is merely extending legacy assets or is continuously strengthening the network’s commercial deliverability.

Ultimately, the meaning of Tier-1 has to return to the actual behaviour of customers and peers. If large customers keep adding capacity, peers continue to maintain direct relationships, critical routes are steadily upgraded, security systems handle more complex attacks, partner delivery stays manageable and capital deployment matches those outcomes, then AS1299’s historical advantage is still being renewed. If the public network position looks stable but port activations slow, critical upgrades are deferred, incidents expose repeated concentration risks or customers gradually shift away, the technical label can lag commercial reality.

The focus of ongoing assessment is therefore not to prove whether Arelion “is Tier-1,” but to judge whether its Tier-1 position is still underpinned by a system that is continuously renewed, deliverable and capital-backed.

The Ultimate Measure of Continuous Renewal Is Whether Customers Get a More Controllable Network

For a customer, renewal itself is not the value; the value is the control that follows it. Higher capacity only genuinely improves the service when the path is verifiable, failover is predictable, maintenance windows are transparent, DDoS response is clear, and cloud and IX boundaries are well defined. Arelion’s engineering investment must therefore be continuously translated into outcomes customers can understand and verify: more stable delivery times, clearer fault ownership, more observable routing behaviour, more consistent cross-region service, and expansion paths that can be planned ahead when demand grows.

This is also the most direct way to judge whether AS1299 stays competitive. If customers must rely on heavy exception processes to get standard service, or every capacity expansion exposes new suppliers and delivery bottlenecks, network scale alone cannot offset operational friction. Conversely, if Arelion can maintain a consistent service demarcation across multiple equipment generations, multiple partners and complex international paths, and hide the upgrade process behind a stable customer experience, the historically built Tier-1 advantage will continue to translate into commercial value.

Continuous renewal is ultimately not about making the network look newer; it is about giving customers predictable, manageable, recoverable connectivity under higher capacity and greater complexity.

This standard also lets different products be compared under the same logic. Whether it is Transit, Ethernet, wavelength, Cloud Connect or SecureConnect, what the buyer really needs is a clear control boundary, measurable performance and an executable recovery mechanism. Product names can change and the service catalogue can expand, but if those underlying capabilities are not also strengthening, renewal remains superficial. For Arelion, the value of continuous renewal ultimately shows in whether AS1299 can keep delivering consistent, transparent and recoverable connections under more demanding conditions.

This also means that Arelion’s network renewal should not be understood merely as technology replacement; it should be seen as a long-term operational capability to continuously maintain global service credibility, capacity availability and a sense of customer control.

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 inherited this system; they did not start from zero. Their task is to renew it without destroying the trust that was accumulated under the former identity.

The decisive test is disciplined conversion. New routes must become diverse, usable paths; new ports must turn into customer traffic; AI positioning must become activated services; DDoS visibility must become protected availability; partner coverage must become governable delivery; private capital must become timely upgrades rather than hidden risk. As long as these conversions hold, the Tier-1 status continues to have economic meaning; when they fail, the label often outlives the advantage it once described.