Lopez Penaloza Edson Max, AS272997 and the Public Record Behind a Peruvian Connectivity Supplier

Summary

• Official LACNIC records identify LOPEZ PENALOZA EDSON MAX as the registrant entity for active, directly allocated AS272997 and for active IPv6 block 2803:ed90::/32. The ASN record also presents EDSON MAX LOPEZ PENALOZA as legal representative, joining the same name components to both resources without establishing business size, network performance or a corporate title beyond the registry field.
• SUNAT resolution RSNAAF 221-2022 names EDSON MAX LOPEZ PENALOZA with RUC 10407058165 in a public direct-contracting context. Procurement aggregators connect that exact RUC to a supplier profile and internet-service records, but their listings do not replace original tender documents or prove contract value, execution, coverage or service quality.
• The defensible conclusion is limited but useful: one identifiable individual supplier has a public footprint spanning state-procurement records and internet-number resources. The unresolved questions concern the actual topology, customers, contracts, delivery results, organizational structure and operational performance behind those identifiers.

A profile built from identifiers rather than biography

The public record around Lopez Penaloza Edson Max does not resemble a standard executive profile. It does not provide a supported account of education, career milestones, ownership history or a founding story. What it provides instead is a set of identifiers that can be aligned with unusual precision: the name LOPEZ PENALOZA EDSON MAX, RUC 10407058165, AS272997 and IPv6 prefix 2803:ed90::/32. The value of the profile lies in that alignment, not in filling biographical gaps with assumptions.

Each identifier belongs to a different administrative or technical system. The RUC distinguishes a supplier in Peruvian public records. An autonomous system number identifies a routing domain in the internet-number registry. An IPv6 prefix identifies a block of address space registered to an entity. A procurement resolution records an official public action, while procurement aggregators organize references to supplier and tender activity. No single record explains the entire operation, but the repeated identity makes the records relevant to one another.

That distinction is important because a sparse record can easily be overstated. An ASN may be treated as proof of a large network. A procurement appearance may be described as a completed contract. A supplier profile may be turned into a claim about revenue or customers. None of those conclusions follows here. The documents establish public visibility at specific points in the connectivity and procurement systems. They do not measure the commercial or operational activity behind those points.

The resulting story is therefore about traceability. Lopez Penaloza Edson Max can be located in a state-supplier context through one exact RUC and in a network-resource context through one exact ASN and one exact IPv6 block. This creates an accountability boundary around a named connectivity supplier. It allows readers to ask better questions about who is associated with the resources and procurement appearances, while keeping unanswered questions clearly separate from verified facts.

Keeping one exact identity in view

Name discipline is central to this profile. Lopez is a common surname, and the evidence does not authorize combining records merely because they include that word. The relevant boundary is exact: LOPEZ PENALOZA EDSON MAX, RUC 10407058165, AS272997 and 2803:ed90::/32. A record outside that combination may concern someone else, even if a partial name appears similar.

The official network records use two presentations of the same name components. The registrant entity is written as LOPEZ PENALOZA EDSON MAX, while the legal representative is shown as EDSON MAX LOPEZ PENALOZA. The order changes, but the component names remain the same. That internal consistency matters because it supplies a person-level bridge inside the registry itself. It is stronger than matching only a surname, and it avoids importing unrelated Lopez records into the analysis.

The RUC provides another safeguard. Procurement pages may normalize names differently, capitalize them differently or arrange personal names according to their own display rules. RUC 10407058165 gives the comparison a stable numeric anchor. When the official SUNAT document and supplier-oriented pages connect that number to Edson Max Lopez Penaloza, the identity claim rests on more than text similarity.

This does not mean every page carrying the RUC has equal authority. The SUNAT resolution is an official public document. The LACNIC entries are authoritative for the internet resources they describe. Procurement aggregators are secondary surfaces that help identify relevant activity, but their fields require confirmation from original records before detailed claims are made. Exact identity closure prevents person confusion; source hierarchy prevents a correct identity from being used to support an unsupported outcome.

The disciplined approach also affects language. This article does not shorten the subject to an ambiguous "Lopez" when a conclusion depends on identity. It uses Lopez Penaloza Edson Max or Edson Max Lopez Penaloza and keeps RUC 10407058165 nearby when discussing procurement. That repetition is functional. It preserves the boundary between this Peruvian supplier and other people whose names share only one element.

RUC 10407058165 is the procurement anchor

