Summary

  • 2FAST A/S is legally active in Aalborg, but the current public evidence does not support classifying it as a regional ISP. Danish company information places it in other IT and computer services, its 2019 annual report said its principal activity was managing company capital, and the latest public accounts disclose a very small financial footprint without reported revenue.
  • The company once had a credible independent internet-routing role. RIPE's original AS49514 registration recorded two intended upstreams, Jay.net's AS16095 and AS3308, and RIPEstat observed 62.122.160.0/21 behind AS49514 from January 2010 until October 2011.
  • The 2,048-address block survived the withdrawal of 2FAST's own route. It was observed behind AS28717 from late 2013 to April 2025 and has been originated by GlobalConnect's AS31027 since April 2025. On 10 July 2026 the prefix was visible to all 327 IPv4 peers counted by RIPE RIS, while AS49514 itself originated no IPv4 or IPv6 space and had no observed neighbours.
  • The present failure surface is therefore a carrier-hosting chain, not an evidenced local-access chain. Public records do not establish 2FAST-owned fibre, towers, poles, customer-premises equipment, field crews, retail subscribers, a service area, an operating facility or physical route diversity. The parties most plausibly exposed are users of systems or addresses within the retained /21, but even that population is not publicly enumerated.

The regional-ISP label does not survive the first test

An autonomous-system number beside a company name can create a persuasive illusion. AS49514 is registered to 2FAST A/S. The associated address block is visible across the public internet. Several addresses answer network probes, and third-party inventories associate web domains with the range. Read quickly, those facts resemble the footprint of a small internet provider. Read in sequence, they describe something different: an old independent routing identity that stopped announcing routes, paired with address space now carried by a much larger network.

The distinction is not cosmetic. A regional ISP sells access to homes or businesses across a defined area. Its operating surface normally leaves some combination of retail tariffs, address checks, installation terms, customer support hours, coverage descriptions, licences, network notices, maintenance reports, fibre or radio construction, subscriber equipment and field-service work. None of that current evidence could be established for 2FAST. The company's public identity is legal and administrative, not a present access offer.

Current Danish company information points in the same direction. Proff's 2FAST profile, drawing on CVR/Virk information, lists CVR number 30604040, a 1 June 2007 start date, normal status and industry code 629000, other IT and computer service activities. It gives the purpose as conducting computer-related business and associated activities. That purpose is broad enough to include hosting, systems work or connectivity, but it does not say the company now runs an access network.

The ownership and management record is compact. Ownr's CVR-derived profile identifies Thomas Byrdal as director, Richard Byrdal as board chair, BYRDAL HOLDING ApS as the legal owner and GEKKO-IT A/S as a secondary registered name. It also lists one production unit at Ved Stranden 14-16 in Aalborg. These are useful identity anchors. They do not locate a router, a fibre handoff, a server room or a repair depot. A registered office can host management while technical service is delivered elsewhere by suppliers.

The appropriate downgrade is consequently direct. 2FAST is an active Danish company with retained internet-number resources and a documented network-services history. It is not evidenced as a current regional ISP. The only assigned controlled topic that remains strongly supported is Peering and transit, because the public record can show how route origin and carrier responsibility changed. Regional ISP economics and Local support labour would presume a current subscriber business and a local repair organisation that the evidence does not establish.

The accounts describe continuity without an operating network

The financial record makes the category problem sharper. 2FAST's 2019 filed annual report states that the company's principal activity consisted of managing its capital. It reported DKK 37,342 of profit, DKK 434,407 of total assets and DKK 428,407 of equity. The balance sheet showed no fixed assets. Almost all assets were receivables from affiliated companies, with DKK 45 in cash. That is not the balance-sheet shape one would expect from a company then carrying a sizeable owned access plant.

The filing is old enough that it cannot settle current operations by itself. A company can change activity after a reporting year, lease all infrastructure rather than own it, use contractors, or run services whose equipment is expensed or held by another company. The significance lies in the direction of the evidence: by 2019, long after AS49514 had disappeared from observed routing, management itself described capital administration rather than telecommunications operation as the principal activity.

