Summary

  • Registro.br binds CNPJ 32.179.884/0001-80 to AS270453, active IPv4 allocation 200.71.96.0/22 and active IPv6 allocation 2804:6c38::/32, creating an exact legal and number-resource identity.
  • RIPEstat observed five overlapping IPv4 prefix records and three overlapping IPv6 prefix records during the checked 13-27 July 2026 interval. Those records describe routing visibility, not extra address space, customer coverage or physical path diversity.
  • The company-controlled website presents residential and business fibre-labelled offers and displays a Juquehy address, but its speed, quality and stability language remains marketing rather than independent evidence of installed coverage or performance.
  • The checked AS270453 and 200.71.96.0/22 origin-prefix pair returned RPKI valid with a maximum length of /24. That narrow result cannot be generalized into a claim that the entire network is secure, leak-proof or resilient.

1. One Exact CNPJ Prevents a Loose Name Match

The name 4TELECOM is compact enough to be useful in advertising and generic enough to be dangerous in a database join. A numeral, a common industry word and a Brazilian company suffix can produce nearby records that look related even when they are not. CNPJ 32.179.884/0001-80 supplies the stable identity required to move beyond that ambiguity.

Registro.br places the exact CNPJ on the AS270453 record and on the associated IPv4 and IPv6 allocations. The company-controlled website repeats the same identifier on its about and contact pages. That convergence supports a single legal-resource identity without relying on visual branding, a search-engine result or a partial company name.

The directory boundary is equally important. The current public profile uses the country-suffixed slug 4telecom-ltda-br and corresponds to the published company record. A separate same-name record with the shorter slug is archived. Any later assessment must remain attached to the published country-suffixed entity rather than treating the two records as interchangeable.

This distinction is not administrative housekeeping. If an article, local claim or future relationship were linked to the wrong entity, a clean technical observation could become a false corporate assertion. The ASN and address resources belong to the CNPJ named by the registry, not to every company that shares a similar name.

Exact identity closure answers the first accountability question: which legal organization is named on the registered resources? It does not answer who owns every asset, who operates each access segment, or which subcontractors and suppliers participate in service delivery. Those layers require their own evidence.

The same discipline should govern future updates. A changed trade name, new domain or additional establishment should be reconciled through the legal identifier and current registry material before it is joined to AS270453. Name similarity can guide a search; it should never complete the join.

2. Juquehy Provides a Location Signal, Not a Coverage Map

The company website gives an address on Avenida Benedito Izidoro de Moraes in Juquehy, within Sao Sebastiao, Sao Paulo. That is a meaningful location signal because it places the public-facing operation in a coastal community rather than leaving the ASN detached from a local commercial context.

An office or contact address is not a service boundary. It can host administration, sales, support, network equipment or some combination of functions, while the actual access footprint may be smaller, larger or shaped by wholesale arrangements. Nothing in the address alone identifies which streets, condominiums, businesses or public institutions can order service.

Coastal geography makes that distinction economically relevant without proving anything specific about 4TELECOM's plant. Regional access networks often face uneven settlement density, seasonal demand, difficult rights-of-way and dependence on a limited number of transport corridors. Those general conditions make route and supplier concentration important questions, but they are not evidence that this operator experiences a particular failure mode.

The company's contact page repeats the Juquehy address and published contact points. Repetition across company-controlled pages improves confidence that the location is intentional public information. It still remains self-published and does not establish property ownership, equipment presence, network control or the extent of local operations.

Customers evaluating service need a different artifact: address-level serviceability with the product, installation conditions and expected handoff clearly identified. Municipal buyers and enterprises may need a route map, responsible legal entity and supplier chain. The public address is a starting point for those requests, not a substitute.

The most defensible description is therefore narrow. 4TELECOM publicly associates its legal identity with Juquehy. The available evidence does not establish a municipal coverage claim, a coastal backbone, a last-mile ownership claim or a verified facility at the displayed address.

3. The Website Describes an Offer, Not a Measured Network

4TELECOM's website markets residential and business internet and labels its plans as fibre. It displays retail speed tiers and lists installation, Wi-Fi, support and other benefits. The about page describes high performance, stability and quality as elements of the company's mission and positioning.

