Summary

  • LACNIC binds the exact identity PELOSA JAVIER ALBERTO (NORDESTE TELECOMUNICACIONES) to active AS273942, IPv4 allocation 200.107.68.0/22 and IPv6 allocation 2803:8f50::/32.
  • RIPEstat saw three component IPv4 /24s through 327 of 328 IPv4 RIS peers at its 27 July 2026 snapshot, while it saw no IPv6 prefix from the ASN.
  • Exact-prefix RPKI validation was valid for all four IPv4 /24s and the IPv6 /32, demonstrating that origin authorization can exist without a visible route.
  • ENACOM granted Javier Alberto Pelosa a TIC and Internet-access licence in 2020, then cancelled that named licence effective 24 October 2022 following his request.
  • The evidence does not identify any later licence holder or prove that current routing is unauthorized; it defines a permission and operator-continuity question that remains open.

1. One Network Identity, Four Accountability Layers

AS273942 is easy to find in public technical records. It is harder to say exactly what each record proves. A regional number registry associates the autonomous-system number and two address allocations with a named registrant. RPKI data authorizes that ASN to originate specific prefixes. BGP collectors show which origin-prefix relationships are visible at a particular time. A national regulator records whether a named person holds a communications-services licence.

Those systems overlap, but none is a substitute for the others. A regulator does not allocate globally unique IP addresses. A registry does not determine whether a person currently satisfies every national service rule. A ROA does not send a route. A BGP announcement does not carry a licence certificate. Treating one layer as a universal answer creates false confidence precisely where accountability should be most exact.

Nordeste Telecomunicaciones makes the separation unusually legible because the timelines diverge. ENACOM's cancellation has effect from October 2022. LACNIC registered AS273942 and its address resources in September 2024. RIPE's current snapshot then sees three IPv4 /24s from that ASN in July 2026. The later technical identity plainly exists. The captured sources do not explain the legal or commercial arrangement under which it is used.

That unresolved space must remain unresolved. A licence may have moved to another legal entity. A wholesale provider may carry connectivity under a different permission structure. A trade name may have been retained after a corporate change. The network may serve a purpose outside the assumptions a reader brings to the word "Internet provider." None of those possibilities is established here.

The defensible finding is narrower and more useful. Public records expose a working network-resource surface while leaving the present permission holder unproved. This is not a verdict on legality. It is a reminder that operational continuity can cross administrative boundaries, and that each boundary needs its own evidence.

2. The Exact Name Prevents a Brand-Only Shortcut

The public profile and LACNIC registrant record use the same combined identity: PELOSA JAVIER ALBERTO (NORDESTE TELECOMUNICACIONES). That wording matters. It joins a person's legal name to a trade name without inventing a separate company, subsidiary or ownership structure. The LACNIC entity handle is AR-NOTE1-LACNIC, and its status is validated.

The autonomous-number record points to that same handle as registrant. It also names Javier Pelosa as legal representative and JAP128 as the administrative, technical and abuse contact. These fields create an accountable registry chain. They show who is recorded for the resource and who is named for coordination. They do not establish who owns a router, signs a customer contract or operates every part of the delivery path.

Keeping the combined identity intact avoids two opposite errors. One is to reduce the subject to the brand "Nordeste" and accidentally mix it with an unrelated company. The other is to treat the parenthetical trade name as proof of a corporation that the records do not name. The source language already provides the correct boundary, so there is no reason to enlarge it.

The registrant address points to Posadas, Argentina. It can help distinguish the record and direct contact. It is not a coverage map. A registry address does not prove that customers, upstreams, routers or cable routes are located in the same city. Nor does it establish that the entire network is operated from that address.

Identity precision is not bureaucratic ornament. Routing incidents, abuse reports, peering requests and due-diligence questions all depend on matching the right resource to the right accountable subject. The exact person-and-trade-name record is the stable join across the ASN, address space and regulatory history. Everything beyond that join requires separate proof.

3. AS273942 Arrived After the Licence Timeline