The latest public series does not reverse that conclusion. The Regnskabsbasen company page, based on Danish CVR material, reports 2024 total assets of DKK 975,708, equity of DKK 532,649 and net profit of DKK 54,028. Its machine-readable company result supplies annual totals from 2012 through 2024 but leaves revenue and operating result undisclosed throughout that series. Proff separately reports 2024 gross profit of roughly DKK 2,000 and pre-tax profit of roughly DKK 12,000.

Those numbers prove that the company files accounts and retains capital. They do not reveal broadband turnover, subscriber count, transit expense, installation income, field wages, network rent, power costs or investment in active equipment. The total 2024 asset base is less than DKK 1 million. Even without assuming how it is composed, that is a modest company scale for an operator supposedly responsible for poles, towers, fibre routes, powered nodes, customer equipment and round-the-clock repair across a region.

Small size alone is not disqualifying. Community networks and specialised business providers can operate with few employees, outsourced construction and leased transport. But a claim of current operation needs positive evidence. Here the financial material supplies legal continuity and a small economic footprint; it does not supply the missing network, customers or service territory. Treating the accounts as proof of an ISP would reverse the burden of evidence.

There is also a difference between assets that have economic value and assets that move packets. The IPv4 block may be valuable, contracts or receivables may sit on the balance sheet, and the company may retain rights associated with older services. None of those possibilities means 2FAST has technicians standing by in Aalborg or a fibre ring carrying household traffic. The accounts do not break out internet-number rights, equipment, hosted systems or related-company balances in enough current detail to assign an operating function.

A real network-services history remains visible

The downgrade should not erase what 2FAST once did. The first version of the company's RIPE autonomous-system record, created in June 2009, named 2FAST A/S and declared import and export policies with AS16095 and AS3308. The first version of the 62.122.160.0/21 address registration, created in March 2009, likewise named 2FAST, used the network name JAYNET-2FAST-DK and marked the range as provider-independent assigned space.

Those two records establish more than a directory label. A provider-independent /21 gave 2FAST 2,048 IPv4 addresses that could remain registered to it across a carrier change, subject to registry and sponsorship arrangements. An autonomous system gave it a distinct routing policy identity. The declared use of two external autonomous systems shows an intended design with more than one route provider, even though a registry policy does not prove simultaneous physical circuits, equal capacity or successful failover.

AS16095's current RIPE registration keeps the name JAYNET and says Jaynet became part of Sentia Danmark. AS3308 is now identified by RIPEstat as Norlys Digital A/S. Corporate and network names have changed since 2009, so present labels should not be projected backward mechanically. What matters is that the original 2FAST policy named two distinct autonomous systems at the time.

There is also qualitative corroboration for a broader IT-services offer. A public recommendation on Thomas Byrdal's LinkedIn profile describes a customer using 2Fast for hosting, internet connections, IP telephony, a content-management website and hardware. The statement is historical, self-selected and not a substitute for a dated contract. It supports the view that 2FAST once acted as a combined IT and connectivity supplier rather than proving any current retail footprint.

An unofficial Jaynet review page carries a former customer's statement that Jaynet acquired 2fast in Aalborg and moved the customer's servers to Jaynet's server park. That is a useful market signal, not an authoritative acquisition record. It suggests a transfer of hosting customers and technical responsibility. It cannot establish the transaction date, legal scope, assets sold, consideration, surviving obligations or whether every customer moved. A company announcement, transaction filing or contract notice would be needed to settle those points.

The strongest history remains the route table, because it records what the wider internet actually observed. RIPEstat's AS49514 routing history shows 62.122.160.0/21 originated by 2FAST's AS from 7 January 2010 through October 2011. Its current routing status identifies the last observed 2FAST-originated route in October 2011. This was not merely an ASN allocated on paper; it had a visible, if relatively short, production life.

AS49514 stopped, but the address block did not

The central infrastructure story is the separation of routing identity from address ownership. AS49514's route vanished, but 62.122.160.0/21 later returned under another origin. RIPEstat's prefix routing history shows three distinct phases.

In the first phase, AS49514 originated the /21 from January 2010 until October 2011. The history then shows a long observation gap. It does not establish whether addresses were unused, privately reachable, carried in a way the selected collectors missed, or undergoing a transition. Public BGP history can show absence from its collected global routes; it cannot prove that every device was powered off.

