Summary

  • LACNIC records bind AS265848, 45.224.104.0/22, and 2803:4a20::/32 to FIBERMAX S.A.
  • RIPEstat observed both aggregate resources announced throughout the reviewed 14-28 July 2026 interval.
  • The tested IPv4 and IPv6 resources had valid RPKI origin authorization for AS265848.
  • An official 2017 record supports Fibermax's Internet-access registration; a later cancellation concerned a separate subscription-broadcasting registration.
  • None of those records proves Fibermax's physical access footprint, usable capacity, route diversity, uptime, or recovery performance.

1. The Public Network Identity Is More Precise Than the Company Description

Fibermax presents itself to customers as a fibre-to-the-home provider in the southern part of the Buenos Aires metropolitan area. Its website offers several retail speed tiers and makes availability subject to technical and geographic conditions. That is a recognisable commercial proposition, but it is not the most precise starting point for infrastructure analysis. Marketing pages describe what a customer may be able to buy. They rarely disclose the full chain of systems, organisations, physical links, permissions, and external dependencies that must work before the advertised service can reach a home.

The more reliable opening is the network identity that can be matched across independent records. LACNIC identifies an autonomous system, an IPv4 allocation, and an IPv6 allocation under the exact organization name FIBERMAX S.A. Public routing data then shows those resources in use as announced prefixes. RPKI data adds a separate statement about which autonomous system is authorised to originate them. An Argentine regulatory record establishes permission to provide Internet access under the exact legal identity and tax identifier.

Those layers answer different questions. The corporate and regulatory records identify the legal subject. The address registry records identify assigned number resources. BGP observations show what selected collectors could see at a particular time. RPKI records show route-origin authorization. None is a substitute for the others, and none by itself describes the physical last mile.

Keeping those questions separate produces a more useful profile. It avoids reducing Fibermax to a generic company description, but it also avoids inflating a visible ASN into proof of a wholly owned, resilient network. The public evidence supports a clear operating identity. The delivery boundary remains only partly visible.

2. Exact Entity Matching Prevents a Familiar Name From Becoming a False Match

Company names are poor identifiers when used alone. A short name can refer to different legal entities, an old record, a brand, or an organization in another country.

Fibermax is especially vulnerable to that problem because the name is descriptive and could plausibly be used by unrelated connectivity businesses. The relevant public company record is the Argentine entity FIBERMAX S.A., not every result containing the word Fibermax.

The authoritative match combines several fields rather than relying on spelling. The public company profile uses the exact legal name and an Argentina-specific canonical identity. The production company record is published and classified as a company. LACNIC's registrant handle uses the same legal name. ENACOM Resolution 2115/2017 identifies FIBERMAX SOCIEDAD ANÓNIMA and CUIT 30-71534748-9. The company website describes a consumer Internet service in the same national setting.

That convergence matters because network-resource evidence can otherwise be attached to the wrong entity. An ASN is not a brand keyword. It belongs in a chain of evidence that connects the number-resource holder to the exact directory company and the legal record. Here, AS265848, the IPv4 block, and the IPv6 block all point to registrant handle AR-FISA31-LACNIC, whose organisation name is FIBERMAX S.A.

An archived same-name company record without the Argentina-specific canonical suffix does not change that conclusion. Archived or historical records can explain why duplicate-looking names appear, but they should not be used as the live publication target. The exact published entity is the stable anchor for this analysis, its directory link, and future research updates.

3. The Internet-Access Registration Is Permission, Not a Map of the Plant

ENACOM Resolution 2115/2017 is valuable because it identifies the legal company and the service category with unusual precision. The record says FIBERMAX SOCIEDAD ANÓNIMA, CUIT 30-71534748-9, sought and received registration for value-added Internet access services. It describes a broad scope that can include fixed or mobile, wired or wireless, national or international service.

That language establishes a regulatory permission and a registration fact. It does not identify every asset used to deliver the service. A licence does not say whether a particular feeder route is owned, leased, shared, or purchased from another operator. It does not identify central-office equipment, ducts, poles, towers, wholesale access, transit contracts, power arrangements, or customer-premises devices. It also does not reveal which authorised service forms are actually offered in every locality.

