Summary

  • LACNIC binds active AS22080, active AS61518, 200.112.160.0/19 and 168.121.212.0/22 to Broadbandtech S. A.
  • RIPEstat observed 59 prefix entries for AS22080 during the reviewed interval, with full IPv4 visibility from 329 of 329 responding RIS peers at the last observation.
  • AS61518 remains active in the registry but had no current RIS-announced prefix and no current IPv4 or IPv6 visibility in the captured routing status.
  • The reviewed BGP snapshot exposed several immediate pre-origin autonomous systems, led by AS52361, but did not disclose complete topology or commercial relationships.
  • Two exact AS22080 origin-prefix checks were RPKI-valid; those examples do not establish universal authorization coverage or operational security.

1. Two Registry Identities, Two Different Operational Signals

Broadbandtech S. A. is not represented in public number-resource records by a single identifier. LACNIC's RDAP service records both AS22080 and AS61518 as active autonomous systems under the same organization name. That shared registrant is the starting point for a bounded company-network analysis.

The routing layer does not mirror the registry symmetrically. AS22080 appears throughout the reviewed RIPEstat material, with a long observation history, dozens of prefix entries and broad IPv4 visibility. AS61518, despite remaining active in the registry, produced no current announced-prefix result in the captured view.

That difference is more informative than a generic profile of a telecommunications company. It shows how an organization can maintain more than one valid administrative routing identity while only one has a visible current role in the public collector data being examined. The distinction is factual, dated and independently reproducible.

It is not a verdict on the second ASN. The evidence does not establish whether AS61518 is dormant, reserved, used privately, visible through another measurement system or held for a future purpose. A quiet public signal creates a monitoring question, not a licence to invent an explanation.

2. The Exact Company Boundary Comes First

The relevant directory object is Broadbandtech S. A. at the Argentina-specific slug broadbandtech-s-a-ar. The authoritative production check identifies one published company entity for that route and excludes an older archived same-name alias. That exact boundary prevents the network evidence from drifting onto a similarly named organization.

LACNIC independently reinforces the identity match. Both autonomous-system records use Broadbandtech S. A. as the organization and refer to the same registrant handle. The administrative, technical and abuse-contact handle is also consistent across the two records. Those matches support one two-AS registry identity.

Identity closure is necessary but not sufficient for every later claim. It establishes which company is recorded against the resources. It does not prove that both ASNs support the same product, that every address is used by the company itself or that the organization's marketing accurately describes delivered service.

Keeping the identity boundary narrow also preserves future auditability. If a route changes origin, an ASN becomes visible or a resource is transferred, the comparison can be made against a fixed entity and exact directory path rather than an ambiguous brand label.

3. LACNIC Records AS22080 as the Older Autonomous System

LACNIC marks AS22080 active and records an event dated 2 August 2001. That age gives the autonomous system a substantially longer administrative history than AS61518. The record connects the number to Broadbandtech S. A. and supplies the stable identity used by other measurement systems.

A registry record is best treated as a ledger entry. It preserves uniqueness, assignment history, holder identity and operational contact metadata. It does not monitor every router, verify commercial agreements or certify that a route is functioning. Its authority is administrative and referential rather than all-seeing.

AS22080 becomes operationally meaningful when that ledger entry is compared with running routing data. RIPEstat's first-seen record also reaches back to 2001, while the reviewed last-seen timestamp was current to 28 July 2026. The two layers therefore align on a long-lived and presently visible routing identity.

That alignment still says nothing about Broadbandtech's customer count, access technology or service quality. It identifies a durable public edge from which narrower questions about announcements, authorization and adjacent networks can be asked.

4. AS61518 Is Active in the Ledger but Quiet in the Reviewed Routing View

AS61518 has a later LACNIC registration event, dated 17 January 2020. Its status remains active, and the registrant information closes on the same company identity as AS22080. Administratively, the second autonomous system is not an expired or unrelated record.

RIPEstat returned no current announced prefixes for AS61518. Its routing-status response recorded historical first-seen and last-seen information, with the last observed route in February 2020, while current IPv4 and IPv6 visibility were both zero in the captured response.

The correct statement is therefore deliberately limited: the ASN remains active in LACNIC's registry but was not currently visible as an origin in the reviewed RIS data. “Active” and “announcing” describe different layers, and the public records show that they do not always move together.

