Arelion's AS1299: Tier-1 Reach Requires Constant Renewal

Summary

• Arelion is the private operator formerly known as Telia Carrier; Twelve99 remains a technical and historical identity, while AS1299 is its global routing identity.
• AS1299 reaches the entire internet through customer and settlement-free peering routes, but Tier-1 status does not guarantee shorter paths, superior support, or immunity to incidents.
• IP transit and dedicated access coexist with Ethernet, wavelengths, managed optical networks, cloud and exchange connectivity, DDoS mitigation, mobile, voice, and AI Direct.
• Accumulated routes, fibre, points of presence, peers, and knowledge create an advantage; continuously funding capacity, security, and expansion remains a burden, with no standalone public financial statements.

Four names describe four different layers

The business started within the Telia group and operated for years as Telia International Carrier, then as Telia Carrier. Polhem Infra completed the acquisition of Telia Carrier on 1 June 2021, transferring control away from Telia Company. The operator adopted the name Arelion in January 2022. These dates divide the corporate history: references to Telia ownership are correct before the completion and incorrect when used to describe the current company.

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

AS1299 is another layer. It is the autonomous system identity through which the backbone originates, receives, selects, and announces routes. An ASN is not a legal entity nor a physical cable. It identifies a routing domain whose policy manifests in routers, points of presence, and interconnections. Arelion operates this domain, while the underlying paths may use fibre under different ownership and contracting arrangements.

The four-part distinction—former brand, current company, technical host name, and routing system—avoids several common mistakes. It prevents historical continuity from turning into a false ownership claim; prevents a technical identifier from being treated as a subsidiary; and forces network-scale claims 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 backbone's operational identity.

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

The term “Tier-1 backbone” compresses several facts into a single label. At the routing layer, a Tier-1 autonomous system can reach the entire internet through routes learned from customers and through settlement-free peering with other large networks. It does not need to buy an upstream transit service to obtain general global reach. This position matters because it eliminates a category of supplier dependency and allows the network to sell full-table transit to third parties.

It is also a maintained position, not one granted once and for all: peers may change policies, traffic may migrate, and the operator must preserve sufficient capacity and direct relationships so that free exchange remains acceptable to both sides.

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

Arelion's current profile makes this difference especially clear. The company's commercial claim is not just that AS1299 has global reach. It is that this reach can be converted into IP transit, private packet transport, optical services, cloud and exchange access, network-layer security, and operational support. Thus, buyers experience Tier-1 status through a service contract whose value depends on demarcation, geography, capacity, routing policy, and the ability to repair faults.

From a national incumbent operator lineage to an international carrier

Arelion dates the organic development of its backbone from 1993. The network grew within Telia's lineage, but its operational logic was international. A domestic operator serves retail, mobile, and enterprise customers within a national market. An international carrier needs to connect other networks across borders, install routers in neutral facilities, acquire long-distance routes, 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 operator already had customers and infrastructure relationships far beyond Telia's domestic business. Telia Company agreed to sell it to Polhem Infra in October 2020; the acquisition was completed the following June. It is the completion, not the announcement, that marks the transfer of control. Polhem Infra's account also recorded the continuation of a strategic network relationship with Telia, showing that corporate independence did not eliminate commercial interdependence.

The 2022 rebranding gave the independent operator a name unlinked to the former parent. The underlying asset was not a newly assembled network. It was a mature backbone whose fibre routes, PoPs, customer connections, and peering relationships had accumulated over decades. This matters because connectivity cannot be reproduced simply by installing a software control plane. A new entrant can lease capacity and bring up ports quickly in selected markets, but cannot immediately create the history of direct routes, operational trust, and fault-recovery practice embedded in a long-standing global network.

Independence also changed the investment question. Within Telia, the operator competed for capital in a diversified telecommunications group. Under Polhem Infra, it became a focused infrastructure asset backed by capital from Swedish pension funds. This structure may favour long-duration investments, but it does not eliminate return targets nor make capital unlimited. It changes who decides, how the asset is framed, and what evidence outside observers can see.

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

Arelion reports more than 80,000 kilometres of fibre, more than 350 points of presence, and service in 129 countries. It also reports more than 2,000 customers and about 450 access partners. These numbers describe different layers and must remain attributed to the company. Fibre kilometres concern physical reach; PoPs, interconnection and service locations; countries, commercial availability; and access partners extend delivery beyond direct facilities. Adding these numbers together would not produce any meaningful measure.