RUC 10407058165 is the strongest connector across the procurement-facing records. A name can be reordered or abbreviated, but the number remains specific. The TodoLicitaciones supplier profile for PE-RUC-10407058165 lists LOPEZ PENALOZA EDSON MAX as a Peruvian supplier and associates the identifier with internet-related service records. That supports a supplier identity and a connectivity-related procurement footprint.

The correct emphasis is on the identifier and the category of public appearance. A supplier profile does not establish the size of an enterprise, the number of staff, annual sales or the geographic reach of an operation. It also does not prove that every listed opportunity became a signed and performed contract. What it does is make the RUC searchable within a public procurement context and connect the exact supplier identity to internet-service activity.

This is useful because network registries and procurement systems answer different questions. LACNIC can say who is registered around a number resource. A procurement record can say which supplier identity appeared in a public purchasing process. RUC 10407058165 is the fixed point on the commercial-administrative side, just as AS272997 is the fixed point on the routing side. Aligning them through the exact name creates a more meaningful profile than either system could provide alone.

The RUC should not be treated as a substitute for an organizational chart. The supplier is presented under an individual's name, but the available public records do not describe employees, subcontractors, upstream providers or a separate operating company. Nor do they establish how decisions are divided between technical, commercial and administrative work. The number identifies the supplier boundary visible to procurement systems; it does not reveal every person or asset behind that boundary.

AS272997 is the strongest network anchor

The LACNIC RDAP record for AS272997 is the clearest technical source in the record. It identifies AS272997 as an active direct allocation, names LOPEZ PENALOZA EDSON MAX as the registrant entity and lists EDSON MAX LOPEZ PENALOZA as legal representative. Those fields place the exact subject of this profile at the center of a specific internet routing resource.

An autonomous system number gives a network a distinct identity in interdomain routing. It is the number other networks can use when exchanging and interpreting route information. That makes an ASN operationally meaningful, but its existence is not a performance certificate. The record does not state how much traffic AS272997 carries, which routes are currently announced, how many upstream relationships exist or how resilient the network is. It establishes registration and status, not a quality score.

The phrase "direct allocation" also has a bounded meaning. It strengthens the connection between the registry and the named holder because the record is not merely an informal reference on a marketing page. LACNIC is the authoritative regional registry for the resource. Yet direct allocation does not answer whether all connectivity sold under RUC 10407058165 traverses AS272997, whether the ASN is used for every customer, or whether other networks participate in delivery.

Active status must be read with the same care. It means the registry record presents the resource as active. It does not prove continuous route visibility, active customer sessions or a specific level of network utilization. Registry status and observed routing activity are related questions, but they are not identical. A complete operational assessment would require current routing observations and network disclosures that are not established by the cited records.

The independent IPinfo reference for AS272997 provides a secondary check that the ASN is recognized outside LACNIC's interface. Its role remains limited: LACNIC is authoritative for the allocation and named holder, while a third-party ASN page cannot establish traffic, peers, reach or performance.

Still, AS272997 is more than a decorative technical detail. It gives the supplier profile a precise network entity. Public procurement references show an internet-service context, while the ASN shows that the same named identity is registered around an autonomous system. The combination supports describing Lopez Penaloza Edson Max as a connectivity supplier with a documented routing-resource footprint, provided the article does not turn that footprint into claims about scale or results.

The IPv6 /32 adds a second technical anchor

The LACNIC RDAP record for IPv6 block 2803:ed90::/32 provides a second official network-resource link. It presents the block as active and associates it with LOPEZ PENALOZA EDSON MAX through the same LACNIC entity and representative chain. The matching identity across the ASN and IPv6 records reduces the chance that AS272997 is an isolated or misattributed reference.

An IPv6 prefix and an ASN describe different parts of network administration. The ASN identifies a routing domain. The prefix identifies address space that can be organized and routed. Having both records under the same identity creates a coherent registry surface for operating an IPv6-capable network, but it does not prove how the address block is subdivided, whether it is announced in full or in parts, or how much of it reaches end users.

The /32 notation should therefore be understood as a resource boundary, not as a customer or capacity count. Address space is not equivalent to deployed infrastructure. A registered IPv6 block does not disclose routers, fiber, wireless links, data-center presence, transit contracts or support systems. It does not establish that every internet service associated with RUC 10407058165 includes IPv6, nor does it show whether customer equipment receives IPv6 connectivity.