These statements matter because they show how the company presents its service to prospective customers. They distinguish the public offer from an ASN that exists only in registry interfaces. They also explain why the regional-ISP category is a better fit than a data-centre or generic software frame.

Marketing language has strict evidentiary limits. A plan labelled 300, 500 or 800 megabits per second is an advertised product tier, not proof of installed capacity, peak-hour throughput or availability at a specific address. “Fibre” can describe the access medium, a network segment or a product family without disclosing ownership or end-to-end topology.

Promises of stability or quality are similarly non-measurement statements. To evaluate them, a reader would need comparable latency, loss, outage, repair and utilization data collected under defined conditions. A live website does not provide that evidence merely by using performance language.

The business and residential distinction raises useful questions. Enterprise service may involve different support, addressing, handoff and restoration terms from household access. The public page does not establish whether those distinctions exist contractually or technically. It only shows that both markets are addressed in the offer.

The safest editorial use is attribution. 4TELECOM presents itself as a fibre internet provider for residential and business customers. The public records independently establish its legal and routing identity. Coverage, throughput, ownership, service levels and customer experience remain unresolved until evidence closer to delivery appears.

4. AS270453 Creates a Traceable Control-Plane Identity

An autonomous-system number gives a network a distinct identity in interdomain routing. Registro.br assigns AS270453 to 4TELECOM LTDA and the exact CNPJ, allowing public route observations to be attributed to the legal resource holder rather than inferred from a brand name.

That attribution is valuable for monitoring. Prefix origins, withdrawals, more-specific announcements and observed path relationships can be followed over time under one stable identifier. Counterparties can ask precise questions about routing policy, origin authorization and the relationship between the ASN and customer-facing services.

An ASN is not a complete map of the business. It does not reveal subscriber count, revenue, staffing, support practice or ownership of access plant. A regional provider can operate its own ASN while buying transport, leasing fibre or using third-party field services. The public routing identity does not disclose that mix.

Nor does the ASN expose every dependency. Private interconnections, Layer 2 transport, dark-fibre leases, tower access, pole agreements and managed services may remain invisible in global BGP data. A clean control-plane identity can coexist with a complex physical and contractual delivery chain.

This is why the ASN should be described as a legibility asset rather than a scale claim. It makes the network's public routing surface observable and gives responsibility a stable label. It does not prove that the company owns the paths over which customer traffic travels.

The distinction is commercially useful. A buyer can ask who controls AS270453 policy, which registered resources support the contracted service, what change process applies to route announcements and how incidents are communicated. Those questions build on the identifier without assigning capabilities the identifier cannot prove.

5. The IPv4 /22 Defines a Registered Boundary

Registro.br assigns 200.71.96.0/22 to the same company and CNPJ. The active allocation spans 200.71.96.0 through 200.71.99.255, representing 1,024 IPv4 addresses. This is an authoritative administrative boundary for the registered resource.

Registered space is not equivalent to customer space. Addresses may be used for infrastructure, management, shared translation, servers, dynamic pools or reserved capacity. Some may not be active at a particular time. The /22 cannot be converted directly into a subscriber count or device count. The allocation also says nothing about where traffic exits or where users connect. Geolocation services can reflect inferred egress points, stale registration data or commercial database choices. An address registered to a company in Brazil does not prove that every associated endpoint is in Juquehy or even in the same municipality.

RIPEstat's routing-status response reported 1,024 visible IPv4 addresses at the query snapshot. That aligns the visible address total with the registered /22, but it still does not reveal utilization. Visibility means collectors saw routes covering the space, not that each address carried customer traffic.

IPv4 scarcity gives the resource economic relevance. Directly registered space can support operational flexibility and clearer origin control. Yet value depends on use, policy, demand, reputation and contractual conditions. The public block size alone is not a valuation and does not establish market power.

The correct conclusion is exact and modest: 4TELECOM holds an active IPv4 /22 tied to its legal identity, and routes covering that space were visible at the checked time. Address assignment, customer use, service geography, capacity and performance remain separate questions.

