Summary

  • LACNIC RDAP binds active AS271887 and active IPv4 allocation 200.23.85.0/24 to FIBERCOM S.R.L. in Lules, Argentina.
  • RIPEstat observed that single /24 announced by AS271887 during the reviewed 14-28 July 2026 interval, with 327 of 329 responding IPv4 RIS peers seeing the route at the routing-status snapshot.
  • All 335 paths in the captured BGP-state response place AS265798 immediately before AS271887, a visible adjacency that does not disclose commercial terms or physical diversity.
  • The tested RPKI response returned unknown and no validating ROAs; that result is not proof that the route was invalid, hijacked, unreachable, or insecure.
  • Public records do not establish Fibercom's subscriber count, service footprint, physical access-network ownership, usable capacity, redundancy, uptime, or restoration performance.

1. A Small Public Footprint Can Still Carry a Large Dependency

The Internet does not require a company to announce thousands of routes before its network identity matters. A regional access operator may present only a small address block to the global routing system while supporting many private customer sessions, local access links, aggregation devices, and operational dependencies behind that block. The public footprint is a control-plane boundary, not a complete inventory of the service.

FIBERCOM S.R.L. illustrates that distinction. The reviewed registry records identify one autonomous system and one IPv4 /24. Public collectors saw that /24 with Fibercom's ASN as origin. The result is a precise external identity that can be monitored over time. It is more useful than a generic description of a connectivity company because it identifies a specific routing actor and a specific address resource.

Yet the footprint remains narrow. A /24 contains 256 IPv4 addresses, but address count is not subscriber count. Customers may use private addressing, carrier-grade NAT, dynamically assigned addresses, or services that do not map one public address to one location. Infrastructure devices may also consume part of the space. Nothing in the allocation says how many customers exist, how much traffic crosses the network, or how broadly service is offered.

The infrastructure question is therefore not whether the public footprint looks large. It is what has to keep working behind that footprint for users to remain connected. Registry and routing records can identify the edge. They cannot, by themselves, enumerate the physical and organisational chain that sustains it.

2. Exact Company Identity Comes Before Network Interpretation

The name FIBERCOM S.R.L. is not unique enough to serve as an identifier by itself. Public records contain more than one Argentine company with that legal name, and an archived company record also exists under a similar slug.

Attaching network evidence to the wrong row would create a clean-looking but false account of the operator.

The relevant company is the published Argentina company Entity with identifier cmqk44v1t00e5t26bn2rps4k7 and canonical slug fibercom-s-r-l-ar. LACNIC's AS271887 record names FIBERCOM S.R.L. as registrant handle AR-FISR12-LACNIC and places the organisation in Lules. The IPv4 record uses the same registrant handle and company name. Both records also identify Carlos Diego Zurita as the administrative, technical, and abuse contact.

That combination is stronger than a name match. The company, ASN, address block, location, and contact identity converge. It creates a bounded link between the legal organisation and the network resources. Personal contact details are not needed in public reporting; their value is in resolving the organisation, not in exposing telephone numbers, email addresses, or street-level information.

A separate ENACOM resolution from 2022 concerns another FIBERCOM S.R.L. with CUIT 30-71726659-1. That record cannot be merged into this company merely because the legal name is identical. The collision is an important warning: legal names may repeat, while network-resource records depend on exact holder identity. Every later claim must stay anchored to AS271887, the LACNIC registrant, and the exact company Entity.

3. AS271887 Is a Routing Policy Identifier, Not a Business Metric

An autonomous system number identifies a network that presents a distinct routing policy to other networks. LACNIC records AS271887 as active and assigns it to FIBERCOM S.R.L. That gives the company a durable key in the interdomain routing system, allowing observations from registries, route collectors, and security metadata to be joined without relying on branding.

The number says very little about business scale. ASNs are used by national carriers, regional ISPs, universities, hosting companies, enterprises, public institutions, and small specialist networks. The existence of an ASN does not reveal revenue, headcount, subscriber count, traffic volume, or number of sites. It also does not establish that every customer service is routed directly through the ASN.

