Arelion's AS1299: Tier-1 reach demands constant renewal

Summary

• Arelion is the private operator formerly known as Telia Carrier; Twelve99 remains a technical and historical identity, while AS1299 carries its global routing identity.
• AS1299 reaches the entire internet through customer routes and settlement-free peers, but Tier-1 status guarantees neither the shortest path, the best support, nor immunity from incidents.
• IP transit and dedicated internet access sit alongside Ethernet, wavelengths, managed optical networks, cloud and exchange connectivity, DDoS mitigation, mobile, voice and AI Direct.
• Routes, fibre, points of presence, peers and accumulated know-how create the advantage; continued funding of capacity, security and expansion remains the burden, without standalone public accounts.

Four names describe four different layers

The business was born inside the Telia group and operated for a long time under the names Telia International Carrier and then Telia Carrier. Polhem Infra completed the acquisition of Telia Carrier on 1 June 2021, transferring control away from Telia Company. The carrier adopted the name Arelion in January 2022. These dates divide the company's history: references to Telia ownership are accurate before the completion, but no longer describe the current company.

Twelve99 did not disappear with the rebranding. That name remains visible in the technical domain twelve99.net, notably in the public looking glass, and stays associated with AS1299. This continuity is useful to engineers, because autonomous system numbers, hostnames, route filters, customer configurations and operational references often require more stability than a commercial brand. It does not create a second company. Twelve99 represents technical continuity; Arelion is the current commercial and institutional identity.

AS1299 constitutes yet another layer. It is the autonomous system identity through which the backbone originates, receives, selects and announces routes. An ASN is neither a legal entity nor a physical cable. It designates a routing domain whose policy is expressed through routers, points of presence and interconnections. Arelion operates this domain, while the underlying paths may run over fibre subject to different ownership and contract regimes.

This four-part distinction — former brand, current company, technical hostname and routing system — avoids several common mistakes. It prevents historical continuity from becoming a false claim of ownership, stops a technical identifier from being treated as a subsidiary, and forces network numbers to be attributed to the company that publishes them. It also reveals the central theme of Arelion's story: corporate control changed faster than the operational identity of the backbone.

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

The phrase "Tier-1 backbone" compresses several realities into a single label. At the routing level, a Tier-1 autonomous system can reach the entire internet using routes learned from its customers and settlement-free peering agreements with other large networks. It does not need to buy upstream transit to obtain general global reach. This position is important because it removes one category of provider dependency and allows the network to sell full-table transit in turn.

It must, however, be maintained: peers can change policies, traffic flows can shift, and the carrier must keep enough capacity and direct relationships for the settlement-free exchange to remain mutually acceptable.

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

Arelion's current profile makes this distinction especially visible. The commercial proposition is not limited to the global reach of AS1299. The company states that it can convert that reach into IP transit, private packet transport, optical services, cloud and exchange access, network-level security and operational support. Buyers therefore encounter the Tier-1 status through a contract whose value depends on demarcation, geography, capacity, routing policy and the ability to repair faults.

From the lineage of a national incumbent to an international carrier

Arelion traces the organic development of its backbone to 1993. The network grew inside Telia's lineage, but its operating logic was international. A national telecom operator serves consumer, mobile and business customers in a domestic market. An international carrier must connect other networks across borders, install routers in neutral sites, acquire long-distance paths, maintain optical capacity and negotiate interconnection with organisations that may also be competitors.

This difference helped make Telia Carrier separable from its former parent. By 2020, the carrier had customers and infrastructure relationships well beyond Telia's national business. Telia Company agreed to sell it to Polhem Infra in October 2020; the acquisition completed the following June. It is the completed transaction, not its announcement, that marks the transfer of control. Polhem Infra's narrative also mentioned maintaining a strategic network relationship with Telia, evidence that capital independence did not erase commercial interdependence.

The 2022 rebranding gave the independent carrier a name that no longer pointed to its former owner. The underlying asset was not a newly assembled network. It was a mature backbone whose fibre routes, points of presence, customer connections and peering relationships had accumulated over decades. This reality matters, because direct connectivity cannot be replicated by simply installing a software control plane. A new entrant can quickly lease capacity and open ports in some markets; it cannot instantly recreate the history of direct routes, operational trust and restoration practices of a long-standing global network.

Independence also changed the investment question. Inside Telia, the carrier competed for capital within a diversified telecom group. Under Polhem Infra, it became a specialised infrastructure holding, funded through Swedish pension capital. This structure can favour long-term investment, but it does not remove return targets nor make funds unlimited. It changes who decides, how the asset is presented and what information observers can access.

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

Arelion reports more than 80,000 kilometres of fibre, over 350 points of presence and services in 129 countries. The company also reports more than 2,000 customers and about 450 access partners. These figures describe different layers and must remain attributed to the company. Kilometres of fibre relate to physical reach; PoPs relate to interconnection and service locations; countries describe commercial availability; access partners extend delivery beyond direct sites. Adding them together would yield no coherent measure.

The physical chain can include fibre owned by Arelion, controlled through long-term agreements or leased as capacity; optical systems installed on that fibre; routers and switches; colocation space and power; cross-connects to customers and peers; capacity on submarine systems; cloud on-ramps; and local access circuits provided by other carriers. Arelion can control the service and routing policy while sharing physical failure domains with its suppliers. "Global backbone" describes an operational system assembled under several forms of control, not proof that one company owns every trench, cable and building.

The distinction is operational, not semantic. Two logical routes can appear diverse on a diagram while traversing the same duct or submarine cable. Two services can be sold separately while sharing a router, an optical line system or a site power feed. Conversely, leased infrastructure can be highly resilient when the contract, monitoring and physical diversity are well designed. Ownership alone does not answer the question of reliability; the relevant evidence concerns the failure domain and the provider's ability to observe and restore it.

Arelion's commercial platform therefore starts with mastery of a chain. The company must know which segment belongs to its backbone, which depends on a site, which is provided by an access partner, which endpoint is controlled by a cloud provider and where the contractual SLA changes. The customer sees a single order and a single support relationship, but the underlying incident can span multiple organisations. Part of the carrier's value lies in making this chain manageable without claiming it is unique.

Fibre provides the path; optics provide usable capacity

Fibre length is a geographic measure, not a capacity measure. One fibre can carry varying numbers of wavelengths, and each wavelength can be upgraded with newer coherent optics and line systems. The same physical route can therefore carry far more traffic after an equipment refresh, without needing a new trench. Arelion's programme around 400G and higher speeds belongs to this optical layer, where transponders, coherent modules, amplifiers and spectrum engineering turn glass into active transport.