LACNIC registered AS273942 on 24 September 2024 and marked it active. The record directly associates it with AR-NOTE1-LACNIC. An autonomous-system number gives a routing policy domain a unique public identifier. It allows peers and observers to attribute BGP announcements, apply filters, validate origins and coordinate incidents.

The date belongs to the number resource, not necessarily to the start of the business. It should not be called a founding date, a service launch or the moment the trade name began operating. ENACOM's earlier record already proves that Javier Alberto Pelosa had sought and obtained Internet-service permission years before the ASN registration.

The reverse is also true. The existence of a later ASN does not renew an earlier licence. Number-resource assignment and national service authorization follow different administrative processes. A registry can accurately record a resource holder without deciding the legal basis for every service the holder may provide in a country.

RIPEstat says the ASN was first seen with the covering IPv4 /22 on 23 May 2025. That observation comes after both the resource registration and the effective date of the licence cancellation. It confirms a later running-code event, but it does not explain the contractual or regulatory context around that event.

The chronology is therefore a question generator rather than a conclusion. What entity, permission or service arrangement supported the later route? Did the trade name migrate into another corporate structure? Was the ASN used for wholesale interconnection, internal connectivity or another role that does not map neatly onto the cancelled personal licence? The captured records do not answer.

AS273942 remains operationally important even with those unanswered questions. It provides a durable identifier around which routing observations, RPKI authorizations and contact metadata can be organized. Its value is traceability, not a presumption that every surrounding legal fact has been resolved.

4. A /22 Allocation Contains More Than the Visible Route Set

LACNIC assigns IPv4 block 200.107.68.0/22 to the same registrant and records AS273942 as its origin autonomous system. The allocation spans 200.107.68.0 through 200.107.71.255, a total of 1,024 IPv4 addresses. Its status is active.

Allocation size must not be confused with current global routing. RIPEstat's announced-prefix response for 13 to 27 July 2026 lists three more-specific routes: 200.107.68.0/24, 200.107.69.0/24 and 200.107.70.0/24. It does not list 200.107.71.0/24, and it does not list the covering /22 throughout that requested interval.

The three visible /24s cover 768 addresses. That arithmetic describes announced address space, not active customers or utilized addresses. A routed prefix can contain unused addresses, infrastructure addresses, customer assignments, translation pools or other arrangements that are invisible from BGP. The public route says nothing about how densely the space is used.

The unlisted fourth /24 illustrates another boundary. It remains inside the active registered /22, and it has an exact valid ROA for origin AS273942. Yet it is not part of the observed announcement set. Registration and authorization preserve the option to originate it. They do not demonstrate that the option is currently exercised.

More-specific announcements can be used for traffic engineering, policy separation, filtering convenience or operational segmentation. None of those explanations can be selected from the captured data. Three /24s should not be described as three sites, three upstreams, three customer zones or three independent networks.

The correct state description is simple: the registrant holds an active /22; three component /24s are visible from AS273942 in the dated observation; the fourth component /24 is not visible there. That statement preserves both the registry ledger and the running route without turning either into an unsupported infrastructure story.

5. Collector Visibility Is Broad but Not Universal Truth

The RIPE routing-status snapshot reports that 327 of 328 IPv4 RIS peers see AS273942. Within that collector set, the three visible /24s therefore have broad reach. The same response reports two observed neighbours and a last-seen route of 200.107.70.0/24 from origin 273942 at 27 July 2026, 08:00 UTC.

High collector visibility is strong evidence of a public BGP announcement. It is not a performance certificate. RIS peers sample route propagation from specific observation points. They do not measure end-user latency, packet loss, throughput, availability or repair time. A route can be widely visible while the service behind it experiences local problems, and a route can be absent from one collector view while still existing in a limited context. The neighbour count is similarly bounded. Two observed neighbours in the response do not prove two physical circuits, two providers or complete redundancy.