What AS271887 does provide is accountability at the Internet edge. Other operators can identify the origin shown in BGP, compare it with the registered holder, inspect route-origin authorization, and contact the responsible organisation when routing or abuse issues arise. A future change in origin or announced space can be detected against this baseline.

That accountability is operationally meaningful even when the public footprint is compact. It helps distinguish Fibercom from another company with the same name, and it establishes a concrete network surface for further research. The correct interpretation is therefore neither dismissive nor expansive: AS271887 makes Fibercom's routing policy externally identifiable, but it does not reveal the full architecture or performance of the service.

4. The Registered /24 Defines a Number-Resource Boundary

LACNIC's IPv4 RDAP response identifies 200.23.85.0/24 as an active allocation registered to FIBERCOM S.R.L. The range begins at 200.23.85.0 and ends at 200.23.85.255.

The exact match between the address record and the AS registrant provides a clear number-resource boundary.

A /24 is also an important operational unit in the global routing system. It is commonly the longest IPv4 prefix accepted without special arrangements across much of the public Internet. That makes the block independently announceable in a way that a smaller prefix often is not. The route data confirms that AS271887 did announce this /24 during the reviewed interval.

Registration does not prove use of every address. Some may be assigned to infrastructure, some to customers, some held in reserve, and some unused. The public record does not expose allocation policy inside Fibercom. It cannot support a utilisation rate or a customer estimate.

Nor is address space a physical asset map. The block does not reveal where routers are installed, how fibre reaches a neighbourhood, which facilities host equipment, or who owns the transport. Number resources provide uniqueness and a record of responsibility. They should not be converted into geographic ownership or assumed control of every underlying component. The strongest supported statement is that Fibercom holds and originates one clearly registered IPv4 /24.

5. Route Visibility Moves the Evidence From Registry to Running Code

A registry record can remain active even when a prefix is not visible in BGP. The RIPEstat announced-prefixes response adds a different kind of evidence: it reports 200.23.85.0/24 announced by AS271887 from 14 July through 28 July 2026. That dated observation connects the registered resource to running routing behaviour.

The routing-status response extends the timeline. It reports the prefix-origin pair first seen on 23 April 2021 and last seen on 28 July 2026. These dates do not prove uninterrupted service between those moments, but they show that the relationship was not merely created for the two-week review window. It had a history in the collector data.

Time qualification is essential. BGP visibility changes. Prefixes can be withdrawn, origins can change, upstream policy can shift, and collector coverage can vary. The correct description is that public collectors observed this prefix with AS271887 as origin at the captured times. It is not a permanent guarantee.

Running-code evidence is stronger than a promotional statement when the question is whether a route appeared on the Internet. It is still narrower than an end-to-end service measurement. A visible BGP route does not prove that customer traffic flowed successfully, that every destination could reach the prefix, or that access services behind it were functioning. It establishes an observable control-plane state.

6. Nearly Universal RIS Visibility Is Not Universal Reachability

At the routing-status snapshot, RIPEstat reports that 327 of 329 responding IPv4 RIS peers saw 200.23.85.0/24 originated by AS271887. That is broad visibility within the responding RIS peer set.

It increases confidence that the route was not an artefact of one collector session or one isolated vantage point.

The denominator matters. The result describes RIS peers participating in that measurement, not every autonomous system on the Internet. Peers are distributed across networks and locations, but they are not a complete census of forwarding paths. Two peers can see the same route while reaching it through shared infrastructure, and a network outside the measurement system can make a different policy decision.

Visibility also differs from reachability. A route may be accepted in the control plane while packets fail because of filtering, forwarding errors, congestion, return-path problems, application failures, or local access outages. Conversely, a collector may not report a route that remains reachable through another path. BGP is one layer of the service.

The 327-of-329 figure should therefore be used as a bounded observation: AS271887's /24 was broadly visible to the responding RIPE RIS peer set at the reviewed time. It must not become a percentage uptime claim, an availability guarantee, or evidence of global customer service. Its value lies in establishing a stable measurement baseline and showing that the route had wide control-plane propagation.

7. One Prefix Does Not Mean One Router, Site, or Customer Network

RIPEstat reports one announced IPv4 prefix and 256 IPv4 addresses for AS271887, with no IPv6 prefix in the captured routing-status response. That compact footprint is easy to visualise, but it should not be translated into a simplistic physical diagram.