The distinction is important because regulatory scope is often wider than operational deployment. A company may be permitted to offer several service types while choosing to operate a narrower network. It may also combine its own equipment with third-party facilities. Public permission should therefore be treated as a boundary around lawful activity, not as evidence that every possible infrastructure component exists or is controlled by the licensee.

For Fibermax, the 2017 record strengthens the legal identity and confirms an Internet-access role. It supports describing the company as a connectivity operator rather than a company that merely happens to hold address space. But it cannot support claims about fibre ownership, service quality, geographic reach, redundancy, or resilience. Those questions require evidence about the running network and the physical delivery chain.

4. A Later Broadcasting Cancellation Must Stay Within Its Own Service Boundary

A 2026 ENACOM record introduces a fact that could easily be overstated. It says the authority cancelled a subscription-broadcasting registration previously granted to FIBERMAX S.A. under Resolution 1125/2019, effective 27 March 2025.

The cancellation concerns that named broadcasting registration.

It would be incorrect to turn that service-specific action into a claim that Fibermax lost all telecommunications authority or that its 2017 Internet-access registration was cancelled. The public record does not say that. Different registrations can cover different services, and an action affecting one does not automatically extinguish another. The narrower interpretation is both more accurate and more useful: the company's permissions have changed over time, and the public record distinguishes between subscription broadcasting and Internet access.

The underlying 2019 attachment was not suitable as an independent basis for further claims in this review because the available download did not provide a complete, reliable document. The later official resolution is sufficient to establish the limited cancellation fact. Anything beyond that would require another complete authoritative record.

This example shows why infrastructure profiles need service-level precision. Regulatory histories can contain grants, modifications, surrenders, cancellations, and migrations. A company can remain visible in routing while a separate service registration changes. Running code and legal permission are related but not identical layers. Public reporting should state which layer changed and resist turning a partial record into a conclusion about the entire operating business.

5. AS265848 Is a Routing Identity, Not a Measure of Scale

An autonomous system number identifies a network that presents a distinct routing policy to the Internet. LACNIC records AS265848 as active and associates it with FIBERMAX S.A. The registration date and last-change date in the reviewed response are both 19 October 2017. That gives the company a stable public routing handle, but the number itself says nothing about subscriber count, revenue, staff, or geographic scale.

An ASN can be used by a large national carrier, a regional operator, an enterprise, a university, a hosting provider, or a small access network. The number does not specify how much traffic crosses it, how many routers participate, how many upstreams exist, or how many physical sites are involved. Those properties must be observed or documented separately.

What AS265848 does provide is a key for joining several public evidence layers. LACNIC connects the ASN to the registrant. RIPEstat can be queried for prefixes originated by the ASN and for collector-visible paths. RPKI validation can test whether the origin is authorised for a particular prefix. Changes over time can then be compared against a frozen baseline.

That is the practical value of the routing identity. It makes Fibermax's Internet-facing resource footprint more observable than a company name alone would allow. It creates a reference point for questions about announcements, authorization, and external adjacency. It does not make the rest of the operating model transparent. The access network, customer dependencies, power systems, and recovery procedures remain outside the meaning of the ASN.

6. The IPv4 Allocation Defines a Registered Resource Boundary

LACNIC's IPv4 RDAP response identifies 45.224.104.0/22 as an active allocation registered to FIBERMAX S.A. The range begins at 45.224.104.0 and ends at 45.224.107.255.

A /22 contains 1,024 IPv4 addresses, although registry allocation does not mean every address is assigned, active, customer-facing, or reachable at any given moment.

The allocation is important because it defines a bounded address resource linked to the exact company. It can be compared with routing data, RPKI records, reverse DNS, abuse contacts, and future operational observations. That makes the resource useful for accountability and measurement. It does not transform the address block into a physical asset or a map of Fibermax's service area.

The public BGP state included both the /22 aggregate and four component /24 routes. More-specific announcements can be used for traffic engineering, policy, mitigation, or other operational reasons. Their presence does not reveal the business purpose behind them. Nor does a /24 correspond automatically to a city, a fibre ring, a customer segment, or an independent failure domain.