What the prefix does establish is administrative continuity. The same named supplier identity is visible around both an autonomous system and an IPv6 block. For public accountability, that continuity is useful because it makes the technical footprint more identifiable. If a procurement buyer or network counterpart needs to distinguish this operator from another similarly named supplier, AS272997 and 2803:ed90::/32 provide exact reference points.

The two registry entries also reveal an important constraint on public analysis. Registry records are strongest when answering identity and resource questions. They are weak when asked to answer service-delivery questions. The IPv6 record can support a statement that the resource is active and registered to Lopez Penaloza Edson Max. It cannot support a claim that a particular institution received IPv6 service, that deployment succeeded, or that the network met any technical target in a procurement.

The SUNAT resolution supplies an official procurement link

The procurement side gains its strongest official anchor from SUNAT resolution RSNAAF 221-2022. The document names EDSON MAX LOPEZ PENALOZA together with RUC 10407058165 in a public direct-contracting context. That exact pairing connects the person and supplier number in an official Peruvian record, independently of the procurement aggregators.

The resolution is evidence of a verifiable public decision context. It shows that the supplier identity entered a formal record connected to direct contracting. It should not be stretched beyond that purpose. The document's presence does not, by itself, establish the technical content of every service associated with the supplier, the value ultimately paid, the quality of performance or the resolution of any later contractual issue.

Nor should the fact that the document is a resolution be presented as evidence of wrongdoing. Administrative resolutions can record many kinds of public action. The relevant fact here is the identity and direct-contracting context described in the official document. Nothing in the available record supports an allegation, sanction narrative or adverse character judgment about Lopez Penaloza Edson Max.

The SUNAT record matters because it closes a gap that a secondary supplier page cannot close alone. The exact RUC and name appear in an official document. That allows the procurement identity to be compared responsibly with the LACNIC identity. The comparison does not depend only on a search-engine match or a commercially maintained profile; it rests on primary records in two separate domains.

At the same time, the SUNAT resolution and the LACNIC entries should remain distinct. One belongs to a public contracting process. The others belong to internet-number registration. Their common name supports identity alignment, but neither document states that AS272997 or 2803:ed90::/32 was used in the service underlying the resolution. The connection is person-level and supplier-level, not proof of a specific technical implementation.

Procurement aggregators reveal internet-service activity with limits

Secondary procurement pages add the category of service that the SUNAT identity record does not establish by itself. A TodoLicitaciones internet-service listing places PE-RUC-10407058165 among bidders in an internet-service context. That is relevant corroboration for describing the named RUC as a connectivity supplier rather than merely a supplier whose line of work is unknown.

The listing must be attributed to the aggregator and kept within its evidentiary limits. It can support saying that the RUC appears in an internet-service procurement record and in a bidding context. It cannot, without the underlying official files, support a detailed account of the award, the buyer's evaluation, the contract amount, the implementation schedule or final performance. Even when an aggregator displays an award-related identifier, the original record is needed before that field becomes a publication-grade claim.

The LicitacionesPeru profile for Lopez Penaloza Edson Max provides a separate public supplier profile. Its value is corroborative: another procurement-oriented service recognizes the exact individual supplier. It does not replace SUNAT as the official identity anchor or provide authority for conclusions that the public document and LACNIC records do not contain.

Using aggregators in this limited way helps avoid two opposite mistakes. The first is ignoring useful public leads simply because they are secondary. The second is treating a convenient summary page as if it were the complete procurement file. Here, the supplier and internet-service associations are useful. Detailed outcome claims remain reserved until original tender, award and contract-execution documents can be reviewed.

This restraint directly affects how the supply result is described. The records support a procurement appearance and an internet-service bidding role. They do not establish that every appearance resulted in an award, that an awarded service entered production, or that an institution accepted the work. Procurement participation, contract formation and completed delivery are separate stages. The cited pages make the first stage visible and point toward the second; they do not close the third.

The distinction also protects the individual from overstatement. A positive claim about successful delivery would be unsupported, but so would a negative claim about failure. The available pages do not provide a verified performance record either way. The responsible conclusion is procedural: RUC 10407058165 is publicly associated with internet-service procurement activity, while the exact commercial and operational outcomes remain open.

From procurement appearance to supplier outcome

Public procurement creates a chain of decisions, and the cited records illuminate only parts of it. A buyer defines a need. Suppliers may appear in a process. An administrative record may document a contracting route. A contract may then be signed, implemented, monitored and closed. The public footprint around Lopez Penaloza Edson Max confirms identity and participation at selected points, but it does not document every link in that chain.

