Summary

  • AS210057 (as-name INFINITYWIFI, organization INFINITY LINE SRL) originated 136.148.140.0/22 and 185.182.208.0/24—roughly 1,280 IPv4 addresses—continuously across the June 6–September 6, 2026 window, with valid ROAs, valid route objects and zero new, left or unstable prefix events.
  • Reach depends entirely on two customer-to-provider upstreams, AS50877 AIRBEAM (Italy) and AS9002 RETN (United Kingdom); no internet exchange peerings were observed between June 23 and September 23, 2026, and no IPv6 is announced.
  • Registry and routing hygiene is complete on every automated surface that checks one: the RIPE record shows no retrieved modification after July 7, 2026, the IRR as-set verifies, and PeeringDB's automated RIR status check passed on August 17, 2026. None of it identifies who exercises durable operational control.
  • No retrieved source supports any linkage between AS210057 and Comcast or the Xfinity WiFi service; the finding is a supported absence, not a denial beyond the evidence.
  • Continuity is duration, not a state change. The observable deltas that would constitute real change—another upstream, a peering, IPv6, a confirmed ASPA, an origin change, a registry or PeeringDB change, or a named operator—are specified at the end of this article.

A quarter of continuity, and still no operator

Every network produces evidence at two speeds. Packets produce it continuously: announcements, withdrawals and path changes are visible, within the limits of where one watches from. Registries produce it in steps: a record is created, modified, checked or expires, and between those steps it simply sits. When the continuous stream and the discrete record agree for long enough, observers start treating the combination as a personality—this network is stable, this network is professional, this network can be trusted. For AS210057, that inference is where the case becomes interesting, because the inference is only half earned.

The stable part is real and now quantified. Qrator's Radar recorded both prefixes as originated by AS210057 across the entire June 6–September 6, 2026 window: 136.148.140.0/22 observed by 573 vantage points and 185.182.208.0/24 by 559, 100 percent propagation in each case, with a change table reading zero new, zero left, zero unstable prefix events and valid ROAs and route objects on both prefixes throughout. Qrator Radar's prefix window The uninterrupted part is real as well: the network's RIPE record was created on May 18, 2026 at 10:27:44 UTC and carries a last-modified timestamp of July 7, 2026 at 17:43:39 UTC, with no retrieved data evidencing any change since. RIPE Database query

What the combination does not yet earn is the personality. Stability plus hygiene plus time describes a surface, not an operator behind it. A stub network running on two transit contracts and no interconnection of its own can generate exactly this evidence pattern indefinitely—whether it is run by a small ISP serving a handful of subscribers, by a leased-resource vehicle of some larger arrangement, or by an artifact that someone keeps alive because letting it lapse would cost more than maintaining it. The record does not distinguish among those possibilities.

Saying precisely what the record does distinguish, and naming the events that would force the distinction into the open, is the work of the sections that follow.

What the RIPE record does—and does not—establish

The registry layer is the only layer with a named party, so it deserves an unsentimental reading. The RIPE database's query interface returns the object at the center of this story: an aut-num for AS210057 with as-name INFINITYWIFI, organization ORG-ILS14-RIPE—the legal entity INFINITY LINE SRL—status ASSIGNED, created 2026-05-18T10:27:44Z, last modified 2026-07-07T17:43:39Z, and maintained by RIPE-NCC-END-MNT together with the LIR-side maintainer lir-it-infinity1-1-MNT. RIPE Database record

Each field does specific, bounded work. The organization field binds the number to a legal person: INFINITY LINE SRL is the entity of record through which the resource relationship with the registry runs. The ASSIGNED status marks the resource as allocated for end use rather than held in reserve. The maintainer set defines who may change the object, which makes it the practical gate on the record's future. The timestamps make the whole construction auditable in time. These are real properties, and on them the registration layer is in good order.

What the object cannot do is more consequential for this article. An aut-num is a registration claim—processed by the registry, binding a number to an organization as of a date. It is not an observation of operations. The record says nothing about who holds the ROA signing keys for the two prefixes, who authenticates against the LIR maintainer in practice, who answers the abuse contact, whether INFINITY LINE SRL employs anyone, or whether the resource serves subscribers, resale customers or nobody at all.

The stable timestamps bracket a period in which the record has been consistent in retrieved views—but a mirror's silence is not the registry's certification, and a stable record is compatible with any operating reality behind it, from meticulous to abandoned.

The disciplined conclusion: the registry would hold INFINITY LINE SRL responsible for the number's registration. Whether that party—or anyone acting for it—is the party that runs the network is exactly the question the record is built not to answer.

