Summary

  • The available evidence separates registry assignment, database-maintenance authority, route authorization, observed routing, operational control and contractual responsibility.
  • A correction path can be identified only after the failed proposition is identified: a database error, suspected route misuse, service outage and consumer claim belong to different procedures.

The name INFINITYWIFI appears in the context of autonomous system AS210057, but the evidence package does not establish that the directory entity, the ASN, a legal company, a network operator and any similarly named consumer service are the same thing. The first discipline is therefore identity separation.

The IANA RDAP bootstrap registry indicates which Regional Internet Registry should provide authoritative RDAP service for an autonomous-system range. The RIPE NCC RDAP record for AS210057 and the native RIPE aut-num object are the relevant places to inspect the current registry label, linked organisation, status, contacts, maintainers and recorded events. The RIPE Database interface can help distinguish those fields from one another. A label such as an AS name is not, by itself, proof of incorporation, physical operation or a customer-service obligation.

The RIPE object-version endpoint may show how recorded fields changed over time. That history can establish that a database object changed; it cannot alone establish that a router, service or legal relationship changed on the same date. Likewise, RIPE NCC delegated statistics can help characterize resource assignment, but an administrative country code or assignment row is not proof of a company’s place of incorporation, infrastructure location or traffic origin.

Derived registry views such as the RIPEstat AS overview and RIPEstat WHOIS data are useful for orientation, but the native registry object remains the better basis for exact wording. An abuse-contact lookup can identify a channel for reporting suspected abuse or malicious traffic. It does not automatically identify the person who controls routers, owes a customer remedy, or can authorize a refund.

Seven layers of responsibility

The evidence should be read as a ledger rather than a single chain of ownership.

  1. Registry assignment. IANA and RIPE NCC records establish which registry service and current record are associated with AS210057. They do not identify every operator or service counterparty.
  2. Database maintenance. A maintainer or authorized account may be able to alter a RIPE Database object. That is authority over a record, not necessarily ownership of the ASN or control of the network.
  3. Route authorization. An inverse-origin search for RIPE IRR route objects can reveal policy assertions associated with an origin. An IRR object is not the same as cryptographic authorization and does not prove that a route is currently announced.
  4. Observed routing. Announced-prefix data, routing-status data, BGP-state data, and routing history describe what a collector observed during a defined interval. Observation is evidence of visibility from a vantage point, not proof of lawful control or a customer relationship.
  5. Cryptographic authorization. RPKI history, the RIPE RPKI guidance, the ROA profile in RFC 6482, and RIPE’s routing-security documentation help explain whether a prefix-origin relationship was authorized under the relevant system. Authorization still does not prove who operated every router or who owed an end user a service.
  6. Independent observation and network relationships. RIPE RIS, Route Views, the PeeringDB record, and BGP.tools’ AS view can provide corroborating observations or declared network information. They should not be promoted into proof of complete operational control.
  7. Service responsibility and remedy. A service obligation requires evidence such as an operative agreement, account record, invoice, support exchange, incident record or applicable regulatory jurisdiction. A registry contact is not automatically a service provider.

The identity bridge remains the missing instrument

The UK company-register search is relevant to testing whether a legal entity can be identified under a similar name. It cannot, without a matching corporate, registry, operational or contractual record, prove that a company is the holder or operator of AS210057. The available evidence also does not establish an identity bridge to Comcast or Xfinity WiFi. Name similarity is not an affiliation record.

That limitation matters because each conclusion would otherwise be overstated. A registered label cannot prove who configures routers. A route observation cannot prove who is entitled to announce a prefix. A maintainer field cannot prove who serves subscribers. An abuse mailbox cannot prove who owes compensation. A public company search cannot prove that a company operated a particular ASN during a particular period.

Match the remedy to the failed proposition

If the failure is an inaccurate database field, the first route is the RIPE Database documentation and support process, followed by the relevant RIPE contact channel or the authorized maintainer where appropriate. The remedy sought is correction of the record, not a finding about physical network control.

If the issue is suspected route misuse or malicious traffic, the initial path can include the registered RIPE abuse channel, the resource holder, and affected network operators. The technical case should preserve the prefix, origin, observation time, collector, validation status and relevant messages. A route collector can show what happened from its vantage point; it cannot by itself adjudicate the underlying rights.

If the issue is service failure, the relevant counterparty must first be identified. The Ofcom consumer complaint guidance may be relevant where the provider, service and jurisdiction fall within its scope. Ofcom’s General Conditions material describes obligations imposed on covered providers, but it does not establish that INFINITYWIFI or AS210057 is such a provider. The Communications Act framework and automatic-compensation guidance likewise cannot substitute for proof of provider identity, service terms, dates, fault and applicable jurisdiction.

A remedy therefore has at least four predicates: a named actor, a proven failure, standing or contractual connection, and a procedure with jurisdiction over the requested outcome. Without those predicates, a contact address is only a lead. Ofcom’s guidance on automatic compensation provides a further procedural reference where its conditions apply: automatic-compensation guidance.

What would change the finding?

The analysis would materially advance if a current RIPE organisation object linked AS210057 to a verified legal entity; if a dated contract or operator statement identified who could initiate or reverse routing changes; if a prefix-level authorization and collector record were aligned for the same interval; or if a customer account, incident record or regulator proceeding identified the service counterparty and remedy. Those documents would not collapse every layer into one fact, but they would connect the relevant layers with named instruments.

For now, the defensible conclusion is narrower: the public record provides separate routes for examining registry data, database authority, route authorization, routing visibility and possible remedies. It does not yet identify the person or legal entity with demonstrated power to control AS210057’s routing or to answer for a subscriber-service failure.