Summary

  • LACNIC RDAP ties AS270637, IPv4 block 181.192.108.0/22 and IPv6 block 2804:6f14::/32 to NetPurus Servicos de Telecomunicaces LTDA and the CNPJ handle used across public records. Other records spell the company name Telecomunicacoes; the common CNPJ supports a spelling cross-reference, not a change to the directory identity.
  • Anatel Act 3,331 of 20 March 2025 and two Boca do Acre municipal contracts signed in June 2026 identify a current legal and institutional operating surface. They establish authorization and procurement facts but disclose no deployment, endpoint, service level, physical path, capacity, performance or continuity design.
  • RIPEstat observed fourteen aggregate and more-specific IPv4 and IPv6 announcements and one visible logical neighbour, AS4230, through 25 July 2026. Those observations make the network-resource boundary visible without proving a commercial agreement, a single upstream, one physical route or the condition of local access service.

A regional provider seen through official edges

The available evidence does not begin with a detailed network map. It begins with names, identifiers and public obligations. NetPurus appears in a corporate-data mirror, a federal regulatory act, a municipal gazette, an autonomous-system record and public routing observations. Each record describes a different edge of the same subject. Together they make the operator more identifiable than its physical delivery system.

That distinction matters for a provider serving a locality such as Boca do Acre. A customer encounters internet access as one service, but responsibility is distributed across legal identity, number resources, local access, external reachability, support and any public contract that defines an institutional relationship. The records available here illuminate the first two layers and parts of the last. They do not reveal the intervening equipment or arrangements.

The useful conclusion is not that the missing detail must be unfavourable. Absence of public topology is common and can protect security as well as commercial confidentiality. The analytical value lies in knowing exactly where the public record stops. It is possible to identify the company attached to an ASN, the CNPJ named in contracts and the authority that granted a particular authorization without pretending to know how a connection reaches a building.

This produces an accountability boundary. On one side are facts that an outside reader can test: a registered autonomous system, allocated address space, dated announcements, an official act and two specified contracts. On the other are outcomes that require different evidence: whether a location is serviceable, how traffic is handed off, how a fault is isolated, what happens when a component fails and whether promised service is delivered.

The boundary is especially important when institutional buyers appear in the record. A contract with a municipal fund makes the provider relevant to public administration. It does not automatically make the service critical, resilient or satisfactory. Public dependence has to be described according to the scope and term of the contract, not enlarged by assumptions about the endpoints behind it.

NetPurus can therefore be assessed without either romanticising a remote local operator or treating sparse disclosure as failure. The public material supports a precise account of identity and network-resource control. It also supports a precise list of questions that remain unanswered. Holding both in view is more informative than forcing the company into a fully visible infrastructure model that the evidence cannot sustain.

Two spellings and one stable identifier

The BTW directory names the subject NetPurus Servicos de Telecomunicaces LTDA. LACNIC's RDAP record for AS270637 uses the same Telecomunicaces rendering. Corporate, regulatory, municipal and first-party records instead use Telecomunicacoes. The difference is small on the page but significant for attribution: changing one spelling silently could attach a claim to the wrong record or conceal a genuine data-quality issue.

The common CNPJ resolves the practical connection while preserving the difference. The number 29.942.267/0001-80 appears in public company material and in official records. RDAP presents the corresponding numeric handle, 29942267000180, alongside the autonomous-system holder. That alignment supports the conclusion that the differently spelled names refer to the same registered company in the sources considered here.

It does not authorize a directory rename. A directory is an identity system with its own current record, and the exact subject remains the Telecomunicaces entry. The public spelling can be disclosed as a cross-reference because readers should be able to understand why an official act or municipal contract looks slightly different. Disclosure is not the same as adjudicating which spelling should replace the other everywhere.

There is another reason for restraint: a separate same-name directory row exists outside the article's bound identity. The article does not merge, link or draw claims from that row. A company name alone is not a sufficient join key when records may be duplicated. The exact directory entry, its slug and the CNPJ-backed public evidence provide a safer chain.

Boca do Acre is a legal anchor, not a coverage map