One /24 can be originated from multiple routers. It can be presented through redundant sessions, carried between several internal sites, or concentrated in one location. It can support customer NAT pools, infrastructure addresses, servers, management systems, or a mixture of uses. External BGP does not disclose the internal arrangement.

The reverse mistake is also possible: a company can operate an extensive access network while announcing very little address space. Private addressing and carrier-grade NAT can separate the number of public addresses from the number of subscribers. Wholesale or partner arrangements can further decouple the public route from the physical access plant.

The public footprint is therefore best understood as an edge identity. It identifies the resource that other networks route toward Fibercom. It does not define the number of routers, access nodes, fibre kilometres, service locations, or failure domains behind that edge. Any physical reconstruction would require facility records, network diagrams, field evidence, operator disclosures, or measurements that are not present here.

8. The BGP Snapshot Shows a Consistent Immediate Neighbour

The captured RIPEstat BGP-state response contains 335 observations for 200.23.85.0/24. Across those observations, AS265798 appears immediately before origin AS271887.

The consistency makes the adjacency a material feature of the reviewed control-plane state.

The CIDR Report provides an auxiliary view. It lists one observed adjacent AS, AS265798, and one originated /24. It also warns that its upstream and downstream labels describe relative topology from the collection point and should not be confused with provider, customer, or peer relationships.

That warning is decisive. An AS path records the sequence used to advertise reachability. It does not publish the contract between neighbours. AS265798 could provide transit, a reseller or wholesale arrangement, exchange-mediated connectivity, private peering, or another form of service. Public BGP cannot determine the commercial label.

The immediately pre-origin position does establish a visible handoff. It identifies where the globally observed path entered Fibercom's ASN during the snapshot. That makes AS265798 relevant to continuity questions and future comparisons. It does not prove exclusivity, physical colocation, circuit count, or the absence of backup paths. The correct language is “observed adjacent ASN” or “immediately pre-origin ASN,” not “sole upstream provider.”

9. Path Consistency Can Hide Physical Concentration or Hidden Diversity

Seeing the same immediately pre-origin ASN in all 335 observations may look like evidence of a single dependency. It is evidence of a consistent selected control-plane path. The physical interpretation remains open.

The same pair of autonomous systems can connect through multiple circuits, devices, buildings, or cities. Those links may share no physical route, or they may share almost everything. BGP normally exposes the AS sequence, not conduit, fibre, power, rack, or interface diversity. Several independent sessions between the same ASNs can therefore appear identical in the public path.

A backup relationship can also remain hidden until needed. An alternative ASN may announce the prefix only during a failure, or Fibercom may prefer one path so strongly that collectors do not select another. The absence of a second visible neighbour in a snapshot is not proof that no backup exists.

The opposite risk is equally important. Multiple visible AS paths can converge on the same cable, facility, or power source. Logical variety is not physical redundancy. Assessing resilience requires evidence about failure domains, not just route strings.

For Fibercom, the public data creates a specific unanswered question: what infrastructure and contractual arrangements support the AS265798-to-AS271887 handoff, and what changes when that path is unavailable? The snapshot identifies the dependency surface but cannot score its resilience.

10. RPKI Returned Unknown, Not Invalid

The captured RIPEstat RPKI validation response for AS271887 and 200.23.85.0/24 reports status unknown and returns no validating ROAs.

That result requires careful interpretation because “unknown” is neither “valid” nor “invalid.”

A valid result would mean an applicable route origin authorization matches the prefix, origin ASN, and maximum prefix length. An invalid result would mean an applicable authorization exists but does not permit the observed origin or prefix length. Unknown generally means the validator found no applicable authorization for the tested route.

The distinction matters. The frozen response does not demonstrate that AS271887 was an unauthorised origin. It demonstrates that the tested RPKI system did not return a validating authorization. The LACNIC registration independently identifies Fibercom as holder of both the ASN and the /24, which supports the identity while leaving the RPKI authorization layer unresolved.

