Summary

  • CNPJ 01.472.702/0001-30 links C-ComTelecom's official web presence to AS265369, the domain ccomtelecom.com.br, the IPv4 allocation 168.205.100.0/22 and the IPv6 allocation 2804:2ed4::/32.
  • A dated RIPEstat snapshot showed twelve visible IPv4 prefixes, three IPv6 prefixes and twelve observed neighbouring ASNs, making the routing identity traceable without proving commercial relationships, physical topology or service quality.
  • The company's own website describes a multi-municipality fibre service, while a municipal record supports one specific public-sector broadband procurement. Neither establishes universal serviceability, owned plant, measured performance or market scale.
  • The exact checked AS265369 and 168.205.100.0/22 origin-prefix pair returned RPKI valid. That narrow result should not be generalized to every route or to the operator's entire security programme.

1. The Exact Identity Is Held Together by the CNPJ

The name in the network registries is awkward: C-ComTelecom Servios Ltda-ME. The missing letters in “Servios” could look like a separate company if the text were read without its identifiers. The official website instead uses C-ComTelecom Serviços, while the privacy notice renders the legal name without diacritics. Those variations converge on CNPJ 01.472.702/0001-30, which is the decisive identity field.

The same CNPJ appears in the official privacy notice, the Registro.br autonomous-system record, the Registro.br domain record and the address-allocation records. That repetition allows the legal identity, public brand, domain and number resources to be joined without guessing from a similar name. It also explains why a typo preserved in a registry should not be treated as evidence of a second operating company.

Registro.br names Carlos Eduardo Lagreca Alves as the legal representative associated with the resources. The privacy notice gives Rua Paulo Franco Werneck 296 in São José do Vale do Rio Preto, Rio de Janeiro. These are useful accountability points. They indicate whom the technical records refer to and where the company says its administrative contact sits; they do not map the location of every network asset.

The exact directory record uses the country-suffixed slug for the published company identity. A separate plain-slug record with the same display name is archived. That distinction matters because a research article should connect to the active entity whose identifier matches the evidence, not revive or merge an archived entity merely because the names look alike.

Identity closure is therefore strong but bounded. The CNPJ supports one company across spelling variants and network records. It does not establish a corporate group, transfer rights to another entity, or prove that every service marketed under the brand is delivered by the same equipment, contract or operational team. The identifier solves the “who” question more reliably than it solves the “how” question.

2. The Official Website Defines the Commercial Claim

C-ComTelecom describes itself as a telecommunications service provider that began in São José do Vale do Rio Preto. Its public pages market fibre access to households and businesses and present a regional footprint extending beyond the company's home municipality. This is direct evidence of how the operator positions its service and which market it says it addresses.

The site presents plans with advertised access speeds and says the topology is fully fibre-based. Those statements are commercially relevant because they describe the product customers are invited to buy. They remain first-party claims. The pages do not disclose a methodology for measuring delivered speed, a network diagram, ownership records for the fibre, or an independent audit of the access architecture.

A coverage selector names fourteen municipalities, including Petrópolis, Teresópolis, Três Rios and Juiz de Fora. The breadth of that list suggests an ambition beyond a single-town provider. Yet a municipality-level selector is not an address-level serviceability test. It does not reveal whether coverage is continuous, whether it reaches only selected neighbourhoods, or whether access depends on partners in some places.

The commercial presentation also does not separate owned infrastructure from leased or shared inputs. A provider can legitimately sell fibre access while using ducts, poles, transport, exchanges or upstream capacity supplied by others. The customer experience can still be coherent, but the capital structure and failure domains differ. The website does not identify those boundaries.

The safest reading is therefore literal. C-ComTelecom says it operates a regional fibre-access business and markets service across a named set of municipalities. That statement helps define the company's intended operating surface. Independent public records are needed to test the network resources behind it, while plant ownership, detailed coverage, capacity and performance remain questions for more specific evidence.

3. A Coverage List Is Not a Serviceability Map