In the second phase, AS28717 began originating the same /21 in December 2013 and remained the observed origin into April 2025. The current AS28717 registration calls it GlobalConnect-AS28717 and notes that it was formerly Zen Systems. PeeringDB's AS28717 entry says that network is part of GlobalConnect, is single-homed behind AS31027 and is being gradually decommissioned. That account fits the next visible change, although it does not disclose a 2FAST-specific migration.

In the third phase, AS31027 began originating 62.122.160.0/21 in April 2025. There was a short overlap in the coarse routing-history intervals before AS28717 disappeared. On 10 July 2026, the prefix's RIPEstat routing status showed AS31027 as the sole observed origin and visibility at all 327 listed IPv4 RIS peers. The prefix overview named GlobalConnect A/S as the holder of the active origin AS.

That sequence is compatible with a carrier consolidation from a legacy GlobalConnect network into the group's main Danish AS. It is not proof of why the move happened or what equipment changed. The route could have shifted while servers stayed in place, while workloads moved between facilities, or while only an upstream configuration changed. BGP reveals the public origin and path; it does not show the rack, cable, power feed or customer application behind an address.

The resource registration remained with 2FAST. RIPE's current inetnum record still names JAYNET-2FAST-DK, references the 2FAST organisation and marks the range assigned provider-independent. The current organisation record gives the company name, Denmark, CVR number 30604040 and the Aalborg address. Administrative persistence and route operation have therefore diverged without the address block itself disappearing.

Registered policy is not current forwarding

The present AS49514 record still lists route policy with AS28717 and AS3308. On its face, that can look like two available upstreams. RIPEstat's live checks say otherwise. The AS overview marked AS49514 unannounced at the 10 July 2026 observation point. Its announced-prefix result returned an empty list, and the neighbour result counted no observed neighbours.

The routing-consistency result makes the mismatch explicit. It finds the /21 and both declared peers in registry policy, but it does not see the prefix, imports or exports in BGP under AS49514. The correct reading is not that 2FAST currently has two working upstreams. It is that an old policy remains registered while the public route has moved elsewhere.

Route registrations add another layer of potential confusion. A RIPE route search for the /21 returns route entries for AS28717, AS31027 and AS49514. The AS31027 entry was created in January 2024; the AS49514 entry was created in April 2025, years after that AS was last observed originating the block. These entries authorize or document possible routing policy. They are not three live announcements and do not provide three-way resilience.

Route-origin authorisation behaves similarly. RIPEstat's checks report a valid authorisation for the current AS31027 origin. Separate valid authorisations also exist for AS28717 and AS49514. Multiple authorised origins can ease controlled migration or fallback, but they widen the set of origins that route-origin validation would accept. They do not establish that dormant routers, carrier circuits or failover procedures are ready.

This is the installed-versus-usable distinction in its clearest form. AS49514 is installed administrative capacity: it exists and is assigned. Its policy names peers, and a valid origin authorisation exists. Usable public routing capacity through AS49514 is zero in the current observation because it announces no space. The /21 is installed address capacity registered to 2FAST and usable public address capacity because GlobalConnect announces it. Neither measure says how many addresses host working services, how much traffic the block carries or what bandwidth is available.

The /21 is live, but its operating purpose is opaque

At 2,048 addresses, 62.122.160.0/21 is large enough to matter to a small hosting or business-connectivity operation. Yet address count is not customer count. One customer can use many addresses; many users can share one; network equipment and spare inventory can consume space; old assignments can remain configured after workloads move. The public route proves reachability toward the block, not utilisation inside it.

A current IPinfo range profile associates the /21 with 2FAST while identifying AS31027 as the announcing network. It reports eleven hosted domains across seven addresses and says 27 addresses responded during its scan. The same service places some responding addresses around Aalborg. These observations suggest that at least part of the range still reaches active systems. They cannot identify the operator of each machine, the contractual customer, the physical facility or the completeness of the scan.

Another commercial geolocation result illustrates the uncertainty. IP2Location's view of 62.122.162.96 labels the address 2Fast A/S and data-centre or transit use, but places it in Copenhagen. IP geolocation is inferred from network and commercial datasets, not a survey of rack coordinates. The Aalborg and Copenhagen labels should not be averaged into a route. Their disagreement is evidence that the exact operating location is unresolved.