A wavelength service provides the customer with a dedicated optical channel on a qualified route. It suits predictable, high-volume movements such as data centre interconnect, replication or carrier aggregation. The customer obtains a crisper capacity boundary than in public IP transit, even though the wavelength still depends on the physical fibre, optical equipment and route protection. The word "dedicated" concerns the channel; it should not be extended to the idea that the customer owns a physically isolated cable.

Arelion also sells dark fibre and a Managed Optical Fiber Network. The managed offering shifts more design, equipment and operations responsibility to the carrier. For a large enterprise, a cloud operator or a service provider, this can avoid building an optical engineering team for each route. In return, the customer depends on Arelion's supported geography, supplier choices, restoration process and lifecycle decisions.

Optical services also show why the carrier cannot treat an old backbone as a finished asset. Traffic grows, interfaces move to higher speeds and customers expect new paths to clouds and data centres. Each upgrade consumes capital before demand is certain. Limited public evidence capacity can cause congestion and poor service; excessive capacity can tie up optics, ports and contractual commitments. A carrier's financial discipline therefore plays out in capacity planning long before the customer sees a speed change.

Points of presence turn long-haul capacity into a market

A point of presence is where backbone capacity becomes available for interconnection. It can house routers, optical systems, switches, customer ports and cross-connects inside a data centre or carrier hotel. A dense PoP map can reduce the distance between Arelion and customers, peers, clouds and exchange points. It also exposes operations to the power, cooling, physical access and cross-connect procedures of those sites.

The reported total of over 350 PoPs is a scale indicator, not proof that every product and every port speed exists at every site. One location may provide IP transit but not a given wavelength route; 400 Gb/s Ethernet requires technical validation; a cloud connection depends on the provider's on-ramp; and a remote enterprise site may need a partner loop. The right buying question therefore becomes "Which service is available at this demarcation?" rather than "Is Arelion present in this country?".

PoP density also influences connectivity. Direct interconnection reduces the number of intermediate networks a route may traverse, and more direct customers and peers can improve path choice. Arelion claims that 95% of end users in the US and Europe can be reached in a single network hop and describes AS1299 as the most connected backbone in the world by its metric. These claims must remain attributed, because the result depends on the dataset, definition and date. Single-hop reach does not guarantee minimal latency for every flow, and connectivity is not traffic market share.

The packet layer transports multiple products over shared infrastructure

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

Arelion's Ethernet portfolio includes point-to-point EVPL and multipoint ELAN, with speeds from 10 Mb/s to 400 Gb/s, subject to route and technical availability. Documentation describes segment routing and Flex-Algo mechanisms for certain low-latency paths within its MPLS backbone. These controls can improve determinism in the provider domain, but they do not make a local access loop or external endpoint that escapes its full control disappear.

Service-level figures make this boundary visible. Arelion publishes 99.999% availability for MPLS backbone services, 99.99% for basic PoP-to-PoP Ethernet, and 99.5% for an end-to-end service that includes managed interface equipment and an access loop. These figures are not interchangeable. The lower commitment on the broader service reflects the addition of third-party equipment and dependencies. Actual terms remain specific to the contract and route.

A customer can also run several services over one port using logical separation. This reduces cross-connect and interface costs, but concentrates services onto a single physical failure domain. A port failure can affect multiple logically distinct circuits at once. Efficient multiplexing and concentrated risk must be explained together.

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

An IP transit customer typically operates an autonomous system, announces its prefixes via BGP and receives routes to the internet from Arelion. The carrier forwards outbound traffic to other networks and returns traffic to the customer's prefixes. The product is sold in terms of reach, capacity and service, while its underlying value comes from AS1299's relationships with customers and peers.

The exchange looks simple because BGP hides the physical path behind route announcements. In operation, Arelion must maintain full tables, filter invalid or unauthorised announcements, balance flows, provision capacity, secure sessions, manage communities and restore faults across many PoPs. A multi-homed customer with a second carrier gains redundancy and path choice, but also gets a more complex routing problem. It must understand preferences, inbound traffic engineering and fault propagation at each provider.

Tier-1 economics do not mean every interconnection is free. Settlement-free peering removes payments for a defined exchange with qualified networks. Arelion continues to pay for fibre, sites, equipment, power, access, staff, maintenance and other commercial relationships. It may also buy local services or partner access where that is more efficient than building directly. The absence of upstream transit spend is only one element of the cost structure, not a cost-free network.

The carrier's routing position must also be preserved. If the flow balance, geographic reach or commercial policy changes significantly, a peer may seek different terms or end the relationship. The practical advantage 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 with it without settlement.

Dedicated Internet access shifts more routing responsibility to the provider

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

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

SecureConnect bundles internet access or transit with automated DDoS protection. This bundling reduces purchasing and configuration boundaries for customers who would otherwise contract transport and mitigation separately. The protection keeps a defined perimeter. It does not secure credentials, endpoints, application logic or attacks outside the selected network service.

BGP communities make routing policy a product component

BGP communities are labels attached to route announcements. Arelion can interpret the customer's labels and apply provider-defined actions, such as modifying preference, limiting propagation, appending AS path prefixes or triggering blackholing. They give the customer influence over the provider's network without direct access to its routers.

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

Communities also carry a failure risk. A misplaced label can remove reachability or send traffic on an unwanted path. A remote-triggered black hole deliberately discards traffic destined for a target so that the attack does not congest wider links. This action is useful in an emergency because it trades a target's availability for network stability. It is not a cost-free mitigation.

Looking glasses expose part of routing reality

Arelion's Twelve99 looking glass makes it possible to examine routes, pings and traceroutes from certain network locations. The tool answers practical questions: how does AS1299 see a prefix, which path is chosen from a given point, and where does latency appear on that view? It also preserves the name Twelve99 as a technical identity after the rebranding.

A looking glass provides evidence from one observation point, not an audit of the entire network. It does not show every alternate path, historical incident, internal preference or physical fibre route. BGP policy can vary by location, and a traceroute can hide equipment or react differently under load. The tool is most valuable when combined with customer measurements, route collectors, tickets and the provider's performance data.

Arelion also publishes monthly IP performance indicators. These reports make it possible to track provider-chosen metrics over time, although the methodology and scope remain the company's own. Transparency increases when an operator publishes operational data; independent assurance still requires clear definitions and external observations.

RPKI reduces a routing risk without fixing all of BGP

