Summary

  • Four IPv4 blocks announced by AS271551 all sit inside 179.63.44.0/22: added up they come to 2,304 addresses, and the space they cover is 1,024.
  • Three documents print three different IPv4 prefix counts for the same AS — four, four and one — and a broadband ranking measures the company in a fourth unit, 916 accesses and 0.8% of Chapecó.
  • No document in this corpus shows a single RPKI-valid origin for any of the five announcements, and no page read for this article prints a counting rule for an access, a prefix or a connected network.

The column that adds, and the column that does not

The Hurricane Electric toolkit's page for AS271551 opens with a six-line count. Verbatim: Prefixes Originated (all): 5 Prefixes Originated (v4): 4 Prefixes Originated (v6): 1 (bgp.he.net/AS271551).

That addition is clean, and it crosses address families: four plus one is five. Then the same page prints 1,024 IPv4 addresses for those four blocks, and the arithmetic stops being additive. The announced blocks are 179.63.44.0/22, 179.63.44.0/23, 179.63.46.0/23 and 179.63.47.0/24, plus IPv6 2804:7d48::/32. One instrument, two rules: it adds across families and refuses to add inside one.

Four blocks, one box

The block sizes are not ambiguous. A /22 covers 1,024 addresses. A /23 covers 512. The other /23 covers 512. The /24 covers 256. Add the four printed blocks and the total is 2,304 addresses.

Now look at where the smaller three sit. 179.63.44.0/23 is inside 179.63.44.0/22. 179.63.46.0/23 is inside it too. So is 179.63.47.0/24. The union of the four announcements is therefore not 2,304 addresses; it is exactly the 1,024 addresses of the /22, which is the number the toolkit prints on the same page.

That leaves 1,280 addresses entered more than once by the summation, and a sum that overstates the covered space by a factor of 2.25. Both figures are my arithmetic on the printed block sizes, not a publisher's statement, and neither is an error by anybody: adding is the right operation for counting announcements and the wrong one for counting distinct address space. The mistake lives in the choice of operation, which no page here makes explicit.

Three documents, three counts, three verbs

The count changes again when you ask who is speaking.

Hurricane Electric counts originated prefixes: four IPv4, one IPv6, five in total. InternetData's record for the same AS prints four IPv4 prefixes and one IPv6 prefix, the organisation identifier 16605117000139, country BR, the rotation DIRECT ALLOCATION, a creation date of 2020-12-14 and 0.00% RPKI-valid routes (internetdata.io/AS271551). PeeringDB, which is a form the network fills in for itself, prints one IPv4 prefix and one IPv6 prefix, describes the network as Network Types Cable/DSL/ISP, and carries a last-updated date of 2022-09-30 with an RIR status flag refreshed 2024-06-26 (peeringdb.com/asn/271551).

Four, four, one. Add the all-family line and you can also say five. The verbs are doing the work: originated is what an observer saw a network announce, allocated is what a registry records, self-reported is what the operator chose to publish about itself. Those are three different objects, and only the second is a custody record.

What the identity chain does close

Nothing in this article questions who the company is. That chain is unusually tight for a small operator.

The registry organisation identifier on the AS record is 16605117000139, which is the company's Brazilian tax number written without punctuation: CNPJ 16.605.117/0001-39. The whois mirror that reproduces the aut-num record prints exactly that string in the owner field: ownerid: 16.605.117/0001-39 (whois.ipip.net/AS271551). The same page attributes the aut-num to 20201214 and lists inetnum objects for 179.63.44.0/22 and 2804:7d48::/32.

The Registro.br whois reproduction goes further. It prints the owner string, the responsible party, routing and abuse contacts all on the handle WIALM90, the creation and change dates 20201214, and the two inetnums (ipgeolocation.io/browse/asn/AS271551). The header date on that page, 2026-06-19, is the date of somebody's query, not a change to the record.