The company's own domain no longer supplies a current service surface. A live DNS lookup for 2fast.dk returns an address associated with a domain-parking service and authoritative nameservers at parkingcrew.net. The site does not resolve into the 2FAST /21. A parked domain does not prove the company has stopped every activity, and a company can provide services without a public website. It does remove one of the most ordinary ways a current ISP would publish offers, support contacts, outage notices and serviceability information.

The combination is unusual but coherent: the legal company survives; the old web identity is parked; the old AS survives without routes; the provider-independent address block survives with active endpoints; and a carrier now originates that block. This looks more like retained network resources and legacy hosting continuity than a current regional access business. It may support valuable services, but the public record does not enumerate them.

Provider-independent space explains the block's endurance

The ASSIGNED PI status is central to understanding why the address block could survive several carrier eras. RIPE's current IPv4 policy distinguishes provider-independent space from addresses drawn from a carrier's own provider-aggregatable allocation. The point of independence is administrative portability: an end user can retain its assigned range while changing the network that announces it, provided the applicable registration and contractual requirements continue to be met.

That is almost exactly what the route history shows. The prefix remained identified with 2FAST while the observed origin moved from AS49514 to AS28717 and then AS31027. This continuity can spare operators and customers from renumbering every server, firewall rule, remote-access configuration, DNS record and third-party allow-list when a carrier arrangement changes. For a hosting business, continuity of public addresses can be commercially important even after the original routing design is retired.

Portability does not mean autonomy from all suppliers. RIPE explains that holders of independent internet-number resources maintain a contractual link through a sponsoring Local Internet Registry. The 2FAST records currently identify GlobalConnect as the sponsoring organisation and use GlobalConnect-linked maintainers and contacts. The company retains the resource registration, while the sponsor supports registry administration and the carrier supplies the observed route.

This creates a layered stewardship problem. The address holder needs accurate records and authority over the prefix. The sponsor needs a valid contractual and administrative basis. The announcing network needs filters, route policy and operational approval. The host needs working equipment and local transport. A failure or ownership change at any one layer may require coordination with the others, even though only AS31027 appears as origin in the public route.

The persistence of the registration is itself evidence of maintenance, but only administrative maintenance. The AS49514 version list records nineteen revisions between 2009 and 2022. The inetnum version list records sixteen revisions through 2022, and the associated organisation entry was updated again in 2026. These changes show that the records were not simply abandoned in their 2009 form. They do not prove a 2FAST engineer changed a router or attended a facility.

The current multiple-origin authorisations fit the portability story. RIPE's RPKI guidance notes that a prefix holder can authorise a third party as BGP provider and can maintain separate authorisations when one prefix may be originated from multiple ASNs. For 2FAST's /21, AS31027, AS28717 and AS49514 each have an authorisation. This makes the historical origin changes less likely to be rejected by networks that validate route origins.

It also creates a housekeeping question. Every extra authorised origin is another AS that could originate a route without failing origin validation. That may be intentional for migration or contingency. If AS28717 is being decommissioned and AS49514 has been dormant for nearly fifteen years, retaining all three authorisations may provide flexibility, or it may preserve rights that are no longer operationally needed. Public data cannot identify intent. A robust review would ask whether each authorisation has a documented purpose, owner and expiry decision.

Renumbering risk remains the alternative. If the company ever returned the provider-independent assignment, systems still tied to those addresses would need new space unless another arrangement preserved them. DNS can be changed, but external allow-lists, certificates, remote peers and embedded configuration often lag. The fact that the /21 has remained visible under later origins suggests continuity mattered to someone. It does not reveal whether the beneficiaries were 2FAST, former customers, affiliated companies or services managed wholly by a carrier.

The economic value of continuity should not be confused with the economics of a regional ISP. A stable address block can support hosting or business systems without paying for street-by-street access construction. Its costs concentrate in sponsorship, transit or carrier service, facility operation, equipment and administration. That is a different cost base from fibre drops, radio installations and household support. It reinforces the category downgrade while explaining why the network resources can remain useful.

The physical asset boundary stops at the carrier handoff