IPv4 scarcity can make address holdings commercially relevant, but the public record still needs disciplined language. The allocation indicates registered control and responsibility within the number-resource system. It does not establish a market valuation, a transfer right beyond registry policy, or actual utilisation. The strongest supported statement is that Fibermax has a clearly registered IPv4 boundary that is visible in routing and covered by a valid origin authorization.

7. The IPv6 /32 Extends the Identity Beyond Legacy Address Space

The IPv6 record adds a second resource layer. LACNIC identifies 2803:4a20::/32 as active and registered to FIBERMAX S.A., covering the range from 2803:4a20:: through 2803:4a20:ffff:ffff:ffff:ffff:ffff:ffff. The reviewed record dates its registration and last change to 19 October 2017, the same day as the ASN and IPv4 records.

An IPv6 /32 is a substantial allocation intended to support structured addressing. It gives an operator room to assign many customer and infrastructure subnets without reproducing IPv4's scarcity model. Yet allocation size is not a measure of deployment. The public record does not show how Fibermax subdivides the block, how many customers receive IPv6, whether prefix delegation is offered, or what equipment supports it.

In this case, the routing evidence is stronger than a registry-only inference because RIPEstat observed the /32 announced during the reviewed interval. That supports saying the IPv6 aggregate was visible in public routing, not merely reserved in a registry. It still does not prove universal reachability, customer adoption, traffic volume, or parity with the IPv4 service.

The distinction between allocated, authorised, announced, and usable remains central. LACNIC establishes allocation. RPKI establishes origin authorization. BGP collectors establish observed announcement. Customer usability would require tests from relevant networks and service-level evidence. Each layer moves the analysis forward, but no single layer completes the operational picture.

8. Dual-Stack Announcements Move the Evidence Into Running Code

RIPEstat's announced-prefixes response for AS265848 covers the interval from 14 July to 28 July 2026. It reports 45.224.104.0/22 and 2803:4a20::/32 announced throughout that period.

This matters because it connects the registered resources to observed routing behaviour.

A registry record can remain unchanged even when a resource is not visible on the Internet. An announcement shows that public collectors observed the prefix with the ASN as origin during the specified interval. For Fibermax, the paired IPv4 and IPv6 aggregates support a bounded description of dual-stack routing presence. They do not prove that every customer product is dual-stack or that both protocols follow identical physical paths.

The timeline is also important. Route visibility is not a timeless company attribute. Prefixes can be withdrawn, split into more-specifics, originated from another ASN under an authorised change, or become visible differently across collectors. The correct statement is tied to the reviewed dates. Future reporting can compare later observations without pretending that a two-week window proves continuous operation before or after it.

Running-code evidence deserves priority over promotional claims when the question is what the Internet could see. At the same time, public collectors are instruments with limited vantage points. Their agreement can strengthen confidence that an announcement was widely visible, but they do not represent every network. A routing observation is therefore stronger than a marketing statement and narrower than a universal reachability test.

9. The BGP Snapshot Reveals More-Specifics Without Explaining Their Purpose

The RIPEstat BGP-state response is timestamped 28 July 2026 at 13:59:52. It contains observations for the IPv4 /22 aggregate, four component /24s, and the IPv6 /32. The aggregate records establish the principal public resources, while the more-specific IPv4 routes show additional routing granularity at that moment.

Announcing an aggregate and its component routes can affect how traffic is selected. More-specific routes normally win longest-prefix matching, so they may be used to steer traffic toward particular paths or policies. But the public paths do not reveal why Fibermax chose that structure. The /24s could support traffic engineering, operational separation, mitigation, or another policy. Assigning a reason without operator documentation would be speculation.

The observed /24s also should not be described as separate networks, facilities, cities, or coverage zones. Prefix length is a routing property. It does not reveal where the addresses are used or whether the more-specifics terminate on different hardware. The same physical dependency could support several prefixes, and one prefix could be served through multiple devices.

What the snapshot offers is a baseline. A future disappearance of the aggregate, a change in more-specifics, or a new origin could be compared against it. Such a change would be a signal for investigation, not an automatic diagnosis. Routing changes need context from the operator, affected users, and other measurement systems before they can support conclusions about service impact.