RPKI deployment is not universal, and the absence of a ROA is not itself proof of compromise or poor operation. It does mean that relying networks cannot derive a “valid” route-origin state from that layer for the tested pair. The responsible statement is factual and narrow: the route was visible, the registry identities aligned, and the RPKI query returned unknown with no validating ROAs.

11. Unknown Authorization Is a Monitoring Gap, Not an Incident

Security metadata can be valuable without becoming an accusation. The lack of a validating ROA in the captured response means there is less cryptographic information available to distinguish the expected origin from an unexpected one. It does not establish that a hijack occurred or that traffic was misdirected.

Many legitimate routes remain RPKI unknown. Networks decide independently how to treat valid, invalid, and unknown routes. Route-origin validation policies commonly reject or de-preference invalid routes while continuing to accept unknown ones. Actual behaviour varies across operators and can change over time.

The useful operational implication is a baseline. Future measurements can ask whether the status remains unknown, becomes valid after a ROA is published, or changes because the route or registry data changes. If an unexpected origin appears while the route remains unknown, investigators would need to combine registry, BGP, operator, and traffic evidence before drawing conclusions.

The gap should also remain separate from physical resilience. A ROA would improve authorization metadata, but it would not add a backup circuit, power source, router, or access route. Security metadata and continuity controls answer different questions. Fibercom's visible RPKI state is an accountability issue at the routing layer, not a substitute for evidence about the service's physical operation.

12. No IPv6 Announcement Was Established in the Frozen Evidence

The reviewed LACNIC and RIPEstat records establish an IPv4 identity. They do not establish an IPv6 allocation or announcement for Fibercom in this evidence set.

That absence must not be turned into a broader claim that the company has no IPv6 capability anywhere.

An operator can use another organisation's resources, private interconnection, an upstream-assigned prefix, or an arrangement that does not appear under its own ASN in the queried data. It can also deploy IPv6 internally or to selected customers without originating a directly registered aggregate from AS271887. The current evidence simply does not show such a resource.

The limitation matters because “dual stack” is often used casually. Here, the supported public routing claim is single-stack IPv4 for the observed ASN and prefix. Describing the network as dual stack would add a fact not present in the frozen records.

Future research could revisit LACNIC allocations, routing tables, DNS, customer measurements, or operator documentation. Any new result should be dated and linked to the same exact company identity. Until then, the accurate account is that AS271887 originated one visible IPv4 /24 and the reviewed source set did not establish an IPv6 announcement.

13. Legal Permission and Running Routing Are Separate Evidence Layers

Official Argentine search results identify a 2017 Internet-access licence record for FIBERCOM SOCIEDAD DE RESPONSABILIDAD LIMITADA, CUIT 30-71491723-0. An official supplier-registry result uses the same CUIT and names Carlos Diego Zurita, consistent with the contact identity in the LACNIC records.

Those matches strengthen the legal-identity chain, but the full official 2017 documents were not available as complete local captures in this review. The licence URLs are therefore best treated as bounded identity leads rather than a foundation for detailed claims about current service scope.

Even a complete licence would answer a permission question, not a physical-deployment question. Regulatory authority to provide Internet access does not identify which fibre is owned, leased, or shared. It does not disclose upstream contracts, installed capacity, customer coverage, power arrangements, or recovery procedures. Permission can be broad while actual deployment is narrow.

Running BGP provides complementary evidence. The route shows that AS271887 and its /24 were visible to public collectors. That does not prove the exact services authorised by a licence or the legal status of every offering. The two layers converge on an operator identity but must not be collapsed into one another.

14. The Same-Name 2022 Company Must Remain Outside the Boundary

ENACOM Resolution 1279/2022 is a complete official PDF and contains the name FIBERCOM S.R.L. It also carries CUIT 30-71726659-1, which differs from the CUIT associated with the 2017 licence lead.

That difference is not a formatting issue. It identifies another legal entity.

The 2022 record is useful precisely because it prevents overconfident matching. A researcher who searched only the company name could attach the later resolution to AS271887 and build a false regulatory history. The exact tax identifier blocks that mistake.

The network records do not include a CUIT field, so the match relies on the LACNIC registrant handle, organisation name, Lules location, and Carlos Diego Zurita contact identity. The 2017 supplier and licence results align with those details. The 2022 CUIT does not.