A BGP neighbour can be reached through many physical arrangements, and the collector view may not expose every relationship. Contract terms, shared facilities and common failure domains remain unknown.

The visibility ratio also cannot reveal customer geography. BGP propagation is global control-plane information. It says that other networks can learn a route, not where access lines terminate or where subscribers live. The exact registrant address in Posadas does not change that limitation.

What the snapshot does provide is a dated, reproducible running-code fact. AS273942 was not merely reserved in a registry. Three IPv4 routes were being seen widely enough to appear across almost the entire IPv4 RIS peer set. That evidence deserves weight, but only for the question it actually answers.

Operational accountability improves when observations are phrased with their scope. "Visible to 327 of 328 RIS peers at the captured time" is stronger than a vague claim that the network is online, because it states the measurement and leaves room for what the measurement cannot see.

6. RPKI Validity Depends on the Exact Prefix

RPKI validation for the four component IPv4 /24s returns a valid result for origin AS273942. Each response includes an exact /24 ROA with maximum length 24. Those exact records authorize the origin-prefix combinations used in the validation request.

The same responses also show a covering ROA for 200.107.68.0/22 with maximum length 22. When that /22 authorization is evaluated against a /24, its validity is invalid_length. This is not a contradiction in the final result. The exact /24 authorization supplies a valid match, while the parent authorization is too restrictive to validate a more-specific route.

That detail demonstrates why RPKI cannot be summarized by saying that "the block has a ROA." Prefix length is part of the security policy. A holder may authorize a covering aggregate without authorizing more-specific announcements, or publish additional exact records for the more-specifics it expects to originate. Validators evaluate the route against the available set.

For the three visible /24s, the exact ROAs align with the observed origin. A receiving network using route-origin validation can classify those origin-prefix pairs as valid. That reduces one class of accidental or unauthorized origin mismatch. It does not secure the entire BGP path, prove route availability or prevent every form of hijack.

The fourth /24 has the same exact authorization but is not visible in the announced-prefix set. This is useful counterevidence to a common assumption: valid does not mean announced. The RPKI state describes permission within the routing security system. The BGP collector describes current observation.

Good stewardship requires both records to remain accurate. Exact authorizations should match intended routing policy, and operators should remove stale permissions when they no longer serve continuity or planned deployment. The public data does not establish whether the unseen /24 is staged, reserved or stale. It only makes the difference observable.

7. IPv6 Is Registered and Authorized but Unseen

The IPv6 allocation 2803:8f50::/32 is active, registered to AR-NOTE1-LACNIC and records AS273942 as origin. An exact /32 ROA with maximum length 32 validates that origin-prefix pair. The administrative and route-origin authorization layers are therefore present.

RIPEstat's routing-status snapshot sees no IPv6 prefix from the ASN. Zero of 324 IPv6 RIS peers in the response sees AS273942. The announced-prefix set also contains only the three IPv4 /24s. In the captured view, the IPv6 resource stops before the public running-route layer. That state should not be described as failure. Operators often receive address space before deployment, authorize a prefix ahead of a change window or retain resources for continuity. The prefix could also be used in a private or narrowly visible context that does not meet the collector threshold. None of those possibilities is confirmed.

Nor should the /32 be presented as deployed capacity. IPv6 allocation size reflects address architecture, not subscriber count or traffic. A single /32 can support extensive hierarchical delegation, but no delegation plan, customer assignment, DNS configuration or access-device support appears in the source set.

The valid ROA remains useful even without a visible route. It establishes the intended origin if the exact /32 is later announced. Monitoring systems can watch for that transition and compare it with policy. The authorization also makes an unexpected different origin easier to evaluate.

The evidence supports a precise dual-stack sentence: Nordeste has registered and RPKI-authorized IPv4 and IPv6 resources, while only three IPv4 /24s are visible from AS273942 in the dated RIS observation. Anything stronger would replace measurement with assumption.

8. The 2020 Licence Granted Permission, Not Assets