The most defensible supplier outcome is therefore visibility, not quantified commercial success. RUC 10407058165 can be located in an official direct-contracting context and in internet-service procurement pages. That means the supplier identity reached formal public purchasing systems. It is a real organizational result because public-sector supply requires an identity that can be named and recorded. It is not the same as proving revenue, customer retention or satisfactory completion.

The network records add another outcome: technical resources are registered under the same individual identity. AS272997 and 2803:ed90::/32 create an identifiable internet-number footprint adjacent to the procurement footprint. This does not prove that a public buyer's traffic used those resources. It does show that the supplier identity associated with internet-service bidding is also associated with the administrative resources of an autonomous network.

For an institution evaluating a connectivity provider, those two forms of visibility answer different preliminary questions. The RUC helps identify the supplier in a contracting process. The ASN and prefix help identify a network-resource holder. Neither replaces due diligence on service design, authorization, financial capacity, support processes or past delivery. The public records narrow the identity question so that those later checks can be directed at the correct party.

This is also where claims about organizational success must stop. The record does not show an expanded team, a completed network build, a particular public institution connected, or a service-level target met. It shows that an individual supplier crossed two public thresholds: procurement visibility and resource-registry visibility. Those thresholds are meaningful, but they are the beginning of an operational assessment rather than its conclusion.

Technical and commercial constraints remain separate

Connectivity supply is constrained by more than possession of number resources. A provider may need access infrastructure, transport, upstream connectivity, routing policy, monitoring, customer equipment, installation capacity, support and administrative processes. AS272997 and 2803:ed90::/32 identify parts of the technical control surface, but the records do not disclose how the rest of that system is assembled.

Procurement introduces a different set of constraints. A public buyer may require defined scope, delivery timing, service levels, reporting and remedies. The cited procurement pages do not expose a verified set of terms for a particular completed service. As a result, the article cannot compare what was promised with what was delivered. It can identify the supplier and the internet-service context, but not score execution.

The separation matters because technical registration is sometimes mistaken for technical readiness. An ASN can exist before, during or after different phases of network activity. An IPv6 block can be registered without public evidence of customer deployment. Conversely, a supplier can provide connectivity using upstream or partner resources that do not appear under its own name. The records here do not establish which model applies to any specific procurement.

Commercial visibility is similarly incomplete. A bidder appearance does not reveal whether pricing was sustainable, whether capacity was reserved, whether equipment was available or whether a buyer accepted a proposal. Those questions relate to the constraints under which a supplier makes decisions, but the public evidence does not show the decisions themselves. Any account of motive or strategy would therefore be speculation.

What can be said is more modest. The named supplier maintained a public identity capable of appearing in procurement records and a separate registry identity around autonomous system and IPv6 resources. That combination may reduce ambiguity for counterparties, but it does not remove the practical constraints of delivering internet service. Registry coherence is an accountability asset, not proof that all operational dependencies were solved.

Organizational responsibility without invented titles

The records identify Lopez Penaloza Edson Max in two formal roles: registrant entity and legal representative within the LACNIC record. They also identify the same person and RUC in a supplier context. Those roles justify discussing responsibility for the public identities. They do not justify assigning titles such as founder, chief executive, network director or owner, because none of those titles is established here.

This distinction is especially important for an individual supplier. A RUC under a person's name can be the visible contracting boundary while technical or field work involves other parties. The records do not say whether work is performed alone, by employees, by contractors or through partnerships. They also do not identify who makes day-to-day routing, procurement or service decisions.

The legal-representative field creates accountability but not a complete governance map. It indicates who the registry presents in that role around AS272997. It does not define every legal obligation outside the registry or show how authority is delegated. Likewise, the registrant-entity field establishes the named resource holder but does not describe beneficial ownership of equipment or contractual rights in other infrastructure.

A careful profile can still draw an organizational conclusion. The public-facing identities are unusually consistent: the same name components appear around the ASN and IPv6 block, and the exact RUC ties the person to procurement records. This consistency makes it easier to trace questions to a defined subject. It does not prove that the underlying operation is simple, large, small, centralized or decentralized.

Responsibility here should be framed as a set of verifiable interfaces. The registry interface names the holder and representative. The procurement interface names the supplier. The internet-service listing identifies the service category in which the RUC appears. These interfaces show where public accountability begins. They do not reveal the private decisions, staffing arrangements or commercial relationships behind them, so the article leaves those matters open.