Nothing in the 2022 resolution should be used to describe Plan861's company, licence, assets, or services. Its role is negative evidence: it proves that the legal name is not unique and makes the identity boundary explicit. This is a recurring infrastructure-research problem. Names and brands are convenient search terms; exact entities require registrant handles, legal identifiers, locations, and contact continuity.

15. Registry Records Act as a Ledger, Not a Claim of Territory

LACNIC records who is responsible for an ASN and address block within the number-resource system. That function supports uniqueness, contactability, transfer recording, abuse handling, and operational continuity. It does not grant sovereignty over a geographic area or prove ownership of physical infrastructure.

The distinction is especially important for a regional ISP. A registered /24 can be used in one locality or across several service arrangements. It can traverse facilities and transport owned by other companies. The holder remains responsible for the number resource without necessarily owning the ducts, poles, buildings, or fibre that carry packets.

Treating the registry as a ledger produces more accurate accountability. The record says which organisation should maintain the registration and respond to resource-related issues. BGP shows that the organisation's ASN originated the prefix at the reviewed time. RPKI shows that no validating authorization was returned for the tested pair. Each layer records a different operational fact.

None of those records should be turned into advocacy about ownership, permission, or legitimacy. Their value lies in observable responsibility. Fibercom's entry provides a stable identity against which future changes can be checked. The company still needs separate evidence to establish the physical network and service boundary behind that identity.

16. Contact Continuity Is Part of Infrastructure Continuity

Number-resource operations depend on more than routers. Other networks need a way to reach the responsible organisation when routes change unexpectedly, abuse reports arise, or coordination is required.

Registry contacts therefore form part of the operational continuity layer.

LACNIC associates Carlos Diego Zurita with administrative, technical, and abuse roles for both AS271887 and 200.23.85.0/24. The repetition helps connect the records and resolve the company identity. The public analysis does not need to reproduce personal contact details; the relevant fact is that the same accountable contact role spans the ASN and address block.

Contact accuracy can degrade. People change roles, organisations reorganise, email domains change, and stale records can delay incident coordination. The reviewed data does not establish when a contact method was last tested or how quickly Fibercom responds. It only shows the registered responsibility.

That limitation is still informative. Operational continuity includes the ability to update records and receive notices, not just keeping interfaces up. A future discrepancy between the company, contacts, and route origin would be a reason for focused investigation. At present, the records are internally coherent enough to establish the exact resource holder.

17. The Public Edge Does Not Reveal the Access Plant

Customers experience an access network, not an ASN. Their service may depend on neighbourhood fibre or wireless links, poles or ducts, aggregation switches, optical equipment, power supplies, authentication systems, DNS, upstream connectivity, and support operations. Most of that chain is invisible in public BGP.

The route to 200.23.85.0/24 shows how other networks learned to reach the public block. It does not show how packets travel from Fibercom's edge to a home or business. Internal routing and layer-two topology are normally hidden. External paths cannot identify splitters, cabinets, towers, building entrances, backhaul circuits, or customer-premises devices.

Public legal records are no substitute. A licence can permit an access service without listing every installed asset or ownership arrangement. The exact company may own some components, lease others, and depend on wholesale or shared infrastructure. None of those possibilities is resolved here.

The physical dependency therefore remains the main unanswered question. What must stay powered and connected for the routing identity to translate into usable customer service? Without plant maps, operator documentation, outage evidence, or field measurements, the answer cannot be reconstructed from the ASN. The analysis should preserve that boundary rather than fill it with assumptions.

18. Capacity Cannot Be Derived From Address or Route Counts

Address space is not bandwidth. A /24 says how many IPv4 addresses sit within the registered range, not how many bits per second Fibercom can move.

One prefix can be carried over a low-capacity circuit or a high-capacity network. The route table does not expose interface speed, optical channels, committed information rate, oversubscription, or customer demand.

Collector count is not capacity either. The fact that 327 RIS peers saw the route means the announcement propagated broadly in the control plane. It does not measure traffic volume, latency, packet loss, congestion, or usable throughput.