6. The IPv6 /32 Adds a Material Dual-Stack Signal

The same CNPJ holds active IPv6 allocation 2804:6c38::/32. At the registry layer, that creates a coherent dual-stack profile alongside the IPv4 /22. The address family is not a loose association; it is bound to the same legal resource holder.

A /32 is a substantial administrative unit in IPv6 terms. RIPEstat expresses it as 65,536 possible /48 units. That figure describes address-space mathematics, not households passed, customers connected or future revenue. Most of the possible space can remain unassigned without reducing the validity of the registration.

The routing data showed the /32 and two /33 more-specifics during the checked interval. This is stronger than registration alone because it demonstrates public route visibility. It does not establish that every retail product offers native IPv6 or that customers receive stable prefix delegations.

Operational IPv6 quality involves more than an announcement. Customer-premises equipment, recursive DNS, firewall policy, support systems, content paths and troubleshooting practice all influence the user experience. None of those layers is visible in the allocation record.

For enterprises, the observed IPv6 footprint creates useful diligence questions. A buyer can ask whether native IPv6 is available, what delegation size is offered, whether addressing survives equipment replacement, and how the service is monitored. The public record makes those questions concrete without answering them.

The bounded positive statement is that AS270453 had registered and observed IPv4 and IPv6 resources during the dated window. A broader “fully IPv6-ready network” claim would require product and measurement evidence not present in the public sources.

7. Five IPv4 Records Do Not Mean Five Separate Networks

RIPEstat's announced-prefixes response lists 200.71.96.0/24, 200.71.97.0/24, 200.71.98.0/23, 200.71.98.0/24 and 200.71.99.0/24. The records were visible during the checked 13-27 July 2026 interval.

These prefixes overlap. The two /24s under 200.71.98.0/23 sit inside the larger record, and all five records fall within the registered 200.71.96.0/22. Counting them as five independent blocks would inflate the visible resource footprint and obscure the actual address boundary. More-specific announcements can reflect traffic engineering, supplier policy, fault isolation, internal organization or temporary operations. The route table records the outcome, not the operator's motive. Without an engineering disclosure, the public cannot know why each prefix is announced at a particular length.

The pattern also does not map cleanly to geography. A /24 is not automatically one neighbourhood, one point of presence or one customer class. The same facility and transport corridor can carry multiple announcements, while one prefix can serve users across several physical areas.

What the records do show is a granular public origin pattern under AS270453. That pattern can be preserved as a baseline and compared with later observations. A changed parent or more-specific may deserve follow-up, but it should not be labelled expansion, outage or rerouting until corroborating evidence identifies the cause.

The address total remains 1,024. Route count is a policy observation, not a capacity measure. Keeping those concepts separate prevents technical detail from becoming a misleading scale claim.

8. Three IPv6 Records Describe One Registered /32

The IPv6 response follows a similar pattern. RIPEstat lists 2804:6c38::/32 together with 2804:6c38::/33 and 2804:6c38:8000::/33. The two /33s partition the /32 rather than adding new registered space.

Announcing both the covering route and its halves can support policy choices, but the data does not say which choices. The records do not reveal whether the /33s correspond to suppliers, regions, services or operational stages. Any such mapping would be speculation.

This distinction matters because IPv6 numbers look enormous. Expressing a /32 as many /48 units can tempt readers to interpret address abundance as deployed scale. IPv6 planning deliberately allocates large spaces; allocation size and commercial footprint have a weak direct relationship.

The observations do provide one meaningful signal: the company's IPv6 identity is visible in more than a single coarse record. That can support ongoing monitoring of origin, prefix length and route changes. It still cannot show the share of customers using IPv6 or the quality of those paths.

Security interpretation also needs precision. The RPKI response in this evidence set concerns the IPv4 parent, not every IPv6 route. The IPv6 announcements should not inherit a validity conclusion from a different prefix. Each origin-prefix pair needs its own current authorization check.

The responsible reading is therefore structural. One active /32 was registered to 4TELECOM, and the checked collectors saw the /32 plus two /33 more-specifics. Deployment, adoption, customer delegation, routing intent and authorization for each IPv6 route remain to be established separately.