The physical chain may include fibre that Arelion owns, controls through long-term agreements, or leases as capacity; optical systems installed over that fibre; routers and switches; colocation space and power; cross-connects with 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 suppliers. “Global backbone” describes an operational system assembled through several forms of control, not proof that a single company owns every trench, cable, and building.

This distinction is operational, not merely semantic. Two logical routes may appear diverse on a diagram yet still traverse the same duct or submarine cable. Two services may be sold separately and share a router, an optical line system, or a facility's power feed. Conversely, leased infrastructure can be highly resilient when contract, monitoring, and physical diversity are well designed. Ownership alone does not answer the reliability question; the relevant evidence is the failure boundary and the provider's ability to observe and restore it.

Arelion's commercial platform therefore starts from controlling a chain. It must know which segment belongs to its own backbone, which depends on a facility, which is supplied by an access partner, which endpoint is controlled by a cloud provider, and where the contractual SLA changes. The customer sees a single order and support relationship, but an underlying incident may span several organisations. Part of the operator's value lies in making this chain manageable without pretending it is singular.

Fibre provides the path; optics provide usable capacity

Fibre length is a geographical measure, not a capacity number. A single strand can carry different amounts of wavelengths, and each wavelength can be expanded with new coherent optics and line systems. Thus, the same physical route can carry much more traffic after an equipment upgrade without opening a new trench. Arelion's ongoing program for 400G and higher capacities belongs to this optical layer, where transponders, pluggable coherent optics, amplifiers, and spectrum engineering turn glass into active transport.

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

Arelion also sells optical fibre and a Managed Optical Fiber Network. The managed offering shifts more design, equipment, and operations responsibility to the operator. For a large enterprise, cloud operator, or service provider, this can avoid building an in‑house optical engineering organisation for each route. The cost of this choice is greater dependence on the geography supported by Arelion, on its suppliers, on the restoration process, and on lifecycle decisions.

Optical services also show why the operator cannot treat an old backbone as a completed asset. Traffic grows, interfaces migrate to higher rates, and customers expect new paths to clouds and data centres. Each upgrade consumes capital before demand is certain. Underinvestment can create congestion and poor service; overinvestment can leave optics, ports, and contractual commitments idle. A carrier's financial discipline, therefore, is hidden in capacity planning long before the customer notices a speed change.

Points of presence turn long-distance capacity into a market

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

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

PoP density also affects 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 United States and Europe can be reached within one network hop and describes AS1299 as the most connected backbone in the world according to the metric it chose. These claims must remain attributed, as the result depends on the dataset, definition, and date. One-hop reach does not equate to the lowest latency for every flow, and connectivity is not traffic market share.

The packet layer carries several products over shared infrastructure

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

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

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

A customer can also place several services on a single port through logical separation. This can reduce cross-connect and interface costs. However, it concentrates services into a single physical failure domain. A port failure can affect several logically distinct circuits at once. Efficient multiplexing and concentrated risk must appear in the same explanation.

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

An IP transit customer normally operates an autonomous system, announces prefixes via BGP, and receives internet routes from Arelion. The operator carries outgoing traffic towards other networks and returns traffic for the customer's prefixes. The product is priced and contracted as reach, capacity, and service, while the underlying value comes from AS1299's relationships with customers and peers.

The transaction seems simple because BGP hides the physical path behind route announcements. In operation, Arelion must maintain full tables, filter invalid or unauthorised announcements, balance traffic across links, provision capacity, secure sessions, manage communities, and recover faults across many PoPs. A customer multihomed with another operator gains redundancy and path choice, but also acquires a more complex routing problem. It must understand preferences, inbound traffic engineering, and how failures propagate through each provider.

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

The operator's routing position must also be preserved. If the traffic balance, geographical reach, or commercial policy changes materially, a peer may seek other terms or end the relationship. The practical barrier is therefore accumulated and defended continuously. The network needs enough customers, direct reach, capacity, and operational credibility that other large backbones keep exchanging traffic settlement‑free.

Dedicated internet access transfers more routing responsibility to the provider

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

The distinction matters during failures and changes. A transit customer can use its own ASN, prefixes, communities, and multihoming policy. A DIA customer typically has less control and relies more on the provider's edge routing and support. Neither model is inherently superior. Transit suits organisations with routing expertise and a need for policy control; DIA suits buyers who prefer a managed demarcation.

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

BGP communities turn routing policy into a product feature

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