The public record shows decisions, but not their rationale

Several observable outcomes imply prior decisions without revealing why they were made. AS272997 was directly allocated and is active in the registry. IPv6 block 2803:ed90::/32 is active under the same entity chain. RUC 10407058165 appears in a direct-contracting document and internet-service procurement pages. These are durable public results, but the records do not contain a narrative from Lopez Penaloza Edson Max explaining the choices behind them.

It would be easy to label the network-resource combination as a deliberate growth strategy or a commitment to IPv6. That language would move beyond the evidence. The records show that the resources exist under the name. They do not disclose an application rationale, deployment plan, investment case or timing decision. A technical resource can support many operating models, and the public entries do not choose among them for the reader.

The same caution applies to procurement. Appearance in an internet-service process can indicate a willingness to compete or supply, but it does not reveal pricing logic, risk assessment, capacity planning or reasons for participating in one process rather than another. The SUNAT resolution records an official context, not the supplier's internal reasoning. Psychological interpretations or claims about ambition would add narrative without adding evidence.

There is still an analytical point to make. Public decisions become more accountable when they produce records that can be joined by exact identifiers. The RUC allows procurement appearances to be distinguished. The ASN and prefix allow network resources to be distinguished. The repeated name allows the two domains to be compared. This traceability is a documented result even when motive remains unknown.

For readers, the absence of rationale should direct the next inquiry rather than invite speculation. Useful questions would concern how AS272997 is used, whether the IPv6 block is deployed, which services were contracted, what obligations applied and what results were accepted. Those questions follow naturally from the public record. None has to be answered in advance by assigning a strategy or personality to the individual.

What counts as a documented organizational result

The first documented result is identity closure. LOPEZ PENALOZA EDSON MAX, EDSON MAX LOPEZ PENALOZA and RUC 10407058165 can be aligned without relying on a partial surname match. The second is technical registration: AS272997 and 2803:ed90::/32 are active and connected to the same LACNIC identity chain. The third is procurement visibility: the RUC appears in an official direct-contracting context and internet-service listings.

These results are organizational because they place a supplier in systems that require persistent identifiers. They allow a public buyer, network counterpart or researcher to distinguish the subject from unrelated providers. That distinction can support due diligence, troubleshooting and record review. It does not establish that such activities occurred in any particular case, but it creates the public reference points they would use.

Another result is cross-domain coherence. The procurement identity is not disconnected from the technical identity. The same person's name links the RUC-facing documents to the ASN and IPv6 records. Coherence reduces one form of uncertainty: who the records concern. It leaves other forms untouched, including the size of the operation, the architecture of service delivery and the outcome of contracts.

The record also shows a limit in organizational disclosure. No supported brand, corporate structure or team is visible in the cited sources. That may reflect the way an individual supplier is recorded, the narrowness of public documents or both. Whatever the reason, the article cannot convert a person-level identity into a corporate profile. The result is a map of accountable identifiers, not a complete organization chart.

Finally, the public footprint documents entry into two regulated or administered environments without demonstrating performance within them. Internet-number registration and public procurement both create responsibilities, but records of entry are not records of success. The profile can say that the supplier is legible in both environments. It cannot say that every technical or contractual responsibility was fulfilled, failed or even tested in the same engagement.

Failures and unresolved questions cannot be filled by inference

The public record does not document a specific service failure. There is no verified outage, breach of contract, rejected installation or adverse performance finding in the cited material. It would therefore be wrong to imply that Lopez Penaloza Edson Max failed to deliver connectivity. The absence of a proven failure is not proof of successful performance; it simply means the available records do not support either verdict.

The most important unresolved procurement question is outcome. The aggregator pages show supplier and internet-service activity, but original files would be needed to establish the buyer, evaluated offers, final award terms, signed scope, amendments, acceptance and payment. Without that chain, an award-related field on a secondary page remains a lead. It cannot carry a detailed account of public spending or supplier performance.

The main unresolved technical question is use. The records do not establish whether AS272997 currently originates routes, whether 2803:ed90::/32 is visible in global routing, which upstream networks are involved or whether the resources serve the same customers referenced by procurement pages. They also do not show access technologies, coverage, installed capacity, redundancy, monitoring or incident response.

Organizational structure remains unresolved as well. The cited records do not identify employees, contractors, a separate company, investors or a management hierarchy. They do not state who performs installations, operates equipment, negotiates transit or responds to customer issues. The legal-representative field and individual supplier identity create clear public points of reference, but they do not answer every responsibility question.