9. The Observation Window Is a Baseline, Not an Uptime Claim

The announced-prefixes response covers 13-27 July 2026. A multi-day window is more informative than a single instant because it reduces the chance that every record reflects only a fleeting announcement. It still remains bounded by the selected dates and collector coverage.

RIPEstat's routing-status snapshot reported high peer visibility for both address families at the query time. That means the origin was broadly observable from the checked RIS vantage points. It does not mean every network on the Internet saw an identical path or that every customer service was operating normally.

Control-plane visibility and customer availability can diverge. A prefix can remain globally visible while a local access segment, power supply, customer router or application is impaired. A route can also be withdrawn for maintenance without producing a prolonged customer outage.

The data does not support an annual uptime percentage. It cannot establish conditions before 13 July or after 27 July, and it does not define an outage in service terms. Longitudinal reliability analysis would require consistent collection plus a separate record of customer-impacting events.

Dates should travel with every route statement. That discipline allows future reviewers to distinguish a genuine network change from a different query period or collector method. It also prevents a positive July observation from becoming a timeless claim about the network.

The interval is best used as a monitoring baseline. It establishes which exact prefixes were visible under AS270453 during the period. Later checks can identify withdrawals, new more-specifics, origin changes or IPv6 shifts, while interpretation waits for corroborating evidence.

10. Three Observed Neighbours Are Not Three Contracts

RIPEstat returned three observed neighbouring ASNs: AS10429, AS263327 and AS270340. In the collector data, each appeared on the left side of observed paths toward AS270453. This is a route-path observation, not a contract disclosure.

An adjacent ASN can reflect transit, peering, a customer relationship, route-server behaviour or another arrangement. Public BGP paths do not disclose payment terms, committed capacity, duration, exclusivity or operational responsibility. Labelling every neighbour an “upstream” would go beyond the evidence.

The three records also do not prove three physically independent connections. Separate AS relationships can share a building, cable route, power system, router or wholesale dependency. Conversely, one commercial relationship can use several physically diverse handoffs. Resilience requires failure-domain evidence. A credible claim would need route and facility maps, supplier identities, capacity commitments, independent-path declarations, failover design and test or incident results. Neighbour count can guide those questions but cannot verify the answers.

The observations still have practical value. They identify networks relevant to route monitoring and counterpart diligence. A newly visible or disappearing neighbour may justify follow-up, particularly if prefix visibility changes at the same time. The cause should remain unassigned until corroborated.

4TELECOM's public routing identity is therefore connected, but the commercial and physical character of those connections is unknown. That is a meaningful boundary, not a deficiency to be filled with assumption.

11. RPKI Validity Solves One Narrow Origin Question

Routinator returned a valid result for AS270453 and 200.71.96.0/22, with a route origin authorization permitting maximum length /24. The finding gives a concrete answer to a specific question: was the checked origin-prefix pair covered by a matching authorization at the query?

The maximum length is relevant because the observed IPv4 records include /24s. An authorization allowing up to /24 can cover those lengths when the origin and other conditions match. A complete review would still check each current route rather than treating one parent response as a permanent blanket.

Validity does not prove that every network rejects invalid routes. It does not show router patching, access security, monitoring quality or incident response. RPKI addresses authorization of route origins; it is not a general cybersecurity certificate.

Nor is a valid route guaranteed to remain available. It can be withdrawn, congested or affected by failures. Origin authorization reduces one class of ambiguity, but it does not create capacity, redundancy or customer service.

The result should be reported with its exact scope and time. The checked AS270453 and 200.71.96.0/22 pair was RPKI valid with maximum length /24. Claims that the entire network is secure, leak-proof or resilient would exceed that result.

IPv6 deserves separate treatment. The observed 2804:6c38::/32 and /33 records are visible routing facts, but this source set does not supply a matching IPv6 validation conclusion. Missing validation evidence should remain missing rather than being inferred from the IPv4 response.

12. PeeringDB Adds Identity but Little Presence Detail