It is a powerful form of delegated control. An operator can make a prefix less attractive in a region, limit where it is announced, or sacrifice reach to protect the rest of the network during an attack. The semantics are specific to AS1299; a community value used by another operator may mean something else. Customers need up‑to‑date documentation, controlled changes, and a way to verify the result with routing tools.

Communities also carry failure risk. An incorrect tag can withdraw reach or send traffic along an unintended path. A remotely triggered black hole deliberately discards upstream traffic for a destination to stop an attack from congesting wider links. This action is useful in an emergency because it trades a target's availability for network stability. It is not cost‑free mitigation.

Looking glasses expose only part of the routing reality

Arelion's Twelve99 looking glass allows inspecting routes, pings, and traceroutes from selected network locations. The tool answers practical questions: how does AS1299 see a prefix, what path is selected from a given observation point, and where does latency appear in that view? It also preserves the name Twelve99 as a technical identity after the corporate rebranding.

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

Arelion also publishes monthly IP network performance metrics. These reports help buyers track provider‑chosen measures over time, but methodology and scope remain defined by the company. Transparency improves when the operator exposes operational data; independent assurance still requires clear definitions and outside observation.

RPKI reduces one routing risk without fixing BGP as a whole

A Route Origin Authorisation lets a prefix holder declare which autonomous system may originate the route. Origin validation can classify an announcement as valid, invalid, or not found. Filtering invalid origins reduces some hijacks and misconfigurations. Arelion's educational material presents RPKI as a part of routing security.

The mechanism checks the origin authority of covered prefixes. It does not validate the full AS path, does not guarantee a peer exports routes correctly, nor does it prevent all route leaks. A valid origin can still propagate along an unintended path, and operational errors can occur in filters, route objects, or customer configuration. RPKI narrows the trust problem; it does not replace BGP policy, monitoring, and incident response.

For a Tier‑1 operator, this boundary matters because route security and availability can conflict. Aggressive filtering can block legitimate traffic when records are wrong; weak filtering can spread invalid announcements. The operator needs graduated policy, customer communication, exception handling, and current data. Claims that “RPKI makes BGP secure” hide the operational judgment that remains.

IX Connect sells access to interconnection, not full internet reach

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

The transport does not create the peering policy. The customer still needs exchange participation when required, compatible ports, bilateral or route‑server agreements, and its own filters. A remote path can also introduce an additional dependency compared with a router physically placed at the exchange. IX Connect is therefore an access service to a route market, not a replacement for the customer's interconnection strategy.

This product shows why a Tier‑1 carrier both competes and cooperates with exchanges. Arelion peers at these locations and sells transport to them. A customer can replace part of paid transit with direct peering and still buy capacity from Arelion 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 physical network.

Cloud Connect brings the backbone to a provider‑controlled demarcation

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

The service ends at a shared boundary. The cloud provider controls its virtual interface, regional availability, quotas, and internal network. The customer controls account, routes, and workloads. Arelion controls the carrier path it sells. A failure can lie on any side, and the parties need aligned configurations. Calling the entire route “private” can be misleading if it suggests a single provider owns all components or that no shared infrastructure exists.

Cloud connectivity also shifts the operator's competitive position. Hyperscalers operate large private backbones and carry ever more traffic between their own regions. Arelion's opportunity lies in connecting enterprises, data centres, multiple clouds, and networks that do not share a single administrative domain. The limitation is the same: it cannot determine what happens inside a cloud nor replace the provider's fabric.

DDoS defence has become part of backbone capacity planning

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

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

The 6.1 Tb/s observation should not be converted into a mitigation capacity guarantee. An attack can be observed on the backbone without a single customer receiving the full volume, and service commitments depend on architecture and contract. Effective mitigation also depends on detection time, BGP convergence, scrubbing centre location, clean‑path capacity, and false‑positive control. Application‑layer attacks can slip through volumetric filters because the packets look legitimate.

Remotely triggered blackholing is the emergency extreme of the design. A community can cause traffic destined for an attacked prefix to be dropped upstream. This protects shared capacity but leaves the target unavailable. Scrubbing tries to preserve service; blackholing accepts an interruption to contain the damage. A mature DDoS product needs both mechanisms, clear triggers, and customer authority over when to use the harsher response.

SecureConnect bakes mitigation into the connectivity purchase rather than treating it as an optional system bolted on later. This can improve adoption because the protection is already active before the incident. The strategic test is not the package name, but the attach rate, response evidence, the scope of protected services, and the ability to scale as attack peaks grow.