10. AS263769 Is a Visible Adjacency, Not a Disclosed Contract

All 701 route observations in the reviewed BGP-state response place AS263769 immediately before origin AS265848. That consistency makes AS263769 a prominent visible adjacency in the dataset.

It is reasonable to say that public collectors saw paths reaching Fibermax through that neighboring ASN at the captured time.

It is not reasonable to call AS263769 Fibermax's exclusive upstream, contracted transit provider, owner, or sole route to the Internet without additional evidence. AS paths show sequence, not commercial terms. A neighbouring ASN may provide transit, settlement-free peering, a reseller relationship, an exchange-mediated path, or another form of connectivity. Public path data cannot disclose the contract.

The word “exclusive” is especially risky. Collector visibility can be incomplete, and routing policy can hide backup paths until they are selected. A second link might exist but remain unused in the observed control plane. Conversely, many different collector paths can still converge on one physical dependency. Path diversity and physical diversity are not the same thing.

The useful conclusion is therefore narrower. Fibermax's public routing identity was consistently visible behind AS263769 in the reviewed dataset. That creates a measurable external dependency signal and a question for future research: what commercial and physical arrangements support the handoff? Until the operator or another authoritative source answers it, the public path should remain an observation rather than a contract claim.

11. Collector Counts Measure Observation, Not Audience or Availability

The BGP-state response contains 701 observations and 682 unique source identifiers. Those figures indicate that the route state was seen from many collector sessions. They do not mean that 701 networks carried customer traffic, that 682 customers were connected, or that the service reached a particular share of the Internet.

Collectors sample the control plane. Their sessions can be concentrated in particular regions, facilities, or networks. Multiple sessions may see substantially the same path. A high count can reflect broad measurement visibility without proving diverse forwarding paths. A low count can reflect measurement limitations without proving poor reachability.

For infrastructure reporting, collector counts are most useful as context for confidence and comparison. If a prefix appears through hundreds of sessions, an observation is less likely to be an artefact of one vantage point. If the count changes sharply, it can prompt investigation. Neither condition provides an uptime percentage or a customer-impact estimate.

The same caution applies to timestamps. The BGP-state response is a snapshot, while the announced-prefixes response summarises a two-week interval. Together they show sustained visible announcements and a detailed moment within that period. They still do not establish minute-by-minute continuity, convergence speed, packet loss, latency, or application performance. Those require active measurements and operational data.

12. RPKI Validity Answers an Authorization Question

RPKI allows a holder to publish a cryptographically verifiable statement authorising an autonomous system to originate a prefix, subject to a maximum prefix length. RIPEstat reported the tested IPv4 and IPv6 resources as valid for AS265848. The IPv4 ROA covers 45.224.104.0/22 with maxLength 24. The IPv6 ROA covers 2803:4a20::/32 with maxLength 48.

The IPv4 maxLength is operationally relevant because it permits the observed /24 more-specifics as well as the /22 aggregate. The validation result therefore aligns with both the registered allocation and the observed route granularity. The IPv6 maxLength allows authorised more-specifics down to /48, although the reviewed announcement set showed the /32 aggregate.

Validity means the origin and prefix length match an applicable authorization. It does not mean every network enforces route-origin validation, that the route is immune to leaks, or that the path is secure end to end. RPKI does not authenticate the full AS path. It also does not test forwarding, capacity, customer configuration, or recovery.

Even with those limits, valid authorization is material. It reduces ambiguity about whether AS265848 is permitted to originate the resources and provides a baseline for detecting a future invalid origin or overly specific route. It is a security-metadata layer that complements, rather than replaces, routing observation and operational practice.

13. A Valid ROA Does Not Turn an Announcement Into a Resilience Claim

Network security and network resilience overlap, but they are not interchangeable. A valid ROA can help networks reject certain unauthorised origins.

It cannot keep a router powered, restore a cut fibre, repair a failed optical module, replace a transit session, or maintain customer access during a local outage.

The public evidence for Fibermax contains no verified topology, no inventory of diverse paths, no power architecture, and no recovery-time data. It does not show whether the IPv4 and IPv6 services share the same access equipment, aggregation layer, transport, upstream handoff, or power source. A neat control-plane record can coexist with a fragile physical dependency.