PeeringDB associates ASN 270453 with the name 4TELECOM and the company website. It marks the general policy as open and reports an acceptable RIR status. Those fields reinforce the identity connection already established by Registro.br.

The record is operator-maintained and was last updated in July 2022. It reports no exchange count, no facility count, no traffic level, no geographic scope and no prefix counts. That sparsity sharply limits present-tense operating conclusions. An open policy is a posture, not proof of a live peering session. It does not establish where a handoff exists, who participates, what capacity is available or whether traffic currently flows. The record should not be used to manufacture an interconnection footprint that it does not list.

The absence of exchange and facility records also needs restraint. It may mean no presence was reported, not that no interconnection or facility use exists. Operators differ in how completely and frequently they maintain public directories.

PeeringDB's useful contribution is identity continuity. The ASN, company name and domain align in another infrastructure-specific source. That reduces accidental matching and gives future reviewers a dated record to compare with later operator updates.

Current interconnection diligence still requires direct, attributable evidence. A counterpart should ask where handoffs occur, which relationships are contracted, how capacity is monitored and whether paths share facilities. The public record gives the question a target without supplying the answer.

13. Resource Control Creates Options, Not Guaranteed Independence

Holding an ASN, an IPv4 block and an IPv6 /32 gives a regional provider more direct control over public addressing and routing than a reseller with no visible number-resource identity. That can support portability, clearer policy and more precise incident attribution.

The resource set creates options. It may allow the operator to originate its own prefixes, adjust relationships or keep addressing more stable when commercial arrangements change. Whether those options are fully exercised depends on contracts, facilities, staff, equipment and operating practice.

Administrative control is not the same as physical independence. A company can control its public origin while relying on leased access, wholesale transport or shared infrastructure. Those arrangements can be entirely legitimate, but they distribute cost and failure responsibility differently from owned end-to-end plant.

The public data does not show bargaining power. Three observed neighbours do not reveal committed volumes, pricing, alternatives or switching costs. A visible ASN can improve negotiating position, yet actual leverage depends on local market structure and available handoff locations.

IPv4 scarcity adds potential economic value, but utilization is unknown. IPv6 creates address flexibility, but customer adoption is unknown. Neither resource should be converted into a revenue or valuation claim without operational and financial evidence.

The strongest economic conclusion is conditional: 4TELECOM controls identifiable number resources that could support a more flexible regional network model. Whether that potential delivers lower cost, better continuity or broader service remains unproved.

14. Access Delivery Has More Layers Than BGP Can Show

Customer traffic crosses several layers before it reaches the public Internet. Premises equipment, drops, distribution plant, aggregation, transport, power, routing, DNS and support processes can each affect the experience. BGP reveals only part of that chain.

AS270453 and its prefixes describe the public control-plane edge. They cannot show whether a customer's final connection is fibre to the premises, a shared building network, a wireless extension or a wholesale circuit. The website's fibre label is a product statement, not a complete topology.

Physical ownership is similarly opaque. Fibre can be owned, leased, shared or obtained through capacity agreements. Cabinets and access equipment can sit on property controlled by different parties. Public route data cannot assign those assets to the legal holder.

Power and maintenance create another hidden layer. Backup systems, spares, field staffing, dispatch coverage and restoration practice determine how a regional service behaves during disruption. None can be inferred from prefix size or route visibility. This gap explains why a visible ASN is informative without being sufficient. It narrows who can answer routing questions and establishes a monitorable origin. It does not replace serviceability, asset, supplier and operating evidence.

Customers and partners should therefore align each claim with the layer that can prove it. Registry data supports resource control. Route collectors support visibility. Contracts and diagrams support dependencies. Measurements and incident records support performance. Mixing those layers creates false confidence.

15. Residential and Business Buyers Need Different Proof

The website addresses both residential and business customers. The two groups can share a physical access network while requiring different evidence about service, support and risk. A public plan page does not establish how the underlying commitments differ.

Residential buyers usually need address-level availability, installation terms, equipment details, realistic speed expectations and support access. A fibre label is useful, but the buyer still needs to know whether the final handoff is available at the premises and what conditions affect installation.