Nothing in the source set explains the quiet state. It would be speculative to call AS61518 abandoned, private, unused, reserved or failed. The operationally responsible posture is to retain the ASN in monitoring and record a future appearance or administrative change if one occurs.

Silence in one public measurement system should remain silence in that measurement system, not a universal statement about the resource.

5. Two Active IPv4 Records Expand the Number-Resource Picture

The company identity is also attached to two active IPv4 resource records. LACNIC binds 200.112.160.0/19 to Broadbandtech S. A., with a registration event dated 14 September 2005. A separate record binds 168.121.212.0/22, dated 4 February 2016, to the same registrant.

Together, the records establish a broader administrative footprint than either ASN alone. They show that the organization is not merely named in an autonomous-system record; it is also recorded as the holder of two address blocks that appear in the AS22080 routing material.

Address-space size must not be translated into market size. A /19 and a /22 describe number resources, not subscribers, sites, traffic volume or physical coverage. Addresses may be assigned to infrastructure, customers, internal systems or translation pools, and not every registered address must be active.

The useful conclusion is narrower. Broadbandtech has an identifiable number-resource surface that can be tracked across registry, routing and RPKI systems. Those systems reveal administrative and control-plane changes while leaving the delivery network behind them largely unobserved.

6. The /19 Record Is a Holder Fact, Not a Fibre Map

200.112.160.0/19 is a sizeable contiguous IPv4 block. The LACNIC response identifies Broadbandtech as the recorded holder and marks the resource active. That exact registration gives analysts a stable starting range for comparing visible more-specific announcements and route-origin authorization.

The block does not disclose where addresses are used. A registered range can span infrastructure roles and customer assignments without corresponding neatly to geography. Even when a website lists service localities, the address record cannot confirm which town, building or access link uses a particular address.

Nor does the range prove ownership of the transport carrying those addresses. Fibre, microwave, leased capacity, towers, ducts and customer-premises equipment exist in a different evidence layer. The number-resource ledger follows responsibility for addresses, not title to every physical component that may carry their traffic.

That separation matters during incidents. A route can remain visible while a local access segment fails, and a physical path can continue operating while an address announcement changes. Registry and routing evidence should be used to frame questions about delivery, not to substitute for delivery evidence.

7. The /22 Record Provides a Second Dated Resource Anchor

The active 168.121.212.0/22 record adds another independently dated resource to the company boundary. Its 2016 registration event is later than the /19 record and earlier than AS61518. This chronology shows additions to the recorded number-resource surface over time.

The /22 also appears directly in one of the reviewed RPKI validation checks. RIPEstat reported AS22080's origin of the aggregate as valid under a covering authorization that permits up to /24. Registry identity, observed origin and authorization metadata align for that exact example.

One aligned example should not be expanded into a claim about every route. The announced-prefixes response contains many entries, including more-specifics. Each origin-prefix pair has its own validation state, and the two captured checks cover only the pairs that were explicitly queried.

Still, the /22 is valuable as a compact accountability unit. Future checks can compare its holder, origin, visibility and authorization without relying on marketing claims or inferred topology. Changes can be described precisely at the layer where they occur.

8. AS22080 Produced 59 Prefix Entries in the Reviewed Interval

RIPEstat's announced-prefixes endpoint returned 59 entries for AS22080 during the observation interval from 14 to 28 July 2026. The set includes IPv4 blocks associated with the registered ranges and more-specific announcements within those spaces.

An entry count is not the same as 59 unrelated allocations. Aggregates and more-specific routes can coexist, and route collectors may record changes across the interval. The figure is best read as the size of the captured announcement set rather than a measure of customers, routers or independent networks.

The result nevertheless confirms a materially visible origin. AS22080 is not represented by one isolated prefix in the reviewed data. Its routing footprint includes enough specific entries to make change monitoring, authorization checks and adjacent-AS analysis operationally useful.

The observation remains time-bounded. Announcements can be withdrawn, aggregated or replaced. Any later statement about the current count should be based on a fresh capture rather than treating 59 as a permanent attribute of Broadbandtech's network.

9. Full IPv4 Visibility Describes Collector Reach, Not Availability

RIPEstat's routing-status response reported AS22080 visible to 329 of 329 responding IPv4 RIS peers at the last observation. That is a strong public control-plane signal: the route set reached every participating IPv4 vantage point counted in that response.