A Route Origin Authorisation allows a prefix holder to indicate which autonomous system may originate it. Origin validation then classifies an announcement as valid, invalid or not found. Filtering invalid origins reduces some hijacks and misconfigurations. Arelion's educational material presents RPKI as one part of routing security.

The mechanism verifies origin authority for covered prefixes. It does not validate the full AS path, guarantee that a peer exports routes correctly, or prevent all leaks. A valid origin can still be propagated via an unwanted path, and mistakes can affect filters, route objects or customer configurations. RPKI shrinks the trust problem; it does not replace BGP policy, monitoring or incident response.

For a Tier-1 carrier, this limitation matters, because security and availability can be in tension. Aggressive filtering can block legitimate traffic when records are wrong; weak filtering can propagate invalid announcements. The operator needs progressive policies, customer communication, exception management and up‑to‑date data. Saying "RPKI secures BGP" hides the operational judgement that still remains necessary.

IX Connect sells access to interconnection, not full Internet reach

Internet exchange points provide places where networks can establish peering. IX Connect transports a customer from an eligible Arelion site to an exchange port, enabling remote participation without building a separate local presence. The product can reduce cost and time to reach multiple peers, especially when entering a new market.

The transport does not create the peering policy. The customer must still have the required membership, compatible ports, bilateral or route-server agreements and its own filters. A remote path also adds a dependency on a router physically installed at the exchange. IX Connect is therefore an access service to a route market, not a substitute for the customer's interconnection strategy.

This product shows why a Tier-1 carrier cooperates with exchange points while also competing with them. Arelion peers there while selling the transport that gets traffic there. A customer can replace some paid transit with direct peering while buying Arelion capacity to reach the exchange or cover the rest of the internet. The boundaries between transit, peering and transport are commercial choices built on the same infrastructure.

Cloud Connect brings the backbone to a demarcation controlled by the cloud provider

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

The service terminates at a shared boundary. The cloud provider controls its virtual interface, regional availability, quotas and internal network. The customer controls its account, routes and workloads. Arelion controls the transport path it sells. A failure can be on any side, and the parties must align their configurations. Labelling the whole as "private" can be misleading if it suggests that one provider owns every component or that no shared infrastructure exists.

Cloud connectivity also changes the carrier's competitive position. Hyperscalers operate large private backbones and increasingly move traffic between their regions. Arelion's opportunity lies in connecting enterprises, data centres, multiple clouds and networks that do not share the same administrative domain. Its limit is identical: it cannot dictate what happens inside a cloud nor replace the provider's internal fabric.

DDoS defence is now part of backbone capacity planning

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

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

The 6.1 Tb/s observation must not become a guaranteed mitigation capacity. An attack can be observed on the backbone without a customer receiving the full volume, and commitments depend on architecture and contract. Effectiveness also depends on detection time, BGP convergence, scrubbing centre locations, clean-path capacity and false-positive control. Application-layer attacks can pass volumetric filters when packets look legitimate.

Remote-triggered blackholing is the emergency side of the arrangement. A community can cause traffic destined for an attacked prefix to be dropped upstream. This protects shared capacity but makes the target unavailable. Scrubbing seeks to preserve service; blackholing accepts an interruption to contain damage. A mature product needs both mechanisms, clear triggers and well-defined customer authority for the most severe response.

SecureConnect integrates mitigation into the connectivity purchase rather than leaving it as an optional system to assemble later. This can improve adoption because protection exists before the incident. The strategic test is not the bundle's name, but attachment rate, response evidence, the scope of protected services and the ability to scale as peaks rise.

AI Direct bundles long-haul transport for distributed AI systems

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

This boundary is economically important. Training inside a campus depends on a high-performance local fabric whose latency and collective behaviour cannot be replaced by a long-distance carrier. WAN demand appears when datasets, checkpoints, replicas, inference traffic or entire workloads move between sites. Arelion's advantage is its reach; its service must connect to the internal AI fabric, not become that fabric.

In May 2026, the company added 400G EVPL to AI Direct. The announcement establishes a high-capacity packet option on qualified routes, not universal availability. Arelion had also announced Danish network investments and cable landing station environments in April, presented as part of a Nordic corridor for AI. Earlier additions included North American expansion, notably a PoP in Oklahoma City, while a distribution programme in Mexico broadened commercialisation. These events show an active strategy, but the company has not published activated utilisation, customer concentration or per-project amounts.

The strongest evidence that AI Direct goes beyond relabelling would be named high-capacity customers, activated ports, recurring traffic and per-route commitments. Announcements of an "AI highway" express intent. They do not reveal what share of revenue, utilisation or new capacity is actually tied to AI workloads. The available materials support a credible transport portfolio and an investment direction, not the claim that AI has already transformed Arelion's economics.

Enterprise services monetise the backbone beyond transit

Transit prices face long-term pressure as capacity improves and buyers have alternatives. Arelion can respond by selling services that pair the same routes with more control, demarcation and support. Ethernet, Smart IP-VPN, Cloud Connect, IX Connect, managed optical networks and DDoS protection multiply the problems solved for a single customer.

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

The broad offering also increases internal complexity. Capacity reserved for private services, public transit and mitigation must be planned together. A change on an optical path can affect several packet products. A local delay can block an otherwise automated global order. Asset reuse improves economics only if isolation, change control and capacity accounting remain accurate.

Mobile data, IoT, voice and messaging services further expand the catalogue. Evidence is stronger for the backbone and connectivity; these adjacent services must therefore be presented as current offerings, without assigning them undocumented market shares. Their strategic relevance is that Arelion is not a pure IP transit wholesaler, even though AS1299 remains its defining technical identity.

Access partners extend reach while altering the SLA boundary

Arelion reports about 450 access partners. These carriers can connect a customer's building to an Arelion PoP when the backbone does not reach the site directly. The model extends coverage without requiring Arelion to build every last mile. It also gives the customer a single commercial relationship for a path assembled by multiple providers.

The access loop is often the least standardised part. Lead times, repair, bandwidth, jumbo frames, demarcation equipment and local regulation vary. Arelion can monitor and manage the loop, while the physical repair belongs to another carrier. The published availability, lower for an end-to-end Ethernet service than for a PoP-to-PoP service, reflects this exposure.

Global presence must therefore be read as delivery capability, not as a map of owned sites. For buyers, diligence means naming the local provider, identifying route diversity, understanding escalation rights and verifying whether a second access shares the same duct. A global contract simplifies governance without changing the local physics.

Operations turn network assets into usable service