Business buyers may need static addressing, service-level terms, escalation paths, maintenance windows, restoration objectives and clarity about upstream dependencies. The existence of AS270453 and direct number resources makes those questions easier to frame, but it does not answer them.

Organizations with continuity requirements should ask whether primary and backup services share poles, ducts, buildings, suppliers or power. Separate invoices and different AS paths can still converge on one physical failure domain. Public neighbour data cannot resolve that risk.

Security-sensitive customers can also ask how RPKI, route filtering and change control are implemented. The valid IPv4 origin observation is a constructive starting point. It should lead to current operational evidence rather than a broad assumption about security posture.

The operator's public identity is sufficiently precise for these conversations. Customers can cite the CNPJ, ASN and exact prefixes instead of relying on a generic brand. That precision is valuable even while the delivery evidence remains incomplete.

16. Procurement Should Separate Four Evidence Layers

A disciplined procurement review can organize the available information into four layers: identity, number resources, routing observations and service delivery. The first three have useful public evidence for 4TELECOM. The fourth remains mostly private or undisclosed.

Identity evidence should bind the exact legal company, CNPJ and directory entity. Number-resource evidence should record the ASN and allocations from the authoritative registry. Routing evidence should preserve exact prefixes, origins, validation results, neighbours, dates and collector limitations. Service-delivery evidence requires different documents. Buyers may need serviceability confirmation, handoff design, supplier and facility dependencies, capacity commitments, escalation ownership, maintenance policy, performance measurements and restoration history. A route table cannot substitute for them.

Keeping the layers separate improves fairness as well as rigour. It avoids dismissing a smaller operator because it lacks the disclosure volume of a national carrier, while also avoiding promotional assumptions based on a compact technical footprint. Each claim is judged against evidence appropriate to its layer.

The method also makes updates easier. A routing change can be recorded without rewriting the legal identity. A new product claim can be attributed to the website without changing the registered resource facts. A verified service map can later close a delivery gap without altering the ASN history.

The public record already supports a strong first three layers. The next useful disclosure would not be another generic quality statement. It would be evidence that connects those layers to specific customer delivery commitments.

17. The Exact Questions That Would Close the Delivery Gap

The first question is geographic: which addresses or zones are serviceable, through which access method, and under which legal entity? A useful answer would distinguish marketed territory from installed availability and identify whether validation occurs before an order is accepted.

The second question concerns infrastructure control. Which parts of the access and transport path are owned, leased, shared or purchased? Counterparties do not need every sensitive engineering detail, but they do need to understand who is responsible for maintenance and where supplier concentration exists.

The third question concerns interconnection. What commercial relationships support AS270453, where are the handoffs, and which paths are physically independent? The observed neighbour set supplies candidate ASNs for clarification but not the contractual answer.

The fourth question is operational. What capacity-monitoring, change-control, incident-response and restoration practices apply? Metrics should come with definitions and time windows. A single best-case speed or broad reliability phrase is not comparable evidence.

The fifth question concerns IPv6. Which products receive native IPv6, what prefix delegation is offered, and how is continuity handled across equipment or service changes? The registered and visible /32 makes this a practical product question rather than a theoretical one.

Finally, route security should be documented at current scope. Which IPv4 and IPv6 announcements have valid origin authorizations, how are invalid routes handled, and how frequently are records reviewed? The checked IPv4 result is positive, but a repeatable policy would be more informative than one snapshot.

Answers become more useful when they include definitions. “Availability” should identify the measured service boundary, exclusions, observation interval and aggregation method. “Capacity” should distinguish installed, purchased, committed and usable bandwidth. “Diversity” should identify shared ducts, poles, buildings, power and suppliers rather than counting labels. Without those definitions, comparable-looking figures can describe very different operating realities.

A proportionate evidence package need not expose sensitive network configuration. It can provide a current serviceability confirmation, a high-level dependency diagram, the responsible legal entity, dated origin-authorization status, maintenance and escalation contacts, and measurements summarized over a stated period. That would close the most commercially important gaps while preserving security and supplier confidentiality.