For a normal regional ISP assessment, the physical chain begins at a customer's router or radio, continues through a drop, pole, tower, cabinet or street fibre, reaches aggregation and then exits through upstream carriers. For 2FAST, public evidence begins much farther up that chain. It shows addresses, route origins and administrative contacts. It does not show a customer access line.

The safest physical interpretation is a carrier handoff serving systems that use the /21. Those systems could be physical servers, virtual machines, firewalls, mail platforms, customer equipment or reserved addresses. They require a facility, power, cooling, switching, transport and people able to intervene. Public sources do not identify who owns that equipment, where it is housed, whether 2FAST manages it directly or whether a supplier provides the whole stack.

GlobalConnect's role is visible at several boundaries. AS31027 is the current origin. The /21's registry record is maintained through GlobalConnect-linked contacts. AS28717, the preceding origin, is also now a GlobalConnect network. The current 2FAST autonomous-system entry lists GlobalConnect-linked administrative and technical contacts. That is strong evidence of carrier and registry support. It does not transfer legal registration of the /21 away from 2FAST, and it does not establish who answers a customer support call.

No public record reviewed for this article identifies a 2FAST data-centre suite, an Aalborg network operations room, a carrier entrance, a power supply, a generator, batteries, a spare-router inventory or an on-call roster. The Ved Stranden address is a registered business location, not verified network plant. Nor is there current evidence of 2FAST-owned poles, towers, ducts, street cabinets, radio spectrum or premises equipment. Drawing any of those assets into a current network map would be invention.

This changes the likely repair sequence. If an endpoint in the /21 fails, the first questions concern the host, switch, power domain and facility. If the entire /21 disappears globally, the questions move toward the route origin, carrier edge and route policy. If only one distant user cannot reach it, the fault may lie elsewhere on the internet. None of those cases requires a 2FAST crew to repair a household drop, because no such access responsibility is evidenced.

One current origin is not one physical route

The public BGP view shows AS31027 as the sole origin of 62.122.160.0/21. That is an important concentration at the policy layer: all global reachability for the aggregate currently names one originating AS. It should not be translated into a claim that one fibre, one building or one router carries every packet. A large carrier AS can operate many edge routers and paths while presenting one origin number to the world.

The reverse mistake is equally risky. Global visibility at all 327 observed RIS peers does not prove physical redundancy. Every peer can learn a route that ultimately depends on one local handoff, one powered switch, one rack or one cross-connect. Route collectors see the advertisement after it has propagated; they cannot inspect the local common point that might fail before traffic reaches the carrier backbone.

The move from AS28717 to AS31027 may improve operational consolidation. PeeringDB describes AS28717 as a legacy network behind AS31027 and being decommissioned, so carrying the /21 directly from AS31027 removes one visible legacy layer. It may also change route policy, monitoring and support ownership. No public evidence establishes the physical before-and-after design, measured latency, outage reduction or available headroom.

The dormant AS49514 is not an observable backup. To provide fallback, it would need working routers, sessions to one or more carriers, filters, accepted announcements, monitoring, capacity and a tested decision process. The valid route-origin authorisation and registry policy solve only narrow prerequisites. RIPEstat sees no current neighbours or announcements, so it would be misleading to count AS49514 as a second live exit.

AS3308's continuing presence in the registered policy is also not a proven alternate. The company may retain a contract or configuration that is invisible, but no current public path shows AS3308 adjacent to AS49514. A resilience claim would need a current session observation or operator disclosure, followed by proof that the physical handoff is independent of GlobalConnect's route. Neither is public.

Outsourcing changes the recovery contract

Moving route origin to a carrier can remove operational work from a small resource holder. GlobalConnect can manage external BGP sessions, filtering, propagation and backbone routing at a scale that 2FAST's current financial footprint would struggle to reproduce independently. The full visibility of the /21 and its valid current origin show that this part of the arrangement is functioning at the observation point.

What outsourcing does not remove is the need to define the line between carrier and customer. A provider may commit to deliver the prefix to a handoff while the customer remains responsible for the router beyond it. A managed host may own the router and servers but depend on a separate facility for power. Another agreement may place almost everything with one supplier. Without the contract, a route registered to 2FAST and originated by GlobalConnect cannot reveal where responsibility changes.