That gap is not a criticism of RPKI. It is a reminder to ask each system the question it can answer. RPKI addresses route-origin authorization. BGP collectors address visible routing state. Licensing addresses permission. A company website addresses its own service proposition. Resilience requires evidence about failure domains, redundancy, monitoring, maintenance, and restoration.

The absence of that evidence should be stated as uncertainty, not converted into a negative claim. Fibermax may have diverse infrastructure or documented continuity practices that are not public. The record reviewed here cannot verify them. A responsible profile marks the boundary and identifies what additional evidence would change it.

14. Registered Resources Carry Responsibilities as Well as Visibility

Number-resource records are often treated as technical inventory, but they also support accountability. An ASN and address block provide stable identifiers for routing, abuse handling, coordination, and change tracking. Registry contacts and security metadata help other operators determine who is responsible for a resource when something goes wrong.

That function is closer to a ledger than to ownership of territory. LACNIC records allocation and responsible parties within the policy system. It does not grant control over a geographic region, a customer population, or every physical path associated with the addresses. The legitimacy of the record comes from accurate registration, operational use, and the ability to maintain continuity through changes.

Fibermax's records are internally coherent: the ASN, IPv4 block, and IPv6 block share the same registrant handle and registration date. Their active status and matching organisation name make the identity straightforward to follow. RPKI adds security metadata that aligns with the observed origin.

The remaining accountability questions sit beyond the registry. How quickly are contacts updated? How are incidents communicated? What happens when a route or access dependency changes? Which systems support continuity for customers? Public number-resource records make those questions easier to direct, but they do not answer them on their own.

15. The Company Website Describes an Offer, Not an Independent Measurement

Fibermax's website says it provides fibre-to-the-home service in Zona Sur and advertises plans from 100 to 400 Mbps. The site repeatedly makes plans subject to technical and geographic availability. That qualification is meaningful: the commercial offer is conditional on the operator's ability to serve a location.

The claims can be quoted as the company's own description. They should not be presented as independently verified coverage or performance. A website does not show how many addresses are serviceable, how often advertised speeds are achieved, what contention exists, or how service behaves during failures. It also does not establish who owns the ducts, poles, fibre, aggregation links, or upstream capacity.

The relationship between the website and the routing record is nevertheless useful. The site shows that the company offers an access service, while AS265848 and the announced resources show an Internet-facing routing identity. Together they make a plausible operator profile. The gap between them is the physical and commercial delivery chain.

That gap is precisely where infrastructure research should focus. A customer-facing offer depends on access plant, power, aggregation, upstream routing, address assignment, support systems, and restoration procedures. Public routing records illuminate only part of that stack. Treating the marketing claim as attributed and bounded preserves its value without allowing it to fill every missing layer.

16. The Last Mile Cannot Be Reconstructed From the ASN

The path from Fibermax's network edge to a subscriber can include neighbourhood fibre, splitters, cabinets, poles, ducts, building access, optical network terminals, power supplies, and customer equipment. None of those components appears in an ASN record.

BGP begins at a different layer, where prefixes and policies are exchanged between networks.

Even a detailed AS path does not identify the physical route taken inside an operator's network. Internal routing is usually hidden. Two customer areas may share an aggregation node or power dependency without that fact appearing in external BGP. Conversely, one external ASN can represent many sites and internal paths.

The official licence likewise does not reveal the plant. It permits a service category, not a specific physical design. The company website uses FTTH language, but it does not provide an independently verifiable network map or asset register. Those facts support a service description while leaving ownership and dependency questions open.

The safest conclusion is that Fibermax has a visible public routing edge and an attributed fibre-access proposition. The connection between them is operationally important but not fully documented in the sources reviewed. Reporting should follow that dependency rather than assume it: from number resources and route authorization, through external adjacency, into aggregation and the access network, and finally to customer premises.

17. Physical Diversity Cannot Be Counted From Prefix Diversity

The BGP response shows multiple prefixes, but prefix diversity is not physical diversity. The /22, four /24s, and IPv6 /32 could all travel through the same upstream handoff, the same facility, the same conduit, or the same power domain. Public paths do not reveal whether that is the case.