The address closes too. PeeringDB's organisation record 33434 prints Address 1 Rua Maravilha, 320E, Efapi, Chapecó, SC, 89809-540 (peeringdb.com/org/33434). The Receita-derived record for CNPJ 16.605.117/0001-39 prints Rua Maravilha 320E, Efapi, Chapecó/SC, CEP 89809-540, razão social HIPERLINK TELECOMUNICACOES LTDA, situação ativa since 31/07/2012, capital social R$ 20.000,00, and the principal CNAE 6190601 – Provedores de acesso às redes de comunicações (maiscnpj.com.br). PeeringDB does not print the CNPJ, so that link is by street address rather than by tax identifier — close, not sealed. The contact handle seals it better: WIALM90 appears across owner, routing and abuse fields, and the name attached to it is the same name the Receita-derived record lists as sócio-administrador.

Two dates deserve a line, because they are the only pair here that looks like a discrepancy and is not. The company was opened on 31 July 2012. The aut-num was created on 14 December 2020. That is about eight years and four months apart, my subtraction of two dates in two registers describing two different objects. A company can exist for years before it needs its own routing identity.

So the identity closes across a tax register, a routing register, a self-reported peering record and a whois mirror. The size does not close at all.

The only document that shows traffic

Everything so far is a record of custody or a form filled in by a party. One document in the corpus is a measurement.

IPinfo maps 179.63.44.0/22 to AS271551 with LACNIC as the registry, and then shows a traceroute taken from a probe in Pittsburgh on 18 June 2026 whose second-to-last hop is 179.63.47.71, answering in AS271551. The excerpt carries the five-hop line 5 [AS271551] 179.63.47.71 151.13 ms. The same page reports 190 addresses in the range answering ICMP, with replies tagged AS271551 from Chapecó and Osasco (ipinfo.io/AS271551/179.63.44.0/22).

That is a single vantage point and a dated snapshot, and the AS-path attribution is IPinfo's mapping rather than a registry field. It is also the only evidence in this file that the network is carrying traffic at all. A reader weighing this company should notice the asymmetry: one measurement of liveness, four records of identity, and three mutually inconsistent statements of size.

Five rows with the same word in the last column

The most consistent number in the whole corpus is the absence of a validation result.

ping.pe lists the five originated prefixes, each with origin AS271551 and each with RPKI status NOT-FOUND, in rows of the form | 179.63.44.0/22 | AS271551 | hiperlink telecomunicações ltda me | NOT-FOUND | (records.ping.pe/271551). Hurricane Electric prints zero RPKI-originated-valid prefixes. InternetData prints 0.00% RPKI-valid routes. Three documents, three observations, one reading.

What that reading means is narrower than it sounds. NOT-FOUND says no covering route origin authorisation was found for the announcement as that source observed it. It does not say the announcement is illegitimate, and it does not say no ROA exists at LACNIC: no RPKI repository was queried for this article, and the three documents carry three different observation times, one of which is not printed at all. A prefix can be perfectly validly held and still have no ROA, because a ROA is a signature an operator chooses to publish, not a permission slip the registry requires.

The fourth unit

None of the documents above measures the thing a customer actually buys. One does try, in a different unit entirely.

Radar da Telecom's broadband ranking for Chapecó, dated 19/11/2026 and stated to draw on ANATEL access, complaint and satisfaction data plus IBGE and Receita CNPJ records, lists the company as HIPERLINK TELECOMUNICAÇÕES LTDA - ME with 916 accesses and a 0.8% market share (radardatelecom.com).

It prints no denominator and no rule for what an access is. Divide 916 by 0.8% and you get about 114,500 accesses in the local market; that figure is mine, derived from two printed numbers, and it appears on no page in this corpus. It is the sort of number a reader will want and should not be handed without its label.

So the company has now been counted four ways: in announcements (four IPv4, one IPv6), in addresses (1,024 or 2,304), in self-reported prefixes (one), and in subscriber accesses (916, at 0.8%). Four units, four questions, and no page that converts between any two of them.

The regulator's list is not a verdict