Municipality names are useful for orientation but weak as a measure of reach. A Brazilian municipality can contain dense urban districts, rural roads, steep terrain and areas served by different physical routes. Being present somewhere within a municipal boundary does not mean that every residence, business or public building can order the same product on the same terms.

Serviceability usually depends on details absent from a marketing selector: the nearest distribution point, available splitter capacity, pole access, building entry, distance from existing plant, local rights of way and installation economics. Two addresses on the same street can have different results. A list of cities cannot show those constraints, even when it is accurate as a general statement of presence.

The difference matters for interpreting expansion. Adding a municipality to a website may indicate a completed network, a limited launch, a partner arrangement, a sales test or a planned footprint. Without dated build disclosures or address-level availability data, the change should not be converted into a kilometres-of-fibre estimate or a subscriber forecast.

It also matters for resilience. Geographic breadth can look like diversity, but several towns may depend on the same transport corridor or external supplier. Conversely, a compact footprint can contain multiple paths and well-tested failover. Municipal coverage and route diversity are different properties, and neither can be inferred from the other.

The coverage selector is still valuable because it provides a list against which future evidence can be checked. Public tenders, pole agreements, local permits, outage notices and attributable expansion announcements may confirm activity in individual places. Until such evidence is available, the list should be reported as C-ComTelecom's own description of its sales area rather than an independently verified network map.

4. One Municipal Record Anchors a Specific Service Context

A 2024 record from the municipal legislature in São José do Vale do Rio Preto identifies C-ComTelecom and the same CNPJ in a procurement involving two broadband links. The record specifies a minimum of 600 Mbps for the links. This is more concrete than a generic marketing page because it places the legal company inside a dated public-sector purchasing context.

The procurement supports a narrow conclusion: at least one municipal body documented a broadband requirement involving this provider under its exact identifier. It shows that the company was not merely a dormant holder of network resources at the time of that record. It does not establish the status of the service today, the route used, or whether the stated minimum was continuously achieved.

Contract values and technical requirements can also be misread as market indicators. One public agreement does not reveal total revenue, customer concentration, margins or the proportion of business generated by government clients. It cannot establish market share in the municipality or in the wider region. The record is a transaction-specific observation, not a financial profile.

Nor does the procurement prove physical ownership. The provider could deliver the contracted links through owned fibre, leased transport, third-party infrastructure or a combination. The public document does not provide a route diagram or supplier schedule. Its value lies in connecting the exact company to a defined service obligation, not in filling the missing topology.

For future monitoring, the record creates a useful baseline. Renewal documents, amendments, performance notices or new tenders could show how the relationship developed. Each would need to be read on its own terms. The current evidence supports one dated municipal broadband engagement and no broader claim about universal coverage, measured quality or government dependence.

5. AS265369 Is a Public Accountability Point

An autonomous-system number gives a network a distinct identity in interdomain routing. Registro.br assigns AS265369 to C-ComTelecom's CNPJ, making the legal holder behind the origin visible. That connection is valuable for incident response, due diligence and longitudinal monitoring because route observations can be compared with a stable administrative identifier.

The ASN does not describe the internal network. It does not reveal router models, access technologies, fibre paths, exchange ports, customer circuits or staff responsibilities. A regional provider may operate substantial local plant while relying on external transport, or it may control a compact routing layer over infrastructure supplied by partners. The number itself does not choose between those models.

AS265369 was registered in March 2016. That date marks an administrative milestone, not necessarily the launch of every current product or the start of commercial operations. Registry update dates can reflect contact maintenance and should not be read as investment events. Commercial chronology needs company statements, contracts or other attributable records.

The identifier does allow precise questions. Which services are expected to use AS265369? Who can authorize route changes? How are incidents involving the registered prefixes escalated? Which systems monitor unexpected origins or withdrawals? These questions are stronger than asking whether the provider “has an ASN”, because they focus on control and responsibility.

The evidence supports an active, traceable routing identity tied to the exact company. It does not support a rating of network scale or maturity. The useful distinction is that AS265369 creates an observable control-plane surface. Whether that surface corresponds to a broad, diverse and consistently delivered service depends on evidence that the registry cannot provide.