Casa dos Dados, a third-party mirror that attributes its material to Receita Federal data, reported the company as active when checked. It gave an opening date of 15 March 2018, an address at Avenida Mario Diogo de Melo 10060 in Boca do Acre, Amazonas, and a principal activity concerning access provision to communications networks. These details provide legal and geographic context with the necessary attribution to the mirror.

The record anchors the company in Boca do Acre. It does not show that every part of the municipality can receive service. A headquarters or registered address can identify where a company is based without describing the reach of its connections. Even a principal activity aligned with communications says what the registered business is organized to do, not how many customers it currently serves or what technology reaches them.

The distinction between location and serviceability is fundamental. Municipal boundaries are broad, while internet access is delivered at specific premises or handoff points. A statement that a provider is in Boca do Acre is much less demanding than a statement that an address in Boca do Acre is connected. The latter requires current qualification evidence at an appropriate geographic level.

Corporate status has similar limits. An active registration is evidence about legal standing in the source consulted. It is not a health check on the network. It cannot establish regulatory compliance across every service, the condition of equipment, the availability of support, solvency, traffic levels or customer satisfaction. Those questions belong to other records and observations.

For readers assessing a regional ISP, this is the right use of corporate evidence: identify the legal party, date the registration, locate its declared base and compare the CNPJ with other records. It is the beginning of a traceable account. Turning it into a network footprint would trade precision for an unsupported picture.

The company website preserves a dated market claim

NetPurus's website describes the business as an internet provider in Boca do Acre and refers to wireless technology. It lists Boca do Acre, Vila Caqueta and several kilometre references along BR-317 among its coverage points. It also presents expansion, support, plan speeds and prices. Those statements help explain how the company presented itself to potential customers.

The page carries a 2021 copyright. That date changes the weight of every commercial detail on it. The material can be described as first-party language visible on the site, but it cannot be treated as a current independent measurement. Coverage points may have changed. Plans may have been withdrawn or revised. A support channel may no longer operate in the same form.

First-party information is not worthless because it is promotional. It can reveal the intended service area, terminology and offer. The problem arises when marketing language is made to prove an outcome it was never designed to measure. A list of locations does not establish address-level availability. A stated speed does not establish delivered throughput. A promise of expansion does not show what was built.

The wireless description also needs discipline. It supports the bounded statement that the website marketed wireless service. It does not identify frequencies in use, radio locations, access architecture or ownership of any supporting structure. The separate Anatel act establishes an authorization of its own kind, but it still does not fill in those physical details.

The BR-317 references are relevant because they make the old offer geographically specific. They are not evidence of a verified route along the highway, nor do they locate any cable, radio, relay or customer. A place name in marketing material can guide future verification while remaining short of physical proof.

The website is most useful when read as one dated layer beside newer official records. It provides an older customer-facing description. The 2025 authorization and 2026 contracts provide more recent institutional dates. None can silently update the others. The resulting timeline supports continuing public relevance while leaving the present retail offer unresolved.

What the Anatel act actually establishes

Anatel Act 3,331, dated 20 March 2025 and published in the federal gazette, authorizes the use of specified radio frequencies for NETPURUS SERVICOS DE TELECOMUNICACOES LTDA, CNPJ 29.942.267/0001-80. The act associates that authorization with the Private Limited Service. It is an official regulatory fact tied to the same company identifier.

That is a meaningful operating signal. A named legal entity holds a defined authorization from the national telecommunications regulator. The record is newer than the dated website and gives readers a formal point of accountability. It also confirms the Telecomunicacoes spelling used outside the directory and links it to the shared CNPJ.

The act is narrower than a network description. Authorization to use frequencies does not prove that a radio was installed, activated or used at a particular place. It does not identify a mast, antenna, link endpoint or customer service. The text cannot support a statement about the scale or condition of a wireless deployment.

The service classification also matters. The authorization is associated with the Private Limited Service. It should not be converted into evidence of a nationwide retail footprint or into a general conclusion about every authorization that may be relevant to the company's internet offer. Regulatory instruments answer the question stated in the instrument, not every adjacent business question.

Nor does the act establish ownership. A legal holder may use arrangements involving rights, leases, suppliers or other parties, and the public record considered here does not specify them. The safe statement is that the company received the authorization described. The unsafe statement would add a physical system or property interest not shown by the act. Read correctly, the authorization strengthens the accountability picture. It gives a date, authority, company and purpose. It tells a reader where one formal responsibility sits. It leaves deployment and service outcomes to evidence capable of showing them.

