Summary
- LACNIC records tie VASTELECOM E INFORMATICA LTDA ME and CNPJ 10.171.347/0001-50 to AS264425 and the active IPv4 block 131.221.184.0/22, creating a clear public accountability surface for the network resources.
- RIPEstat observed AS264425 announcing both IPv4 and IPv6 routes on 24 July 2026. That visibility demonstrates an operating routing footprint, but it does not identify paid transit, physical fibre paths, failover design, or customer-level availability.
- VAS Informatica markets residential and corporate fibre plans in Mogi Guacu, Mogi Mirim, and Estiva Gerbi, while its support material describes routers, customer equipment, installation moves, billing, and service requests.
- The unresolved issue is the distance between logical autonomy and physical resilience. Public records do not establish route diversity, pole or duct independence, backup power, field staffing, spare equipment, restoration targets, or whether nominally separate retail locations share a common backhaul dependency.
- The defensible conclusion is neither that VAS lacks resilience nor that its ASN proves it. The evidence supports a regional access operator with visible routing control and leaves the most consequential failure boundaries open.
A network that is easier to see from afar than from the street
The most concrete public view of VAS Informatica begins far above the customer connection. In the global routing system, AS264425 is visible as an origin for Internet address space. In the regional registry, VASTELECOM E INFORMATICA LTDA ME is named as the holder of that autonomous system and of an IPv4 block. On the company's own site, the VAS Informatica name appears beside residential and corporate Internet offers in three municipalities. These pieces fit together well enough to establish an operating regional provider with its own number resources.
Yet they describe different layers. A route collector sees announcements exchanged through routers. A registry states responsibility for identifiers and address space. A retail site describes products, service locations, equipment, and support procedures. None of those views is a diagram of the physical access network. None shows where cables run, which ducts or poles carry them, how traffic leaves the region, where power is backed up, or how many field teams can respond when a line is damaged.
That separation matters because customers experience the network from the bottom up. A household does not receive an autonomous system number; it receives a connection that crosses customer equipment, an access drop, local distribution, aggregation, transport, and one or more external interconnections. A small business may value a provider's local presence and direct support, but its continuity depends on every physical and operational handoff between the premises and the wider Internet. The fact that the provider controls a route announcement is important at one layer and incomplete at all the others.
VAS therefore presents a useful test of what public Internet evidence can and cannot prove about a regional ISP. The records are richer than a bare marketing page. They connect a legal entity, a tax identifier, an ASN, address resources, dual-stack routing observations, a network profile, named service cities, and ordinary customer-support obligations. At the same time, the evidence stops precisely where resilience becomes most tangible: shared civil infrastructure, upstream contracting, route separation, power, spares, and repair labour.
The gap should not be treated as evidence of weakness. Small and regional operators rarely publish engineering diagrams, commercial contracts, restoration playbooks, or inventories of spare equipment. Silence can reflect commercial sensitivity as easily as operational fragility. But the gap also cannot be filled with assumptions. A visible ASN is not a certificate of physical independence. A fibre offer is not proof of universal coverage. A second observed routing neighbour is not automatically a diverse upstream. The honest account begins by preserving those distinctions.
The legal and routing identity is unusually clear
The strongest identity bridge is supplied by LACNIC's public RDAP data. The autonomous-system record assigns AS264425 to an organization named VASTELECOM E INFORMATICA LTDA ME. Its registrant handle corresponds to CNPJ 10.171.347/0001-50. The separate RDAP record for 131.221.184.0/22 ties that active IPv4 resource to the same CNPJ and presents the same Brazilian operational contact across technical and abuse responsibilities.
This alignment matters because regional telecom names can be ambiguous. A trading name may differ from a legal name; a reseller may use another operator's infrastructure; an old corporate suffix may survive on one page after a business changes form. Here, the registry and company site give the VASTELECOM legal identity and VAS Informatica brand enough common ground to discuss the network without collapsing unrelated businesses into one subject.
PeeringDB adds a consistent self-description, naming the network VAS Informatica, listing VASTELECOM as an alias, reproducing the full legal name, and associating ASN 264425 with the website and the IRR set AS-VASTELECOM.
Number-resource accountability has practical value. Routing problems, abuse reports, configuration questions, and interconnection discussions require stable identifiers and reachable contacts. A provider whose name, ASN, address space, and public presence agree gives other operators a clearer starting point. The records also make longitudinal observation possible: route visibility can be examined over time without relying solely on the provider's own description of its service.
Still, registration should not be mistaken for exhaustive control. RDAP identifies the listed holder of resources; it does not prove who operates every router, who supplies transport, where addresses are deployed, or which physical assets carry the traffic. The common contact across administrative, technical, and abuse roles may reflect direct responsibility, a compact organization, or a chosen contact arrangement. It does not reveal staffing depth or round-the-clock operational coverage.
What the registry closes is the identity question at the resource layer. VASTELECOM E INFORMATICA LTDA ME is not merely a similar name found beside a broadband offer. It is the named holder behind AS264425 and 131.221.184.0/22. That gives the analysis a firm subject. It does not give the subject a fully visible network.
Current announcements show real routing activity
RIPEstat's observations add a second kind of evidence: the resources are not only registered but visible in routing. On 24 July 2026, its routing-status data reported AS264425 as visible, with observed RIPE RIS peers seeing both IPv4 and IPv6 announcements. The response counted seven announced IPv4 prefixes covering 1,024 addresses and seventeen IPv6 prefixes expressed as 65,536 /48 equivalents.
The announced-prefix feed provides more detail. It showed 131.221.184.0/22 as well as component /23 and /24 routes during the 10-24 July observation window. For IPv6, it showed 2804:1e60::/32 and more-specific /36 announcements. The first-seen value for the IPv4 aggregate traces its observed origin to December 2014. Taken together, these observations support a durable and currently visible dual-stack routing footprint.
That is meaningful operating evidence. Announcing an IPv4 aggregate and more-specific routes requires an organization, or a party acting for it, to maintain routing arrangements through which those announcements reach the wider Internet. IPv6 visibility broadens the footprint beyond a legacy IPv4-only presence. More-specific routes may be used for traffic engineering, policy, operational organization, or other reasons, although the public feed does not disclose which reason applies here.
Visibility also creates an externally testable surface. A route can be seen or withdrawn; its origin can be compared with the registered holder; changes can be observed from multiple collectors. This does not make the routing system transparent, but it is more substantive than a static claim that a company "has a network." AS264425 participates in the public routing environment in a way that can be independently observed.
The limits are equally important. A collector's view does not identify customer sessions, physical circuits, router locations, contractual rights, or the people responsible for a change. It cannot show whether the IPv4 aggregate and its more-specifics travel over physically separated paths. It cannot establish that IPv6 is offered to every retail customer merely because IPv6 routes are visible. It cannot distinguish a planned maintenance event from a fault, nor can it measure the customer impact of a routing change without other evidence.
Even the long observation history should be kept in proportion. A first-seen date in 2014 indicates that the aggregate has been observed with this origin over a long period. It does not prove uninterrupted service throughout that period, unchanged corporate control, or a particular level of performance. The durable fact is the public routing identity. Service continuity at the premises remains a different question.
An ASN gives policy control, not physical independence
An autonomous system is a unit of routing policy. It allows an operator to originate address space and exchange reachability with other networks under its own ASN. For a regional ISP, this can be strategically important. The operator is not invisible behind a larger provider's public identity; it can be recognized in routing, maintain its own policy, and present its prefixes to neighbouring networks.
That autonomy can improve accountability and create options. A provider with its own ASN and address resources may be able to change external connectivity arrangements without renumbering every service behind another organization's addresses. It can use routing policy to influence how traffic enters or leaves, subject to the contracts and physical connections available. It can maintain IPv4 and IPv6 announcements under one public identity. None of these possibilities should be dismissed.
But logical choice only becomes operational choice when the underlying connections exist. If two routing adjacencies ultimately traverse one physical cable, one pole line, one duct, one exchange point, or one upstream transport segment, the routing table may look more diverse than the failure domain really is. If a provider can announce through more than one neighbour but reaches those neighbours through a shared local handoff, a single physical incident may remove both paths. Public route observations alone cannot resolve that geometry.
The reverse can also be true. A compact routing view may hide useful physical safeguards. An operator could buy protected transport, use physically separated access paths, keep spare optics, or maintain rapid local repair arrangements without publishing any of it. The absence of evidence in a route collector is not evidence that those measures are absent. It means only that the routing layer cannot answer the physical question.
This distinction is especially important when describing resilience. Resilience is not a synonym for "has an ASN," "announces IPv6," or "has multiple observed neighbours." It is the ability of a service to continue, degrade gracefully, or recover when components fail. That outcome depends on route policy, physical separation, equipment design, power, monitoring, staffing, spares, vendor access, and customer communication. An ASN touches only part of that system.
For VAS Informatica, the public record supports the statement that the network has its own visible routing identity. It does not support the stronger statement that the access service is physically independent of any particular supplier or route. The difference is not semantic caution for its own sake. It is the difference between what remote observers can verify and what customers actually rely on.
Routing neighbours are observations, not contracts
RIPEstat's neighbour view records autonomous systems seen adjacent to AS264425 in collected routing paths. Such data can help show that a network is not isolated and can reveal how its routes appear to travel through the Internet. It is useful for forming questions about interconnection and for watching how route visibility changes.
The data does not disclose the commercial relationship behind an adjacency. A neighbouring ASN might be a paid transit provider, a peer, a route-server entity, a customer, an intermediary visible because of route propagation, or part of an arrangement that has changed since the observation. Without contract-quality evidence, it would be wrong to label any observed neighbour as VAS Informatica's upstream, backup provider, or resilient alternate.
That boundary matters because the word "upstream" carries economic and operational implications. Paid transit affects cost, bargaining power, capacity planning, and failure response. Peering may reduce some traffic costs or shorten some paths without replacing global reachability. A backup relationship may exist commercially but fail to provide protection if it shares facilities with the primary path. A routing collector can show adjacency patterns; it cannot show prices, committed capacity, service guarantees, maintenance responsibilities, or civil-route separation.
The PeeringDB profile adds a self-reported interconnection context but does not close these questions. It classifies the network as a regional Cable/DSL/ISP, identifies IPv4 and IPv6 unicast support, and lists the IRR set. It also reports a heavy-inbound traffic ratio and a 5-10 Gbps traffic band. Those fields were presented as operator-supplied and last shown as updated in 2022. They are useful as a historical statement of how the network described itself, not as an independent measurement of current traffic or capacity.
In a regional access network, a heavy-inbound pattern would be plausible because residential and small-business users often download more than they upload. But plausibility is not proof, and an old self-classification cannot establish today's mix. New content caches, business customers, local interconnection, plan changes, or network expansion could alter traffic. The safe use of the profile is to note the operator's stated network type and interconnection identity while preserving the age and self-reported nature of the capacity fields.
The questions left open are the ones that determine exposure: How many commercially independent ways can traffic leave the service area? Are those handoffs physically separated? Do they share power, buildings, poles, or transport vendors? How quickly can routing move when one path fails, and which destinations remain reachable? The nine public sources do not answer them. They make the questions more precise.
The retail offer places the network in three municipalities
VAS Informatica's own website supplies the customer-facing geography that routing records lack. Its fibre-plan page names Mogi Guacu, Mogi Mirim, and Estiva Gerbi as served cities. It presents residential packages at 200, 400, 600, and 800 Mbps and states that upload rates are half the advertised download rates. The broader site also markets corporate Internet access.
These offers show that the business is not merely holding number resources or presenting itself as an IT consultancy. It is selling access in a defined regional market and addressing both households and companies. The city list gives the article a real local context: neighbouring municipalities in the interior of Sao Paulo state, rather than an abstract Brazilian footprint inferred from a country code.
The plans should be read as offers, not measurements. An advertised speed describes a product tier under the provider's stated terms. It does not prove that the rate is available at every address, delivered at every hour, or sustained under every network condition. The site itself is the authority for what VAS chooses to market; it is not an independent audit of throughput, latency, contention, or installation reach.
The phrase "100 percent fibre" requires the same discipline. It can describe the intended access medium or the product as marketed. It does not disclose the complete physical path, the ownership of each segment, or whether every location in the named municipalities can be connected. The site also refers to more than a decade of wireless-service experience, which supplies business history but not a map of current wireless assets or a basis for claiming a particular mixed topology.
Regional geography introduces a useful resilience question. Three named municipalities can represent genuine dispersion of customers and operations, yet they can also share transport corridors, suppliers, maintenance resources, or upstream handoffs. Municipal boundaries do not automatically create network diversity. Two customers in different cities may still depend on one aggregation point or transport segment; two customers in the same city may have quite different physical paths. Only detailed engineering evidence could establish which arrangement applies.
The retail page therefore tells us where the service is presented and how it is packaged. It does not tell us how the physical network reaches each address. That is not a flaw in a sales page; it is simply the boundary between commercial information and infrastructure proof. For customers assessing continuity, the missing detail is where the marketed connection meets common failure domains.
The support pages reveal the work hidden behind the line
VAS Informatica's FAQ is valuable because it describes ordinary operating obligations that routing data cannot see. It discusses customer-premises equipment, routers, testing a connection directly on a device, requests for support, plan changes, billing procedures, and charged installation moves. These are mundane details, but they locate the provider in the daily work of access delivery.
A broadband service does not end when a route is announced. It must be installed, powered, configured, billed, moved, diagnosed, and repaired. Some faults occur in the provider network; others arise in home Wi-Fi, a router, cabling inside the premises, or a customer's device. Guidance to test directly helps separate the access link from the local wireless environment. Procedures for moving an installation show that location changes require physical work rather than a simple account update.
This operational surface matters economically. Local support can be an advantage for a regional ISP because proximity may improve communication and practical knowledge of streets, buildings, and recurring issues. It is also a cost centre that scales differently from bandwidth. Faster plan tiers can be marketed digitally, but a damaged drop, a failed router, or a relocation request may require equipment and labour at a specific place.
The FAQ does not reveal how that labour is organized. It does not state the number of technicians, whether crews are employees or contractors, where spares are stored, which hours are covered, or how work is prioritized during a wider incident. It does not provide restoration targets or prove that any target is met. The presence of support procedures establishes an operating obligation, not a measured performance record.
Customer equipment creates another boundary. A provider may supply or manage a device without every symptom being caused by the access network. Conversely, a working router light does not establish that upstream connectivity is healthy. Effective diagnosis requires visibility across the premises, access segment, aggregation, and external routes. Public support text can show the expected first steps while leaving the monitoring and escalation system unseen.
The repair question is therefore inseparable from the routing question. AS264425 can remain visible from some observers while a local group of customers loses access because of a damaged distribution segment. It can disappear from collectors while some local services remain reachable. Public routing is a broad signal; support operations handle the granular reality. VAS's site confirms that this granular work exists, but not how much capacity stands behind it.
Fibre is a medium, not a resilience guarantee
Fibre access can offer high capacity and low signal loss over distance, but the material itself does not guarantee continuity. A fibre strand can be cut. A passive connector can be contaminated or damaged. Active equipment at either end can fail or lose power. A route can be physically intact while the external interconnection beyond it is unavailable.
The "100 percent fibre" marketing claim should therefore be understood as a statement about the access product, not a complete resilience description. To assess resilience, a customer would need to know whether important links have physically separate alternatives, whether alternative paths converge on common structures, whether equipment and power are protected, and whether the provider can detect and repair failures. None of those conditions follows automatically from the word fibre.
Ownership is also distinct from use. An ISP can deliver a fibre service over plant it owns, leases, shares, or accesses through wholesale arrangements. Different segments can have different owners and maintenance responsibilities. The available evidence does not establish which model VAS uses, so it would be improper to describe poles, ducts, street cabinets, backbone links, or fibre routes as company assets.
This distinction affects incident response. When a damaged segment is maintained by another party, restoration may depend on notification, access permission, contractor availability, and coordination. When the provider owns and maintains a segment, it still depends on staff, vehicles, spares, safety procedures, and civil access. Neither model is inherently superior in every circumstance; the relevant point is that responsibility can cross organizational boundaries invisible to a retail customer.
The three-city service description makes shared dependencies particularly important. Regional networks often grow along practical corridors where rights of way, existing infrastructure, and customer demand make expansion possible. That may produce efficient coverage, but efficiency and diversity are not the same thing. Without a physical map, one cannot tell whether municipal links are separated, where they converge, or what event could affect several areas at once.
The right conclusion is deliberately narrow. VAS markets fibre service in three municipalities. The evidence does not show universal fibre availability, plant ownership, route mileage, or topology. It also does not show that the network lacks any of those things. A customer-facing resilience assessment would need the physical and contractual layers that the public record leaves out.
The economics of a regional operator sit at the handoffs
Regional ISPs occupy a demanding position between global Internet systems and street-level service. They buy equipment, obtain number resources, manage routing, arrange external connectivity, install customer links, answer support requests, and collect local-currency revenue. The public evidence around VAS touches several of those functions without revealing their cost structure.
Owning an ASN can reduce dependence on another provider's numbering and public identity, but it does not eliminate dependence on transport and interconnection. IPv4 resources are finite and operationally useful, yet a registered /22 says nothing about how addresses are assigned or how many customers share them. IPv6 announcements expand the available address architecture, but they do not show retail adoption. Each visible resource creates options while leaving implementation costs unknown.
Retail plan tiers also create obligations beyond headline speed. Higher download rates may require access equipment, aggregation, and external capacity to be planned for patterns of simultaneous use. The website's stated upload ratio defines part of the commercial offer, but the evidence provides no measurements of utilization or congestion. It would be speculative to infer either excess capacity or strain from the plan table alone.
Repair capability is another economic choice. Keeping more staff, spare equipment, diverse transport, and backup power can improve readiness but raises recurring cost. Relying on shared suppliers or on-call contractors can be efficient but may add coordination dependencies. A small provider has to choose where resilience spending produces the most customer value. The public sources do not disclose VAS's choices, so this article cannot score them.
What can be said is that the important costs gather at handoffs. Customer premises meet the access network. Local distribution meets aggregation. The regional footprint meets external connectivity. A support request meets a field or technical team. A provider-controlled resource meets infrastructure that may be supplied by others. Failures and delays often occur not only within components but between the organizations responsible for them.
That is why a simple scale narrative would miss the point. The evidence does not supply customer count, revenue, market share, or route mileage, and none should be inferred. Resilience depends less on a guessed measure of company size than on whether critical handoffs are understood, monitored, contractually supported, and repairable. The ASN makes one handoff visible. The website makes several customer obligations visible. The rest remain outside public view.
IPv4 and IPv6 visibility answer different questions
AS264425's dual-stack presence is significant because IPv4 and IPv6 are not interchangeable evidence. The IPv4 record connects the legal entity to 131.221.184.0/22, and RIPEstat sees the aggregate and component routes. That gives the provider a visible block of scarce IPv4 space. The IPv6 observations show 2804:1e60::/32 and more-specific /36 announcements, indicating that the routing footprint is not confined to IPv4.
The route counts should not be converted into customer or capacity estimates. Seven IPv4 prefixes do not mean seven sites, seven upstreams, or seven independent paths. Seventeen observed IPv6 prefixes do not reveal seventeen access regions or customer deployments. Prefixes are units of routing policy and address organization. Their physical and commercial meanings require evidence that the feeds do not provide.
The RIPEstat routing-status presentation of 65,536 /48 equivalents describes the size of IPv6 address space in a normalized form, not traffic capacity. IPv6 numbers are intentionally vast, and an address-space measure cannot be read as throughput, utilization, or subscriber reach. Similarly, the 1,024 IPv4 addresses covered by the observed announcements do not establish how many are assigned, translated, reserved, or used for infrastructure.
More-specific announcements can be operationally interesting. They may allow different policies for parts of an allocation or reflect how a network organizes reachability. But they can also appear for reasons unrelated to physical diversity. Seeing an aggregate and components does not prove that the components leave through separate routers, facilities, or suppliers. A routing design can contain logical granularity while resting on a shared physical base.
For customers, dual-stack routing can matter only when it reaches the service they use. Public visibility confirms that the ASN participates in both address families from the collectors' perspective. It does not show whether each residential or corporate plan receives IPv6, how customer equipment is configured, or whether applications experience equivalent paths. Those would require service-specific evidence.
The responsible finding is therefore technical but modest: VAS has a currently observed dual-stack routing footprint associated with its registered identity. That footprint gives operators and researchers more to observe than a single IPv4 route. It does not convert address abundance into proven capacity or routing granularity into proven redundancy.
What a failure could look like cannot be inferred from route feeds
Infrastructure analysis often becomes most useful when it asks how failure propagates. In VAS's case, several categories are conceivable in general: a local access cut, loss of power at active equipment, failure of customer equipment, an external connectivity interruption, congestion, or a shortage of repair resources during a wider event. The public evidence does not establish that any of these has happened to VAS, how often it might happen, or how long recovery would take.
That boundary should remain explicit. There is no supported outage history in the nine sources. There are no restoration-time measurements, service-level results, or incident reports. A hypothetical failure mechanism can clarify what evidence is missing, but it cannot be written as an event in the company's history.
Different failures would also appear differently from outside. A cut affecting one neighbourhood might leave AS264425 fully visible in global routing. A problem at a major aggregation or external handoff could affect many customers and alter route visibility. A customer router issue could leave the provider network untouched. A route withdrawal could be planned, erroneous, or protective; the collector alone would not establish the cause.
This mismatch explains why global visibility is an incomplete customer metric. Route collectors observe control-plane information from selected vantage points. Customers experience a data path that includes local and physical components outside that view. Both are legitimate perspectives, but they answer different questions.
The support material suggests the provider expects to distinguish at least some premises-level problems through device testing and service requests. That is a normal part of access operations. What remains unknown is how observations are escalated when the fault lies beyond the premises, how shared incidents are recognized, and what resources are available for repair. No staffing level, spare inventory, or response time can be inferred.
A more transparent resilience account would connect the layers without exposing sensitive diagrams. It could describe categories of external connectivity, whether critical paths are physically separated, the broad approach to backup power, how customers are notified, and which restoration targets apply to business services. VAS is not uniquely deficient for not publishing these details; many providers do not. Their absence simply means that public routing evidence cannot carry the conclusion alone.
Corporate customers need a different answer from residential buyers
The company website addresses both residential and corporate access, but the consequences of interruption can differ sharply. A household may lose entertainment, communication, remote work, and access to online services. A business can also lose payment processing, cloud applications, voice services, remote administration, and customer contact. The same physical line can carry very different economic dependency.
The public offer does not provide enough detail to characterize corporate service terms. It does not establish dedicated capacity, guaranteed restoration, route diversity, or any particular service-level commitment. It would therefore be wrong to treat the presence of a corporate offer as proof of enterprise-grade resilience.
For a business buyer, the most useful questions sit below the product name. Is the connection delivered over a path distinct from another circuit at the premises? If a second provider is used, do both providers share the same poles, ducts, building entry, or upstream transport? Does the supplied router support a practical failover design? Who is contacted outside ordinary hours? Which failures are covered by a commitment, and how is performance measured?
None of these questions assumes that VAS performs poorly. They are procurement questions prompted by the gap between visible network autonomy and unknown physical dependencies. An ASN can make a provider a more legible counterparty because its routes and resources are publicly identifiable. It cannot replace due diligence on the service actually delivered to a site.
The regional character of the business may be valuable in both markets. Local support and a known service area can improve communication and practical response. Yet the evidence does not quantify that advantage. The article can identify local operating obligations and visible routing identity without converting them into a performance rating.
Public accountability is strongest where the identifiers agree
The most reliable part of the VAS story is the agreement among public identifiers. The legal name appears in LACNIC records. The CNPJ binds the organization across the ASN and IPv4 resource. PeeringDB connects the VAS Informatica name, VASTELECOM alias, legal entity, ASN, website, and IRR set. The website presents the same business to customers.
This agreement reduces one common risk in infrastructure research: attributing routes or services to the wrong similarly named organization. It also gives affected parties several ways to orient themselves. A customer sees the brand and legal identity; a network operator sees the ASN and prefixes; a registry query supplies the listed holder and contacts.
Accountability, however, is not the same as disclosure. The records establish who is named, not every party on whom service depends. A transport provider, infrastructure owner, contractor, equipment vendor, or power utility could be operationally important without appearing in the route origin. The website's support procedures identify VAS as the customer's counterparty while leaving those dependencies behind the service boundary.
That boundary is commercially normal. Providers do not generally publish every contract or asset relationship. The analytical task is not to demand exposure of sensitive details but to avoid treating the visible identifiers as a complete operating model. Where the identifiers agree, claims can be firm. Where physical or commercial arrangements are absent, conclusions should remain open.
This creates a balanced view of autonomy. VAS is autonomous enough to be visible under AS264425 and to originate its registered resources. It is accountable enough for the legal holder and customer brand to be linked through public data. Whether it is physically independent, operationally diverse, or rapidly repairable is not demonstrated by those facts.
The distinction is useful beyond one company. Internet infrastructure often looks decentralized at the routing layer while relying on concentrated local facilities, rights of way, power, transport, or labour. Public ASN data reveals who speaks in routing; it does not reveal every shared dependency beneath that speech. VAS offers a clear regional example because the routing identity is strong and the physical picture remains sparse.
What better evidence would change the assessment
Several kinds of evidence could narrow the uncertainty without requiring publication of exact network diagrams. First, a clear description of external-connectivity categories could distinguish paid transit, peering, and other arrangements while avoiding confidential commercial terms. Evidence of physically separate handoffs would matter more than the number of observed routing neighbours.
Second, high-level access architecture could explain whether the three municipalities are connected through shared or separated aggregation paths. The relevant question is not route mileage or a marketing count of fibre; it is which failures can affect multiple areas at once. A provider could answer that at a category level without identifying precise equipment locations.
Third, operational evidence could describe monitoring, backup power, spare-equipment strategy, and field-response coverage. Again, no staffing number should be guessed from the FAQ. Broad, current statements from the operator or independent service records would be needed to assess repair capacity and restoration expectations.
Fourth, customer-facing terms could distinguish best-effort residential products from any corporate options that carry different support or continuity commitments. The current site establishes residential and corporate marketing but not independently verified performance. Published service terms and measured results would be necessary before making claims about compliance.
Fifth, current interconnection information could update the older PeeringDB capacity and traffic fields. The existing profile is useful for identity and self-described scope, but its 2022 update context makes the 5-10 Gbps band unsuitable as a current measured fact. Fresh operator statements would still be self-reported; independent traffic measurement would require a different form of evidence.
An assessment should improve when new evidence arrives, not by stretching old evidence. Until then, the most useful contribution is a clean map of certainty and uncertainty. VAS's resource identity, dual-stack visibility, regional offer, and support surface are visible. Plant ownership, topology, redundancy, customer count, measured capacity, performance, outage history, and repair time are not.
The practical meaning of visible autonomy
What, then, does AS264425 give VAS Informatica? It gives the network a stable public identity in routing. It ties observed announcements to a registered organization. It supports both IPv4 and IPv6 visibility. It gives other networks a recognizable origin with which to exchange reachability and against which to evaluate registry information.
For a regional provider, those are substantial capabilities. They can make the business less opaque than a reseller that appears only behind another operator's addresses. They can support policy choices and make changes observable. They create a basis for technical accountability when routes do not match expectations.
But the practical value stops short of a resilience verdict. The ASN does not reveal whether the access drop to a customer is protected, whether municipal transport shares a corridor, whether external handoffs have independent power, or whether repair crews have the equipment needed for a particular fault. It cannot show whether two nominal paths converge below the level visible to BGP.
The most accurate description is therefore visible autonomy with unverified dependencies. "Visible" matters because the routing activity is current and tied to the legal entity. "Autonomy" matters because the provider originates resources under its own ASN. "Unverified" matters because absence from public sources prevents a finding either way. "Dependencies" matters because every access provider, large or small, relies on physical and organizational systems beyond an ASN.
This framing avoids two opposite errors. One would dismiss the provider as merely local or small and overlook the real technical footprint. The other would see an ASN, dual-stack announcements, and several route neighbours and declare the network resilient. The evidence supports neither simplification.
VAS's public profile is strongest when read layer by layer. At the registry layer, identity is clear. At the routing layer, current IPv4 and IPv6 activity is clear. At the retail layer, named municipalities, plan tiers, and support obligations are clear as first-party statements. At the physical and repair layers, the decisive facts remain private or unreported.
A regional network should be judged by the boundaries it can explain
The central issue is not whether VAS owns enough infrastructure or has enough neighbours. Those quantities are not available, and inventing them would obscure the more important question. The issue is whether a customer or counterparty can understand which layer the provider controls, which layer it buys or shares, and what happens when responsibility crosses that boundary.
Public number resources show control and accountability at one boundary. The company controls, or is publicly responsible for, an ASN and registered address space. Routing observations show those resources reaching the wider Internet. The retail and support pages show that VAS assumes customer-facing obligations around access, equipment, billing, plan changes, and installation moves.
The missing boundaries are physical and organizational. Who maintains each critical segment? Which paths share structures or transport? What protection exists against local power loss? How are widespread faults distinguished from premises problems? What spares and labour are available? Which restoration expectations apply? These questions remain unanswered by the current evidence.
A small regional operator does not need to mimic a national carrier's public reporting to answer them usefully. Even a concise resilience statement could separate routing diversity from physical diversity, describe the broad support model, and tell business customers how to procure genuinely independent access. Such disclosure would make the ASN more meaningful to readers because it would connect logical autonomy to the service below.
Until such evidence is available, the responsible conclusion is restrained. VASTELECOM E INFORMATICA LTDA ME is the registered network-resource holder behind AS264425 and 131.221.184.0/22. AS264425 has a currently visible dual-stack routing footprint. VAS Informatica markets residential and corporate fibre access in Mogi Guacu, Mogi Mirim, and Estiva Gerbi and publishes ordinary customer-support procedures.
Those facts establish an operating regional access provider with a legible Internet identity. They do not establish ownership of the physical plant, a particular topology, route redundancy, universal availability, a customer count, current measured capacity, performance, outage history, or repair time. The network is visible from the Internet. Whether its most important dependencies are separated, protected, and rapidly repairable remains beyond what the public evidence can show.