6. Registered Address Space Shows Administrative Control

Registro.br assigns 168.205.100.0/22 to the same CNPJ. A /22 contains 1,024 IPv4 addresses and establishes an administrative allocation under the company identity. The record is important because it connects an Internet number resource to the legal operator rather than leaving the network's addressing dependent on an unnamed third party.

The IPv6 allocation, 2804:2ed4::/32, provides a parallel resource surface. A /32 is a provider-scale IPv6 block designed for hierarchical delegation. Its enormous numerical size should not be compared with IPv4 address counts as a measure of business scale. IPv6 architecture intentionally gives operators room for structured subnetting.

Allocation is not the same as use. Registered space may be announced in aggregate or through more-specific routes, held in reserve, delegated to customers, used for infrastructure or left temporarily unannounced. The RDAP entities do not show which addresses serve households, businesses, routers, management systems or public contracts.

The records also do not prove physical location. An allocation registered to a company in São José do Vale do Rio Preto can be originated from several points, transported through external facilities or used across a regional network. IP addresses do not encode fibre ownership or a city-level point of presence. Location claims require separate operational evidence.

What the allocations do establish is a durable accountability baseline. Unexpected origins can be compared with the registered holder. Customers can ask how address assignments are handled and whether IPv6 is available for a particular product. Researchers can distinguish administrative resources from observed routing. These are meaningful benefits, provided the records are not stretched into coverage or capacity claims.

7. Twelve Visible IPv4 Prefixes Expand the Routing Picture

RIPEstat's dated routing-status snapshot reported twelve visible IPv4 prefixes originated by AS265369, covering 6,144 addresses in its summary. The announced-prefix response includes the registered 168.205.100.0/22 as well as 189.36.208.0/21, 187.121.236.0/22, 138.118.44.0/22 and several more-specific routes. The result is a wider observed footprint than one allocation record alone would suggest.

The set is useful because it confirms current control-plane activity at the time checked. AS265369 was not merely a registry entity without visible routes. Public collectors saw a collection of announcements associated with the origin, and those announcements can be monitored for changes in origin, aggregation and visibility.

Prefix count is not a scale metric. One network can announce a few large aggregates, while another announces many smaller routes for traffic engineering or historical reasons. The number twelve does not measure subscribers, traffic, revenue or geographic coverage. Even the summary of IPv4 addresses cannot be converted into a customer count because addresses serve many different technical roles.

More-specific routes need contextual interpretation. They can support routing policy, resilience, mitigation or operational segmentation, but the prefix list alone does not reveal the purpose. A new more-specific announcement is not automatically expansion, and a withdrawal is not automatically an outage. Timing and corroborating evidence are necessary.

The defensible conclusion is that AS265369 had a non-trivial, publicly visible IPv4 origin surface in the checked snapshot. That strengthens the case for treating C-ComTelecom as an active regional network operator. It does not close the relationship between those routes and the municipalities, products, fibre assets or service levels presented on the company's website.

8. IPv6 Visibility Adds Evidence Without Measuring Adoption

The same RIPEstat snapshot reported three visible IPv6 prefixes for AS265369 and summarized them as 65,536 /48 equivalents. The registered 2804:2ed4::/32 appears in the announced set together with more-specific routing information. This shows that IPv6 is present in the operator's public routing identity rather than existing only as an unannounced registration.

That observation should not be translated into universal customer availability. An operator may announce IPv6 for infrastructure or selected services while some access products remain IPv4-only. The route collector does not reveal which plans include IPv6, what prefix length a customer receives, whether delegations are stable, or how reverse DNS is managed.

The /48-equivalent summary is especially easy to misuse. It describes address-space structure, not active subscriptions or deployed endpoints. A single routed aggregate can represent a large potential hierarchy while carrying little traffic. Conversely, a carefully aggregated network can serve many customers without a long list of visible prefixes.

Public visibility also differs from continuity. A prefix can be present in collector tables while a downstream service is impaired, and a route absent from a particular view may still be reachable elsewhere. The checked observation should retain its date and collector context. It is a control-plane baseline, not an uptime result.