AI Direct assembles long‑distance transport for distributed AI systems

AI Direct is Arelion's connectivity portfolio for moving data between AI clusters, data centres, and clouds. It combines services already familiar to carriers—Ethernet, wavelengths, internet access, managed optical networks, and security—under an AI infrastructure proposition. The bundle does not provide GPUs, storage systems, or model‑training software. Its role starts when data needs to leave a facility or administrative domain.

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

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

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

Enterprise services monetise the backbone beyond transit

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

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

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

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

Access partners expand reach and change the SLA boundary

Arelion reports about 450 access partners. These carriers can connect the customer's building to an Arelion PoP where the backbone lacks direct local fibre. The model expands coverage without requiring Arelion to build every last mile. It also gives the customer a single commercial relationship for a path assembled by several providers.

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

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

Operations turn network assets into a usable service

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

Automation can reduce provisioning time and expose state, but a global operator cannot reduce every event to an API call. Fibre repairs require field crews; a cloud endpoint can reject a configuration; a peer can change policy; a colocation facility can demand a cross‑connect; and a local carrier can miss a delivery date. Carrier‑automation quality includes how clearly it represents exceptions and responsibilities, not just how fast it accepts a normal order.

Arelion reports customer experience recognition and a high net promoter score. These claims may signal a deliberate service culture, but methodology and response population are not independently audited in the provided evidence. Awards and surveys should accompany operational detail, not replace it.

The business model reuses a single infrastructure base across several demarcations

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

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

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

Pension‑fund‑backed ownership changes the horizon, not the economics

Polhem Infra owns Arelion. According to its current description, Polhem Infra is jointly owned by the Third AP Fund and the Fourth AP Fund of Sweden. This links the operator to national pension capital through an infrastructure investment vehicle. The structure fits well with an asset whose routes and interconnection position are built over long periods.

Long‑duration capital can tolerate investments whose return takes several years, such as fibre rights, optical upgrades, and new PoPs. It can also favour stable cash generation over short‑term signalling to equity markets. The owner still has fiduciary duties and return requirements. Pension‑fund affiliation does not mean routes will be funded independently of demand, and it does not reveal how much debt, operational cash, or owner equity supports Arelion.

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

Management cannot take personal credit for every architecture decision. The backbone is the accumulated work of engineering, operations, procurement, sales, and partner teams across decades. Leadership sets capital allocation, risk tolerance, product direction, and disclosure. The day‑to‑day quality of the network depends on distributed knowledge and institutional memory.

Private ownership leaves the key financial questions unanswered

The provided evidence does not establish revenue, profit, debt, capital investment, valuation, traffic volume, contract duration, or current and separate customer concentration for Arelion. The absence is material because a global carrier must continue funding equipment, route rights, colocation, access, and security capacity. Product announcements show activity; they do not show return.

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

This opacity changes how performance is judged. Public routing data and looking glasses can show reach and path behaviour. Press releases can show route and product activity. Customer announcements can show selected deployments. None of these sources reveals whether capital is being deployed with adequate returns, whether a single customer dominates revenue, or whether leverage constrains the next upgrade.

The correct conclusion is limited: Arelion appears to be an active global carrier with a broad portfolio and ongoing investment. The provided evidence does not support a profitability estimate or the claim that pension‑fund ownership guarantees the next capital cycle.

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

Arelion's roots and ownership base are Nordic, while its backbone stretches across Europe, North America, and Asia. The company reports service in 129 countries. This number represents commercial reach, not a count of owned fibre systems or direct PoPs. A buyer needs three maps: where Arelion has backbone and facilities, where it can deliver via partners, and where a specific service is technically available.

Europe remains a dense part of the network's lineage. North America is a major transit and enterprise market, and recent additions such as Oklahoma City were positioned around cloud and AI data‑centre demand. The 2026 Danish investment involved routes and a landing‑station environment important for Nordic and submarine connectivity. In Mexico, route development and a channel programme broadened access to a growing market. The package provides less public route detail for Asia than for Europe and the United States.

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 an entire submarine system. Cable faults, station incidents, and shared terrestrial backhaul can affect multiple carriers. Logical route diversity must therefore be tested against cable and duct diversity.

Geopolitics can also change route economics. Cross‑border regulation, sanctions, licences, cable security, and national resilience policies influence where carriers can build and how customers assess risk. The provided package does not establish a specific current dispute involving Arelion; these factors belong to analysis as structural constraints, not as allegations.

Competition takes place across several layers simultaneously

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