A backbone is only worth what can be provisioned, observed and repaired. Arelion's customer model includes the MyArelion portal, service management and network operations support. These systems turn ports, routes, tickets, planned maintenance and performance into the customer experience.

Automation can speed provisioning and expose status, but a global carrier cannot shrink every event to an API call. Fibre repairs require field crews; a cloud endpoint may reject a configuration; a peer may change its policy; a site may require a cross-connect; a local carrier may miss a delivery date. The quality of automation includes how clearly it represents exceptions and responsibilities, not just the speed of a normal order.

Arelion reports customer experience accolades and a high NPS. These claims may reflect a deliberate service culture, but the methodology and response population are not independently audited in the provided materials. Awards and surveys must complement operational detail, not replace it.

The business model reuses an infrastructure base across multiple demarcations

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

This reuse can improve asset utilisation. A fibre route and a PoP generate more revenue when they serve multiple products and customer groups. The carrier still needs separation and headroom. If every service is planned on the same optimistic assumption, an attack or a traffic shift can reveal hidden contention. Accounting must distinguish reserved ports, normal traffic, protected traffic and failure scenarios.

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

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

Polhem Infra owns Arelion. Polhem Infra is jointly owned by the Swedish Third AP Fund and Fourth AP Fund, according to its current description. The carrier is therefore linked to national pension capital through an infrastructure vehicle. The structure matches an asset whose routes and interconnection position are built over long periods.

Long-term capital can tolerate investments whose return stretches over several years, such as fibre rights, optical upgrades and new PoPs. It can also favour stable cash generation over short-term listed-market signals. The owner still retains return obligations. Pension affiliation does not mean routes will be funded regardless of demand, and it does not reveal the share of debt, operational cash flow or equity deployed.

The governance change after 2021 was more visible than the technical change. AS1299 continued to route while board control, funding and 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 leadership page shows a team spanning strategy, commercial, legal, HR, technology and operations, but does not constitute a complete statutory register.

It would be wrong to personally attribute every architecture decision to the leadership. The backbone is the accumulated work of engineering, operations, procurement, sales and partner teams over several decades. Leadership determines capital allocation, risk tolerance, product direction and communication. Day-to-day quality depends on distributed expertise and institutional memory.

Private ownership leaves core financial questions unanswered

The materials provided do not establish standalone current revenue, profit, debt, capital expenditure, valuation, traffic volume, contract duration or customer concentration. This absence is important, because a global carrier must continually fund equipment, route rights, colocation, access and security. Product announcements show activity; they do not show returns.

Historical transaction information would describe the 2020–2021 sale, not the 2026 value. Repeating an old figure would ignore traffic, asset, capital and market changes. Equally, a connectivity ranking cannot substitute for revenue or margin. A network can be highly connected in a market where the price per bit is falling.

This opacity changes how performance should be assessed. Public BGP data and looking glasses show reachability and paths. Press releases show route and product activity. Customer announcements show some deployments. None of these sources reveal whether capital is earning an adequate return, whether a single customer dominates revenue, or whether leverage constrains the next upgrade.

The correct conclusion remains bounded: Arelion appears to be an active global carrier, with a broad portfolio and ongoing investment. The evidence provided does not permit an estimate of profitability or a claim that the pension ownership guarantees the next capital cycle.

The economics of renewal sits between physical ownership and contractual control

The investment question is more complex than the choice between owning or leasing a specific route. A Tier-1 carrier must maintain several forms of control simultaneously. Fibre ownership gives direct authority over a physical path, yet still leaves dependencies on permits, power, repair crews, landing stations and equipment suppliers. Long-term fibre rights can resemble ownership in operational planning while locking in multi‑year contractual commitments. Shorter capacity contracts preserve flexibility, but expose the carrier more to renegotiation, pricing and provider availability.

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

This distinction matters because a network's economics are formed before the service is sold. Arelion may need to install line systems, routing capacity, cross-connects and reserve headroom before a new customer firmly commits its traffic. Opening a PoP can require site contracts and equipment while the business case still rests on future demand. A high-capacity corridor intended for AI uses may look compelling at the market level while each buyer still does not know where its long-term workloads will sit. Capital therefore arrives before some of the revenue evidence that is supposed to justify it.

The same timing problem applies to resilience. A backup route is valuable precisely when the primary fails; some of its capacity can therefore appear underused in normal operation. Finance teams may see idle headroom where operations see protection. The network must decide how much apparently free capacity is economically justified by the contracts and failure scenarios covered. Too little reserve can turn a fibre cut or equipment failure into customer loss; too much reserve can degrade returns if reliability is not priced in.

Arelion's broad portfolio makes this calculation harder, because the same physical and packet infrastructure supports products with different load profiles. Transit can vary sharply and face price pressure. Ethernet and wavelengths can carry large contractual flows. DDoS protection requires capacity that may sit lightly used until an attack day. Cloud connections depend on the location and growth of external platforms. A planner cannot therefore simply add traffic averages.

They must model correlated peaks, protection failovers, maintenance windows and the possibility that several services converge onto the single remaining path during an incident.

The expanded positioning of AI Direct in 2026 adds another uncertainty. Arelion has a credible reason to present high‑capacity Ethernet and optical services as transport infrastructure for distributed AI systems, because data movement between sites creates real WAN demand. But AI-related demand does not remove the ordinary investment discipline of a carrier. The route must connect real sites, ports must be activated, customers must pay for capacity and traffic must last long enough to justify equipment and contractual commitments. A popular market does not turn unused capacity into return.

Supplier strategy also shapes the renewal cycle. Routing and optical platforms are not interchangeable without cost. A major refresh can create years of operational familiarity, spares management, software dependencies and vendor support. Open line systems and coherent modules can reduce some lock‑in by separating certain layers of the optical stack. Interoperability must still be designed and tested. Optionality is only valuable if the carrier retains the skills and procedures that actually enable its use.

Sites create a comparable form of dependency. A PoP becomes more valuable as customers, peers and clouds connect there; that density also makes moving more difficult. Cross‑connects, customer equipment, maintenance procedures and commercial relationships accumulate around the location. A data centre can therefore gain bargaining power even if Arelion owns the routers installed inside. The practical question is whether alternative sites, route diversity and sufficient commercial leverage exist so that one building or operator does not become a hidden strategic bottleneck.