IPv6 nevertheless improves the due-diligence picture. It shows that the exact ASN has both IPv4 and IPv6 routing surfaces and gives customers a concrete starting point for product questions. The missing details are operational: assignment policy, customer deployment, traffic, security controls and support. Those fields determine whether registered capability becomes a dependable service.

9. Full Collector Visibility Is Not an Availability Guarantee

RIPEstat reported AS265369 visible to all RIS peers in the IPv4 and IPv6 snapshot used for this review. Broad collector visibility indicates that the routes reached the observation points participating at that time. It is stronger than seeing an announcement at only a small subset of collectors and provides a useful dated picture of propagation.

The phrase “all RIS peers” has a defined boundary. It refers to peers in the RIPE Routing Information Service observation set, not every network on the Internet. Collectors sample the global routing system through participating sessions. Their view is extensive but not identical to universal reachability from every access provider, enterprise or country.

Route presence also cannot test application performance. A prefix may be visible while latency, packet loss, DNS, authentication or last-mile access is degraded. BGP collectors do not measure whether a household receives its advertised speed or whether a municipal circuit meets a service-level commitment. Control-plane propagation and end-user quality are separate layers.

The snapshot remains valuable for change detection. If future observations show reduced visibility, a different origin or a changed prefix set, the variance can be recorded and investigated. Attribution requires care: maintenance, collector changes, policy adjustments and incidents can produce similar public symptoms. A route event becomes an outage claim only with supporting evidence.

For C-ComTelecom, the broad observation confirms that its routing identity was meaningfully present in public tables at the checked time. It supports describing an active network-resource surface. It does not prove continuous availability, path diversity, customer reach, congestion performance or the physical route by which traffic entered and left the regional footprint.

10. Twelve Observed Neighbours Are Not Twelve Contracts

RIPEstat listed twelve unique neighbouring ASNs around AS265369 in the checked paths. The response grouped them as six left-side observations, one right-side observation and five with uncertain direction. This reveals that the ASN appeared alongside multiple other networks in public path data, offering clues about the wider routing environment.

An observed neighbour is not automatically an upstream, peer or customer. AS paths show adjacency in a route view, but they do not disclose the commercial agreement, direction of payment, traffic ratios, capacity, handoff location or legal counterparty. Route servers, policy choices and partial visibility can further complicate interpretation.

The left and right labels should not be treated as a contractual taxonomy. Their meaning depends on path orientation and observation context. The uncertain group is a reminder that public data does not always support even a directional inference. Naming every neighbour as a supplier would turn a technical trace into an unsupported procurement map.

The count also cannot establish resilience. Twelve observed ASNs may represent several independent relationships, repeated views of a smaller set of dependencies, or paths that converge on common physical infrastructure. A network with fewer visible neighbours can have diverse circuits; a network with many can share a single vulnerable corridor. Contracts and physical-route evidence are needed.

The neighbour set is best used as a monitoring index. Changes can raise questions about routing policy, supplier arrangements or network events, but each interpretation needs corroboration. For customers, the practical requests remain concrete: identify contracted upstreams, exchange participation, backup paths, handoff locations and tested failover procedures. Public adjacency alone cannot answer them.

11. PeeringDB Describes an Interconnection Posture in the Operator's Own Terms

PeeringDB's record for AS265369 describes C-ComTelecom as a regional Cable/DSL/ISP network. It lists one Internet exchange and one facility and places traffic in the 50-100 Gbps band. These fields provide a compact account of how the network presents itself to the interconnection community.

The database is user-maintained. Network operators or their representatives supply and update much of the information, which makes it useful for contacts and interconnection discovery but different from an audited capacity statement. The traffic band is self-reported; the listed exchange and facility describe directory entries, not proof of active ports, contracted capacity or current utilization.

The category labels are broad as well. “Cable/DSL/ISP” does not establish the access technology used at every location, and “regional” does not define an exact market boundary. The official website's fibre claims provide more specific product positioning, but they still do not transform the PeeringDB entry into an independent topology audit.