The same caution applies to the consistent AS265798 adjacency. A single commercial relationship can include multiple circuits and capacity tiers, while several relationships can share one bottleneck. Public AS paths reveal none of those details.

Claims about capacity would require operator disclosures, procurement records, interface telemetry, facility information, independent performance measurements, or customer data with a clear methodology. No such evidence is present in the frozen set. Fibercom's installed and usable capacity must therefore remain unknown, as must the amount of headroom available during failures or demand peaks.

19. Redundancy Requires Documented Failure Paths

A resilient network is not defined by the number of labels in a routing table. Redundancy is meaningful only when alternative components survive the same failure and can carry the required load. Two routers sharing one power feed, two fibres in one conduit, or two BGP sessions over one circuit may not provide independent protection.

The public evidence for AS271887 does not disclose multiple upstream ASNs, facilities, conduits, power systems, or access paths. It also does not prove that the visible AS265798 adjacency is physically singular. Both conclusions would exceed the evidence.

The right question is conditional: if the visible handoff, its facility, its transport, or its power source fails, what path takes over, and how quickly? A credible answer would identify the failure domain, alternative route, capacity under failover, monitoring trigger, operating owner, and recovery procedure.

No public record reviewed here supplies that chain. Fibercom may operate protections that are not publicly documented. The absence of documentation is not proof of absence. It means redundancy remains unverified and should not be advertised as an established property.

This is where future incident evidence could add value. A route withdrawal, service notice, maintenance event, or customer-impact report could reveal which components changed together and how recovery occurred. Until such evidence exists, the responsible assessment is a visible routing edge with an unknown physical resilience design.

20. A Stable Route Can Coexist With a Local Service Failure

BGP describes interdomain reachability, not every component of customer service. AS271887 can continue announcing 200.23.85.0/24 while part of the access network is down.

A failed local power supply, fibre cut, authentication platform, DNS resolver, or aggregation device might affect customers without changing the global route.

The reverse can also happen. A BGP withdrawal can make the public block unreachable even while local equipment remains powered and connected. Customers may retain access to local resources while losing external connectivity. The route and the access service are related but distinct operational layers.

This separation matters when interpreting incidents. A stable route should not be used to dismiss customer reports. A withdrawn route should not automatically be blamed on a physical cable cut. Investigators need timestamps from several layers: BGP, active probes, service status, power, facility alarms, customer reports, and operator communications.

The current baseline is useful because it fixes the expected external state: one /24, origin AS271887, broad RIS visibility, and a consistent immediate neighbour. Future deviations can be compared with that state. Diagnosis still requires evidence from the systems behind it.

21. The Single Visible Origin Creates a Useful Change Baseline

At the captured time, the registry holder, BGP origin, and company identity align. That coherence makes future changes easier to interpret. A different origin ASN, a new prefix, a withdrawn route, a second adjacency, or a changed RPKI state would be visible departures from the baseline.

Not every change would be harmful. A new origin could reflect a merger, network migration, managed service, or legitimate operational transition. A second prefix could support growth. A valid ROA could close the current authorization gap. A new adjacency could add capacity or diversity, though physical independence would still need proof.

The baseline should therefore support questions rather than automatic alerts. Who authorised the change? Does the registry reflect it? Was the public company identity preserved? Did customer reachability change? Is the new path physically distinct? Were contacts and security metadata updated?

This approach treats routing data as a record of running systems. It avoids freezing the company into a static description. Fibercom's network identity can evolve, and an evidence-based profile should evolve with it while preserving the distinction between observed control-plane change and inferred business or physical meaning.

22. What Better Evidence Would Clarify the Operating Boundary

The most valuable additional evidence would describe the path between AS271887's Internet edge and actual users.

An operator network map with facility and ownership boundaries could identify where Fibercom controls equipment and where it depends on third parties. Circuit or interconnection information could clarify the AS265798 handoff and any alternatives.

Power evidence would identify which sites need utility service, backup generation, batteries, or shared building systems. Capacity evidence would distinguish installed links from lit and usable capacity, including what remains during maintenance or failover. Neither can be inferred from the /24.

Customer-facing measurements could establish IPv6 availability, latency, packet loss, throughput, and reachability across several locations and times. They would need a transparent methodology and should not be generalised beyond the measured sample. Outage and maintenance records could reveal failure paths and restoration behaviour.