At the physical and optical layer, companies such as Zayo compete for fibre and wavelength demand. In cloud connectivity, Megaport and Equinix Fabric offer software‑defined interconnection across partner ecosystems and facilities. At the enterprise layer, regional carriers, SD‑WAN providers, and managed‑service firms can assemble alternatives over internet underlays. These are overlapping, not identical, categories.

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

Exchange points can both complement and replace transit. A network with enough traffic can peer directly for key destinations and buy less transit. It still needs reach for the rest of the internet, transport to exchanges, and operational support. IX Connect and transit place Arelion on both sides of this decision.

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

Connectivity creates both resilience and contagion

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

Physical concentration can produce the same dual effect. Dense PoPs improve interconnection, but a facility outage can affect many services. A logically diverse topology may share a single fibre duct. A DDoS platform can protect customers, but a diversion‑policy error can move a large volume of legitimate traffic. Scale amplifies both capacity and impact radius.

Resilience therefore depends on controls less visible than maps: maintenance discipline, staged configuration, route filters, RPKI validation, community governance, optical protection, capacity headroom, scrubbing location, out‑of‑band access, incident communication, and tested rollback. Arelion's public tools and product pages establish elements of this system, but the package does not contain a full incident history or independent audit.

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

Sustainability claims require denominator discipline

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

Responsible editorial treatment separates efficiency from absolute impact. A route upgrade can reduce energy per bit carried; a new route can increase total equipment and energy. Leasing infrastructure also shifts part of the emissions and consumption to suppliers rather than eliminating them. Without consistent scope, baseline, and traffic data, broad environmental improvement claims would be unsupportable.

Sustainability matters strategically because customers and pension‑fund‑linked owners may require credible evidence on energy, procurement, and resilience. It also matters operationally: optical density, cooling, and power availability affect where capacity can be deployed. The monitoring question is whether reporting becomes granular enough to connect network expansion to measured resource use.

What the public evidence does not show

The network‑scale numbers in this profile are mainly current claims by Arelion. The research package does not contain an independent, route‑by‑route audit of the more than 80,000 kilometres, a uniform definition for every PoP, nor a complete inventory of owned versus leased infrastructure. It also contains no traffic time series comparable across competitors.

The connectivity claim depends on the metric. The 95% one‑hop claim describes Arelion's reported reach in the United States and Europe, not a guarantee for every destination, protocol, or moment. Monthly performance reports are useful but provider‑selected. A purchase decision still needs per‑route testing and contractual terms.

Product availability is also conditional. Ethernet supports rates up to 400 Gb/s; this does not mean every location, tail, or route delivers 400G. AI Direct is a connectivity bundle, not proof of AI‑customer revenue. An observed 6.1 Tb/s attack does not reveal contracted scrubbing capacity. MEF/Mplify certification supports trust in the service definition, but it does not certify every access tail or incident outcome.

The financial gap is larger. Revenue, margin, debt, capex, valuation, and current customer concentration are not disclosed in the provided materials. This prevents a complete economic model. The gap should remain visible rather than being filled by assumptions derived from route rankings, customer counts, or owner identity.

The economics of renewal sits between physical ownership and contractual control

Backbone renewal does not happen in a single cycle. Fibre can remain useful far longer than the optical equipment installed on top of it; routers can span several software generations before needing replacement; ports, transponders, and coherent modules may need upgrading as capacity grows; colocation, power, cross‑connect, local access, and submarine capacity contracts can expire on different calendars. The result is an infrastructure in which the network identity seems continuous while many of the components that make the service usable are replaced, renegotiated, or reconfigured at distinct moments.

This difference changes how ownership is interpreted. Owning a stretch of fibre does not mean single‑handedly controlling all the elements needed to deliver an end‑to‑end service. Likewise, using contracted infrastructure does not mean an absence of operational control. What matters is the combination of physical rights, contracts, observability, escalability, and authority to restore service. A route can be robust even with third‑party assets when responsibility boundaries are clear and physical diversity is real.

Another may appear fully integrated yet still share power, buildings, ducts, or optical systems with services that ought to be independent.

For Arelion, this logic makes investment look less like a single build program and more like a permanent sequence of renewal decisions. The company must balance asset lifetimes, supplier support, traffic growth, power availability at facilities, port capacity, partner coverage, and the need to maintain headroom. Upgrading only one layer does not solve the whole problem.