Interconnection presence can carry economic significance. An exchange may create options for local traffic exchange, and a facility listing can identify a place where the network expects to be found. Whether those options reduce transit cost, latency or dependency depends on active sessions, traffic distribution and contractual arrangements that are not disclosed here.

Read together, PeeringDB and RIPEstat show a network with a self-described interconnection surface and a publicly visible route footprint. They do not provide the same type of evidence. The collector observes paths; the directory records operator-supplied attributes. Keeping those roles separate preserves their value and avoids turning a public profile into independently verified capacity.

12. The Checked RPKI Pair Was Valid

RIPEstat's Routinator-backed validation response returned valid for the exact pair AS265369 and 168.205.100.0/22. It identified a route-origin authorization consistent with that origin and prefix, with a maximum length of 32. This is a positive and specific routing-security signal at the time of the check.

The scope is narrow. The result applies to one origin-prefix pair and the authorization state visible to the validator. It does not establish that every IPv4 or IPv6 prefix announced by AS265369 is valid. It also does not prove that the operator maintains a complete security programme, monitors incidents continuously or follows a particular change-control process.

Maximum length 32 permits more-specific IPv4 announcements within the covered space down to /32 under the authorization. That flexibility may be intentional, but the public response does not explain policy. A broad maximum length should not be praised or criticized without knowing the operational requirements and the complete set of authorizations.

Validation status can change. A certificate or ROA update, route-policy change, registry issue or incorrect origin can move a pair between valid, invalid and not found. Monitoring should therefore retain the exact origin, prefix, time and validator. A generic statement that “C-ComTelecom is RPKI protected” would lose the detail needed to evaluate future changes.

For counterparties, the valid pair supports focused questions about responsibility. Who manages route-origin authorizations, how quickly are changes published, and what happens if an unexpected origin appears? The available evidence answers only the baseline: this exact AS265369 and 168.205.100.0/22 combination validated successfully when checked.

13. Registered Resources Can Improve Regional Bargaining Power, but the Evidence Does Not Price It

Controlling an ASN and portable address resources can give a regional ISP more options than operating entirely under a supplier's identifiers. The company can establish an independent routing identity, manage origin policy and potentially change connectivity arrangements without renumbering every service. Those capabilities can improve operational autonomy and counterpart visibility.

The resources do not guarantee bargaining power. A provider may still depend on a limited set of transport routes, facilities or upstream networks. Local geography, fibre access, exchange availability and traffic scale affect commercial choices. The public records show route visibility and several observed adjacencies, not the prices, capacities or contractual alternatives behind them.

IPv4 scarcity gives allocated space potential value, but address counts are not a balance-sheet measure. Some addresses may be reserved, delegated or used internally, and transfer conditions are governed by policy. The evidence does not show monetization, utilization, leasing or customer demand. Treating 6,144 visible IPv4 addresses as revenue-producing units would be misleading.

IPv6 capability can reduce long-term dependence on scarce IPv4, yet adoption requires customer equipment, support processes and product design. A visible /32 is an enabling resource rather than proof of commercial deployment. Its economic benefit depends on how the operator integrates it into access, enterprise and public-sector services.

C-ComTelecom's resource footprint therefore indicates strategic optionality, not measured financial strength. The company has a recognizable control-plane identity and registered address space. How much value those assets create depends on traffic, customers, transport economics, service quality and operational discipline. None of those variables is quantified by the current public material.

14. The Delivery Boundary Remains the Central Diligence Question

The most visible facts sit at different layers. The company names cities and fibre products. Registro.br identifies legal control of Internet resources. RIPEstat observes routes. PeeringDB records self-described interconnection attributes. A municipal document identifies one service procurement. Together they form a coherent picture of an active regional provider, but they do not show how every layer is connected.

Physical plant is the largest gap. The records do not identify which fibre routes are owned, leased or shared; where major handoffs occur; which poles or ducts are used; or whether different municipal links share common corridors. Those details determine capital intensity and failure exposure but are not encoded in an ASN or a coverage selector.