Two prefixes, zero events, no IPv6

The routing surface is small enough to describe completely, and its completeness is itself information. AS210057 announces two IPv4 prefixes: 136.148.140.0/22 and 185.182.208.0/24, together roughly 1,280 addresses—on the scale of a single mid-sized enterprise's address space, not the footprint of a consumer access network at any serious subscriber count. Across the June 6–September 6, 2026 window both prefixes held RPKI status Valid and route-object status Valid, with propagation of 573 and 559 observing vantage points at 100 percent and a change table showing no new, no left and no unstable events. Qrator Radar's prefix window

Three months of zero events is a strong statement about the network's maintenance discipline: prefixes do not stay originated, valid and stable across two quarters' boundaries by accident. Someone is renewing, monitoring and, where necessary, repairing the announcement chain. The telling number, though, is the one that is missing. No IPv6 prefixes are announced by AS210057 anywhere in the retrieved data.

For an operating service provider in 2026, that absence is economically legible: IPv6 deployment is the standard marker of a network building for subscriber growth, device compatibility and wholesale interoperability, and its total absence narrows the commercial hypotheses. A network with none is either deliberately minimal, financially constrained, or not serving the subscriber-like base its registration name evokes. The record does not select among those readings; the absence simply prices down the growth story until evidence arrives.

The reachability classification threads the same needle from the measurement side. It belongs with the topology, so it is taken up with the upstreams next.

Two upstreams: a rational, binding dependence

The aut-num's declared policy names the network's entire upstream portfolio: accept ANY from AS50877, accept ANY from AS9002, and export to each the as-set AS210057:AS-INFINITYWIFI together with the bare AS210057. declared import/export policy, Qrator whois view Observed adjacency matches the paper exactly. Qrator's neighbor table for the June 20–September 20, 2026 window lists precisely two customer-to-provider neighbors—AS50877 AIRBEAM, registered in Italy, and AS9002 RETN, registered in the United Kingdom—under the same zero-event change table as the prefixes: no new, no left, no unstable neighbor relationships. Qrator's neighbor table

Independent corroboration from a second measurement plane agrees. At the TOP-IX route server rs02, reached through its neighbor AIRBEAM, both of AS210057's prefixes arrive as RPKI Valid best routes with the AS path 50877 210057, next hop 194.116.96.175 and local preference 100. The covering aggregate 185.182.208.0/22 appears in the same table originated by AS50877 alone, also RPKI Valid. TOP-IX route-server looking glass The distinction deserves its own sentence: AS210057 originates the /24 more-specific of 185.182.208.0/24, while its upstream originates the /22 that contains it. The two facts coexist; conflating them would misattribute a prefix—one of the exact errors layered-evidence discipline exists to prevent.

The third leg of the topology is what is missing from it. No internet exchange peerings were observed for AS210057 across the June 23–September 23, 2026 window. Qrator's peering window Combined with a reachability classification Qrator keeps in its lowest visibility band—Local (5-15%)—the result is a textbook transit-only stub: a network that buys all of its reach at wholesale and sells whatever it sells downstream, owning no interconnection asset of its own.

Read economically, the configuration is neither exotic nor alarming; it is the standard shape of a very small ISP, and at this scale it is rational. Two upstreams is the cheapest path diversity money can buy. It survives the failure or exit of one provider without renegotiating from zero, and it costs far less than exchange membership, cross-connects and peering operations for a traffic profile that would never justify them. The two-upstream choice is a budget decision, not an engineering statement, and this coverage reads it as exactly that.

Rational dependence is still dependence, however—of a doubled kind. Each upstream relationship is a separate contract with its own pricing cycle, its own termination clause and its own tolerance for a small, quiet customer. Either provider can, unilaterally and within a billing cycle, remove half of AS210057's reach; both together can remove all of it. The two-provider structure hedges single-provider failure, and in exchange it doubles the number of counterparties whose commercial decisions shape the network's continuity.

The bargaining power is not symmetrical: AS50877 and AS9002 can replace a customer of this size far more easily than this network can replace either of them. Whatever margin the operation produces—if it produces one—is the residue that survives two transit invoices.

Hygiene is an entry ticket, not market power