18. A Monitoring Agenda Can Stay Proportionate

The exact identifiers make a lightweight monitoring programme possible. AS270453, 200.71.96.0/22, 2804:6c38::/32, CNPJ 32.179.884/0001-80 and the exact directory entity can be tracked without broad name scraping.

Monthly route checks could record announced prefixes, origins, validation state and observed neighbours. Changes should be logged as observations first. A new prefix or adjacency becomes a business or resilience event only when another source explains its meaning. The company website can be monitored for changes in contact details, products and explicit service areas. Because it is a marketing surface, every new claim should retain attribution. It becomes stronger when supported by a regulator, contract, technical document or independent measurement.

Directory identity should remain stable around the country-suffixed entity. The archived same-name record should not absorb new research relationships or claims. If evidence later proves a corporate relationship between the records, it should be stated and supported separately rather than created through an implicit merge.

RPKI monitoring should cover each visible origin-prefix pair, including IPv6. Validity can change as routes or authorizations change. A missing check is not evidence of invalidity, and a prior valid result should not be carried forward indefinitely.

This agenda is intentionally modest. It preserves high-signal facts, highlights actual changes and resists converting absence into accusation. For a regional provider with limited public disclosure, that balance produces a more useful record than either promotional certainty or blanket scepticism.

19. What the Current Evidence Says About Scale

The registered IPv4 space is compact and exact. The IPv6 allocation is administratively large but normal for structured delegation. The route table shows a handful of overlapping records and three observed neighbours. None of these numbers is a direct measure of customers, revenue, traffic or kilometres of fibre.

Scale can appear differently across layers. A provider with a small public routing footprint may serve a meaningful local customer base through efficient addressing and purchased transport. A large address allocation may be lightly used. Public resource size and commercial reach should not be ranked as if they were the same variable.

The company markets several retail speed tiers, but product labels do not disclose aggregate capacity or contention. A higher advertised tier can coexist with a small footprint, while a lower tier can serve a wide area. Capacity planning requires utilization and backhaul evidence unavailable here.

Facility presence is also absent from the PeeringDB record. That does not establish that the company has no facilities or exchange access; it means none is documented in that record. Absence should remain a disclosure gap rather than a negative scale conclusion.

The only defensible scale statement is about the observed public footprint: one ASN, one IPv4 /22, one IPv6 /32, overlapping visible prefixes and three observed route neighbours at the checked snapshot. Commercial and physical scale remain unknown.

This restraint protects comparisons. Regional operators should be compared on consistent service, asset, performance and financial evidence, not on whichever registry fields happen to be most visible. Public routing data is excellent for attribution and change detection; it is poor as a standalone league table.

20. Visibility Is a Starting Point, Not a Delivery Verdict

4TELECOM's legal and technical identity is unusually coherent across public sources. The exact CNPJ appears on AS270453 and both address allocations. The company website repeats the identifier and presents a regional fibre offer. RIPEstat shows dual-stack route visibility, while PeeringDB supplies a consistent operator-maintained name and domain.

The records therefore support a positive conclusion about legibility. Readers can identify the legal resource holder, see which prefixes were visible, verify one scoped IPv4 origin authorization and monitor future changes. That is meaningful infrastructure evidence.

The same records enforce a boundary. They do not prove address-level serviceability, installed fibre ownership, supplier contracts, capacity, path independence, backup power, support performance, outage history or resilience. Marketing claims cannot close that boundary, and route counts cannot be converted into it. For customers, the practical value lies in better questions. Exact identifiers make it easier to request current service maps, dependencies, IPv6 terms, route-security policy and performance evidence. For the operator, answering those questions can turn registry visibility into stronger commercial trust.

For counterparties and researchers, the discipline is to preserve time, attribution and layer. A valid route is reported as a valid route. A company claim is reported as a company claim. A missing asset record remains unknown rather than becoming either proof or suspicion.

AS270453 makes 4TELECOM visible in the public routing system. The delivery system behind that identity remains only partly visible. Treating both truths together gives a more accurate picture of a regional ISP than either a marketing page or a route table can provide alone.

Sources