RIS peers are not Broadbandtech customers. They are measurement vantage points in other networks. Their collective view shows propagation across the sampled routing system, not whether an end user's modem, local loop, wireless link or application was working at the same moment.

A widely propagated route can coexist with local outages, congestion, power failures, DNS problems or equipment faults behind the origin. Conversely, a collector can lose a path without every customer losing service. BGP visibility and service availability answer different questions.

The 329-of-329 result therefore belongs in a routing baseline. It supports the statement that AS22080's IPv4 origin was broadly visible at the reviewed time. It cannot be converted into an uptime percentage, a resilience claim or a guarantee of delivered connectivity.

10. The IPv6 Signal Was Much Thinner

The same routing-status response reported only 3 of 324 IPv6 peers seeing the relevant AS22080 signal. That contrast with full IPv4 visibility is striking, but it needs careful language because the captured data does not describe a complete IPv6 deployment or customer service.

Thin visibility can arise from several conditions: a limited announcement, collector-specific paths, a transient route or a configuration that is not intended to match the IPv4 footprint. The frozen sources do not identify which explanation applies.

It would be wrong to infer that Broadbandtech offers no IPv6 service. It would also be wrong to present the company as having a broadly visible dual-stack origin. The evidence supports only a measured contrast between strong IPv4 visibility and a much smaller IPv6 collector signal.

That contrast is useful for monitoring. A future increase in IPv6 visibility, a stable aggregate announcement or clearer route-origin authorization would be a material change. Until then, the current record should remain a bounded observation rather than a maturity score.

11. First-Seen and Last-Seen Dates Create a Longitudinal Baseline

RIPEstat's AS22080 history reaches back to 2001, matching the period of the LACNIC registration. The reviewed last-seen record extends to 28 July 2026. These dates establish continuity of public observation across a long interval.

Continuity in route history does not prove uninterrupted service. Collector archives may have gaps, route visibility can fluctuate and an origin can remain present while portions of an access network fail. The dates show that AS22080 has repeatedly existed in the public routing system, not that every service was always available.

Longitudinal evidence is valuable because it makes exceptions visible. A future disappearance, origin change, resource transfer or new neighbour can be compared with a stable historical identity. Without that baseline, a one-day routing snapshot has less context.

The dates also distinguish AS22080 from AS61518. One has a long, current public routing history; the other had a brief historical signal ending in 2020 in the reviewed data. That difference is the central operational contrast between Broadbandtech's two AS records.

12. Immediate Pre-Origin ASNs Reveal Handoffs, Not Contracts

The captured BGP-state response contains 15,473 collector observations. Looking at the autonomous system immediately before origin AS22080, several identities appear. AS52361 forms the largest observed group, followed by AS52444, AS22080 path prepending, AS22927 and a much smaller AS52508 group.

An immediate pre-origin ASN identifies the last visible control-plane handoff before the route reaches Broadbandtech's origin. It does not label the commercial relationship. The adjacent system might provide transit, aggregation, peering or another service whose terms are not encoded in the AS path.

Collector counts also are not traffic shares. A path seen more often across the captured observations may be widely selected by the measurement set, but it does not prove that the same proportion of customer traffic uses it. Route selection and traffic engineering are related but not interchangeable.

The defensible use is comparative. The observed neighbour mix shows more than one public path context around AS22080 and supplies a baseline for change. It cannot establish exclusive contracts, circuit count, physical diversity or a complete topology.

13. AS52361 Dominated the Captured Immediate-Handoff Sample

AS52361 was the most frequently observed autonomous system immediately before AS22080 in the captured BGP-state data. That prominence makes it a significant visible dependency at the time of observation, but not necessarily an exclusive one.

The sample reflects collector-selected paths. BGP policy, geography, local preference and route availability influence which path each peer selects. A dominant adjacent ASN may indicate a common route handoff without revealing the volume, commercial priority or physical path behind it.

Operational continuity questions follow naturally. Analysts can watch whether AS52361 remains dominant, disappears or is joined by other adjacent systems. A shift could reflect normal engineering, maintenance, an outage response or a commercial change. Public BGP alone cannot determine the cause.