More optical capacity has limited value if a point of presence lacks enough ports; a new port has limited value if the physical route remains concentrated; a sophisticated BGP policy does not repair a severed cable; and a security service does not replace enough clean capacity to hand traffic back to the customer.

Commercial discipline appears precisely in this coordination. Renewing too early can leave equipment and commitments underutilised. Renewing too late can create congestion, shrink recovery options, and make new speeds unavailable when customers ask for them. The challenge is to match the investment pace to the actual activation pace without waiting for all demand signals to be certain before reserving capacity. This tension exists in any large‑scale backbone, but it becomes more visible in a network that sells several services over the same physical base and must preserve the trust associated with a global routing identity.

There is also a less visible contractual cycle. Agreements with facilities, access providers, capacity suppliers, and other entities can change prices, lead times, support levels, and exit options. Network renewal, therefore, is not limited to equipment. It includes preserving usage rights, renegotiating dependencies, replacing suppliers when necessary, and keeping sufficient information to know where a commercial decision creates a new operational concentration. Arelion's ability to control this contractual layer is as relevant to service as direct ownership of an isolated asset.

Renewal is continuous even when the routing identity looks stable

The stability of AS1299 can give the impression that the backbone is a fixed entity. In practice, an autonomous‑system identity can remain the same while routers, optics, software versions, points of presence, BGP sessions, physical routes, access partners, and available capacity all change. This continuity is useful because customers and peers do not need to rebuild the entire technical relationship each time a component is replaced. At the same time, it can hide how much work is needed to make the network appear stable from the outside.

Every change creates a transition problem. A new routing platform must receive correct policies before taking traffic. An optical upgrade must be coordinated to avoid unnecessary capacity loss. A new point of presence must be integrated into the topology, monitoring tools, support processes, and commercial relationships. A supplier change can require new escalation and repair procedures. The operational goal is not to prevent changes, but to execute them without turning renewal into disruption.

This also explains why a Tier‑1's quality cannot be inferred solely from its persistence in routing tables. The peering relationship must remain economically acceptable; capacity between relevant points must keep pace with traffic; filters and policies must stay correct; security must respond to new attack patterns; and support must retain enough knowledge to diagnose problems that span multiple layers. The identity may be old, but the ability to deliver service is renewed every day by far more recent decisions.

Human and institutional continuity is part of this process. Automated tools can reduce repetitive errors and accelerate provisioning, but high‑impact changes still depend on knowledge about topology, incident history, peer behaviour, facility limitations, and contractual exceptions. When people, suppliers, or platforms change, this knowledge must be transferred into documentation, systems, and processes. A mature network is not just a collection of accumulated assets; it is also a set of practices that avoids repeating known failures and allows interpreting signals that a single tool cannot explain.

For outside observers, the consequence is methodological. Announcements of new products, new speeds, or new points of presence must be separated from evidence of activation. Likewise, a route that continues to be announced does not prove that all the capacity behind it remains the same as in the previous period. Useful tracking combines routing stability with investment signals, per‑location availability, measured performance, incidents, service expansion, and customer behaviour. The question is not whether AS1299 remains visible, but whether the infrastructure and relationships that give it meaning are being renewed at the necessary pace.

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

For a buyer, Tier‑1 status is relevant but limited public evidence to define a service architecture. The procurement must start from the concrete demarcation. One needs to know at which facility the service enters, what port and capacity are available, which leg belongs directly to Arelion, where partner dependencies start, how physical diversity has been verified, and what responsibilities remain with the customer. These answers turn a global network description into a design that can be tested and operated.

The same discipline applies to routing. A transit customer must understand how its prefixes will be announced, which communities are available, how preference and blackholing work, what filters are applied, and how changes can be validated. A dedicated‑access customer delegates more of this responsibility to the provider and therefore needs to know the support boundary even better. In both cases, the word Tier‑1 does not replace a failover policy, nor does it remove the need to test behaviour when a session, an access, or an entire path stops working.

For private services, the question changes but the principle remains. Ethernet, wavelengths, Cloud Connect, and IX Connect have different demarcations and depend on different components. A service can be logically separated and still share the same facility, duct, power, or physical port with another. A cloud connection can be private on the carrier leg and still dependent on the cloud provider's on‑ramp and configuration. A second access can be commercially distinct and still physically correlated with the first. Diligence must look for these convergence points.

Security must also be contracted in terms of mechanism and observable outcome. For DDoS, buyers need to distinguish the volume the backbone can observe, the scope of the mitigation service, the moment traffic is diverted, the scrubbing location, the clean‑path capacity, and the conditions under which blackholing may be used. No single number describes this entire system. The same applies to RPKI and BGP communities: they are important controls, but each covers a specific part of the risk.