That is why the financial opacity linked to private ownership matters in an infrastructure profile. Without current capex, debt, lease commitments and cash flow figures, observers do not know whether renewal is funded from operating cash, owner equity or debt, nor how much headroom remains for the next hardware generation. Technical announcements show that Arelion is investing. They do not show whether the same pace can be sustained if prices fall, demand slows or resilience needs increase.

The strongest external evidence is therefore cumulative. Routes that are actually completed and not merely announced, new PoPs where customers appear, modern interfaces that are genuinely orderable, direct relationships that stay stable and security systems that can absorb larger peaks are all signs of an owner that continues to fund the network. None of these alone proves profitability. Together they show whether capital is being turned into an operational system capable of preserving the economic relevance of AS1299.

For Arelion, the renewal obligation is inseparable from the advantage. Part of this value comes from a network position accumulated over more than three decades. That position saves customers from having to assemble comparable global reach themselves. It also creates an installed base that must be continuously modernised. The more valuable AS1299 becomes as a neutral global path, the greater the potential cost of deferred investment. Tier-1 status therefore brings both bargaining power and a permanent capital obligation.

Geography is a map of services, routes, and dependencies

Arelion's roots and ownership are Nordic, while the backbone spans Europe, North America and Asia. The company reports services in 129 countries. This figure describes commercial reach, not a count of owned fibre systems or direct PoPs. A buyer needs three maps: its own and site infrastructure, delivery via partners, and technical availability of the specific service.

Europe remains a dense part of the network lineage. North America is a large transit and enterprise market, and additions such as Oklahoma City have been positioned around cloud demand and AI data centres. The 2026 Danish investment concerned routes and a landing station environment important for the Nordics and submarine links. In Mexico, route development and the distribution programme broadened access to a growth market. The file provides less public detail for Asia than for Europe and the US.

Submarine connectivity deserves separate treatment. Arelion can buy spectrum or capacity, install equipment in landing stations and operate an end‑to‑end service without owning the entire system. Cable faults, station incidents and shared terrestrial backhauls can affect multiple carriers. Logical diversity must therefore be tested at the cable and duct level.

Geopolitics can also alter route economics. Cross‑border regulation, sanctions, permits, cable security and national resilience policies influence where to build and how customers assess risk. The file does not document current litigation specific to Arelion; these factors must therefore be presented as structural constraints, not as allegations.

Competition plays out on multiple layers simultaneously

At the Tier-1 and global transit level, Arelion faces networks such as NTT, Lumen's Level 3 lineage, GTT, Tata Communications, Cogent and Sparkle. A direct comparison requires dated data on routing relationships, geography, latency, capacity, security, support and price. A single connectivity ranking is not enough.

On the physical and optical layer, firms such as Zayo compete for fibre and wavelength demand. On cloud connectivity, Megaport and Equinix Fabric offer software‑defined interconnection through partners and sites. On the enterprise layer, regional carriers, SD‑WAN providers and managed services can assemble alternatives around the internet. These categories overlap without being identical.

The private backbones of hyperscalers pose another challenge. A cloud provider can internalise traffic between its regions and bundle transport with compute. Arelion remains useful when a customer must connect clouds, enterprises, data centres and networks outside a single provider's control. The more traffic stays within hyperscaler domains, the more some wholesale opportunities shrink; the more workloads are distributed, the more neutral reach becomes valuable.

Exchange points can complement and partially replace transit. A large enough network can set up direct peering to its major destinations and buy less transit. It still needs reach to the rest of the internet, transport to exchange sites and support. IX Connect and transit place Arelion on both sides of this decision.

Arelion's durable advantage is not the impossibility of copying a component. Fibre, routers, cloud on‑ramps and DDoS systems can be acquired. The combined system — routes, peer relationships, customer prefixes, PoPs, optical paths, support and reputation — takes years and continuous investment.

Direct connectivity creates both resilience and contagion

A highly connected backbone offers more path choice and direct reach. It can bypass intermediate networks and shift flows during failures. The same position enlarges the number of organisations exposed to its mistakes. A route leak, a filter error or a capacity incident can propagate beyond direct customers, because other networks depend on the routes learned via AS1299.

Physical concentration presents the same dual effect. Dense PoPs improve interconnection, but a site failure can affect multiple services. A logically diverse topology can share a duct. A DDoS platform protects, but a diversion policy error can move much legitimate traffic. Scale magnifies both capacity and impact radius.

Resilience therefore depends on controls less visible than maps: maintenance discipline, progressive configuration, route filters, RPKI validation, community governance, optical protection, capacity reserves, scrubbing placement, out‑of‑band access, incident communication and tested rollback. Arelion's public tools and product pages establish elements of this system, but the file contains neither a full incident history nor an independent audit.

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

Sustainability claims demand rigorous denominators

Backbone growth consumes equipment, energy, colocation, construction and maintenance. New coherent optics can increase capacity per watt and per unit of space. This efficiency can coexist with rising total consumption if traffic and footprint grow faster. Arelion publishes a sustainability framework, but the evidence provided does not contain a full, audited footprint of the network and the chain.

The responsible treatment is to separate efficiency from absolute impact. An upgrade can reduce energy per bit; a new route can increase equipment and power. Leasing infrastructure shifts some emissions and consumption to suppliers, without removing them. Without consistent scope, baseline and traffic data, sweeping claims of net improvement would be unfounded.

Sustainability is strategic because customers and pension-linked owners may seek credible evidence on energy, procurement and resilience. It is also operational: optical density, cooling and power availability determine where capacity can be installed. Whether reporting becomes granular enough to link expansion to measured resources needs watching.

What public evidence cannot show

The scale figures in this profile are primarily current Arelion claims. The file contains no route‑by‑route audit of the 80,000 kilometres, no uniform definition of each PoP and no complete inventory of owned versus leased infrastructure. Nor does it contain a comparable traffic series across competitors.

The connectivity ranking depends on the metric. The claim of 95% single‑hop reach describes reported reach in the US and Europe, not a guarantee for every destination, protocol or instant. Monthly reporting is useful but provider‑selected. A buying decision still requires specific testing and contractual terms.

Product availability is conditional. Ethernet rises to 400 Gb/s; this does not mean every site, loop or route can deliver 400G. AI Direct is a connectivity suite, not proof of AI revenue. An attack observed at 6.1 Tb/s does not reveal contractual scrubbing capacity. MEF/Mplify certification supports confidence in service definition, not every access loop or incident outcome.

The financial void is wider. Revenue, margin, debt, capex, valuation and customer concentration remain unpublished in the materials. This prevents a full economic model. This void must be left visible rather than filled with assumptions drawn from ranking, customer count or owner identity.