The source set contains no service agreement, facility list or circuit diagram. Accordingly, the route adjacency should be described as observed control-plane evidence, not as proof of a named transit contract or of the physical network used to deliver access.

14. Other Visible Handoffs Complicate a Single-Dependency Story

AS52444, AS22927 and a small AS52508 group also appeared immediately before AS22080. Their presence is evidence against reducing the captured routing picture to one universal AS-level path. It shows that different collector observations reached the origin through different adjacent systems.

That diversity is not automatically resilience. Multiple AS-level neighbours can still depend on one facility, fibre corridor, power source or upstream organization. Public routing paths do not expose those shared physical failure domains.

The reverse is also possible. Two independent circuits to the same adjacent ASN can be physically diverse while looking identical at the AS-path level. Counting distinct autonomous systems therefore underestimates some forms of diversity and overstates others.

The useful result is a list of observed handoffs and a warning about what the list cannot establish. It supports monitoring of routing changes, while any claim about redundancy, failover or contractual diversity requires direct operational evidence.

15. Self-Prepending Is a Policy Signal, Not a Separate Network

Some captured paths included repeated AS22080 values. This is consistent with AS-path prepending, a common routing-policy technique in which an operator repeats its own ASN to influence how other networks rank a route.

Repeated ASN tokens do not represent additional companies, circuits or geographic hops. Treating each repetition as a separate network would inflate the apparent topology. The identity remains AS22080 even when it appears more than once in the path.

Prepending can indicate traffic-engineering intent, but the source set does not disclose the desired policy outcome. It cannot tell readers which path Broadbandtech preferred, whether the technique affected traffic as intended or how the policy interacted with local preferences elsewhere.

The evidence supports a narrow statement: self-prepending was visible in part of the captured path set. That observation adds context to route selection without becoming a claim about capacity, cost, performance or service-level engineering.

16. One RPKI Example Validates a More-Specific Route

RIPEstat reported valid for AS22080 originating 200.112.182.0/24. The route is covered by a 200.112.128.0/18 route-origin authorization whose maximum length permits a /24. The tested origin and prefix length therefore matched the applicable authorization.

This result is a concrete security-metadata fact. It shows that a relying-party validator could confirm the exact origin-prefix pair against the captured ROA data. That reduces ambiguity for networks that use RPKI-based route policy.

Validity does not certify the whole path. It says nothing about the adjacent autonomous systems, physical transport, traffic quality or whether the origin's internal routing is correct. A valid route can still be affected by leaks, outages or equipment failure.

The example should therefore be presented as one verified authorization alignment. It supports route-origin accountability for the exact /24, not a claim that every Broadbandtech announcement is authorized or that the network is universally secure.

17. The /22 Aggregate Also Returned a Valid Result

The second captured RPKI check tested AS22080 with 168.121.212.0/22. RIPEstat again returned valid. The covering authorization matches the aggregate and allows more-specific announcements down to /24.

This alignment is especially clear because the same /22 is directly registered to Broadbandtech in LACNIC's RDAP data. The holder record, observed origin and authorization metadata all point to the same company-AS boundary for that exact query.

Even two valid examples remain a sample. The announced-prefixes response contains 59 entries, and the source set did not validate each one. It would be inaccurate to convert the two results into a universal RPKI-coverage percentage or an assurance about all more-specific routes.

What the sample establishes is still useful. Broadbandtech has at least two exact AS22080 origin-prefix pairs that were valid under the reviewed RPKI data, offering a stronger control surface than registry or BGP visibility alone.

18. Invalid-ASN Alternatives Clarify What the ROA Protects

Each RPKI response also listed AS10617 as an invalid-ASN alternative under the covering authorization. That does not mean an invalid AS10617 route was necessarily active in the reviewed BGP snapshot. It describes how the authorization would evaluate a different origin.

The distinction shows what RPKI contributes. The registry records who holds the address resource, while the ROA specifies which autonomous system is authorized to originate covered routes and at which prefix lengths. Validators compare observed announcements with that security metadata.

An invalid alternative is not evidence of an attack by itself. A routing incident would require an actual conflicting announcement and context about its propagation. The captured data here supports the authorization rule, not an allegation about another network.

For Broadbandtech, the important point is that the two tested AS22080 routes have explicit positive authorization, while a different origin would not satisfy the same metadata. That is a bounded, technically meaningful accountability statement.