Two contracts bring the public-service relationship into view

The Amazonas municipal gazette dated 26 June 2026 records two Boca do Acre contracts with the same company and CNPJ. Both concern multimedia communication service providing internet access. Unlike the older website, these entries document recent public procurement relationships with named municipal funds.

Contract 047/2026 names the Municipal Health Fund. The extract gives a value of R$41,400 and a term from 8 June 2026 to 8 April 2027. Contract 048/2026 names the Municipal Social Assistance Fund, gives a value of R$22,680 and runs from 8 June 2026 to 8 March 2027.

The dates matter because the contracts were current at the time of this article. They show that NetPurus was not visible only through a 2020 ASN registration or a website carrying a 2021 copyright. A municipal authority entered into specified internet-access arrangements with the company in 2026.

The contracting funds also make the institutional context concrete. Health and social assistance are public functions, and internet access purchased by their funds can support administration or service delivery. The extracts do not say how the connections are used. They do not identify buildings, departments, applications, staff or members of the public who may depend on them.

It would therefore be wrong to describe an undocumented critical system. The contracts establish a buyer, supplier, scope, value and term. They do not establish the consequence of interruption. A health-fund contract may be important without every endpoint being clinically critical; a social-assistance contract may support operations without the extract explaining which ones.

The value of the records lies in accountability rather than drama. They identify a recent obligation and the public bodies on the other side of it. That gives future reporting a place to look for contract terms, acceptance evidence, service notices and renewal decisions, while the present article remains within what the published extracts show.

Procurement values are not network measurements

The two contract values can be stated precisely because the gazette states them. They cannot be translated into technical scale. A price may reflect duration, taxes, installation, support, the number of service points, negotiated bandwidth or other terms. The extracts available here do not provide the decomposition.

Dividing the value by months would produce arithmetic, not insight. Without knowing the number and type of connections, it would not yield a meaningful unit price. Comparing the contracts with retail plan prices on a 2021 website would be even weaker, because the products, dates, customers and obligations are different.

The same caution applies to capacity. A larger contract is not evidence of a larger circuit. A longer term is not evidence of higher availability. A named internet-access scope is not evidence of a particular speed, contention ratio or traffic profile. Technical quantities require technical terms or measurements.

Contract existence also cannot certify execution. The extracts show that agreements were made for stated terms. They do not report installation, acceptance, invoices, incidents, penalties, renewals or satisfaction. No conclusion should be drawn here about whether NetPurus has performed well or poorly under either agreement.

This leaves a clear distinction between commercial accountability and operating proof. The company can be identified as the contracted supplier. The municipal funds can be identified as contracting parties. If questions arise, those facts help establish who holds the relevant records and obligations. They do not answer the questions in advance. For a regional ISP, that distinction protects both sides. It prevents a contract from becoming an unearned endorsement of the operator, and it prevents missing technical detail from becoming an accusation. Public procurement creates a documented relationship.

Evaluation of the service needs the documents and observations that describe delivery.

AS270637 is a durable point of attribution

LACNIC's RDAP service identifies AS270637 under the exact directory spelling, NetPurus Servicos de Telecomunicaces LTDA. The record ties the autonomous system to the numeric CNPJ handle and to related IPv4 and IPv6 resources. This is the clearest public network-resource identity in the available material.

An autonomous system number provides an identifier for interdomain routing. It allows a network to appear as an origin or entity in route information visible outside its own administrative boundary. The ASN does not make every part of the operator public, but it gives observers a stable entity around which registration and routing evidence can be organized.

The CNPJ handle is crucial. Similar brand names and variant spellings can create ambiguity, while the company number links the resource record to the legal and institutional records. AS270637 is therefore not merely a technical label detached from the supplier named in Boca do Acre's municipal gazette.

The registration also establishes responsibility at a specific layer. If information about the number resource needs correction, if routing attribution is questioned or if contact with the holder is required, RDAP indicates the organization associated with the ASN. That does not mean the record alone proves contact responsiveness, but it establishes whom the registry names.