Commercial scale is another open area. Nothing here supports subscriber totals, revenue, market share, contract volume or expansion claims. Procurement profiles may collect multiple records, but counts and totals require careful review of the underlying documents and their status. Repeated appearances can show visibility without showing unique completed contracts, because one process may generate several public entries.

The biography is intentionally unresolved. There is no supported basis for describing the subject's education, previous employers, technical training, age, personal background or motivations. Those omissions prevent the article from becoming a conventional leadership narrative. They also keep attention on what the records actually make public: one supplier identity, one RUC, one ASN, one IPv6 block and a bounded procurement footprint.

These gaps are not a reason to discard the profile. They define its proper use. The article can serve as a verified starting point for further reporting or due diligence. It cannot serve as a substitute for contract files, routing measurements, corporate records, interviews or service-performance data. Naming the unresolved questions is part of accurate reporting because it prevents an identifiable footprint from being mistaken for a complete operational history.

A practical framework for verifying future claims

Future claims about Lopez Penaloza Edson Max should first pass an identity test. Does the record contain RUC 10407058165, AS272997 or 2803:ed90::/32, together with the full name? If not, a shared surname is limited public evidence. This first step prevents unrelated Lopez records from entering the profile and protects every later conclusion from a basic attribution error.

The second test is source authority. LACNIC should remain the primary reference for the ASN and IPv6 registration. SUNAT should remain the primary reference for its own resolution. Procurement aggregators can identify useful leads, but details about award, contract and performance should be checked against original public files. IPinfo can cross-check the ASN, but it should not displace the registry on allocation identity.

The third test is stage. A bidder record is not necessarily an award. An award is not necessarily a signed contract. A signed contract is not necessarily a completed installation. A completed installation is not necessarily proof of sustained quality. Any future account should state exactly which stage a document proves and avoid carrying a conclusion from one stage into the next.

The fourth test is technical scope. Registration of an ASN and prefix does not prove routing visibility, customer deployment or service performance. Those claims require observations or documents suited to those questions. If future evidence shows route announcements, that would establish a different fact from allocation. If a contract names AS272997 or the IPv6 block, that could create a service-specific bridge that the current records do not provide.

The final test is outcome language. Positive and negative judgments both require evidence. Claims of reliable delivery, growth or technical leadership are unsupported here, just as claims of failure or misconduct are unsupported. The strongest current wording remains descriptive: the exact individual supplier is documented in public procurement contexts and as the holder of active internet-number resources.

This framework keeps the profile useful over time. New records can be added without changing the identity boundary or lowering the evidentiary standard. A verified contract, routing observation or organizational filing would answer a specific open question. Until then, the existing record should not be made to answer questions outside its scope.

A measured conclusion about Lopez Penaloza Edson Max

Lopez Penaloza Edson Max can be described with confidence as a Peruvian individual supplier whose public identity spans connectivity procurement and internet-number registration. SUNAT resolution RSNAAF 221-2022 names EDSON MAX LOPEZ PENALOZA with RUC 10407058165 in a direct-contracting context. Procurement-oriented pages connect that RUC to a supplier profile and internet-service activity.

LACNIC provides the technical core. AS272997 is an active direct allocation registered to LOPEZ PENALOZA EDSON MAX, with EDSON MAX LOPEZ PENALOZA shown as legal representative. Active IPv6 block 2803:ed90::/32 follows the same entity chain. These records establish a coherent technical identity, while IPinfo supplies only a secondary ASN cross-check.

The records do not establish a traditional leadership biography, a company ownership structure, customer count, revenue, geographic coverage, routing topology or service quality. They also do not prove the detailed award, execution or acceptance of an internet-service contract. No supported finding of success, failure or misconduct follows from the available material.

The defensible result is traceability. RUC 10407058165 identifies the supplier boundary in public purchasing records. AS272997 and 2803:ed90::/32 identify the network-resource boundary. The exact name connects them without merging unrelated Lopez records. That alignment makes the supplier publicly legible and provides a sound starting point for future verification.

What remains is a set of answerable questions rather than a finished corporate story: how the autonomous system and IPv6 block are used, which procurement appearances became contracts, what services were delivered, how the operation is organized and what outcomes buyers experienced. Until primary records or direct measurements answer them, the most accurate profile is the bounded one the public evidence supports.