ENACOM Resolution 144/2020 granted Javier Alberto Pelosa a licence to provide information and communications technology services. The language covers fixed or mobile, wired or wireless, national or international services, with or without the licensee's own infrastructure. It also registered value-added Internet access service.

That wording establishes the named regulatory subject and a service category relevant to connectivity. It does not inventory what was built. "With or without own infrastructure" expressly allows service provision through arrangements that may include leased capacity or third-party facilities. The resolution cannot prove towers, poles, ducts, fibre routes, radio links, data-centre space or customer equipment.

The spectrum clause is equally clear. The licence did not oblige the state to guarantee radio-frequency availability, and any spectrum authorization or permit had to be handled separately. A reader cannot infer licensed frequencies, tower coverage or a fixed-wireless footprint from this record.

The broad list of permitted service forms also does not prove that each form was offered. Legal permission creates a field within which service may be provided. Actual deployment requires separate technical and commercial evidence. The later number-resource records provide one technical surface, but they still do not reveal the access method.

The resolution's strongest contribution is identity continuity. It names Javier Alberto Pelosa, the same person embedded in the LACNIC registrant identity. It therefore links the network-resource subject to a historical Internet-service permission without relying on brand similarity.

Permission should be read as permission. It is neither a network map nor a quality score. That restraint becomes even more important once the cancellation record is added, because a historical grant cannot be silently carried forward after the regulator says it ended.

9. The Cancellation Is Exact and Narrow

ENACOM Resolution 221/2024 cancelled the TIC licence and Internet-access registration granted to Javier Alberto Pelosa under Resolution 144/2020. The measure took effect from 24 October 2022. The full resolution states that Pelosa had requested the cancellation on that date.

The record is exact about the named permission. It should not be softened into a vague claim that the licence merely became uncertain. At the same time, it should not be expanded into a claim that every later use of the trade name or ASN is illegal. The cancellation attaches to the licence and registration described in the resolution.

National communications markets allow many legal and commercial structures. A service can be supplied through a company rather than an individual. A network can carry wholesale traffic, private connectivity or support functions that require different analysis. Assets and trade names can move. The captured sources contain no later licence search result, corporate filing or contract that resolves those possibilities.

The cancellation's retrospective effective date is also important. The resolution was signed in June 2024 and published in July 2024, but its effect is stated as October 2022. That makes the regulatory timeline earlier than the ASN registration in September 2024. It does not make the ASN record inaccurate; it shows that the two systems record different entities.

An ASN is a globally unique routing identifier. LACNIC's role is to keep its allocation and contacts accurate under registry policy. ENACOM's role concerns national service permission. Neither record should be forced to answer the other's question.

The proper conclusion is a bounded gap: the named personal licence ended, while a later network-resource identity became active and now has visible routes. Identifying the current permission or operating entity requires evidence that is not present. The gap is reportable because it affects accountability, not because it proves wrongdoing.

10. Cancellation Does Not Mean the Routes Stopped

The technical data shows that routing activity continued or emerged after the licence timeline. RIPEstat's first-seen field associates the covering IPv4 /22 and origin AS273942 with 23 May 2025. The July 2026 snapshot sees three component /24s. Running code therefore exists later than the cancellation's effective date.

This chronology can be described without making a legal allegation. BGP does not validate a national licence before accepting an announcement. Peers apply routing policy, technical filters and commercial arrangements. RPKI validators check origin authorization, not telecommunications permission. A route can be technically valid in RPKI while the public evidence for a service licence is incomplete. The reverse condition is also possible in many networks. A fully licensed operator can have no globally visible ASN because it buys wholesale access, uses provider-assigned space or operates only at another layer.

Regulatory permission and routing visibility are related to service delivery, but neither is a universal proxy for the other.

Nordeste's records expose the gap cleanly because the RPKI state is valid. The visible IPv4 announcements are not presenting an obvious origin mismatch in the captured validator data. The unresolved issue sits outside that technical gate: which current legal or contractual structure surrounds the routing identity?