Layered over the topology is a security-and-discoverability posture that is complete by the standards of small networks. Qrator's overview counts two valid ROAs and two valid route objects, lists two providers, shows an ASPA section with no confirmed authorization, and classifies reachability in its Local (5-15%) band. Qrator's AS overview The same dashboard's windowed views disagree at their edges: the provider subpage, in the April 29–July 29 window, rendered only AS9002, while the neighbors window of June 20–September 20 and the overview count both AIRBEAM and RETN. Qrator's provider subpage The honest reconciliation is the one this coverage has applied throughout: two upstreams are corroborated by the declared policy and the independent looking glass; the provider composition in any single window is a dynamic render to be re-verified live, not a fixed fact to be hardened.

The voluntary layer confirms the posture. The PeeringDB record for ASN 210057, filed under organization INFINITY LINE SRL, was last updated on August 17, 2026 at 11:56:30 UTC; its automated RIR status check reads ok as of the same day's 22:55:04 UTC update, and its IRR as-set status reads Verified. PeeringDB What the record does not disclose is equally legible: traffic levels, geographic scope, facility presence and network types are all blank. NLNOG's IRR Explorer resolves the as-set AS210057:AS-INFINITYWIFI in the RIPE IRR at depth 1 with exactly one member, AS210057 itself. IRR Explorer

Precision about what this stack proves matters, because over-reading it is the main analytical trap in this subject. Valid ROAs and route objects mean that any neighbor validating origins will accept the announcements as authorized. A verified as-set means import filters built on the RIPE IRR resolve to exactly the network that declares them. A passing PeeringDB check means an automated process found the registry state consistent at a moment in time. Together these make the network filterable, resolvable and processable—the minimum conditions for participating in the 2026 internet at all. Hygiene is the entry ticket.

It is not evidence of scale, market power or control. PeeringDB is self-maintained and voluntary; its ok is a periodic automated check, not a certification of current operation, and its blanks—traffic, scope, facilities—are either modesty, omission, or the signature of a network that lives primarily in registries rather than in facilities. The record does not say which, and this article does not guess. What can be said is that hygiene and attribution are orthogonal: the network passes every published check while the identity of its controller stays off the record, because none of the checks was designed to look for one.

The mirrors multiply; the evidence does not

Beyond the registries and the measurement platforms, the AS210057 record circulates through the commercial ASN-profile ecosystem. TheIPAPI maintains a profile page for the autonomous system, IPGeolocation carries it in its ASN browse index, and DB-IP indexes its profile under the organization's name, as the page address itself advertises. TheIPAPI, IPGeolocation, DB-IP

These services perform a real function—routing metadata made searchable for procurement, security and geolocation audiences—and their repetition of the AS210057-to-INFINITY LINE SRL association keeps the organization's name discoverable. Their evidentiary weight for the attribution question is nonetheless zero, and it is worth saying why plainly. Each profile is a derivative product: a re-rendering of registry and routing data that already exists elsewhere, filtered for presentation. They inherit the registry's association; they do not verify it.

A contact handle rendered in one mirror and stripped in another is an administrative pointer, not a person accountable for operations. A geolocation service's copy of an origin relationship observes the same announcements the route servers observe; it audits nothing. The multiplication of mirrors increases the surface on which the network's existence is visible. It does nothing to increase the depth at which the network is understood.

Continuity is duration, not a state change

BTW published three pieces on this subject in three days in September 2026, and their conclusions frame precisely what the new data adds. The first, published on September 9, decomposed the footprint into layers—administrative registration, origin claims in the authorization objects, observed BGP visibility and the voluntarily declared network profile—and concluded that the layers, while individually verifiable, did not yet form a verified chain to a durable operator, a customer responsibility or a commercial value attributable to INFINITYWIFI; it found, equally, no support in any retrieved source for a linkage between AS210057 and Comcast or the Xfinity WiFi service, framing that as a supported absence rather than a denial. BTW's evidence-chain analysis The second, published the next day, asked the institutional question across the same layers—who can correct an erroneous record, who can authorize or revert a routing action, and who owes a remedy when service fails—and found a different responsible actor, and a different evidence standard, at each. BTW's record-correction analysis The third separated the three meanings of network control outright: registered responsibility, operational routing control and subscriber-service continuity, cautioning that the operator behind the control plane could not be identified from public data and that the directory object could not be equated, on current evidence, with any commercial service of a similar name. BTW's routing-control and continuity analysis

The current dataset is faithful to all three rather than departing from them. Same two prefixes. Same two upstreams. Same voluntary-record posture. Same unanswered attribution question, and the same two supported absences, now carried forward with a quarter's additional duration. What changed is only the calendar: the zero-event record on prefixes, neighbors and peerings now extends deeper into September than the windows those articles could see.