An ASN should never be treated as a complete network. It does not disclose local access media, internal design, support arrangements or physical dependencies. A route can be originated through infrastructure owned, leased or supplied under arrangements the public record does not reveal. Its importance is still substantial. Where customer-facing descriptions are old and local delivery details are sparse, the ASN keeps the network-resource surface traceable. It is one of the few places where the exact directory identity and the operator's public Internet role meet directly.

Address blocks describe delegated resources, not local reach

RDAP links NetPurus to IPv4 block 181.192.108.0/22 and IPv6 block 2804:6f14::/32. These resources show that the holder has public address space in both protocol families. They help explain how AS270637 can be observed originating IPv4 and IPv6 reachability.

The size of an allocation cannot be read as a subscriber count. Public addresses may be assigned in many ways, and address sharing can separate the number of customers or devices from the number of visible IPv4 addresses. IPv6 space is deliberately structured on a scale that makes raw address counts especially meaningless as a commercial measure.

The blocks do not establish geography either. Registry country context and the company's Boca do Acre anchor do not show where each address is used. A prefix observed under AS270637 is not proof that every address sits in Boca do Acre, serves a customer there or belongs to one of the municipal contracts.

Nor do the resources prove utilization. An allocation may be announced in aggregate, in more-specific routes, partly, intermittently or under changing policy. RIPEstat provides dated observations of announcements, but it does not expose the purpose of every address or the occupancy of the block.

The defensible conclusion is narrower and still useful: the same identifiable company holds address resources linked to its ASN, and public observers saw routes in both address families. This establishes a network-resource surface that can be monitored over time.

For accountability, allocations create obligations of accurate attribution and responsible administration. They do not prove retail availability, market share or service quality. Keeping those categories apart allows number-resource evidence to remain strong without asking it to carry a business narrative it cannot support.

Fourteen announcements are a routing snapshot

RIPEstat's announced-prefixes view for AS270637 showed fourteen aggregate and more-specific IPv4 and IPv6 announcements through 25 July 2026. The observation is current enough to establish dated routing visibility close to publication. It is not a timeless description of the network.

The distinction between aggregate and more-specific announcements matters. A single allocated block can appear through several route objects because networks announce a covering prefix and narrower components for policy or reachability reasons. Counting observed announcements therefore does not count distinct physical networks, sites or customer groups.

Fourteen is not a capacity figure. A prefix has an address range and a route has a path attribute, but neither discloses port speed, available headroom, traffic volume or congestion. More routes do not necessarily mean more bandwidth, and fewer routes do not necessarily mean a smaller customer base.

The observation is also bounded by visibility. RIPEstat compiles data from public measurement surfaces, which may not see every route in every context. A route may appear differently across collectors or change over time. The date must travel with the claim. Even with those limits, the snapshot adds something important to the static registration. RDAP says who holds AS270637 and the related resources. RIPEstat shows that route announcements associated with the ASN were publicly visible near the date of review. The two sources answer complementary questions.

Neither shows whether a person in Boca do Acre had a working connection at that moment. Global route visibility can continue while a local access problem affects a premise, and a local connection can encounter problems not visible in interdomain tables. Routing evidence is a view of the outer control plane, not a substitute for end-to-end observation.

One visible neighbour must remain one observation

RIPEstat's neighbour view showed one visible logical neighbour for AS270637: AS4230. This is a useful indicator of how the autonomous system appeared from the observer's vantage points through 25 July 2026. It must not be enlarged into a complete account of external connectivity.

A visible neighbour is not automatically a named commercial service. Public route data does not disclose whether an arrangement is paid transit, another type of relationship or an observation shaped by route propagation. It provides no price, commitment, responsibility clause or termination term.

One visible neighbour also does not prove that NetPurus has only one upstream arrangement. Some relationships may not be visible in the same data, may not propagate the same routes or may serve roles not captured by the snapshot. The public view is evidence of what was observed, not a census of every contract.

Most importantly, logical adjacency is not a physical route. The data does not reveal where connections run, whether two services would share a common component or whether an apparent alternative exists. It cannot support a statement about physical diversity or single-route exposure.

