Summary

  • Computers World is not merely an orphaned name. CWX Telecom's own site says the business was called Computer's World and is known regionally as CWX Telecom, while the current Brazilian internet registry associates AS265107 and its address resources with CWX Telecom LTDA.
  • Public service pages describe a regional access provider: radio and fibre residential plans, dedicated business links with fixed addresses, and coverage centred on Cerro Grande and ten neighbouring municipalities. They do not support treating the company as a general-purpose cloud platform.
  • AS265107 originated one IPv4 /22 and one IPv6 /32 throughout the captured July 1-15 interval, with valid route-origin authorisation. One adjacent network, AS263004, was visible in the routing observation, so physical and commercial resilience remain questions for the provider rather than conclusions available from the route table.
  • CWX publishes phone, email and WhatsApp support channels and says connection tickets are attended within 24 to 48 hours. A business relying on the link should determine whether a separate enterprise commitment covers acknowledgement, restoration, field dispatch, escalation and service credits.

The old name leads to a current operator

A generic name creates a simple diligence problem: it is easy to find the wrong company and difficult to know when two records describe the same one. Searches for Computers World produce retailers and service businesses on several continents. The useful evidence is not the phrase itself but the chain that joins the phrase to a specific Brazilian operator.

The BTW directory entry is the stable starting point, but not proof of what the business currently sells. The stronger bridge comes from the operator's own website. Its company page says that "Computer's World, or CWX Telecom" is an internet-access provider and computer shop in Cerro Grande, Rio Grande do Sul. The contact page is even more explicit: it says the company is named Computer's World but is known regionally as CWX Telecom.

The current registry view then supplies a legal and technical anchor. Brazil's RDAP response for AS265107 identifies the registrant as CWX Telecom LTDA, gives the entity handle 10915964000113, records the autonomous system's registration on July 20, 2016, and shows a last change on January 21, 2026. That numeric handle corresponds to Brazilian CNPJ 10.915.964/0001-13. A secondary company-data page, CNPJ Go, reports an active limited company opened in 2009 in Cerro Grande, with internet access provision as its principal activity.

These sources make continuity more likely than coincidence. The same regional business explains both names; the registry ties the present legal name to the same autonomous system that older network indexes still label Computers World; and the company identifier is consistent across the ASN and company-data views. The prudent conclusion is that Computers World is a legacy identity for the operation now registered and marketed as CWX Telecom.

That conclusion has a boundary. The public evidence does not provide a formal name-change instrument or a complete corporate history. Nor should every old page carrying the Computers World label be treated as current CWX policy. A buyer should put CWX Telecom LTDA, CNPJ 10.915.964/0001-13, on the order form and ask the provider to state which older names, network resources and customer obligations it has succeeded. Identity continuity is useful only when contractual responsibility follows it.

There is a smaller reconciliation task in the addresses. The current company-data page gives Avenida 20 de Dezembro 583 as the registered address. CWX's website gives Rua 8 de Marco 480 as its Cerro Grande contact address. Two addresses can legitimately serve legal and operating purposes, but a buyer should know which receives notices, which houses customer-facing operations and whether either location is relevant to network equipment. A street address is an accountability surface, not a data-centre certificate.

The public offer is connectivity, not an abstract cloud

The company website gives a reasonably concrete answer to "what does it sell?" Its history page says the operation began with radio internet packages and expanded into equipment sales, maintenance and computer-network configuration. The coverage page says CWX serves eleven municipalities: its Cerro Grande base plus Lajeado do Bugre, Sagrada Familia, Sao Pedro das Missoes, Novo Tiradentes, Liberato Salzano, Pinhal, Jaboticaba, Seberi, Sao Jose and Constantina.

The product pages reinforce that local-access interpretation. CWX advertises wireless plans at 2, 6 and 12 Mbps using 5.8 GHz access. Its fibre page lists residential tiers from 50 to 600 Mbps. The business page lists dedicated 100, 200 and 400 Mbps services with a fixed IP address, unlimited transfer and specialist technical support. These are recognisable internet-access products, not vague claims attached only to a company name.

They also set the product boundary. The pages reviewed do not describe virtual machines, object storage, managed databases, backup repositories, container orchestration or an application deployment platform. They do not identify a public cloud control plane or a catalogue of hosted infrastructure. CWX may perform other work privately, and its registered secondary activities include software development and technical support, but the public evidence supports a regional connectivity and IT-services company. It does not support upgrading the word "technology" into an unadvertised cloud estate.