Public tools such as looking glasses and performance reports help form a baseline, but the strongest validation combines these data with the customer's own measurements, failover tests, contractual terms, and operational history. The goal is not to prove that a provider will never fail. It is to know how failure manifests, who can observe it, who has authority to act, and how much of the design remains usable during recovery.

This approach makes the Tier‑1 label more useful, not less. Instead of treating it as synonymous with universal quality, the buyer uses it as a feature of Arelion's routing position and then verifies the layers that turn that position into service. AS1299's strength lies in the combination of interconnection relationships, capacity, assets, contracts, security, and operations. For anyone buying critical connectivity, the decisive question is whether this combination works on the route, at the demarcation, and in the failure scenario that really matter.

The central judgment

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

The barrier is historical accumulation. Arelion inherited decades of routes, facilities, peering relationships, and operational knowledge from the Telia Carrier lineage. Polhem Infra's ownership gave this system an infrastructure‑focused investor and a new brand without replacing the technical identity. Twelve99 remains visible because the network's memory outlasts corporate marketing.

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

The evidence supports confidence that Arelion is active, globally relevant, and technically broad. It does not support confidence about current profitability, leverage, or the speed with which AI‑linked announcements turn into lasting revenue. The most useful conclusion is concrete: today, a Tier‑1 is a routing relationship wrapped in capital‑intensive fibre, optical, packet, security, and operations systems, and its quality is proved repeatedly at the service boundary, not granted once by the label.

The indicators that will show whether the backbone is strengthening

Arelion's next phase should be judged by conversions, not slogans. The company already has a mature routing identity, claims of global scale, and a broad catalogue. The open questions are whether new routes become activated demand, whether higher‑value services offset price pressure in transit, and whether resilience keeps pace with connectivity. The indicators below link technical activity to commercial and operational outcomes.

Peer and route stability

Tier‑1 status depends on maintaining settlement‑free relationships. Material changes in visible adjacencies, path lengths, or AS1299 route propagation would be an early signal of a shift in interconnection economics. Looking glasses and external BGP observations can reveal the change, though they do not explain the commercial terms behind it.

Activated capacity, not just announced

New 400G products, optical upgrades, and route announcements matter when ports are lit, traffic grows, and customers commit. One must track qualified 400G availability, completed routes in Northern Europe and North America, new PoPs, and deployments with named customers. A cadence of announcements without evidence of activation would weaken the AI and capacity narrative.

Product mix beyond transit

Traffic volume can grow while the per‑bit price falls. Evidence that SecureConnect, Cloud Connect, IX Connect, managed optical networks, and Ethernet are being attached to existing accounts would indicate that Arelion is monetising integration rather than relying solely on commoditised transit. The company does not disclose revenue by product, so customer and service announcements are the available proxies.

Access partner performance

Growing through roughly 450 partners expands reach but can introduce delivery and repair variation. One should track the difference between direct‑PoP and end‑to‑end results, last‑mile lead times, recurring regional incidents, and any eventual disclosure of tighter partner qualification. The published SLA gap already shows that the last mile changes the risk profile.

DDoS scale and mitigation evidence

The 2026 report establishes the attack environment observed by Arelion. Future reports should be read for peak growth, botnet composition, mitigation time, customer impact, and scrubbing distribution, not just a headline number. Observing a larger attack does not, by itself, prove stronger protection.

Capital and governance signals

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

Five scenarios supported by the evidence

AI WAN demand becomes a lasting growth engine

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

Traffic grows while economics tighten

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

Security convergence improves retention

Customers buy transit or DIA together with automated mitigation, giving SecureConnect a larger role in renewals and incident response. Success would appear in attach rates, customer references, and evidence of preserved availability during major attacks.

Hyperscalers internalise more transport

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

A correlated route, facility, or capital shock exposes concentration

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

Professional implications by stakeholder

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

Control, incentives, and decisions shaping the next decade of AS1299

Arelion's leadership problem is not choosing between “network” and “business”. The network is the business, and every technical choice locks in 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 route and capacity changes; peers determine settlement‑free relationships; facilities and partners control parts of the physical path; customers control prefixes, demand, and multihoming; and cloud providers control the other side of the on‑ramps.

The strategy only works when these authorities are aligned.

Decision one: fund physical diversity before advertising reach