The neighbour count says nothing about capacity or performance. It does not disclose interface rates, traffic balance, latency, congestion or failover behaviour. It cannot show whether the relationship is sufficient for customer demand or how the operator responds to a fault. Its proper role is to identify a visible external dependency boundary. AS4230 appeared beside AS270637 in the dated public view. That provides a starting point for examining route changes and organizational responsibility if new evidence arises. It does not pre-write the answer to resilience, commercial or physical questions.

The local access system remains out of sight

The article can identify NetPurus as a Boca do Acre provider identity, a municipal supplier and the holder associated with AS270637. It cannot describe the system connecting a customer premise to that ASN. No checked source supplies a current, independently verified account of the local handoff.

The old website's wireless language is not enough. It indicates how the company marketed service but does not locate or verify any equipment. The Anatel act is not enough either: it establishes a frequency authorization, not deployment. Routing observations begin beyond the point where local access has already done its work.

This missing layer includes questions about the medium used at a specific location, responsibility for installation, equipment at the customer edge and the point where traffic enters the operator's routed domain. It also includes maintenance and support. None can be answered from an ASN or a public contract extract.

The absence is not evidence that the operator lacks these capabilities. A working provider necessarily has some means of delivering service to its customers, but the form, ownership and condition of that means are not established here. The analytical discipline is to avoid turning necessity into a detailed factual claim.

This matters because operating responsibility changes across handoffs. A problem inside customer equipment, in local access, in routing configuration or beyond the operator's external boundary may present the same symptom to the user. Diagnosing it requires visibility that public route data alone cannot offer. NetPurus's public record is strongest where global coordination requires identifiers and where government publication requires named parties. The local access system is a private operating layer between those visible edges.

Future evidence should illuminate it at the level needed to answer a particular question, without demanding disclosure of sensitive detail.

BR-317 references raise questions without drawing a route

The website lists several kilometre references along BR-317 among its coverage points. Those references suggest that NetPurus once marketed service beyond an undifferentiated urban label. They give the first-party description a local vocabulary tied to recognizable places.

They do not draw a network route. A kilometre marker says where a potential service area was described, not how connectivity reached it. The website does not establish whether service at any point was delivered by radio, cable, another provider's connection or a mixture, nor whether the old listing remains current.

The references still shape sensible questions. How is a location qualified before an order is accepted? What is the service boundary when a site is outside a denser settlement? Which party is contacted when the customer-facing connection fails? The answers could differ by address and by the arrangement in force.

Repair access is similarly unresolved. It may be tempting to infer delay or difficulty from a highway reference and the word remote. The sources do not document repair times, staffing, travel conditions, spares or incident history. Geographic context makes these topics relevant, not answered.

The same restraint applies to power and weather. No evidence here records an outage, backup arrangement or environmental event affecting NetPurus. General knowledge about regional conditions cannot be used to assign a specific weakness or strength to this operator.

The proper use of the BR-317 material is therefore modest. It records a dated first-party claim about where the provider sought to offer service. It supports a local-access thesis while reinforcing the need for address-level, current verification. It does not support a line on a map or a conclusion about the route behind any connection.

Institutional dependence should be described at contract scale

The health and social-assistance contracts make continuity a legitimate subject. A public body buying internet access needs the service to support whatever functions fall within the agreement. Yet the published extracts do not define those functions, and the language of dependence must remain proportional to the evidence.

The contracts do not identify a hospital, clinic, office, service counter or remote unit. They do not say whether one or several connections are involved. They do not describe applications, operating hours or alternatives. Without those facts, the impact of an interruption cannot be quantified.

They also do not state a service level. No availability target, restoration time, escalation route, penalty or monitoring method appears in the summarized public record considered here. Such terms may exist in fuller procurement documents, but they cannot be assumed from the contract notice.

This does not make continuity irrelevant. On the contrary, the absence of visible terms identifies the next evidence needed for a public-accountability question. A contracting authority could hold specifications, acceptance records and incident communications that clarify what was purchased and how delivery is assessed. The supplier's ASN and public routes contribute a different view. They show an identifiable Internet-resource domain near the same period. They cannot link any route to a municipal endpoint or show that a contract connection traverses a particular path.

The strongest current statement is therefore institutional and bounded: two municipal funds contracted the company for internet access under stated values and terms. Continuity matters because there are ongoing public agreements. Whether continuity is adequate, how it is designed and what happens during failure remain unproved.