Renewal remains continuous even when the routing identity appears stable

AS1299 can look remarkably stable from the outside. The autonomous system number remains, known peers stay visible, the name Twelve99 continues to provide technical continuity and customers still see a global routing table. This stability is useful, but it can hide how much change is needed beneath the surface. A backbone can keep the same public identity while replacing routers, optical platforms, line cards, software versions, power arrangements, fibre routes and site connections. The real product is the continuity achieved through controlled change.

Hardware generations create a first renewal rhythm. Router capacity must keep pace with rising interface speeds, routing table growth, telemetry and security functions. A chassis or line card that was sufficient when 100G dominated can become a constraint when 400G and higher aggregate speeds become common. The timetable does not depend only on the equipment's ability to keep forwarding packets. Spares, vendor support, power density, software compatibility and the operating cost of running multiple generations in parallel can make a technically functional platform economically obsolete.

Optical systems create a second rhythm. Coherent technologies can sharply increase usable capacity on an existing fibre pair, but an upgrade is not a simple software switch. Distance, fibre characteristics, spectrum, amplifiers, ROADMs, open line system design and operational qualification determine what a route can actually support. Arelion's ability to offer higher‑speed services therefore rests on corridor‑specific engineering, not only on the nominal capability of a transponder or module.

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

Routing standards and operational practices create a fourth rhythm. RPKI adoption, filtering expectations, peering policies, BGP community conventions and security practices evolve without the ASN changing. A network considered well run ten years ago cannot assume that its controls from that time are sufficient today. Customers and peers gradually expect better validation, more transparent routing policy and stronger reaction to leaks and hijacks. Maintaining trust therefore demands renewal of procedures as much as renewal of capacity.

Sites have a slower cycle, but one with heavy consequences. 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 suited to new high‑capacity equipment, while moving existing connections would be expensive. New data centre campuses can pull traffic away from traditional carrier hotels. The network must extend its presence to these new hubs without weakening the interconnection density that makes old sites valuable.

Customer geography also shifts. Enterprise applications migrate to cloud regions; content platforms open edge sites; AI clusters appear in energy‑rich data centre markets; wholesale customers develop new national networks. Arelion could keep the same number of PoPs and still lose relevance if those sites are no longer close to the determining demand. Conversely, a few well‑targeted extensions can sharply increase the value of the existing backbone without radically changing the total site count.

Security capacity follows a particularly uneven demand curve. Normal traffic can be planned around ordinary peaks, but DDoS systems must absorb rare events. The largest attacks of one year can become ordinary a few years later as botnets, access speeds and attack techniques advance. Sizing scrubbing on the average load creates under‑capacity; building unlimited unused capacity destroys economics. The challenge is to maintain enough distributed headroom and diversion flexibility for plausible attacks, while using the infrastructure efficiently in normal times.

Access partners also have a lifecycle. A local carrier can improve, merge, change ownership, retire a product or lose competitiveness. The best option for an enterprise site three years ago is not necessarily the best today. The quality of a global service therefore depends on continuous supplier qualification and the ability to steer new orders and, where possible, existing services towards better alternatives. The partner count measures breadth; the renewal work lies in deciding which ones still deserve the traffic.

Contracts age as well. Long‑term capacity rights can look attractive at signing and then become expensive against market prices. Shorter agreements maintain flexibility but increase renegotiation and price hike risk. Site, fibre and supplier contracts also expire at dates that may not coincide with customer ones. The operator must manage these contractual clocks alongside the physical clocks so that a route does not become economically unfavourable simply because of a misalignment of commitments.

Human skills create a less visible renewal requirement. Global backbones depend on knowledge of routing policy, optical characteristics, historical incidents, supplier behaviour and customer exceptions. Some of this can be embedded in inventory systems and automation; some remains institutional. Departures, reorganisations and outsourcing can remove context that only becomes critical during an unusual incident. A stable network therefore needs succession, documentation and training as much as spare optics.

Automation does not remove any of these cycles. It can improve inventory accuracy, speed provisioning and make dependencies visible, but it raises the importance of reliable data. A wrong site identifier, an outdated route piece of information or a bad supplier demarcation can be propagated faster by an automated workflow than by a manual procedure. The more Arelion standardises deployment and operations, the more important the validation of the data model that underpins that automation becomes.

The commercial consequence is that renewal spend must not be measured only by visible expansion. Replacing a card before it fails, adding headroom on an existing route, moving a customer off a correlated path or upgrading a security platform may create neither a new country nor a new PoP. These investments protect existing revenue. A shareholder who values visible growth above all may underweight them; an operator who treats every precautionary measure as mandatory may overinvest. The useful discipline is to tie each decision to a failure mode, a capacity constraint, a customer contract or a measurable operational gain.

The simple question "Is AS1299 still Tier‑1?" is therefore too narrow. The routing relationship can remain intact while other parts of the service improve or deteriorate. The fuller test is to check whether the network keeps pace with traffic growth, whether physical diversity remains real, whether customers and peers retain confidence, whether security capacity tracks threats and whether capital arrives before technical debt becomes visible as an incident.

Arelion's long history is both evidence and burden. More than three decades of operation show that the system has traversed several generations of hardware, traffic and ownership. They also mean that the network contains decisions made in different technical eras. Renewal means preserving what still holds value and replacing what no longer fits. The ASN can stay constant precisely because many layers underneath do not.

Buyers must verify the service boundary, not just the Tier‑1 label

For customers, useful diligence starts after confirming that AS1299 is Tier‑1. The next question is where Arelion's direct control over the purchased service begins and ends. A transit port in an Arelion PoP, a managed enterprise circuit delivered by a partner, a wavelength on an Arelion route and a Cloud Connect service present different failure domains. The same brand and the same backbone can sit behind contracts that are operationally very different.

The physical demarcation must be explicit. The customer must know whether the handover happens in an Arelion PoP, in a third‑party data centre, at their own site or in a partner facility. If the service includes a local loop, its owner, building entry and whether a second link really takes another physical path must be known. Two circuit IDs do not prove diversity. The determining factors are duct, building entry, site, power feed and upstream path.

The routing demarcation is separate. A transit customer controls its ASN and can use communities, preferences and multihoming. A DIA customer delegates more edge policy. An Ethernet customer may receive a Layer‑2 service with no visibility of internal routing. A Cloud Connect customer reaches an on‑ramp where a second administrative domain begins. Buying teams must document these differences, because they determine who can act during a failure.

