Summary

  • The RIPE Database associates AS210057 (as-name INFINITYWIFI) with responsible organisation INFINITY LINE SRL and an abuse contact of abuse (at) infinitywifi (dot) it — the only publicly registered prevention-and-response artifact for this network. (RIPE Database query)
  • The organisation object ORG-ILS14-RIPE is an Italian LIR (reg-nr 04837890161, Via San Sosimo 23, 24030 Palazzago, phone (as listed in the RIPE organisation object)) carrying abuse-c AR80070-RIPE, and is maintained by RIPE-NCC-END-MNT and lir-it-infinity1-1-MNT. (Qrator Radar WHOIS, IPGeolocation.io)
  • The network announces two IPv4 prefixes — 185.182.208.0/24 and 136.148.140.0/22, roughly 1,280 addresses — with no IPv6, importing transit from AS50877 and AS9002; PeeringDB shows RIR status "ok" and an IRR AS-SET flagged "Verified", last updated 2026-08-17. (PeeringDB, DB-IP)
  • The operator's homepage is a commercial funnel — InfinityHome, InfinityBUSINESS, plans from 24.90 EUR/month with direct telephone assistance — with a generic contact route and no abuse-reporting page, status page or incident-response channel surfaced in retrieval. (infinitywifi.it)
  • No retrieved source shows the registered abuse address was ever exercised, monitored, or bound to any response-time or incident-handling obligation; and a StatusGator page for a namesake "Infinity" service (app.startinfinity.com, Texas and Scotland) is a brand-name collision that must not be attributed to this network. (StatusGator)

The facts above are the whole of what this article can responsibly assert. They come from registry objects, derived mirrors, one voluntary peering record and one commercial homepage — none of which are instruments of operational conduct. That distinction is not a caveat tacked on at the end; it is the finding.

A channel is not a function

Start with the one artifact that looks like a control. The RIPE Database query for AS210057 returns "Responsible organisation: INFINITY LINE SRL" and "Abuse contact info: abuse (at) infinitywifi (dot) it". (RIPE Database query) The same address is reproduced independently by IPGeolocation.io's ASN view, which carries it alongside the organisation object's abuse-c handle AR80070-RIPE, and by DB-IP's mirror. (IPGeolocation.io, DB-IP) Three sources agree on the string, so the fact that a registered reporting channel exists is well corroborated at the registry layer.

What no source establishes is that the channel performs. A registered abuse contact is a declaration, not a mailbox with a service-level agreement. Nothing in the RIPE record commits the organisation to a response time, a triage process, an escalation path, or any remedy for a person harmed by traffic originating from 185.182.208.0/24 or 136.148.140.0/22. Nothing in the retrieved record shows the address was ever sent a complaint at all, let alone answered one.

The distinction between a channel existing and a channel working is the difference between paperwork and prevention, and for AS210057 the public record sits entirely on the paperwork side.

This matters because registry data is self-declared. The RIPE NCC's own documentation on database security explains that every object must be protected by a maintainer, that maintainers are anonymous, and that an LIR's default maintainer allows the resource holder to edit admin-c, tech-c and abuse-contact details. (RIPE Database Security documentation) In plain terms: the party named as INFINITY LINE SRL controls, through the maintainer lir-it-infinity1-1-MNT, who the abuse contact says it is. RIPE-NCC-END-MNT gates registry-side fields. (Qrator Radar WHOIS) The gate proves that the record cannot change without someone holding those credentials — it does not prove that anyone holding them reads the mailbox the record advertises.

What the network's shape tells us about the response question

The routing layer, already documented in two prior BTW reports, is consistent and clean: two IPv4 prefixes announced continuously through the summer of 2026 with valid ROAs and route objects, zero instability events, exactly two upstreams — AS50877 and AS9002 — no observed peerings, and no IPv6. (DB-IP, BTW prior coverage, BTW prior coverage: who can correct the record) PeeringDB's record, last updated 2026-08-17, shows automated RIR status "ok" and an IRR AS-SET marked "Verified". (PeeringDB)

None of that speaks to response. But it narrows the economic envelope within which a response capability could exist. A network that delivers all its traffic through two transit contracts, with no peering relationships and roughly 1,280 addresses, has no visible institutional infrastructure — no NOC peers, no exchange points, no second organisation to share the load. If abuse handling happens anywhere on this network, the public record locates it in one mailbox and one abuse-c handle inside a single Italian LIR office. That is not an accusation of neglect; small providers legitimately concentrate functions in few hands.

It is a statement about where the verifiable surface of response begins and ends — and it ends at the registry boundary.

The storefront and the missing status page

The operator's homepage presents a retail business: residential and business fiber and backup products under the InfinityHome and InfinityBUSINESS names, plans from 24.90 EUR/month, direct telephone assistance, and a generic "Contattaci" contact route. (infinitywifi.it) What the retrieved homepage does not present is any abuse-reporting page, network status page, or incident-response channel. The domain matches the registered abuse address — abuse (at) infinitywifi (dot) it — which is the only bridge between the commercial brand and the ASN in the public record.

Absence in a search is not proof of absence on the site; menus, subdomains and unlinked pages were not exhaustively enumerated. But the asymmetry is itself informative. A provider confident in its incident handling typically surfaces it, because a status page reduces support load. Here the only incident-related surface the public can find is the registry field. Customers are offered a phone number; the internet's abuse-reporting machinery is offered a mailbox that no public evidence shows is monitored.

One search artifact deserves explicit quarantine. StatusGator monitors a service called "Infinity" at app.startinfinity.com, with incident locations in Texas and Scotland, including a resolved incident around September 17, 2026. (StatusGator) That is a different company sharing a word with this one. No outage or incident evidence for the Italian AS210057 network was found in this research; the collision is documented here precisely so it is never accidentally attributed.

What would count as durable repair

Because the current record shows only a declared channel, the honest question is what observations would upgrade it. Three classes of signal would move the picture:

First, published instruments: an abuse-reporting page on infinitywifi.it, a public status page, or a documented incident-response commitment. These are the operator's own surfaces and are cheap to create; their continued absence after months of operation is itself evidence about priorities.

Second, exercised response: a documented complaint exchange — a report sent to the registered address and a reply, or a takedown acknowledged in a third-party abuse tracker. No such record was found for this network.

Third, registry maintenance consistent with live operations: changes to the maintainer-gated contact fields that show a working hand rather than a frozen record. The aut-num was created 2026-05-18 and last modified 2026-07-07. (Qrator Radar WHOIS) Between then and now, the contact layer has been static.

None of these conditions exists as of September 28, 2026. That is not a verdict against INFINITY LINE SRL; it is a map of the gap between what a registry can hold and what a response function requires. A third party can verify that a channel is declared. Only the operator's own conduct — on its website, in its mail logs, in its registry edits — can verify that the channel answers.