ANATEL publishes its Serviço de Comunicação Multimídia provider listing as a paginated legacy page over 17,126 records (sistemas.anatel.gov.br). The page read for this article covered registros 5001-5500 of 17,126 and carried no Hiperlink row.

That is not a finding, and the regulator's own procedure page explains why. It directs readers to the Outorga e Licenciamento data panels and prints, verbatim: Informamos que a consulta das entidades prestadoras de serviços telecomunicações está disponível nos Painéis de Dados de Outorga e Licenciamento. It also states that a provider exempt from authorisation can issue itself a comprovante de cadastro de dispensa de autorização through ANATEL's own system (gov.br/anatel).

So the authorisation chain stays open. One page of a 17,126-record list proves nothing about any single company, and a lawful provider may sit on the dispensa route rather than the outorga route. Anyone who needs the answer has to query the panels, not read a middle page.

A different Hiperlink, a different tax number

There is a second company trading under this name, and it is the one that volunteers a licence claim.

hiperlinktelecom.net, in Vitória da Conquista, Bahia, prints CNPJ: 38.392.512/0001-13, razão social Hiperlink Telecom, and states that it is a Serviço de Comunicação Multimídia provider totalamente legalizados pela ANATEL, describing itself as a subsidiary of Grupo NA Telecom (hiperlinktelecom.net/sobre.html). Different tax number, different state, different company. Not one word of that licence claim can be moved to the Chapecó operator, and the page prints no act or process number even for itself.

This is the cheapest mistake available to anyone researching the name, and it costs nothing to avoid: check the CNPJ before reading the adjective.

The suffix that two registers spell differently

Four documents carry the corporate-size suffix ME in the holder or trade name — the BGP toolkit, the whois mirror, the whois reproduction and the broadband ranking. The Receita-derived record prints the porte as Empresa de Pequeno Porte.

Microempresa and Empresa de Pequeno Porte are distinct regimes under Brazilian tax law, not synonyms, so this is a real disagreement between documents. It is also the kind of disagreement that proves nothing on its own. The aggregator may lag, the holder name in a routing register is a string somebody typed, and no Receita Federal receipt was read for this article. State it as a conflict between documents and stop there. The same record adds a detail worth keeping: among the secondary CNAEs there is no SCM code 6110-8/03, only the access-provider code and retail IT, books and computer repair.

The member row this article could not confirm

The BTW directory card for this entity cites exactly one source: a LACNIC member-directory URL that returned HTTP 404 when retrieved on 22 November 2026 and whose page text therefore cannot be cited here. LACNIC's public associate directory does exist at another address and lists two columns, | Country | Organization Name |, with no IPv4, IPv6 or ASN field at all (milacnic.lacnic.net). The excerpt retrieved ran from the Argentina rows into the beginning of the Brazil block and never reached an H row.

Two things follow, and only two. A listing in that directory would attest an organisational relationship with the registry, not an allocation and certainly not a size. And this article cannot tell you whether the row exists, because the URL is dead and the directory excerpt stopped short. What our own card does tell you is the gap it was carrying: no ASNs and no contacts, recorded from that single directory reference (BTW directory). The AS271551 record fills both gaps. It does not fill in the size.

What a prefix count is good for

The question to carry away is not how big Hiperlink's network is. It is which object any given number belongs to.

Four is a count of announcements. Two thousand three hundred and four is the sum of four block sizes. One thousand and twenty-four is the address space those blocks occupy. One is a form field the operator last touched in 2022. Nine hundred and sixteen is an access count from a commercial panel that prints neither its denominator nor its definition. Each is a number somebody measured or typed, and none of them is interchangeable with another.

Ask the verb before you use the figure. Then ask who printed it: an observer, a registry, the operator's own form, or a ranking. A registry record attests custody of an identifier, and stopping at custody is not pedantry — it is the only reading these documents support. Without that discipline, 2,304 and 1,024 become the same claim about the same company, and a measurement of one street corner in Chapecó becomes a market position.