Capacity is similarly unresolved. A self-reported traffic band is not purchased capacity, peak load or spare headroom. Advertised access speeds do not disclose aggregation ratios or congestion. Public route tables carry no traffic volume. Performance claims require measurements with defined locations, intervals and methodology.

Accountability across suppliers also remains open. Observed neighbouring ASNs may point toward external relationships, but only contracts and operator disclosures can identify the parties and obligations. Customers need to know who owns the access segment, who supplies transport, who controls BGP changes and which support team can act during an incident.

This boundary is not evidence of weakness; it is the limit of what public technical records can establish. Many functioning regional networks combine owned and purchased infrastructure. The diligence task is to document the combination rather than assume that a strong registration trail automatically proves end-to-end delivery conditions.

15. Customers Can Convert Public Clues into Contract Questions

The CNPJ, ASN and prefixes provide unusually precise reference points for procurement. A service agreement can name CNPJ 01.472.702/0001-30, identify whether AS265369 is expected to originate the service routes and state what address resources apply. Precision reduces ambiguity when a brand name and a registry spelling differ.

Coverage promises should be address-specific. Instead of relying on a municipality list, a buyer can request a serviceability confirmation, installation design and clear conditions for construction. For multi-site contracts, each location should identify the access medium, handoff, lead time and responsible party. This turns a broad sales footprint into auditable obligations.

Network terms can separate access, transport and Internet routing. Contracts may state whether links use owned or third-party fibre, which failure domains are shared, and what redundancy is included. If route diversity is material, the provider can supply path or carrier evidence under appropriate confidentiality rather than relying on ASN-neighbour counts.

Operational governance deserves equal attention. Customers can ask who manages RPKI, how routing incidents are detected, what contacts can authorize changes and how escalation works outside business hours. The valid checked route-origin pair is a good baseline, but procedures determine whether that state remains reliable during maintenance and emergencies.

Performance commitments require measurable definitions. Advertised speeds should be connected to test endpoints, service windows and remedies. Availability, latency and repair times need explicit measurement rules. The municipal procurement demonstrates that a buyer can specify a minimum broadband requirement; it does not reveal how that requirement was monitored or enforced.

16. Public-Sector Buyers Face an Additional Accountability Layer

Municipal and other public buyers often need more than a working circuit. Procurement records, budget accountability and service continuity create a demand for exact legal identity and traceable obligations. C-ComTelecom's CNPJ-linked network records make some of that verification easier because the provider can be matched across technical and administrative documents.

Public entities may also depend on connectivity for citizen services, legislative work, education or administration. A failure can have effects beyond ordinary office inconvenience. That raises the importance of restoration procedures, backup access and named escalation contacts. The current municipal record confirms one procurement context but does not disclose the complete continuity design.

Tender specifications can unintentionally overstate what a metric proves. A minimum access speed does not describe latency, availability or route diversity. A fibre requirement does not necessarily establish who owns the fibre. An ASN does not guarantee independent transport. Separating those fields helps a buyer procure the outcome it actually needs.

Transparency can be balanced with security and commercial confidentiality. A public contract need not expose sensitive topology, but the buyer should possess enough documentation to verify legal responsibility, critical dependencies and failover. Summary records can state that evidence was reviewed without publishing route details that would create operational risk.

Future public records may therefore add significant value. Renewals, amendments, penalties, outage notices and new municipal tenders can show whether the relationship expands and how requirements evolve. Each should remain tied to its specific institution and period. One local contract cannot stand in for the provider's entire public-sector performance.

17. The Last Mile Cannot Be Reconstructed from the Route Table

AS265369 is visible where C-ComTelecom exchanges reachability with the wider Internet, but that observation begins after many of the decisions that shape an access service. A route collector cannot see the drop cable into a home, the optical split ratio in a neighbourhood, the power available to a cabinet, or the path a local distribution segment follows between streets. Those elements can dominate the customer experience while remaining invisible to BGP.

The same limitation applies to fault isolation. If a customer loses service while the provider's prefixes remain visible, the cause could sit in customer equipment, an access segment, local power, aggregation, authentication or another internal system. If a prefix disappears, some local services might continue while external reachability changes. Route status is one diagnostic layer, not an end-to-end alarm.