That question belongs to due diligence, not automatic condemnation. A prospective peer might ask for the contracting entity and authority to operate. A regulator might reconcile the resource holder with current licence records. A customer might ask who bears service obligations. Those are requests for missing context.

The public route should remain what it is: evidence that routing code is running and widely visible. It should not be treated as proof that a cancelled permission somehow remains valid, and it should not be treated as proof that no valid successor arrangement exists.

11. Registry Records Are a Ledger, Not a Sovereign

LACNIC's records perform a foundational Internet function. They keep autonomous-system numbers and address blocks unique, associate them with holders and contacts, and expose events that help observers understand changes. Without that ledger, route filtering, incident response and transfer accountability would be far harder.

The registry does not become a national licensing authority by recording an ASN. Its active status means the resource is active within the registry system. It does not certify compliance with every telecommunications, tax, consumer or municipal rule that may apply to a service.

This limitation does not diminish the registry. It clarifies why the data is trustworthy. A recordkeeper is strongest when it says exactly what has been recorded and leaves other decisions to the institutions and operating systems designed to make them. Expanding a registry field into a universal legitimacy claim would make it less accurate, not more powerful.

The same discipline applies to geographic interpretation. LACNIC serves a regional resource community, but an address block is not owned by a geography in the same sense as land. Routes cross borders, businesses change structure and operators use resources through complex supply chains. The recorded holder and policy status are concrete; broad claims about territorial legitimacy are not supplied by the RDAP response.

Nordeste's record is useful precisely because it remains stable enough to join multiple observations. The registrant name, ASN, prefixes and contacts can be compared with RPKI and BGP. The cancellation record can then be placed alongside them without pretending that LACNIC decided its effect.

Accountability improves when each institution's role stays bounded. The registry keeps the resource ledger. The regulator records permission. Operators run routers. Peers decide what to accept. Observers compare the layers and state where they agree or diverge.

12. Running-Code Primacy Has a Limited Meaning

Running-code primacy means that a configured and observed route tells us more about current technical behavior than a business description or allocation alone. Three /24s from AS273942 are visible across 327 IPv4 RIS peers. That is a real operating fact at the captured time.

Primacy does not mean supremacy over law or contract. BGP's ability to propagate a route does not settle who may sell a service, who owns a trade name or who must answer a consumer complaint. It means that operational claims should be tested against the systems that actually carry them. The distinction prevents two forms of storytelling. One treats administrative records as if they automatically create a working network. The other treats a working route as if it automatically proves every administrative permission. Both erase the boundaries that make the evidence informative.

For Nordeste, running code confirms that the ASN is more than an unused identifier. RPKI confirms that the observed origin is authorized for the exact visible prefixes. The registry confirms the holder. The regulator confirms that one named licence ended. No single layer resolves the complete picture.

Operational continuity can persist through changes in entity, licence, supplier or ownership. That continuity is often valuable: renumbering and route migration are costly, and stable resources can reduce disruption. But continuity also creates a need for accurate contact, transfer and permission records so that stability does not become opacity.

The current evidence supports both statements at once. There is observable routing continuity, and there is an unresolved current-authority boundary. Holding those facts together is more rigorous than choosing the one that fits a preferred narrative.

13. Operator Continuity May Survive a Legal Change

Networks are assembled from resources and relationships that do not always change on the same day. An ASN can remain stable while a business incorporates, changes owners, adopts a trade name or replaces an upstream. Address space can be retained during a migration. ROAs can be updated before or after route changes.

That operational reality makes portability important. Stable number resources can preserve filters, customer allowlists, reputation and routing history. Abrupt renumbering can impose costs on customers and peers. Continuity is therefore not inherently suspicious; it is often a legitimate engineering goal.

The accountability requirement is that legal and registry records stay sufficiently accurate for others to understand who controls the resources. Here the exact registrant still names Javier Alberto Pelosa and Nordeste Telecomunicaciones. The named personal licence was cancelled. No source in the set identifies a successor licence or a new legal holder.