That distinction matters to a cloud or platform team because connectivity can still be a critical dependency. A dedicated link may connect an office, branch, tower, on-premises server room or remote workload to a larger platform. Its fixed address may sit in partner allowlists. Its failure may block access to applications hosted elsewhere. The appropriate diligence is therefore not "which cloud features exist?" but "what exact path, address, support and restoration obligations surround the access service we are buying?"

The website's service claims are leads for that conversation, not measurements. Statements about full contracted speed and high stability do not specify the test point, sampling interval, congestion treatment, latency, jitter, packet loss or exclusions. The business plans do not show an uptime percentage, maintenance window, mean-time-to-repair commitment or service-credit schedule. Before signature, those marketing claims need to become definitions that both parties can observe.

AS265107 is the clearest operating proof

The strongest evidence that CWX operates more than a sales page is AS265107. An autonomous system is a unit of routing policy: it lets an operator announce reachability for address space and exchange routes with other networks. It does not prove every service claim, but it gives network engineers something specific to monitor and attribute.

The Brazilian registry's IPv4 record assigns the range 170.254.140.0 through 170.254.143.255 to CWX Telecom LTDA. The ASN record also lists 2804:32f4::/32 for IPv6. In the RIPEstat announced-prefix observation, AS265107 originated both the IPv4 /22 and IPv6 /32 throughout the returned July 1-15 interval. This is valuable evidence of a live dual-stack routing role at the observation point.

Some public route directories display the IPv4 /22 alongside four component /24s. That does not create five independent address holdings. The four /24s partition the same 1,024-address /22, and a route collector may see an aggregate, more-specific routes or both. The allocation remains one /22. A procurement record should distinguish registry allocation, routes observed and addresses actually assigned to the customer's service.

Both aggregate announcements returned valid in RIPEstat's route-origin checks: 170.254.140.0/22 and 2804:32f4::/32 were covered by authorisations naming AS265107. Valid origin authorisation is good evidence that these announcements match the holder's published routing intent.

Its meaning is deliberately narrow. Route-origin validation does not measure uptime, capacity or packet delivery. It does not show whether the customer circuit has power, whether the access radio has line of sight, whether a fibre has been cut, or whether a router accepts a correct route but drops traffic. It also does not establish that every path between a customer and a cloud workload is protected against configuration error or attack.

The returned authorisations permit maximum lengths of /32 for the IPv4 allocation and /128 for IPv6. In practical terms, that leaves room for very specific routes beneath the aggregates to validate if they are originated by AS265107. This may be intentional operational flexibility. It is also a reason for a network customer to ask how route changes are approved, monitored and rolled back. A green validation state is one control; change discipline is another.

Registry contacts add a further clue about the control surface. The current ASN response names Elevate Network as the administrative contact and Maicon Antonio Steffens as the abuse contact. The IPv4 record names Steffens for technical and abuse roles. This is better than an address block with no reachable custodian, but the division of roles should be understood. A customer needs to know who can change BGP policy, who can isolate abuse, who can restore a suspended address and who remains accountable when an external network specialist is involved.

One visible neighbour is not a resilience design

At the captured observation, RIPEstat's ASN-neighbour view showed one adjacent network, AS263004. CWX's current registry policy likewise names AS263004 as the network from which it accepts routes and to which it announces AS265107. A separate bgp.tools view identified the same single upstream and described the network as active.

This convergence is useful: it says the visible route relationship is not an isolated artefact in one directory. It does not tell us the commercial contract, traffic volume, purchased capacity or number of circuits. Most importantly, one autonomous-system neighbour does not reveal the physical topology beneath it.

Two links to one upstream could use separate fibre entrances, routers and power domains. One logical adjacency could also sit on a single vulnerable path. Conversely, an upstream may carry substantial resilience inside its own network. Public BGP data cannot distinguish those designs. It shows who propagates reachability, not where cables run or whether failover worked during the last fault.

For a household connection, that uncertainty may be acceptable at the advertised price. For a hospital office, payment operation, municipal service or company whose cloud access depends on the link, it becomes a design requirement. The buyer should ask whether the dedicated product uses one or multiple access paths, where the demarcation sits, which failure domains are shared, whether customer equipment has backup power, and what happened in the most recent failover test.

The same discipline applies to fixed IP addresses. CWX advertises them on business links, and its own /22 gives it a visible pool from which addresses may be supplied. The public pages do not say whether an address is dedicated, portable, retained after a plan change, protected against reputation problems or replaced after abuse. Customers that bind authentication, mail delivery or partner access to an address need those rules in writing, along with a renumbering and exit procedure.

Support is real work, and CWX publishes its clock