Arelion must measure route diversity at the cable, duct, landing‑station, facility, and power levels, not just by logical topology. A new PoP or path can expand apparent reach while sharing a hidden failure domain with existing capacity. The irreversible risk is entering long‑term infrastructure commitments that cannot deliver the resilience sold on top of them.

The leadership choice is to make physical‑diversity evidence part of capital approval and customer design. This may increase cost or delay some launches. It also reduces the chance of multiple revenue products failing in a single incident and protects the credibility of the global map. A carrier with opaque asset ownership can still be trusted when it demonstrates control of failure boundaries.

Decision two: preserve interconnection neutrality while monetising direct reach

AS1299's moat depends on peers and customers continuing to see the network as a trustworthy exchange partner. Product growth must not distort route policies to the point of weakening that trust. Commercial pressure can encourage aggressive preferences, concentration on large accounts, or underinvestment in routes that seem less profitable but preserve the topology.

Leadership must protect a clear separation between settlement‑free peer policy, customer transit policy, security interventions, and product traffic engineering. The second‑order benefit is easier diagnosis and greater counterparty trust. The third‑order risk is losing direct relationships that cannot be restored by simply buying more fibre.

Decision three: demand activation proof for the AI portfolio

AI Direct gives Arelion a credible language for high‑capacity data‑centre‑to‑data‑centre demand. It can also become a container for ordinary circuits rebadged without new economics. Management must govern the portfolio by route availability, activated ports, named cases, utilisation, protection requirements, and renewal behaviour.

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

Decision four: turn security evidence into an operational learning loop

The DDoS report gives Arelion valuable insight into attack traffic. Leadership should connect that publication to capacity planning, customer architecture, scrubbing location, false‑positive review, and post‑incident learning. Reporting only the peak rewards spectacle; reporting mechanisms and outcomes improves the service.

A stronger loop would distinguish observed attacks, mitigated attacks, customer impact, and the role of blackholing. This would help customers size risk and the owner assess whether security capital protects revenue. The long‑term consequence of weak evidence is commoditisation: SecureConnect becomes a label, not a credible operational capability.

Decision five: make partner reach governable

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

The second‑order effect of good governance is a larger addressable market without equivalent self‑build. The third‑order effect of weak governance is a local supplier degrading the global backbone's reputation. Some failures will remain outside Arelion's physical control; they need not remain outside its evidence and escalation control.

Decision six: disclose enough economics to sustain institutional trust

Private ownership gives Arelion flexibility, but it prevents customers, partners, and infrastructure stakeholders from assessing leverage, capex, or customer concentration. Adopting the full disclosure of a public company is not necessary to improve trust. Management and the owner can publish consistent measures of operational investment, capacity activation, resilience, and sustainability without revealing commercially sensitive details.

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

Second‑order effects of successful execution

If Arelion converts long‑duration capital into physically diverse capacity, preserves peer trust, and attaches higher‑value services, AS1299 will become more than a commoditised transit path. It could be a neutral WAN platform for clouds, enterprises, carriers, and distributed AI infrastructure. This position can improve retention, support capacity forecasts, and make security investment more economically defensible.

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

Third‑order effects of failure

A serious routing‑policy error or hidden physical concentration can damage more than one product. Customers may redirect traffic, peers may reassess trust, security services may lose credibility, and the owner may face a higher capital need at the same time as revenue is at risk. Highly connected infrastructure can transmit reputational loss as fast as packets.

A prolonged capital constraint would have slower but longer‑lasting effects. Delays in optics and PoPs can lengthen paths, increase partner dependency, and make the network less attractive to high‑capacity customers. Once direct relationships and anchor accounts migrate, rebuilding them can take years.

Irreversible risks

The hardest risks to reverse are losing settlement‑free peering relationships, committing to physically correlated routes, underinvesting during a hardware generation, relying on a single large customer segment, and suffering a security incident that reveals weak operational control. Brand damage can be repaired; lost route position or a stranded long‑term infrastructure contract can persist.

Leadership must therefore distinguish reversible product experiments from irreversible network commitments. A portal feature can be changed; a fibre right, landing‑station dependency, or optical architecture can bind the company for years. A price promotion can end; a peering relationship damaged by policy abuse may not return when desired.

The leadership judgment

Arelion's strategic asset is not the Arelion brand alone, nor the hostname Twelve99. 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; they do not start from a blank sheet. 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 diverse, usable paths. New ports must become customer traffic. The 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 meaningful. When they fail, the label survives longer than the advantage it once described.