Regional ISP economics are hidden inside the handoff

The public material contains prices, but they do not form an economic model. The municipal gazette gives contract values. The dated website gives old retail plan prices. Neither reveals the company's customer count, revenue, costs, margins or investment.

A regional provider has to bring together local delivery and external connectivity in a bill that customers or institutions can pay. That basic structure makes access density, support burden and upstream arrangements relevant economic questions. The available evidence does not quantify any of them for NetPurus.

The address allocations cannot stand in for scale. A /22 and an IPv6 /32 show delegated resources, not the number of active subscriptions. Fourteen observed announcements show routing structure, not demand. One visible neighbour shows an observed adjacency, not a transit invoice.

The public contracts are likewise ambiguous as economic signals. They show that municipal buyers selected NetPurus for defined periods and amounts. They do not show the cost of serving those agreements, whether equipment was included, whether the work is profitable or how the values compare with alternative bids.

The older website indicates a retail orientation and a set of marketed locations. It does not establish today's product mix. Without current plans and serviceability evidence, no conclusion can be drawn about competitive position, market share or growth. What is visible is the junction at which economics would have to be tested. A legal entity with number resources and recent public contracts has identifiable obligations. The viability of fulfilling them depends on arrangements and operating capabilities that are not public here. That gap is a reason for targeted evidence, not an invitation to guess.

Accountability crosses three different clocks

NetPurus's public record moves on at least three clocks. Corporate registration offers a relatively stable legal identity beginning in 2018. The website preserves customer-facing language marked by a 2021 copyright. The Anatel act, municipal contracts and routing observations add signals from 2025 and 2026.

These dates should not be flattened. An old website can remain online after an offer changes. A regulatory authorization can remain meaningful without proving daily use. A contract has a defined term. A routing observation can change within hours. Each claim needs the time scale of its source.

The clocks do intersect. The shared CNPJ connects the legal record, official act and municipal contracts. The ASN record connects that identity to number resources. The routing views show recent visibility for the ASN. Together they support continuity of public accountability across systems, even though they do not prove uninterrupted service.

The date differences also expose where updating would help. A current first-party page could confirm which parts of the 2021 offer remain valid. Current service qualification could replace broad historic coverage language. Fuller contract material could define what the 2026 buyers expect.

No one record can refresh another by implication. A 2026 route does not update a 2021 price. A 2026 contract does not prove that every old coverage point remains served. A 2025 authorization does not show that a specific radio was active on 25 July 2026.

Reading the clocks separately produces a more truthful current account. NetPurus has recent institutional and routing visibility. Its public commercial description is older. Its physical and service outcomes remain outside the available observations.

The difference between control and ownership

Public Internet records are often described as evidence of control. Even that word needs precision. RDAP identifies the organization registered for AS270637 and its address resources. Public routes show the ASN appearing as an origin for observed announcements. Those facts concern administrative and routing responsibility.

They do not settle ownership of physical components. A provider can operate through a combination of owned, leased, shared or supplied elements. The source set does not state which arrangement applies to NetPurus. It does not identify property rights in any local or external component.

The municipal contracts identify NetPurus as supplier, but a supplier can rely on other parties while remaining responsible to the buyer under the contract. The extracts do not disclose subcontracting, wholesale services or maintenance arrangements. None should be invented.

The Anatel act identifies the holder of a radio-frequency authorization. It does not answer who manufactured, installed, housed or maintains any equipment, and it does not prove that equipment exists at a named location. Regulatory permission and physical ownership are separate categories.

This distinction matters when discussing fault responsibility. A provider may not own every dependency, yet it can remain the customer's contractual point of contact. Conversely, ownership of an asset would not by itself prove that service is well operated. Accountability depends on obligations and action, not merely title. For NetPurus, the public record supports control-plane attribution and named contractual responsibility. It leaves physical ownership unproved. That asymmetry is common enough to be expected, but it should always be made explicit before drawing conclusions about infrastructure.

What a route observer cannot see during a local fault

RIPEstat can show whether routes associated with AS270637 are visible to its observation surface. If an announcement changes, an outside observer may see a different origin or path. That can be useful for identifying a routing event, but no such incident is documented in the material used here.