19. Two Valid Checks Do Not Establish Universal RPKI Coverage

The temptation to summarize RPKI with a single label should be resisted. Networks can announce aggregates and more-specifics under different ROAs, and authorization state can change. A valid result for one pair does not automatically apply to every route originated by the same ASN.

The 59-entry route set was not exhaustively tested in the sealed evidence. Some entries may be covered by the same authorizations, others by different records, and some may have another status. Without running and preserving each exact query, a network-wide percentage would be invented.

RPKI also protects only the origin authorization layer. It does not validate the full AS path or prove that a route reaches working infrastructure. Other mechanisms and operational controls address those different risks.

The responsible conclusion is therefore sample-based: two AS22080 examples were valid. That evidence can support a focused monitoring baseline, while universal coverage and broader security posture remain unproved.

20. The Official Website Supplies Positioning, Not Independent Verification

Broadbandtech's official site markets internet, HD television, packages and locality-oriented service options. That material helps identify the company's public-facing business and supports its classification as a regional Internet provider rather than a data-centre operator.

The website is operator-authored. It can describe offers and intended markets, but it cannot independently verify coverage, achieved speeds, outage history, restoration performance or market share. Those claims would require measurement, contracts, regulator data or other direct evidence.

Locality menus should not be read as a coverage map. A place name can indicate marketing availability without showing which addresses are serviceable or what access technology reaches them. The public routing data likewise cannot fill that geographic gap.

The website and network records answer complementary questions. One shows how Broadbandtech presents its services; the others expose a number-resource and routing identity. Neither alone reveals the full delivery system that connects end users.

21. Registered, Announced and Usable Are Separate States

Number-resource analysis becomes clearer when three states are kept distinct. A resource can be registered to an organization, announced in BGP and usable by applications or customers. Each state has different evidence and can change independently.

AS61518 demonstrates the first distinction. It remains active in the registry but has no current announcement in the reviewed RIPEstat data. AS22080 demonstrates the second: it is both registered and visibly announcing routes, but those observations do not establish customer usability.

Usability depends on conditions beyond the origin announcement. Internal routing, access links, power, name resolution, equipment and customer provisioning all matter. A globally visible prefix can terminate at an impaired network, while private services can operate without a public origin route.

Treating the states separately prevents both optimism and alarmism. Registration should not be called operation; announcement should not be called service; absence from one collector view should not be called nonexistence. The result is a more accurate operational baseline.

22. The Quiet ASN Is a Monitoring Object, Not a Negative Finding

AS61518's current silence is noteworthy precisely because the registry record remains active. That pairing gives future monitors a clear trigger: a new route from AS61518 would represent a change from the reviewed baseline.

An administrative update would be equally material. If the holder, status or contact data changed, the registry layer would move even if no route appeared. Monitoring both layers avoids assuming that only BGP events matter.

The quiet state should not be framed as waste, failure or concealment. Organizations retain autonomous systems for many reasons, and the source set contains no statement from Broadbandtech explaining this one. A neutral baseline preserves the distinction between observation and judgment.

That neutrality is operationally useful. It allows a later report to describe exactly what changed without having to unwind an unsupported narrative about why the ASN was quiet in the first place.

23. Routing Diversity Cannot Be Converted Into Physical Redundancy

The AS22080 snapshot contains several immediate pre-origin identities, which may suggest multiple external relationships. Physical redundancy, however, depends on where circuits run, which facilities they use, how power is supplied and whether failure domains are genuinely separate.

Two BGP neighbours may share a building, conduit or wholesale carrier. One neighbour may be reached through multiple physically independent links. The AS path cannot distinguish these arrangements, because it represents administrative routing hops rather than the transport layout beneath them.

No source in the frozen set provides facility addresses, circuit diagrams, tower inventories or tested failover results. The correct reader-facing boundary is explicit: routing diversity is visible at the AS level, while physical resilience remains unproved.

This is not a weakness in the routing data. It is a reminder to use each evidence layer for the questions it can answer. BGP is excellent for observing origin and path changes; it is not a substitute for infrastructure disclosure.

24. Contacts Are Part of the Operational Surface

LACNIC's RDAP records include administrative, technical and abuse-contact handles. The same handle appears across Broadbandtech's two autonomous systems, reinforcing the shared organization boundary and providing a recorded path for operational communication.