RPKI could be revisited to see whether a route origin authorization is later published. A valid result would improve the authorization layer without answering physical questions. Registry contact freshness and legal records could also be checked for changes.

Each new source should attach to the exact company and resource identity. The same-name legal collision makes loose matching especially dangerous. Better evidence is not simply more material; it is evidence that narrows a specific unknown without crossing entity or layer boundaries.

23. Customer Dependency Cannot Be Counted From the Public Block

The 256 addresses in 200.23.85.0/24 are not a census of the people or organisations that depend on Fibercom. Modern access networks frequently place many customer sessions behind shared public addresses. They can also assign public addresses dynamically, reserve space for infrastructure, or use resources supplied by another organisation. The relationship between addresses and users is therefore operational rather than one-to-one.

The public route also does not identify customer type. A regional network may serve homes, businesses, public institutions, other providers, or internal services. The frozen records do not establish which of those groups Fibercom serves, how many are connected, or whether any critical service depends on the network. Naming a hospital, school, municipality, enterprise, or locality without direct evidence would create a dependency claim that the route data cannot support.

This uncertainty affects impact analysis. If AS271887's public route disappeared, the number of affected users could not be calculated from the /24. Some customers might retain access through private or alternative paths, while services using the public block could fail even if local connectivity remained. A local access outage could affect many customers without changing the route at all.

The correct dependency statement is conditional. The network's users depend on a chain that includes local access, aggregation, power, address and session systems, the visible external handoff, and remote routing acceptance. The public data identifies one part of that chain. It does not quantify the population behind it. Future impact estimates would need operator data, independent service measurements, or incident reports tied to a known geography and time.

24. An Incident Would Need Evidence From Several Clocks

A useful incident record would align events from systems that run on different clocks. BGP collectors could show when 200.23.85.0/24 was withdrawn, re-originated, or reached through a changed path. Active probes could show when packets stopped returning. Customer reports could identify which locations and services were affected. Power, facility, and access-network logs could establish the physical cause. Operator notices could describe recovery actions.

No one stream would be sufficient. A BGP change may be planned maintenance or a control-plane event with little customer impact. Customer reports may reflect a local access problem while the global route remains stable. A power event can affect one site while redundant equipment elsewhere continues to originate the prefix. The timelines need to be compared before cause and impact are assigned.

The current baseline makes that future comparison possible. Investigators know the expected origin, prefix, broad RIS visibility, immediate observed neighbour, and RPKI state at the reviewed time. They also know what is not established: internal topology, physical location, circuit diversity, backup power, capacity, and customer distribution.

Recovery evidence would be especially valuable. The time between first symptom, route change, operator acknowledgement, restoration, and stable service can reveal which layer controlled the incident. It can also test whether an alternative path was independent and adequately provisioned. Until such an event is documented, resilience remains a question rather than a rating.

25. Fibercom's Observable Network Is Precise but Incomplete

The reviewed records support a clear conclusion. FIBERCOM S.R.L. operates an externally identifiable routing edge under AS271887 and originates registered IPv4 block 200.23.85.0/24. The route was visible during the reviewed July 2026 interval, reached 327 of 329 responding IPv4 RIS peers in the routing-status snapshot, and appeared in 335 BGP-state observations with AS265798 immediately before the origin. The tested RPKI result was unknown.

Those facts are precise because they attach to an exact company Entity, registrant handle, ASN, prefix, date range, and measurement system. They are incomplete because they stop at the public edge. They do not reveal the access plant, service footprint, traffic, capacity, physical path, commercial contract, redundancy, power, uptime, or recovery.

The same-name legal collision reinforces the need for restraint. Public infrastructure research must resolve the entity before interpreting the network. It must then keep registry, routing, authorization, permission, and physical operation as separate layers.

Fibercom's compact footprint is not trivial. It gives customers, peers, and researchers a stable identity and a basis for future monitoring. Its importance lies in what the footprint makes observable and in the operational questions it exposes. The public record shows one route into the global system. The boundary behind that route remains the next subject for evidence, not assumption.

Sources