A local service fault may occur while the same routes remain visible. A problem at a customer premise or within the local handoff may affect one connection without changing global announcements. The observer would continue to see the ASN while the customer experienced a failure.

The reverse relationship is also incomplete. A route change does not reveal its physical cause or customer impact. It may reflect configuration, maintenance, an external dependency or another condition. Without incident evidence, a public table cannot assign blame or count affected users.

The one visible neighbour does not solve this limitation. It gives one logical relationship in the dated view. It does not show how traffic is distributed, which arrangements are available under different conditions or whether any physical component is shared.

Performance remains invisible as well. Reachability in a routing table does not measure throughput, delay, packet loss or application success. No checked source supplies such measurements for NetPurus, and the old plan speeds on the website are offers rather than observed outcomes. This is why network-resource transparency and service transparency should be treated as complementary. The first makes the operator identifiable in the global routing system. The second would require measurements and records closer to the user. NetPurus is visible in the former and largely unmeasured in the latter.

What clearer evidence could show without exposing sensitive detail

The largest gaps could be narrowed without publishing a sensitive topology. A current first-party serviceability method could say whether an address can be served without showing the route. Current legal and brand information could explain the Telecomunicaces and Telecomunicacoes spellings while preserving the exact registered identities.

For the municipal contracts, fuller public documents could state the number and general type of service points, contracted bandwidth, support hours, acceptance criteria and service-level terms if those fields are not protected. Performance records could be aggregated carefully enough to protect users while showing whether obligations are met.

Network-resource evidence could also become more informative over time. Dated comparisons of announced prefixes and visible neighbours can show changes in the public routing surface. They still would not prove physical diversity, but they could identify events that warrant further inquiry.

Any statement about capacity would need a defined unit and scope. Contracted bandwidth at one endpoint, an interface rate and measured available throughput are different facts. None should be inferred from prefix count, address-space size or the number of visible autonomous systems.

Claims about continuity would need an observation period, defined service, affected population and exclusions. Backup arrangements would need evidence that they are independent of the failure being considered and that they function under test or incident conditions. The current sources provide none of those details.

The point is not to demand total transparency from a small provider. It is to match disclosure to the claim. NetPurus can be accountable for identity, contact, contract and service outcomes without publishing every technical dependency. What matters is that a reader can tell which statements are verified, which are marketed and which remain unknown.

A bounded conclusion at the remote network edge

NetPurus Servicos de Telecomunicaces LTDA is firmly identifiable within the limits of the available evidence. The directory name and LACNIC RDAP record align on the Telecomunicaces spelling. The shared CNPJ connects that identity to Telecomunicacoes spellings in corporate, regulatory and municipal material.

The legal and institutional chronology is substantive. A third-party corporate-data mirror reports a Boca do Acre registration opened in 2018. A 2025 Anatel act names the company in a radio-frequency authorization associated with the Private Limited Service. Two 2026 municipal contracts name it as an internet-access supplier to health and social-assistance funds.

The network-resource surface is equally specific. AS270637 is linked to an IPv4 /22 and an IPv6 /32. RIPEstat observed fourteen aggregate and more-specific announcements and one visible logical neighbour through 25 July 2026. These facts make the operator visible beyond a marketing page.

None completes the local picture. The corporate address is not a coverage map. The old website is not a current independent service test. The radio authorization is not deployment evidence. The contracts are not performance reports. The ASN and routes are not a physical diagram.

That incompleteness is the central finding rather than a flaw to be hidden. Public records identify the company that holds resources and accepts recent municipal obligations. They do not reveal how a connection is physically delivered, how much capacity is available, how service performs or how continuity is maintained.

The fair accountability standard follows from that asymmetry. NetPurus should be judged on claims supported at the layer where they are made. Identity and current institutional relevance are well supported. Routing visibility is supported as a dated observation. Physical control, service outcomes and continuity remain open questions.

For Boca do Acre's public buyers and other customers, the practical issue is not whether an ASN can be found. It can. The issue is whether the responsible provider can connect that visible resource identity to a current, testable account of service at the customer boundary. The public evidence has established who stands at that boundary. It has not yet shown what lies across it.

Sources