Similarly, observing one immediate neighbouring ASN across all routes does not prove there is only one physical link. Several links can connect the same pair of autonomous systems. They may be in different buildings or in the same rack. They may have independent optics but share a fibre route. Without facility, circuit, and topology evidence, no reliable redundancy count can be made.

This distinction matters because resilience claims often rely on superficial counts. Two prefixes are not two paths. Two BGP sessions are not necessarily two failure domains. Two carriers may still share a conduit or power source. A robust assessment follows physical dependencies and asks whether failures are truly independent.

For Fibermax, the public record supports no specific claim about redundant upstreams, diverse access routes, or backup power. It also provides no evidence that those protections are absent. The correct position is unknown. A future operator statement, facility record, outage analysis, or measurement from multiple physical vantage points could narrow that uncertainty.

18. The Visible Handoff Creates a Concrete Continuity Question

The consistent appearance of AS263769 immediately before AS265848 gives the profile a concrete continuity question: how does Fibermax maintain reachability when the visible external handoff is impaired? The question is legitimate because the adjacency is observable. The answer is not present in the public routing snapshot.

A backup route may be hidden until failure. Another upstream may be used only for selected prefixes or traffic. The same ASN pair may connect at multiple sites. Alternatively, the public view may reflect a concentrated dependency. Each scenario would have different implications, and BGP path strings alone cannot distinguish them.

Operational continuity also extends beyond transit. The service depends on local access equipment, aggregation, power, DNS, address assignment, customer authentication, monitoring, and support. A stable route can coexist with a local access outage. A routing withdrawal can coexist with equipment that remains powered but isolated.

The public evidence therefore creates a monitoring baseline rather than a resilience score. Future changes in origin, adjacency, or prefix visibility can be detected. If an outage is publicly reported, those changes can be compared with customer symptoms and operator communications. Until such evidence exists, the responsible statement is that the continuity architecture remains unverified.

19. The Regulatory Timeline Shows Why Records Need Dates

Fibermax's regulatory history spans at least the 2017 Internet-access registration, the 2019 subscription-broadcasting registration referenced by a later resolution, and the cancellation effective in 2025 and published in 2026.

The sequence demonstrates that permissions and service portfolios can change while the company identity remains.

Dates prevent records from being blended into one undifferentiated status. The 2017 registration answers a question about Internet access at that time. The later cancellation answers a question about a separate broadcasting registration. Neither record alone establishes Fibermax's entire current regulatory position. A current legal assessment would need the full official register and any subsequent modifications.

The same principle applies to routing. LACNIC's registration dates describe the resource record. RIPEstat's July 2026 interval describes observed announcements. The BGP-state timestamp describes one routing snapshot. These dates should travel with the claims because network state can change faster than corporate registry data.

Date discipline is not administrative decoration. It is what allows future researchers to determine whether an observation is still current, whether a change is new, and which evidence layers moved together. A route change following a regulatory action may be meaningful, but correlation should not be claimed without a documented connection.

20. A Better Baseline Separates Allocation, Authorization, Announcement, and Delivery

Fibermax's public record can be organised into four layers. Allocation is established by LACNIC for AS265848, 45.224.104.0/22, and 2803:4a20::/32. Authorization is established by valid RPKI results for the IPv4 and IPv6 aggregates. Announcement is established by RIPEstat's dated routing observations. Delivery is described only partially through the company's service claims and regulatory role.

The first three layers align cleanly. The resources are registered to the exact company, the origin is authorised, and public collectors observed the routes. That alignment is meaningful because mismatches between those layers can indicate stale records, configuration errors, unauthorised origins, or operational transitions.

The fourth layer is where uncertainty expands. Public sources do not reveal the full access topology, customer reach, physical ownership, usable capacity, or recovery design. It would be a mistake to let the strength of the registry and routing evidence spill over into unsupported delivery claims.

This layered baseline is useful precisely because it is incomplete in a disciplined way. It states what can be verified, identifies the interfaces between systems, and leaves named questions open. Future evidence can be attached to the appropriate layer instead of rewriting the company profile from scratch.