That is the finding, stated exactly. Continuity is duration, not a state change. A network that keeps announcing is not doing something new; it is doing the same thing longer. The informative content of the summer's data is not any event but the persistence of the evidence pattern itself—and persistence here is itself a finding, because whoever controls AS210057 has chosen, or been content, to keep a small, clean, low-visibility footprint alive and current through a full quarter. Nothing in that sentence requires, or rules out, anything about who they are.

The attribution gap, stated precisely

The accumulated record supports one sentence about what is established and one about what is not, and the difference between them is this article's core.

Established: an autonomous system, AS210057, registered since May 18, 2026 to INFINITY LINE SRL and consistent in retrieved views since July 7; two IPv4 prefixes announced continuously since at least June 6, 2026 with valid ROAs and route objects; delivery through exactly two upstreams; no observed peerings; no IPv6; a complete, verifiable hygiene posture on every automated surface that checks one; and no confirmed ASPA. Established as well, in the negative: no retrieved source supports any linkage to Comcast or Xfinity WiFi, and no public artifact identifies the hand behind the credentials.

Not established: durable operational control. Not by the registry's organization field, which binds a number to an entity for registration purposes but does not observe operations. Not by the ROAs and route objects, which prove that authorizations exist, not who authorizes. Not by the upstream relationships, whose commercial terms are invisible to the public record. Not by the mirrors, which are derivative. Not by the voluntary profile, which is self-declared and thin. BTW tracks INFINITYWIFI as a directory entry—a record of a coverage subject, not a finding of control [https://btw.media/en/directory/infinitywifi]—and this article extends that entry's discipline by a quarter's duration rather than closing its question.

Why the gap persists is the part most worth internalizing, because it is structural rather than mysterious. Nothing in the system generates a cost for silence. A registry assigns resources to organizations; it does not publish org charts. A routing system accepts announcements it can validate; it does not ask who holds the key. Upstream providers bill customers; they do not disclose them. Voluntary profiles reward participation, not disclosure. At this scale, anonymity is not merely possible—it is the default equilibrium, maintained by the ordinary operation of every layer rather than by any concealment.

Persistence-without-attribution is not an anomaly awaiting explanation. It is what a small, hygiene-complete, transit-dependent network looks like when no event forces it to become a story.

What would count as real change

Because the current state is continuity, the useful output is the list of events that would end it. Each is observable in public data within days of occurring, and each carries a specific economic meaning.

A third upstream, or a first observed exchange peering, would mark the beginning of interconnection: reach partially owned rather than wholly rented, the cost structure shifted, and the two-upstream dependence described above retired as a description. First IPv6 origination would signal a network building beyond its current footprint; today the count is zero. A confirmed ASPA would move route authorization from ROA-plus-route-object into the newer provider-authorization layer; its absence today is an absence of confirmation, not proof of nothing.

An origin-AS change on either prefix, or the revocation or replacement of either ROA or route object, would end the persistence narrative outright and convert the subject from continuity to event. A substantive modification to the aut-num or its organization after July 7, 2026—a new maintainer, a changed organization, an altered status—would be the registry's own signal that the arrangement behind the number is evolving; the threshold is deliberately substantive, since trivial cosmetic edits exist in any registry's history and the retrieved data shows none since that date.

A downgrade or removal of the PeeringDB record, or an RIR status check that stops passing, would erode the hygiene-complete characterization from the voluntary side.

The single most material change available is attribution: the appearance of a named operator or beneficial owner through a registry edit, a public filing, a service launch under a real brand, or disclosure by the organization itself. That is the event that converts an observed surface into an accountable operation. Until one of these occurs, the correct verb for AS210057 is not grew, launched or failed. It is persisted.

The bounded conclusion

The bounded consequence for readers is compact. A network named INFINITYWIFI exists as AS210057, registered to INFINITY LINE SRL since May 18, 2026, announcing roughly 1,280 IPv4 addresses through two transit providers, fully covered by valid ROAs and route objects, visible in every public mirror, and attributable to no named operator by anything in the public record. Its stability is real and, as of the September windows, unbroken. Its hygiene is real and complete.

Its controller is unnamed—and the three properties are mutually reinforcing rather than coincidental, because the same smallness that makes attribution unnecessary makes persistence cheap.

The next observable condition is the delta list above; any single item converts this subject from continuity back into news. The material uncertainty is unchanged from the first coverage and now carries a quarter's confirmation: the public record, as it stands, cannot answer who runs AS210057—and, short of an attribution event or a state change, nothing observable will answer it for free.