Several transitions are possible, but none can be selected as fact. The individual may remain the resource holder while another entity provides service. A later entity may operate under agreement. The routes may support a narrower network function. The public profile may lag a change. These are hypotheses for verification, not material for assertion.

A useful continuity review would ask for documents or current public records that connect the ASN to the operating and contracting entity. It would also ask whether LACNIC contact fields reflect present authority and whether abuse reports reach the responsible team. Those checks would close the gap without forcing a disruptive resource change.

The record now available establishes the need for that review. It does not establish its outcome. That is the difference between a reality-layer finding and advocacy.

14. Contact Metadata Reduces Coordination Cost

The ASN and both address allocations name JAP128 for administrative, technical and abuse roles. Publicly registered contact functions are part of operational continuity. They give peers, incident responders and affected parties a place to direct questions about routing or resource use.

One person or handle covering several roles may be efficient for a small operator. It can also concentrate responsibility. The record does not show staffing depth, response hours, escalation paths or whether the listed contact remains current. Those factors would require direct testing or additional evidence.

Abuse-contact economics matters because unresolved incidents impose costs outside the originating network. Spam, compromised hosts, misrouting and policy disputes all create work for other operators. Accurate contacts reduce the search cost of finding the responsible party. Inaccurate or unanswered contacts transfer that cost to the wider ecosystem.

The validated registrant status and consistent handle relationships are positive administrative signals. They show that the resource entities are not anonymous. They do not prove fast remediation, strong security practice or continuous monitoring.

Contact data also does not resolve the licence boundary. The person who maintains RDAP records may not be the legal entity contracting with customers. A technical contact may act for multiple organizations. Registry accountability and consumer-service accountability can overlap without being identical.

The responsible conclusion is that AS273942 has a legible registry contact chain. Whether that chain maps to the current service operator and permission holder remains an open question that can be asked directly.

15. The Evidence Cannot Describe the Access Network

The historical licence allowed wired or wireless services, with or without owned infrastructure. That breadth is a warning against selecting an access technology without proof. The sources do not establish fibre-to-the-home, fixed wireless, cable, leased-line delivery or a mixture.

The generic trade name and public routing footprint may invite assumptions about a regional ISP. Those assumptions are not substitutes for network diagrams, municipal permits, spectrum records, equipment inventories or customer-facing technical documentation. A routed /24 cannot tell an observer whether the final hop is optical or radio. Facilities are equally unproved. The record does not identify a data centre, point of presence, tower, exchange port or street cabinet. Two observed routing neighbours are not two physical sites. The registered address is not automatically a network facility.

Capacity claims would be even weaker. Address counts and prefix lengths do not measure bandwidth. Peering-database self-descriptions, where available, would still require careful treatment and are not part of this evidence set. No traffic graph, interface capacity, utilization sample or contract has been captured.

Outage and resilience claims also remain outside scope. The source set contains no incident history, power design, path diversity, backup arrangement or repair-time measurement. Broad route visibility at one snapshot does not establish redundancy. A single failure domain can sit behind multiple BGP relationships.

Restraining these claims makes the network-resource finding stronger. AS273942, its allocations, exact ROAs and visible routes are sufficiently specific to stand on their own. They do not need an invented physical network around them.

16. What Peers and Customers Can Verify Next

A prospective peer can begin with the exact resource set. It can verify that the advertised /24s originate from AS273942, that the exact ROAs remain valid and that contact information matches the party presenting the peering request. It can ask whether 200.107.71.0/24 and 2803:8f50::/32 are reserved, staged or intentionally unannounced.

The peer can also ask for the contracting legal entity and the authority under which the network operates. That request is not answered by RPKI. It belongs beside the technical checks because commercial and operational responsibility must ultimately attach to a party that can sign and perform an agreement.

Customers can ask a different set of questions. Who provides the service and issues invoices? Which entity handles support and complaints? What access technology reaches the location? Which service levels are contractual rather than inferred from public routing? The current records do not answer those questions.