Capacity must be verified at the exact boundary of the purchased service. The backbone may support 400G while a local port, an exchange, a cloud on‑ramp or an access carrier cannot. Buyers with AI or data centre traffic must separate core network capacity from the performance actually orderable at both ends. Route qualification, port availability and protection options are more useful than a general claim that the provider "supports" a given speed.

Latency statements too must be defined per route. Arelion's connectivity can reduce intermediate networks, but the path with the fewest AS hops is not necessarily the physically shortest or the one with the lowest latency. BGP policy, fibre length, metro access and destination location also matter. Latency‑sensitive customers should measure from relevant locations and understand whether the service uses traffic engineering, protected paths or ordinary internet routing.

Availability commitments require the same discipline. The gap between backbone, PoP‑to‑PoP and end‑to‑end SLAs shows why a single figure is not enough. The customer must know which components are included, how planned maintenance is handled, what exclusions apply, how measurement is performed and what remedy follows a breach. A high percentage can still permit a significant outage if the measurement window and contractual recourse do not match the application's real cost.

For DDoS purchases, detection, diversion, scrubbing and emergency blackholing must be examined separately. That a carrier observes multi‑terabit attacks is useful evidence of network visibility. The customer must nevertheless know its protection mode, activation rules, covered prefixes, clean‑traffic return and escalation procedure. It also matters what stays out of scope, particularly certain application‑layer attacks that need other controls.

Cloud connectivity requires a three‑party operational model. Arelion provides the carrier path, the cloud provider controls the interface and internal fabric, and the customer controls account and routing. Troubleshooting works best when identifiers and contacts for these domains are documented before the incident. A private connection holds value because it improves path and control; it does not turn three actors into a single operator.

Partner‑based access requires special attention, because it is one of the hardest places to standardise globally. Buyers should ask whether Arelion monitors the local circuit, receives proactive alerts, controls supplier escalation and can obtain route information. They must also know what happens when the local provider repeatedly misses repair targets. A global contract creates the most value when the primary carrier has enough data and commercial weight to change the outcome, not just pass tickets.

Operational transparency should be assessed before buying, not only after a fault. Looking glasses, performance reports and MyArelion offer useful visibility, but the customer must clarify which metrics are available for its service, how often they refresh and whether data can be exported. When performance is contested, shared timestamps, route observations and incident histories are worth more than a general status page.

Change control is another boundary. Customers must know which changes they can trigger themselves through the portal or BGP communities, which need provider approval and which Arelion can initiate during maintenance or security response. Delegated control is only useful if the action, impact radius and rollback are understood. This matters especially when multiple logical services share a physical port.

A multihomed customer must also test the failure scenario instead of assuming redundancy because they use two providers. Preferences can keep traffic on a degraded path longer than expected; prefixes can be mis‑filtered; inbound traffic can behave differently from outbound. Regular tests show whether the architecture really uses AS1299 and the alternative carrier as intended.

The same applies to optical diversity. A protected wavelength may use two fibre paths, but buyers must verify how those paths are defined and where they converge again. Two links with diverse ends can offer a stronger boundary than two channels that share the same site. The application architecture may itself need to span multiple data centres if the site is a critical failure domain.

On contract renewal, these assumptions should be re‑examined. A service bought three years earlier may now be delivered by a different partner, in a different site or under a different architecture. New cloud regions and data centres can offer better endpoints. The 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 diligence 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 only materialises when routing policy, physical infrastructure, partner access, security and operations work together at those boundaries. The label removes one form 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, but the commercial product is a layered platform. Fibre and optics provide path and capacity. PoPs provide market access. BGP, communities and security provide policy. Ethernet, cloud, exchange and managed services create different demarcations. DDoS systems use backbone visibility as a security function. Operations and support turn the whole into a purchasable service.

The advantage comes from historical accumulation. Arelion inherited decades of routes, sites, peer relationships and know‑how from Telia Carrier. Polhem Infra's ownership gave this system a specialised investor and a new brand without replacing its technical identity. Twelve99 remains visible because a network has a longer memory than marketing.

This history also creates an obligation. Tier‑1 status does not freeze the network at the moment it is reached. Prices change, attacks grow, clouds internalise transport, AI creates new corridors, optics advance and customers expect more automation. Arelion must renew the platform while protecting the routing trust that gives AS1299 its value.

The evidence supports the view that Arelion is active, globally relevant and technically broad. It does not allow conclusions about profitability, leverage or how fast AI announcements become sustainable revenue. The most useful conclusion is concrete: a Tier‑1 today is a routing relationship wrapped in capital‑intensive fibre, optical, packet, security and operations systems, and its quality is proven at every service boundary rather than once and for all by the label.

Indicators that will show whether the backbone is strengthening

Arelion's next phase must be judged by conversions, not by slogans. The company already has a mature routing identity, global scale figures and an extended catalogue. The open questions are whether new routes become activated demand, whether higher‑value services offset transit pressure and whether resilience keeps pace with connectivity. The following indicators link technical activity, commercial outcomes and operations.

Peer and route stability

Tier‑1 status depends on maintained settlement‑free relationships. Material changes in visible AS1299 adjacencies, path lengths or propagation would be an early signal of evolving interconnection economics. Looking glasses and external BGP observations reveal change, without explaining the commercial terms.

Activated capacity rather than announced capacity

New 400G products, optical upgrades and route announcements count when ports are lit, traffic rises and customers commit. What needs tracking is qualified 400G availability, completion of Nordic and North American routes, new PoPs and named deployments. A cadence of announcements without activation evidence would weaken the AI and capacity narrative.

Product mix beyond transit

Volume can rise while price per bit falls. Evidence that SecureConnect, Cloud Connect, IX Connect, managed optical networks and Ethernet attach to existing accounts would indicate that Arelion is monetising integration rather than commodity transit. In the absence of published product revenue, customer and service announcements are the available proxies.

Access partner performance

Growth through about 450 partners widens reach but can make delivery and repair variable. What needs watching is the gap between direct and end‑to‑end results, loop lead times, repeated regional incidents and improvement in partner qualification. The published SLA gap already shows the risk shift at the last mile.

DDoS scale and mitigation evidence

The 2026 report establishes the attack environment Arelion observed. Subsequent reports should be read for peak growth, botnet composition, mitigation time, customer impact and scrubbing distribution, not for a single number. A larger observed attack alone does not prove better protection.

Capital and governance signals

Private ownership limits direct financial analysis. What needs tracking is leadership changes, completed route projects, recruitment, supplier commitments, published financings and evolution of Polhem Infra's posture. Slower deployment or increased reliance on partners may reflect capital discipline, demand uncertainty or both.