That boundary determines the first recovery call. If AS31027 withdraws the route globally, carrier routing staff are central. If the route stays visible but every address fails, the facility or customer-side handoff becomes more likely. If one service fails, its server, software or firewall may be responsible. A useful escalation plan needs these patterns mapped to named responsibilities before an outage; the public record provides no such map.

Service restoration also depends on what has been purchased. Carrier diversity can mean two logical sessions, two access circuits, two entrances into one building, or two genuinely separated facilities and routes. Each costs more and protects against a different failure. The public view exposes only the final origin AS. It does not show whether 2FAST or a host pays for dual access, whether failover is automatic, or whether the second path has enough capacity for the full load.

The labour question moves with that boundary. A regional access operator needs installers and field technicians across its service territory. A hosted-address arrangement may need a remote-hands technician, a network engineer and an account escalation path instead. No current evidence identifies either workforce for 2FAST. GlobalConnect-linked registry contacts show administrative and technical association, but a registry contact is not a guaranteed incident responder for a specific customer service.

Power recovery is similarly local. A carrier backbone can remain healthy while a customer rack loses utility supply. Batteries can bridge short interruptions, and a generator can extend runtime, but neither is evidenced for the unknown facility behind the /21. The company office address cannot substitute for a facility record. Any image of a generator, dual utility feed or redundant data hall would make a claim the reporting cannot support.

Outsourcing can still be the rational design. It can convert capital spending into a recurring supplier bill, pool specialist labour and avoid maintaining a tiny independent edge. The 2019 capital-management description and the later carrier origins are consistent with that direction. They do not establish the contract terms, savings or service quality. The measured conclusion is narrower: current routing responsibility is visibly concentrated in GlobalConnect's AS31027, while the local operating and recovery boundaries remain undisclosed.

What can fail, and who would notice

The most consequential current failure is a withdrawal or loss of reachability for 62.122.160.0/21. If AS31027 stopped announcing the aggregate and no authorised alternate took over, systems using public addresses in the block could become unreachable from the wider internet. Hosted websites, mail services, remote administration or business applications could fail depending on what actually resides there. The public inventories are too incomplete to name all affected users.

A facility or power failure could produce a different pattern. The BGP route might remain perfectly visible while the servers behind it stopped responding. A carrier can continue advertising a customer's block even when the local handoff is down, unless routing or monitoring is configured to withdraw it. That is why a globally visible route is not an availability measurement for every address.

A local transport cut between the hosting site and GlobalConnect could have the same effect. Whether traffic can move to a second entrance depends on physical path diversity, edge configuration and facility design. None is disclosed. The old two-upstream policy cannot answer the question because AS49514 is dormant, and the present route is not originated there.

An equipment fault inside the address holder's environment could affect one subnet or service while leaving the aggregate and other endpoints healthy. Recovery would depend on spare switches, routers, optics, servers, backups and staff or contractor response. The company accounts do not disclose such inventory, and the public company pages do not identify an operations team. Absence of a public roster does not prove nobody is available; it means response capacity cannot be scored.

There is also administrative recovery risk. The company, address sponsor and announcing carrier occupy different roles. A route-policy change may require authorisation from the resource holder and action by the carrier. A facility fault may require a host or landlord. A customer application may belong to a third party. Clear escalation rights matter when these roles are split, but contracts and service-level commitments are not public.

The people affected are therefore not safely described as Aalborg broadband subscribers. They are the owners and users of whatever systems remain on the /21, plus counterparties that depend on those addresses. The third-party scan suggests a small visible set of hosted domains, but it is neither a customer list nor a full dependency inventory. The block could contain private business systems, dormant addresses, services that reject probes or infrastructure that is visible only under other names.

Installed capacity and usable service are different quantities

The evidence offers several numbers that should not be added together. The /21 contains 2,048 IPv4 addresses. AS49514 has one historical prefix registration. Its current policy lists two intended peers. Three origin ASNs have route entries, and three origin authorisations validate separately. None of these is bandwidth.

Current usable public route capacity is simpler: one aggregate is originated by AS31027 and widely visible. There is no IPv6 space announced by AS49514, and no current AS49514 route at all. The prefix may carry many gigabits or almost none; public route data does not say. A responsive address may host a busy platform or a forgotten service. A non-responsive address may still be assigned and filtered.