Regulatory reconciliation could focus on the named cancellation and any later authorization. If a successor entity exists, linking that entity publicly to the trade name and network resources would reduce ambiguity. If the ASN supports a role that does not require the assumptions made here, a clear explanation would also help.

Operators can improve the technical side by keeping RDAP contacts current, reviewing ROAs when routing plans change and documenting whether unused prefixes are reserved. None of those steps requires publishing sensitive topology. They are basic forms of externally legible stewardship.

The next useful evidence is therefore not a larger profile. It is a precise bridge between current legal authority and the already precise technical identity.

17. A Monitoring Baseline for AS273942

The captured data creates a repeatable baseline. On 27 July 2026, AS273942 is active in LACNIC, and the registrant identity matches the public profile. The holder has an active IPv4 /22 and IPv6 /32. Four component IPv4 /24s and the IPv6 /32 have exact valid origin authorizations.

Three IPv4 /24s are present in the dated announced-prefix set. The routing-status response reports 768 announced IPv4 addresses, 327 of 328 IPv4 peers seeing the ASN, no visible IPv6 prefixes and two observed neighbours. The last-seen entry names 200.107.70.0/24.

Future observations can be compared with this baseline. A fourth IPv4 /24 might appear. IPv6 might become visible. An exact ROA might change. The registrant or contact handle might be updated. Each event would describe a change in one layer and should not be overinterpreted as a change in every other layer.

The regulatory baseline is different: the named Resolution 144/2020 licence and Internet-access registration were cancelled effective 24 October 2022. Any current permission claim needs later evidence. Silence in this source set is not proof that no later evidence exists.

Monitoring should therefore keep two timelines. The technical timeline tracks resource and route state. The permission timeline tracks the legal entity and authorization relevant to service. Joining them only when an exact document or record supports the link prevents accidental legal claims.

This baseline is valuable because it can be falsified. If a later registry response, route snapshot or licence record differs, the change can be dated and explained. That is better than a static label such as "active ISP," which hides what active means.

18. Network Legibility Begins With Bounded Claims

Nordeste Telecomunicaciones has a legible public network-resource identity. The combined person and trade name matches across the public profile and LACNIC. AS273942 is active. The registered IPv4 and IPv6 blocks have exact origin authorizations. Three IPv4 routes are broadly visible in RIPE's dated collector view.

The same evidence also contains meaningful limits. One IPv4 /24 and the IPv6 /32 are authorized but unseen. The named personal Internet-access licence was cancelled with effect before the ASN was registered. No captured record identifies a current successor licence, legal migration or service arrangement.

Those limits are not defects to be hidden with generic business language. They are the central accountability finding. A registry is a ledger of resources and contacts. RPKI is security metadata for route origins. BGP is running code observed through peers. A national licence is permission attached to a named subject. Each layer remains necessary because none can replace the others.

The result is neither an endorsement nor an accusation. It is a bounded description of what can be seen and what still needs verification. Current routing cannot be called unlawful from these records, and historical permission cannot be treated as current merely because routes are visible.

For peers, customers and regulators, the shortest unresolved question is the same: which present legal or contractual entity stands behind AS273942 and Nordeste Telecomunicaciones? Answering it would connect an already clear technical identity to an equally clear operating authority.

The answer can be documented without exposing sensitive topology. A current licence or registry reference can identify the authorized service provider. A contracting notice can identify the entity responsible to customers and peers. An updated RDAP record can show whether the resource holder or contact chain changed. A brief statement about the purpose of the ASN can distinguish retail access from wholesale, private or transitional use. Each item would close a specific gap while leaving router locations, commercial terms and security details private.

Until such evidence is available, observers should keep the layers separate, preserve the dated nature of the route snapshot and avoid converting technical continuity into either a legal endorsement or a legal accusation.

Until then, the public record supports one firm conclusion. AS273942 demonstrates operational continuity, but continuity alone does not collapse permission, registration, authorization and routing into a single proof.

Sources