Contact metadata matters when routes leak, abuse reports arrive or transfer questions arise. A registry that maintains accurate responsibility records lowers the cost of finding the party expected to respond. That function is practical even when the registry cannot enforce service quality.

The public analysis does not need to reproduce private contact details. The meaningful fact is that the records expose consistent roles attached to the resources. Whether those channels respond promptly is a separate question that the source set does not test.

Operational continuity depends partly on this administrative layer. Routes and systems can outlast individuals, so current role-based records help preserve accountability across organizational change. Accuracy must still be monitored rather than assumed.

25. Failure Paths Remain Mostly Outside the Public Record

The source set cannot show how Broadbandtech responds to a fibre cut, upstream outage, router failure or power event. BGP may expose a withdrawal or path change, but it does not reveal every local failure or the operational steps taken to restore service.

Likewise, a stable origin announcement does not prove that traffic is reaching customers. Internal aggregation, access equipment and customer-premises systems sit behind the public edge. Problems there may be invisible to global route collectors.

The observed neighbour mix gives analysts a place to watch during an incident. A disappearance of one handoff, a new adjacent ASN or a broad withdrawal would be significant. Yet interpreting the cause would still require direct operational evidence.

The absence of failure-path disclosure should be stated, not filled with assumptions. It protects readers from treating routing visibility as a service-level report and gives Broadbandtech a clear set of questions it could answer with more transparent operational information.

26. Customer and Dependency Boundaries Are Not Visible

Public prefix announcements can include infrastructure addresses and customer assignments, but the reviewed data does not identify which is which. It contains no verified customer list, wholesale relationship map or allocation ledger for individual downstream users.

The immediate AS neighbours reveal visible route handoffs, not all business dependencies. Broadbandtech may depend on transport, power, facilities, vendors or support systems that never appear in BGP. Conversely, a visible adjacent ASN may play a narrower role than its path frequency suggests.

This uncertainty blocks claims about market importance and systemic exposure. A 59-entry announcement set shows control-plane activity, but not how many people or organizations rely on it. Customer impact cannot be calculated from prefix count alone.

A more complete dependency assessment would combine routing evidence with facility, contract, service-area and operational-continuity disclosures. Until such sources exist, the number-resource boundary should remain the centre of the analysis.

27. A Useful Disclosure Would Separate the Same Layers

Broadbandtech could make its network easier to evaluate without exposing sensitive topology. A concise disclosure could identify which ASN is intended for which public role, explain whether AS61518 is expected to announce routes and describe the scope of published RPKI coverage.

It could also distinguish registered resources from customer-facing service. That would prevent readers from treating address blocks as coverage maps and allow the company to discuss continuity in terms that are meaningful without revealing exact physical routes.

For routing resilience, an operator can describe whether it maintains diverse upstream or transport arrangements while withholding commercially sensitive details. Any such statement would still need careful wording because logical and physical diversity are different.

The current public records already provide the identifiers needed for that conversation. Better disclosure would connect those identifiers to operational intent, reducing the gap between administrative identity and what running routing data can show.

28. The Baseline Supports Specific Future Checks

A repeatable monitoring plan can remain compact. For AS22080, track the announced-prefix count, IPv4 and IPv6 visibility, immediate pre-origin ASN mix and exact RPKI status of material origin-prefix pairs. Each observation should retain its timestamp and query boundary.

For AS61518, monitor both RDAP status and the appearance of any announced prefix. A route appearance, holder change or status update would be a material event. The reason should not be inferred without another source.

For the two registered IPv4 blocks, compare holder data, origin AS and authorization metadata. A change in any layer should be described at that layer before drawing a broader operational conclusion.

This approach treats registries as ledgers and routing as running code. It creates accountability without pretending that either system is sovereign over every physical or commercial fact behind the network.

29. Broadbandtech's Public Edge Is Visible, but the Delivery Boundary Is Not

The strongest evidence about Broadbandtech is precise. LACNIC records two active autonomous systems and two active IPv4 blocks. RIPEstat shows a long-lived, broadly visible AS22080 origin with 59 prefix entries, several immediate handoffs and two valid RPKI examples.

The contrast is equally precise. AS61518 remains active administratively but has no current RIS announcement in the reviewed view. IPv6 visibility around AS22080 is thin compared with IPv4. Those facts create monitoring questions without explaining the underlying operational choices.