The absence of more-specific announcements also limits what can be inferred about public traffic engineering. RIPEstat's current status shows the /21 without visible more-specific routes. The carrier may still have rich internal routing, multiple facilities and private failover. From outside, the block presents as one aggregate. If traffic engineering or selective failover exists below that aggregate, it is not exposed through public BGP.

The route-origin authorisations improve one security property. A network performing RPKI origin validation can recognise AS31027 as authorised for the /21, reducing the chance that an unrelated origin is accepted accidentally. This does not stop an authorised carrier from withdrawing the route, a fibre from being cut, a server from losing power or a valid route from leading to an unreachable handoff. Security validity and service availability answer different questions.

Financial capacity is similarly separate. Equity of DKK 532,649 may support obligations and small investments, but it is not a measure of spare routers, generator runtime or carrier bandwidth. The accounts do not isolate network spending. Any resilience judgment that converts the balance sheet into technical capacity would be speculation.

What would justify an upgrade

The company could be reclassified if new evidence established a current access business. The most persuasive material would be a live 2FAST service page with dated tariffs, a defined Danish service area, installation terms, support contacts and legal particulars matching CVR 30604040. Current regulatory or wholesale records naming 2FAST as an active access provider would strengthen that case.

Physical claims would need their own support. A route or asset description could show owned or leased fibre, building access, radio sites, cabinets or customer equipment. Maintenance notices could demonstrate actual repair work and restoration times. Current job postings, contractor statements or service commitments could establish local support labour. None should be inferred from the company's broad IT industry code or its historical connectivity offer.

The carrier-hosting interpretation could also become much more precise. 2FAST or GlobalConnect could identify the facility boundary, whether the /21 serves hosting customers, which party owns the edge equipment, whether two carrier entrances exist, how power is backed up and what happens if AS31027 loses the local handoff. A current statement on the purpose of AS49514 would explain whether it is retained for contingency, administrative continuity or possible future use.

Routing evidence alone can still answer useful follow-up questions. A future reappearance of AS49514, a second concurrent origin, new more-specific routes, an IPv6 announcement or a new observed neighbour would materially change the edge assessment. Each would remain a logical signal until physical independence and capacity were shown.

The acquisition signal also has a clear verification path. A company or buyer announcement, filed sale document, archived customer notice or authoritative corporate history could establish whether Jaynet bought 2FAST's hosting or connectivity business and what remained behind. Until then, the customer review explains the later routing pattern plausibly but cannot carry a factual transaction claim by itself.

A live prefix can outlast the business readers imagine

2FAST is a good warning against equating internet-number resources with an ISP. The company had a real independent route, intended connections to two outside networks and a broad IT-services offer. That history left durable traces: AS49514, a provider-independent /21, route registrations, origin authorisations and addresses that still reach the internet.

The operating arrangement changed. 2FAST's own route disappeared in 2011. The prefix returned behind AS28717, stayed there for more than a decade and moved to AS31027 in 2025. Both later origins now sit within GlobalConnect's network family. The company remained the registered address holder while the carrier supplied public routing.

That split can be entirely functional. A small company does not need to originate its own routes to keep hosted addresses reachable, and outsourcing can place operation in the hands of a better-resourced carrier. It also means that the old resilience questions must be rewritten. Upstream diversity is no longer counted from AS49514's policy. Field repair is not a tower or household-drop problem. The relevant unknowns are the local carrier handoff, hosting facility, power, equipment, supplier escalation and the systems that still depend on the addresses.

The network evidence grade is Negative for the commissioned regional-ISP thesis, not for the existence of every 2FAST-linked service. Legal continuity is strong. Historical routing is strong. Current reachability of the /21 through GlobalConnect is strong. Evidence of a current 2FAST access plant, retail offer, service territory, field workforce and subscriber population is absent.

The responsible headline therefore follows the route rather than the old category. 2FAST retains a live /21, but GlobalConnect carries it. Until current access evidence appears, that is an address-resource and carrier-dependency story, not a local connectivity bill supported by 2FAST poles, towers and repair crews.