Five scenarios supported by the evidence

AI WAN demand becomes a sustainable driver

Neoclouds, enterprises and researchers distribute data and workloads between sites. Arelion activates 400G EVPL and wavelengths on named corridors, and AI Direct becomes a measurable source of traffic and customer expansion.

Traffic rises while economics tighten

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

Security convergence improves retention

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

Hyperscalers internalise more transport

Clouds carry more traffic in their private backbones and reduce some wholesale demand. Arelion stays relevant for neutral multicloud and inter‑data centre paths, but the corridor economics become more selective.

A correlated route, site or capital shock reveals concentration

A peering change, fibre cut, site failure or delayed upgrade affects multiple services. The consequence would depend on physical diversity, reserves, incident transparency and the owner's willingness to fund remediation.

Professional implications by stakeholder

Operators must test policy, communities and multihoming instead of treating Tier‑1 as synonymous with redundancy. Enterprises must map direct and partner segments. Cloud teams must define the boundary with the on‑ramp. Security teams must separate observed volume from contracted mitigation. Investors must link expansion, utilisation and returns. Regulators and resilience planners must examine concentrations of sites, cables and autonomous systems without assuming that ownership is the only form of control.

Control, incentives, and decisions that will shape AS1299's next decade

The leadership problem is not choosing between "network" and "business". The network is the business, and every technical choice fixes capital, supplier and customer obligations for years. The control map is distributed: Polhem Infra controls ownership and investment; management allocates capital and sets priorities; engineering and operations control routes and capacities; peers determine settlement‑free relationships; sites and partners control physical parts; customers control prefixes, demand and multihoming; clouds control the other side of the on‑ramps. Strategy succeeds when these authorities align.

Decision one: fund physical diversity before marketing reach

Arelion must measure diversity at the level of cables, ducts, landing stations, sites and power feeds, not just logical topology. A new PoP can increase apparent reach while sharing a hidden failure domain. The irreversible risk is a long‑term commitment to infrastructure that cannot deliver the resilience sold on top.

The choice is to embed diversity evidence into capital decisions and customer design. This may increase cost or slow some launches, but it reduces the risk of multiple products falling during one incident and protects the credibility of the global map. A carrier that combines several forms of physical control can remain trustworthy if it demonstrates control of failure domains.

Decision two: preserve interconnection neutrality while monetising direct reach

AS1299's advantage depends on peers and customers continuing to regard it as a reliable partner. Product growth must not distort routing policy to the point of weakening that trust. Commercial pressure can encourage aggressive preferences, large‑account concentration or under‑investment in routes that are less profitable but topologically important.

Management must preserve a clear separation between peer policy, customer transit, security interventions and product engineering. The second‑order benefit is simpler diagnosis and strengthened trust. The third‑order risk is the loss of direct relationships that more fibre could not rebuild.

Decision three: demand activation evidence for the AI portfolio

AI Direct gives Arelion a credible language for inter‑data centre demand. It can also become a container for ordinary circuits renamed without new economics. Management must govern by per‑route availability, activated ports, named cases, utilisation, protection and renewal.

This discipline prevents capital from following enthusiasm without customer evidence. It also improves the product, because training data, inference, replication and cloud access have different requirements. The irreversible 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. Management must connect this publication to planning, customer architecture, scrubbing placement, false positives and post‑incident learning. Publishing only the peak rewards spectacle; publishing 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 the owner assess whether security capital is protecting revenue. Over the long term, weak evidence would commoditise SecureConnect into a mere label.

Decision five: make partner reach governable

Partners are necessary for global delivery, but accountability can fragment. Arelion must treat selection, inventory, incident data, diversity and exit rights as part of the architecture. The customer must know which segments are direct, managed or only coordinated.

The second‑order effect of good governance is a wider market without equivalent construction. The third‑order effect of poor governance is that a local provider degrades the reputation of the global backbone. Some failures remain outside Arelion's physical control; they must not remain outside its evidence and escalation control.

Decision six: publish enough economics to sustain institutional trust

Private ownership offers flexibility but prevents customers, partners and stakeholders from assessing leverage, capex or concentration. Full listed‑company reporting is not needed to improve trust. Management and the owner can publish consistent measures of investment, activation, resilience and sustainability without revealing contracts.

Better communication would give meaning to route announcements and reduce the temptation to treat connectivity as a substitute for financial health. It could discipline internal allocation by linking strategy to comparable outcomes. The risk of continued opacity is that counterparties apply their own, often harsher, assumptions in times of stress.

Second‑order effects of successful execution

If Arelion converts long‑term capital into physically diverse capacity, preserves peer trust and attaches higher‑value services, AS1299 becomes more than a commodity transit path. It becomes a neutral WAN platform for clouds, enterprises, carriers and distributed AI. This improves retention, capacity forecasting and the economic case for security.

Success also affects the ecosystem: partners gain traffic and quality pressure; data centres gain interconnection value; clouds gain enterprise reach; exchange points gain remote entities; customers have an alternative to hyperscaler concentration. The benefit is distributed, which explains why no single actor controls the outcome alone.

Third‑order effects of failure

A severe policy mistake or hidden concentration can hit more than one product. Customers reroute, peers reassess trust, security services lose credibility and the owner may have to provide more funding just when revenues are threatened. Highly connected infrastructure transmits reputational loss as fast as packets.

Prolonged capital constraint would have slower but lasting effects. Delaying optics and PoPs can lengthen paths, increase partner dependency and make the network less attractive for high capacity. Once direct relationships and anchor accounts have gone, rebuilding can take years.

Irreversible risks

The hardest risks to reverse are the loss of settlement‑free peers, commitment to physically correlated routes, under‑investment during a hardware generation, dependency on a large customer segment and a security incident that reveals weak operational control. A brand can be repaired; a lost route position or a long‑term infrastructure contract can persist.

Management must distinguish reversible experiments from irreversible network commitments. A portal feature can change; a fibre right, a landing‑station dependency or an optical architecture binds the company for years. A pricing promotion can end; a peer relationship damaged by policy abuse may not return on request.

The management judgement

Arelion's strategic asset is neither the Arelion brand nor the name Twelve99 taken separately. It is the coordinated system behind AS1299: interconnection relationships, physical routes, optical capacity, packet policy, security, operations and the trust of customers and peers. Polhem Infra and management inherit this system. Their task is to renew it without breaking the trust accumulated under the previous identity.

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