What remains unknown is the network customers experience: fibre ownership, serviceable addresses, capacity, uptime, physical redundancy, restoration performance and commercial routing arrangements. Neither a registry record nor a BGP path can responsibly fill those gaps.

Broadbandtech therefore presents a clear reality-layer case. Its number-resource identity and public routing edge are observable and accountable. The physical and commercial delivery system behind that edge still requires direct evidence before stronger claims can be made.

30. Classification Should Follow the Evidence, Not the Planning Label

The exact directory entity and the official website support a regional Internet-provider classification. The number-resource records reinforce that boundary by showing autonomous-system and IPv4 responsibilities associated with the company. Nothing in the source set supports a data-centre, colocation or hosting-facility thesis.

That exclusion is important because infrastructure language can easily drift. An ASN is sometimes described as “infrastructure” in a broad sense, but it does not imply that the holder operates a building with customer racks, power systems or cooling equipment. Routing identity and facility operations are different objects of proof.

The same discipline applies to television and package marketing. Those offers explain Broadbandtech's public commercial positioning but do not turn the routing evidence into proof of content-delivery facilities, head-end ownership or a particular access architecture. Each operational claim needs its own source.

Using the smallest accurate category keeps the monitoring object clear. Broadbandtech belongs here because its public network identity is visible and because the boundary between registry records and route operation can be examined. The classification does not grant permission to invent the parts of the network that remain unseen.

31. The Evidence Is Strongest When Its Limitations Stay Attached

The source set combines three useful evidence types. LACNIC provides administrative identity and resource-holder records. RIPEstat provides time-bounded routing observations and RPKI validation responses. Broadbandtech's own site provides attributed service positioning. Each contributes something different.

Combining them does not erase their limitations. Registry data is authoritative for the recorded ledger state but not for customer experience. Route collectors expose selected public paths but not all traffic or physical delivery. An operator website can describe offers but cannot independently validate performance.

The analysis becomes less reliable when those boundaries are removed. A route count can become a fictional customer footprint; a visible neighbour can become an invented contract; a valid ROA can become a security certification; an active ASN can become a claim of current use. None of those conversions is supported.

Keeping the limitations beside the facts is not excessive caution. It preserves information gain. Readers receive exact identifiers, ranges, dates, visibility measures and authorization examples, along with a clear account of what further evidence would be required for stronger conclusions.

32. Operational Continuity Begins With a Stable Record

Continuity is often discussed only after a service interruption. The public evidence allows a more preventive approach. Stable identifiers such as AS22080, AS61518 and the two IPv4 ranges make it possible to observe administrative and routing changes before attaching a story to them.

The registry layer preserves who is recorded as responsible. BGP exposes whether the public edge is announcing and through which adjacent autonomous systems collectors see it. RPKI adds a check on whether selected origin-prefix pairs match authorization metadata. Those layers together create a compact accountability framework.

They do not replace operational disclosure. Physical diversity, restoration procedures, spare capacity, customer communication and incident history remain outside the captured record. Continuity depends on those systems as well as on accurate number-resource metadata.

Broadbandtech's current baseline is therefore useful precisely because it is incomplete in known ways. AS22080 is visible and measurable; AS61518 is registered but quiet; two tested routes are authorization-valid; the delivery network is not publicly mapped. Future evidence can improve that baseline without rewriting uncertainty as fact.

Sources

https://btw.media/en/directory/broadbandtech-s-a-ar https://www.bbt.com.ar/ https://rdap.lacnic.net/rdap/autnum/22080 https://rdap.lacnic.net/rdap/autnum/61518 https://rdap.lacnic.net/rdap/ip/200.112.160.0/19 https://rdap.lacnic.net/rdap/ip/168.121.212.0/22 https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS22080 https://stat.ripe.net/data/routing-status/data.json?resource=AS22080 https://stat.ripe.net/data/bgp-state/data.json?resource=AS22080 https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS61518 https://stat.ripe.net/data/routing-status/data.json?resource=AS61518 https://stat.ripe.net/data/rpki-validation/data.json?resource=AS22080&prefix=200.112.182.0/24 https://stat.ripe.net/data/rpki-validation/data.json?resource=AS22080&prefix=168.121.212.0/22