CWX provides more support detail than many small network names. The contact page lists a support telephone number, a separate finance number, WhatsApp and a support email address. It says the company has people for remote and online assistance and field teams, and that a connection ticket will be registered and attended within 24 to 48 hours.

That is an attributable support surface. A customer can identify the channel for a fault, distinguish technical from billing contact and expect a recorded ticket. The local coverage area also suggests that some incidents may be handled by people close enough to work on physical access infrastructure. None of this should be dismissed simply because the organisation is small.

But "attended" is not the same as acknowledged, diagnosed or restored. A 24-to-48-hour window could describe ordinary residential support. It may not be the commitment sold with a dedicated business circuit. The public page does not state operating hours, weekend coverage, severity levels, maximum restoration time, escalation tiers or service credits. It does not say whether the person answering WhatsApp can authorise routing, replace customer equipment, dispatch a technician or coordinate the upstream.

This is where automation reaches its limit. A customer portal, monitoring alert or ticket number can make routine work faster. It cannot climb a tower, splice fibre, restore power or decide which customer receives scarce field capacity during a regional event. Local support labour is part of the product, and the contract should expose how that labour is scheduled and empowered.

A serious buyer should test the process before depending on it. Open a low-severity ticket through each agreed channel. Record acknowledgement time and whether the response identifies the circuit without repeated explanation. Ask for the after-hours route, the named escalation owner and the trigger for upstream involvement. Then run a planned failover or disconnect test and measure detection, communication and restoration. The objective is not to ambush the provider. It is to turn a friendly local contact into a repeatable operating control.

The support channels also reveal concentration risk. The site uses a consumer Gmail address for support and WhatsApp for immediate contact. Those tools can be effective, especially for a regional operator, but a customer should ask how ticket history, staff access and continuity are managed if an account is locked, a handset is lost or the usual responder is unavailable. Convenience and accountability are not opposites; the latter requires ownership, retention and a backup route.

A Brazilian network does not settle data locality

The evidence firmly places the legal registrant in Brazil and the advertised access footprint in Rio Grande do Sul. That is useful for jurisdiction, dispatch and network attribution. It does not prove that every operational dataset stays in the same region.

Even a connectivity provider holds more than packets in transit. It may process subscriber identity, billing records, support conversations, device details, authentication state, traffic logs and abuse reports. Some of those records may sit in customer-management software, email, messaging services or monitoring tools supplied by other companies. The website pages reviewed do not identify those systems, their locations, retention periods or access controls.

For a buyer with locality obligations, the right question is therefore split in two. First, where does the traffic path go, and where are the physical access and upstream handoffs? Second, where are account, support, monitoring and security records stored and administered? The ASN answers neither question completely. A Brazilian registration country is not a map of packet paths, and a local service address is not a list of subprocessors.

The contract should identify the controller for customer records, the systems used to manage the service, the locations from which privileged access occurs, the retention and deletion rules, and the process for responding to legal demands. If the provider uses partners for routing administration or field service, the buyer should understand what data those partners can see and which party is responsible for their actions.

What operating assurance would look like

CWX has enough public evidence to move beyond a name-only assessment. The current legal registrant is identifiable. The company describes a specific regional service. The network originates registered IPv4 and IPv6 resources. The route origins validate, an upstream-side neighbour is visible, and support channels are published. Those are meaningful positives.

They are inputs to assurance, not the finished product. Before a critical purchase, the buyer should make six points testable:

  • Service boundary: name the access technology, committed and burst rates, demarcation, customer equipment, installation dependencies and any managed IT work included in the order.
  • Network performance: define how availability, latency, jitter, packet loss and throughput are measured, including the test point, maintenance exclusions and remedy when the service misses target.
  • Resilience: document physical paths, shared failure domains, upstream dependencies, power arrangements and the date and result of the latest failover exercise.
  • Address control: record assigned IPv4 and IPv6 resources, reverse-DNS and filtering responsibilities, abuse procedure, route-change authority, renumbering notice and exit treatment.
  • Support ownership: set acknowledgement, escalation, dispatch and restoration targets by severity, with names or roles that can act outside normal hours and credits where appropriate.
  • Data governance: identify the systems and partners that hold account, support and network-management data, where privileged access occurs, and how records are retained, exported and deleted.

Computers World is therefore not an empty label, but neither is the label the assurance. The public record leads to CWX Telecom, a small regional ISP with a real network and a visible support surface. For ordinary access, that may be enough to begin a commercial conversation. For a link carrying production dependence, the decisive evidence comes next: a scoped contract, observed performance, tested recovery and people who can take responsibility when the normal path stops working.