Advertised access speed is also independent of prefix scale. A /22 can support many addressing designs, and an IPv6 /32 can support an enormous hierarchy, but neither states how much transport capacity reaches a neighbourhood. Oversubscription, traffic patterns, backhaul design and upstream congestion affect throughput. No public address record supplies those values.

Physical ownership is another separate question. A route originated by AS265369 remains attributable to C-ComTelecom at the control plane even if portions of the underlying path use leased fibre, shared poles or third-party transport. That arrangement can be entirely normal. Its operational significance depends on contracts, maintenance responsibilities and diversity, none of which can be inferred from origin validation.

Customers therefore need evidence closer to the service boundary. Address-level availability, installation records, circuit diagrams, handoff descriptions, supplier disclosures and measured service reports can connect the public routing identity to actual delivery. For critical sites, route-diversity claims should identify independent failure domains rather than relying on the number of observed AS neighbours.

This distinction protects both accuracy and accountability. It avoids diminishing the real value of AS265369 while preventing the ASN from becoming a proxy for everything the network does. C-ComTelecom's control-plane identity is unusually legible; the last mile remains a physical and contractual system that must be verified through different records.

18. A Layered Monitoring Agenda Preserves Meaning

Legal identity should be monitored through the exact CNPJ and domain records. Changes to representative, registrant or domain status can be recorded without treating them as immediate network events. The registry spelling should remain attached to the identifier so that later searches do not split the company into artificial duplicates.

Routing monitoring can follow AS265369, the registered allocations and the dated announced-prefix set. New origins, withdrawals, changes in aggregation and shifts in collector visibility are measurable events. Interpretation should wait for corroboration. A route change can reflect maintenance, policy, mitigation or an incident, and public tables alone may not distinguish them.

RPKI monitoring should preserve exact pairs rather than a company-wide label. The current AS265369 and 168.205.100.0/22 result is valid. Other prefixes need their own checks. If a status changes, the relevant ROA, maximum length, origin and observation time should be recorded before assigning cause.

Commercial and physical monitoring needs different evidence. Attributable expansion announcements, permits, pole agreements, exchange membership changes and public procurements can illuminate where the network grows. Measurements and incident reports can address performance. None should be substituted for another merely because they concern the same operator.

The value of this layered approach is comparability. A future reader can see whether legal control, routing visibility, security authorization, geographic claims and contracted service moved together or diverged. That is more informative than a single “network size” score built from incompatible indicators.

19. Legibility Is a Starting Point, Not a Delivery Verdict

C-ComTelecom's public footprint is unusually coherent at the identity and routing layers. The official site and privacy notice connect the brand to CNPJ 01.472.702/0001-30. Registro.br attaches the same identifier to AS265369, the domain and IPv4 and IPv6 allocations. RIPEstat shows a visible dual-stack routing surface, and a municipal record anchors one specific service relationship.

Those facts support a stronger conclusion than a directory listing alone. They show an active regional provider with registered resources and observable routes. The valid checked RPKI pair adds a narrow positive security signal. PeeringDB supplies a self-described interconnection posture that can guide further questions.

The same evidence also defines what remains unknown. It does not prove universal coverage across fourteen municipalities, ownership of every fibre route, purchased capacity, measured performance, customer scale, resilience or the contracts behind observed BGP adjacency. Broad conclusions on those fields would confuse administrative and control-plane evidence with service delivery.

The distinction is useful rather than merely cautious. A traceable ASN and CNPJ make accountability possible: customers, public buyers and counterparties know which operator and resources to ask about. The next step is to connect those identifiers to address-level serviceability, physical dependencies, operating procedures and measurable commitments.

AS265369 therefore makes C-ComTelecom visible without making it fully transparent. The public record establishes the legal and routing surface; the delivery boundary still needs contractual, physical and performance evidence. That is the practical monitoring proposition: preserve the strong identifiers, test each operational claim at its own layer, and do not let route visibility stand in for a complete service-quality verdict.

Sources