21. Changes in Origin or Prefix Shape Would Be Investigative Signals

The frozen baseline creates several testable signals. A future origin other than AS265848 would raise a route-authorization question. A new invalid RPKI state could indicate a configuration or authorization mismatch. Withdrawal of the IPv6 /32 could change the observed dual-stack picture. A shift from the /22 aggregate to more-specifics could reflect traffic engineering, mitigation, or another operational event.

None of those changes would diagnose an incident by itself. BGP can change for planned maintenance, policy adjustment, migration, or measurement reasons. RPKI data can lag an intended transition. Collector visibility can differ across time and vantage points. The signal should trigger corroboration, not an immediate conclusion.

Corroboration might include operator notices, active reachability measurements, DNS observations, customer reports, facility information, and additional collector data. The strongest account would connect the control-plane change to a documented mechanism and observable impact.

This approach keeps the profile useful after publication. It is not a static catalogue entry. It is a dated baseline against which the public network identity can be monitored. The discipline is to preserve the original evidence and avoid turning every change into a failure narrative.

22. The Missing Evidence Is Specific, Not Vague

Several additional records would materially improve the operating picture. A network map could show aggregation and external handoff locations. Facility and circuit information could distinguish logical adjacency from physical diversity. Power and backup arrangements could identify shared failure domains. Customer-side IPv4 and IPv6 tests could establish actual service availability.

Capacity claims would require measurements or operator documentation that distinguishes installed, lit, usable, and sold capacity. A fibre route can exist without being lit. Equipment can be installed without being commissioned. A service can be commercially offered without being available at every address. These states should never be collapsed into one claim.

Resilience evidence would need failure and recovery information: what failed, which dependency was affected, whether traffic shifted, how customers experienced the event, and how long restoration took. A promise of redundancy is weaker than an observed successful failover. An observed stable route is weaker than evidence that the access network remained usable.

Ownership also needs precision. Fibermax may own some infrastructure and lease other components. The public records reviewed do not establish the split. Future reporting should identify the owner, operator, and customer dependency for each material segment rather than use “the network” as if it were a single asset.

Active measurements could narrow several of these gaps without pretending to expose the entire architecture. Repeated IPv4 and IPv6 probes from locations inside the advertised service area could test reachability, latency, packet loss, and protocol parity over time. Traceroutes from several independent networks could show whether the visible external handoff changes, although they would still need careful interpretation because forward and return paths may differ. DNS and certificate observations could identify public service dependencies without establishing ownership.

Customer reports tied to precise times and locations could help distinguish a local access problem from a wider routing event.

The most useful operator disclosure would connect those observations to named operational controls. It could state which parts of the access network are owned or leased, how external connectivity is diversified, which power and aggregation dependencies are shared, and what restoration objectives apply. Evidence of a tested failover would carry more weight than a general redundancy claim. None of that information is required to confirm the ASN or route authorization, but it is necessary before the public routing identity can support conclusions about service continuity.

23. What the Public Record Supports

The strongest supported profile is concise. FIBERMAX S.A. is the exact Argentine company linked to AS265848, active IPv4 block 45.224.104.0/22, and active IPv6 block 2803:4a20::/32.

ENACOM recorded the company for Internet access in 2017 under CUIT 30-71534748-9. The company markets FTTH service in Zona Sur, with advertised plans subject to technical and geographic availability.

Public collectors observed both aggregate resources announced during the reviewed July 2026 interval. A BGP snapshot showed 701 observations and consistently placed AS263769 immediately before AS265848. RPKI validation found the tested IPv4 and IPv6 origins valid. A later official regulatory action concerned cancellation of a separate subscription-broadcasting registration and should remain bounded to that service.

Those facts establish a visible dual-stack routing identity and a route-authorization baseline. They do not establish physical route ownership, coverage, capacity, exclusive upstream terms, redundancy, uptime, or recovery performance. The access and continuity boundaries remain open questions.

That is not an empty conclusion. It identifies what is accountable in public records and what still requires direct evidence. The registry is a ledger, the routing data is a dated view of running code, and RPKI is a security-metadata layer. Together they make Fibermax's Internet-facing identity observable without pretending that the entire delivery system is known.

Sources