DOBLECLICK SOFTWARE E INGENERIA: The Control Layer Behind Regional Connectivity

Summary

• DOBLECLICK SOFTWARE E INGENERIA is the routing-registry spelling of a Popayán-based operator whose public legal name is DOBLECLICK SOFTWARE E INGENIERIA S.A.S.; the company website, NIT 900104400-5, AS264646, address and operational email domain establish that these are spelling variants of the same business.
• Its defensible product is not simply access speed. It is local coordination across claimed fibre and radio infrastructure, a Popayán backbone, upstream networks, customer premises, field work, public-project obligations and a corporate support operation.
• Public routing evidence proves that DobleClick originates a live dual-stack network and has multiple observed external adjacencies. It does not prove physical path diversity, purchased transit capacity, independent power, restoration time or the absence of shared failure domains.
• An institutional buyer should require an ownership-and-dependency map, route and power diversity evidence, measured service history, security controls, field-restoration commitments and a witnessed failover test before treating a second link as genuine continuity.

The service starts before a packet moves

Imagine the first question at a municipal office, clinic or school after a communications failure in south-western Colombia. It is not, “How many megabits did we buy?” It is, “Where did the path break, who can reach it, and what still works while the repair crew travels?”

That distinction is the key to DobleClick. A national carrier can sell an institution a circuit whose commercial endpoint is a building in Cauca or Nariño. A regional operator has to turn that abstract circuit into a working local system: obtain or build the last mile, align a radio, splice fibre, power an access node, configure customer equipment, manage an upstream, answer the institution, and send people into the field. In easy terrain those activities can disappear behind a bandwidth number. In DobleClick’s operating territory they are the product.

A 2023 budget-resolution document from the Government of Cauca makes the point unusually concrete. It records a 2022 educational-connectivity contract with DobleClick and explains why part of the work could not be received by year-end: heavy rain and bad weather impeded installations; windstorms damaged communications towers and fibre cabling; tertiary roads closed; unsafe conditions and armed-group activity prevented work in several rural municipalities. This is not evidence that every DobleClick circuit is fragile, nor is it a verdict on the contractor. It is evidence that the delivery system includes weather, roads, public safety, school readiness and physical assets—not just IP transit.

The company’s own history follows the same logic. DobleClick says it began in 2005 to connect communities in northern Nariño and southern Cauca, initially with wireless broadband, and expanded with help from agreements in the Cauca health sector. Its corporate service pages now advertise tailored internet, data transport, institutional projects, Wi-Fi zones, consulting and corporate support. The arc is from local access problem to regional operating coordinator.

That is the thesis an institutional customer should test. DobleClick may control important pieces of the service, but no regional ISP controls the whole internet path. The procurement task is to separate the assets, people and decisions DobleClick commands directly from the capacity, infrastructure, permissions and recovery dependencies it rents or inherits. A buyer that does not make that separation can pay for apparent redundancy while retaining one upstream, one duct, one tower, one power feed or one escalation chain.

One company, two spellings, one network identity

The assigned name, DOBLECLICK SOFTWARE E INGENERIA, contains the spelling “INGENERIA.” That is not the spelling used in the company’s legal-facing public material. DobleClick’s homepage states that the brand belongs to DOBLECLICK SOFTWARE E INGENIERÍA SAS and prints NIT 900104400-5. Colombia’s MinTIC uses DOBLECLICK SOFTWARE E INGENIERIA S.A.S. with that same NIT in its final evaluation for the 2023 “Conectividad para cambiar vidas” call in Nariño. A secondary business-registry index also lists the company as active under NIT 900104400-5.

The routing records preserve the variant. LACNIC’s registration for AS264646 names the holder “DOBLECLICK SOFTWARE E INGENERIA,” gives a Popayán address and assigns the technical, administrative and abuse contact to an @dobleclick.net.co address. PeeringDB’s AS264646 entry uses the same variant as its network name, supplies “DobleClick” as the short name, “DobleClick Software e Ingenieria” as the long name, and points to https://dobleclick.net.co/.

Those links form a sufficiently strong identity bridge. The NIT joins the website to the legal entity; the domain joins the website to the autonomous-system contacts; the Popayán address appears on both corporate and network records; and PeeringDB joins the brand and domain to AS264646. The misspelling should therefore be preserved when referring to the assigned directory entity or the registry name, while the standard INGENIERIA spelling should be used when quoting legal and government sources.

This matters for procurement rather than mere copy-editing. Contracts, invoices, RUP certificates, MinTIC records, spectrum applications, letters of authorisation and routing-resource evidence can use different representations of the name. A buyer should anchor due diligence on NIT 900104400-5 and AS264646, not on fuzzy name matching. It should also insist that the contracting party, resource holder, service operator and bank-payee identities are reconciled in the award file. A spelling difference that is harmless after verification can otherwise become a weak link in sanctions screening, insurance, tax validation or incident escalation.

A control tower built around Popayán

DobleClick’s public technical description is more revealing than its retail offers. Its internet and data-transport page says the network combines fibre with radio backup, contains 125 nodes across Cauca, Nariño, Huila, Putumayo and Valle del Cauca, and is centred on a backbone in Popayán. It claims last-mile capacities of up to 1 Gbps over fibre and 150 Mbps over radio, with availability “up to 99.7%.” It names MikroTik, Ubiquiti, Huawei, Mimosa and Cambium among the equipment families handled by its staff.

The coverage page adds a claimed 300 kilometres of urban fibre used for GPON access and lists fibre coverage in 13 Cauca locations, 16 Nariño locations, Neiva in Huila and Palmira in Valle del Cauca. It separately claims radio coverage across all of Cauca and Nariño, while warning that service remains subject to a feasibility study. The equipment page identifies Huawei GPON terminals and Ubiquiti radio customer equipment, which is consistent with a mixed fibre-and-fixed-wireless access architecture.

These statements describe a plausible regional control surface. A Popayán operations team can choose a local access method, dispatch a crew, configure an ONT or radio, monitor a node, and integrate an institution’s sites. DobleClick also advertises structured-cabling design, organisational telecommunications consulting, Wi-Fi zones and inter-site data transport. Those adjacent services matter because many “internet failures” at an institution are actually power, Wi-Fi, LAN, CPE, cabling or configuration failures. An operator able to see and service the whole local chain can shorten the argument over who owns the fault.

But every number in that paragraph needs a label. The 125 nodes, 300 kilometres, five-department topology, equipment expertise and 99.7% availability are company claims, not an independently audited asset register in the public evidence. “Backbone in Popayán” does not reveal whether there is a second core site, how the core is powered, whether route reflectors or border routers are geographically separated, or whether a single fibre cut can isolate multiple municipalities. “Radio backup” does not show whether the radio terminates at a node that shares the same upstream, tower power or aggregation path as the failed fibre.

The result is not scepticism for its own sake. DobleClick’s local operating footprint may be precisely why an institution should shortlist it. The right response is to convert marketing nouns into contract exhibits: a node list, asset-owner matrix, high-level route map, power design, spares plan, coverage evidence, NOC boundary and named field depots. The value of a regional operator grows when it can show where its direct control begins and ends.

What DobleClick owns, leases and inherits

The cleanest proof of direct network control is the internet-number resource record. LACNIC registers 138.0.88.0/22 and 2803:1780::/32 to the same DobleClick organisation handle that holds AS264646. The IPv4 block contains 1,024 addresses before subnet and reservation effects; the IPv6 allocation is vastly larger. These records show durable control rights over numbering resources and the ability to originate them under the company’s autonomous-system policy.

Public BGP observations show a broader operating set. In a two-week window ending July 17, 2026, the RIPEstat announced-prefixes endpoint observed AS264646 originating ten IPv4 /24 routes and twelve IPv6 /48 routes. Four of the IPv4 routes are the more-specific components of DobleClick’s own 138.0.88.0/22. Other routes came from 8.242.189.0/24, 8.242.190.0/24, 177.73.155.0/24 and three 190.90.x.0/24 blocks.

The distinction is important. ARIN’s registration for 8.242.190.0/24 identifies DobleClick as the customer registrant but also records a parent network. The observed 190.90.x.0/24 routes sit inside larger address ranges associated in routing records with Internexa. These are signs of provider-delegated or otherwise inherited address space rather than proof that DobleClick owns the parent allocation. Provider-assigned space can be perfectly legitimate and useful, but it can also create renumbering and continuity dependencies if the commercial relationship ends.

Physical infrastructure has the same categories. DobleClick may own a GPON segment, radio, tower electronics, router or customer ONT. It may lease pole space, ducts, dark fibre, lit transport, tower space or a wavelength. It may rely on a public programme to finance an access build, a landlord to power a roof site, an equipment manufacturer to replace a failed optical card, or a carrier to restore a long-haul span. None of those arrangements is inherently weak. The weakness appears when a buyer purchases “DobleClick diversity” without knowing which supposedly separate paths converge on the same inherited asset.

An institutional ownership schedule should therefore cover five layers. First are number resources: which addresses are portable, which are provider-assigned, and who can authorise route changes. Second is passive infrastructure: fibre, duct, poles, towers and rights of way. Third is active infrastructure: OLTs, switches, radios, routers, power systems and monitoring probes. Fourth is external service: transit, peering, transport, DNS, DDoS mitigation and cloud dependencies. Fifth is operational authority: who can approve a change, dispatch a crew, enter a site or escalate to an upstream.

DobleClick’s public record provides a credible starting point for that schedule. It does not complete it. That gap is where an institution should focus technical due diligence.

AS264646 makes the network testable

AS264646 is more than a registry badge. It means DobleClick can originate routes, make interconnection choices and present a distinct network to the global routing system. It also gives a buyer evidence that can be checked independently of a sales presentation.

The current signals are meaningful. DobleClick describes itself in PeeringDB as a regional cable/DSL/ISP network with mostly inbound traffic, a 50–100 Gbps traffic band and an open peering policy. The record says that multiple locations, traffic-ratio conditions and a contract are not required for peering. It also provides distinct abuse, technical, policy, NOC and maintenance contacts. Those are positive signs of an operator that understands interconnection as an operational function.

They are not proof of the advertised capacity or of active public peering. PeeringDB is a user-maintained database, and its DobleClick entry was last updated in February 2024 for the main network fields. It reports four IPv4 and one IPv6 prefix, while the July 2026 RIPEstat observation found ten and twelve respectively. The entry exposes no listed exchange LAN or colocation-facility presence in the public API snapshot, and it does not publish an IRR as-set, route server URL or looking glass in the visible fields.

An open policy without a disclosed interconnection location is an invitation to peer, not evidence that traffic is actually exchanged locally.

Observed BGP relationships add another layer. bgp.tools classifies Lumen’s AS3549 and Internexa’s AS18678 as upstreams. RIPEstat’s ASN-neighbours view sees those networks, another Internexa network, AS262589, and several adjacencies on the other side of AS264646, including Universidad del Cauca’s AS266737 and Tierranet’s AS269746. The topology is consistent with DobleClick buying global reach from larger carriers while also carrying or exchanging traffic for smaller regional networks. BGP adjacency alone cannot prove the commercial relationship, contracted capacity or physical hand-off, so a buyer should treat “upstream,” “peer” and “customer” labels as hypotheses to confirm.

Routing security is better evidenced. RIPEstat’s RPKI-validation checks marked all ten observed IPv4 /24 origins valid for AS264646 at the evidence freeze, and a sampled DobleClick IPv6 /48 was also valid. A valid Route Origin Authorisation means the origin ASN is cryptographically authorised to announce the prefix; LACNIC’s explanation of RPKI is explicit about that limited purpose. It does not validate every AS in the path, prove that DobleClick rejects invalid routes from others, prevent congestion, or show that a fibre path is diverse.

The procurement implication is precise. Ask DobleClick for the current route inventory, ROAs, IRR route and as-set objects, max-prefix settings, upstream BGP sessions, route-policy summary and a monitored list of invalid or unexpected announcements. Ask which routes use DobleClick-owned space and which depend on a carrier’s allocation. Require notice before an origin, upstream or addressing change. Network-resource evidence should become a maintained appendix, not a screenshot attached once at award.

The customer is buying orchestration, not merely bandwidth

For an institution, implementation begins with a feasibility study because DobleClick’s own coverage page says availability is site-dependent. That study should resolve the access medium, line of sight, fibre route, civil work, power, equipment location, building entry, internal cabling and recovery route. A green dot on a coverage map is not a design.

The likely workflow is visible across DobleClick’s service catalogue. The operator surveys the site; selects GPON fibre or a radio link; installs or configures the ONT, antenna or router; joins the access path to its aggregation network; provisions internet or an inter-site transport service; integrates the customer LAN; and hands the service to its corporate monitoring and incident platform. Its structured-cabling offer and telecommunications consulting extend that workflow inside the premises. Its corporate support page says customers can register and follow incidents and request reports on availability and consumption.

Public-programme documents show how much implementation detail sits behind a connection count. MinTIC’s Nariño evaluation checked legal eligibility and technical proposals municipality by municipality. Its technical framework examined deployed fibre coverage, homes passed, proposed connections, mapping, ONT/CPE specifications and installation planning. The final report found DobleClick legally and technically enabled and selected it in Albán, Belén, Buesaco, Colón, El Tablón de Gómez, El Tambo, La Florida, La Unión, Nariño, San Bernardo, San Pablo and Yacuanquer.

DobleClick later said publicly that the programme involved close to 6,000 services. Selection proves that a detailed proposal passed the stated process; it does not, by itself, prove the final number activated, long-run service quality or current network capacity.

The practical control advantage is local coordination. If the same organisation handles the last mile, CPE, monitoring and field dispatch, the institution has fewer seams to manage. But concentration can also turn the operator into a single point of operational knowledge. The customer must retain its own site diagrams, IP plan, device inventory, administrator access, configuration backups, test baselines and escalation record. Otherwise a well-integrated service becomes difficult to diagnose independently and expensive to replace.

Acceptance should be a sequence rather than a speed test. Verify physical route and equipment labels. Test contracted bandwidth in both directions with an agreed method and server. Record latency, jitter and packet loss to relevant institutional applications, not only to a nearby test node. Demonstrate public-address and VPN behaviour. Pull power and cut the primary access under controlled conditions. Confirm alarms reach the NOC and named customer contacts. Measure failover and restoration. Then preserve the results as the baseline for monthly reporting.

The mountain is part of the architecture

South-western Colombia makes a useful distinction between logical redundancy and operational resilience. A fibre and a radio can be different media yet share a tower, aggregation router, power system, upstream hand-off or crew. Two carriers can enter a building through separate ports yet use the same bridge, duct or regional transport provider. A route map can look diverse while both paths remain inaccessible to repair teams after a road closure.

The Cauca resolution is unusually valuable because it names actual delivery constraints: rain, wind, damaged towers and fibre, closed tertiary roads, unsafe sites and public-order conditions. Those hazards belong in the network design. A route across unstable terrain needs restoration materials positioned within reach. A radio site needs wind loading, grounding, lightning protection, secure mounting and backup power. A field plan needs access permissions, local contacts and a rule for suspending work when safety deteriorates. A school installation may depend on the building being safe and ready, not just the operator arriving on time.

DobleClick’s mixed network can be an advantage here. Radio may bypass a severed terrestrial segment or reach a site where civil construction is slow. Fibre can provide capacity and stability where the route is well protected. Local crews may understand road, weather and municipal constraints better than a distant service desk. Yet the phrase “fibre backed by radio” needs a diagram. The customer should know where the paths diverge, where they rejoin, which equipment they share, how each is powered, and whether both still depend on the Popayán core.

Public customers have already used DobleClick in a continuity design. The Lotería del Cauca’s 2022 technology plan described dedicated fibre channels from two ISPs—15 Mbps from EMTEL and 30 Mbps from DobleClick—plus a DobleClick radio antenna for contingency if fibre failed. That is evidence of an institutional customer assigning DobleClick both primary capacity and an alternate medium. It is not evidence that the two DobleClick paths were end-to-end independent, and the document does not publish failover results.

Another public record shows the opposite end of the scale. A Puracé municipal audit described a 6 Mbps dedicated DobleClick channel feeding the municipality’s main telecommunications node, from which connectivity was distributed to departments and other public entities. The example is older and says nothing about present capacity. It illustrates, however, how one access circuit and one main node can become a concentration point for many public workflows.

The buyer’s central question is therefore not “Is there backup?” It is “Which failure is the backup designed to survive?” The answer should cover access cuts, aggregation failure, core failure, upstream failure, commercial power loss, equipment failure, configuration error, cyberattack, denied site access and regional disruption. A backup that survives only one of those scenarios should be priced and described accordingly.

Availability is a budget, not an adjective

DobleClick’s public technical page claims availability of up to 99.7%. If interpreted as an annual service level, 99.7% allows roughly 26 hours and 17 minutes of downtime per year. If measured monthly, it allows about two hours and eleven minutes in a 30-day month. “Up to” also signals that the figure may describe a product ceiling rather than a universal commitment. A hospital, emergency service or transaction-dependent institution cannot purchase on that phrase alone.

The contract must define the measurement boundary. Is availability measured at the optical port, the customer router, the internet edge or a remote probe? Are power failures at the customer excluded? What about planned maintenance, force majeure, denial of site access, upstream failure, packet loss so severe that applications fail, or a backup path that remains technically up but unusably slow? Does the clock stop when the operator calls the service restored, or when the customer and monitoring probes agree?

Colombia’s regulatory framework adds useful context but is not a substitute for a bespoke SLA. CRC Resolution 7714 of 2025 created a municipal availability indicator for wholesale carrier service supplied to fixed-residential internet providers. From July 1, 2026, the staged objectives listed in the resolution are 99.6% for municipal groups 1 and 2, 97% for group 3 and 86% for group 4, rising later for the lower groups. Those are differentiated regulatory objectives for a defined wholesale context, not automatic promises from DobleClick to an enterprise customer.

The CRC also reported a national median fixed-internet download speed of 192.04 Mbps and upload speed of 84.53 Mbps for June 2025, with substantial variation by city and operator. These experience-based national measurements are helpful market context. They cannot predict a dedicated institutional circuit in a smaller municipality. They do reinforce why a buyer should measure both directions, latency, jitter and loss rather than accept a headline access speed.

A serious DobleClick SLA would state committed information rate, burst treatment, measurement interval, availability target, latency and loss objectives, mean time to acknowledge, repair targets by geography, maintenance notice, chronic-failure triggers and credits. Credits should not be the only remedy: a public institution may value an escalation, temporary radio, spare CPE, alternate route or termination right more than a small bill reduction. The agreement should also require monthly raw data and an incident ledger so performance can be reconstructed rather than merely asserted.

Support becomes a product when the evidence survives the incident

DobleClick says it has a corporate management platform for continuous incident tracking and customer-specific reports, plus a dedicated NOC for corporate users. The public site exposes separate support, infrastructure, billing, legal and local commercial contacts. That is stronger than a generic retail form because it suggests role separation and a route from complaint to technical action.

What is not public is just as important: the NOC’s operating hours, staffing pattern, monitoring coverage, escalation thresholds, on-call field roster, spares locations, mean repair history and upstream escalation rights. “Dedicated NOC” is a company claim until a buyer sees a workflow and service report. A pre-award demonstration should open a test ticket, show time stamps, identify the monitoring alarm, trace the escalation, and produce the same report the customer will receive in production.

Field support is where a regional operator can outperform a national service chain. The person diagnosing the signal may know the tower, municipality and access road. DobleClick’s maintenance contacts and infrastructure team are therefore economically meaningful. But local knowledge must be institutionalised. The buyer should ask how many people can perform each critical task, whether configurations and maps are centrally documented, how after-hours access works, and what happens if a named engineer is unavailable.

The public residential contract and billing-discount workflow also show a basic accountability mechanism: users report unavailability, retain a case number, and may receive proportional compensation. An enterprise contract should go further. It should make the incident record portable, preserve root-cause analysis, distinguish customer-premises from access and upstream faults, and require corrective action after repeats. The evidence should survive staff turnover on both sides.

DobleClick’s price is a bundle of distance, mobilisation and risk

DobleClick publishes residential prices but not a corporate tariff card. Its March 2026 promotion priced internet-plus-TV packages from COP 90,000 a month for 100 Mbps to COP 175,000 for 450 Mbps before optional Disney tiers. The offer applied to new activations, tied some benefits to bundled services, and differentiated tax treatment by residential stratum. Those figures are a snapshot of consumer acquisition economics, not a quote for a dedicated institutional circuit.

They still reveal the retail strategy. DobleClick uses increasing speed tiers, television, mobile service and entertainment to raise revenue per household and reduce churn. An introductory activation benefit brings a customer onto a service bundle whose components would cost differently if separated. For a regional ISP, that recurring base helps amortise fibre, OLTs, radios, field teams, spectrum use, content operations, billing and upstream capacity over many connections.

Institutional pricing follows a different cost stack. The visible bandwidth may be the smallest component. Price can include survey work, construction, pole or tower access, fibre distance, radio engineering, managed router, public addresses, symmetric capacity, upstream commit, monitoring, 24-hour cover, spares, travel, security constraints, reporting, insurance and performance risk. A remote 100 Mbps service with a hard restoration target can reasonably cost more than a 450 Mbps residential GPON plan passed by existing fibre.

The absence of public corporate pricing means a buyer needs comparable bid units. Separate one-time construction, activation and equipment from monthly access, transit, management and support. Price primary and backup paths independently. Identify which equipment transfers to the customer, which is leased, and which must be returned. State whether the rate assumes public subsidy, an existing programme build, a minimum term or a cluster of nearby sites. Require a schedule for moves, additions, upgrades, temporary radio and emergency work.

Regional ISP economics also create two opposite procurement risks. A buyer can overpay for local scarcity when only one operator can feasibly reach a site. Or it can force the price below the cost of preventive maintenance, spares and safe field work, then discover that the cheapest link has no resilient operating structure. The correct test is total continuity cost: monthly service plus construction, customer equipment, outage exposure, internal support, secondary connectivity and eventual migration.

Public procurement can improve the economics by aggregating many locations, but it also makes execution lumpy. DobleClick’s selection across multiple Nariño municipalities shows the scale opportunity. The Cauca document shows the mobilisation and acceptance risk when conditions delay many sites at once. A buyer should therefore examine cash-flow capacity, supplier credit, inventory and workforce alongside unit price. Low cost per connection is valuable only if the operator can finance and support the rollout until public acceptance and payment.

Security begins at route origin and cannot end there

DobleClick’s valid RPKI origins are a concrete security control. They reduce the chance that an unauthorised ASN can successfully originate the covered prefixes to networks enforcing route-origin validation. Public registration also exposes an abuse contact and a technical contact. Those are useful foundations for coordination.

They cover only one layer. The MANRS implementation guidance frames routing hygiene around filtering, anti-spoofing, coordination and global validation. An institutional buyer should ask whether AS264646 filters customer and upstream announcements, rejects RPKI-invalid routes, maintains IRR data, sets maximum-prefix limits, validates the first AS, and prevents spoofed source addresses at customer edges. The public evidence does not establish those controls. PeeringDB’s blank as-set and looking-glass fields make direct verification harder, although a blank public field is not evidence that the internal control is absent.

The mixed access network creates further questions. Huawei GPON terminals and radios from several vendors require firmware governance, credential management and replacement planning. Managed CPE should have unique administrative credentials, restricted management planes, configuration backups, authenticated updates and logs with clear retention. The institution should know whether DobleClick can reach the LAN-facing device, which staff and subcontractors can access it, and how access is revoked.

DDoS handling is another dependency boundary. A small regional operator can filter at its edge, purchase upstream mitigation, remotely trigger blackholing, or combine those approaches. The contract should identify mitigation provider and location, detection thresholds, customer notification, clean-traffic capacity, blackhole controls and test procedure. A claim of “protection” without the scrubbing path and capacity is not useful.

DobleClick’s personal-data policy identifies the legal entity, domain and Popayán address and describes duties under Colombia’s Law 1581 of 2012 and Decree 1377 of 2013. It commits to measures against unauthorised access, loss and fraudulent use and to reporting qualifying security violations to the authority. The policy was updated in 2019. It is evidence of a privacy-governance baseline, not evidence of a current information-security certification, audited control environment or telecom-network incident programme.

No ISO 27001 certificate, SOC report, public penetration-test summary, DDoS specification or security-incident postmortem appeared in the frozen public evidence. That does not mean such controls or documents do not exist. It means an institutional customer should request them under confidentiality, verify scope and validity, and avoid turning silence on a website into either an accusation or an assurance.

Public money changes the acceptance test

DobleClick’s institutional history is not a marketing abstraction. Its projects page says it has executed government-linked connectivity work in Cauca, Putumayo, Palmira, Tumaco and Nariño. Independent public documents corroborate participation in substantial projects.

The strongest recent example is MinTIC’s Nariño evaluation. It ties the legal name and NIT to a formal process, records legal and technical compliance, and lists DobleClick among selected ISPs across twelve municipalities. This is good evidence of procurement competence and a deployed-or-deployable local footprint. The report is still an award-stage document. A buyer conducting reference checks should request activation totals, acceptance certificates, service levels, subsidy conditions, disconnections after the support period and current contacts at the programme administrator.

The Cauca resolution records contract DC-SED-LP-286-2022 for internet connectivity at official educational sites, with a value shown as approximately COP 1.192 billion. It also records the reasons a budget reserve was needed when services could not all be received by year-end. That combination—commercial scale plus implementation friction—is more informative than an unqualified project logo. It shows DobleClick operating where continuity depends on project management and external conditions.

There is also a governance issue that must be stated with care. In January 2023, Colombia’s Procuraduría General de la Nación announced disciplinary charges against a former Cauca education secretary over alleged irregularities in the award process for Contract 1618 of 2018, a COP 2.1572 billion school-connectivity contract with DobleClick. The allegation was that the contract had been signed one day before adjudication. The notice concerns charges against the former public official; it is not a finding that DobleClick’s network failed, not a final judgment identified in the evidence set, and not proof of wrongdoing by the company. A procurement committee should record the matter, seek the final case status, and maintain procedural controls rather than convert an allegation into a verdict.

Current regulatory activity creates another useful watchpoint. An April 2026 MinTIC notice about local 900 MHz spectrum for fixed residential internet records an expression of interest from DobleClick under NIT 900104400. The later list in the same notice of expressions that met the cited resolution’s requirements does not include DobleClick. An expression of interest is not a spectrum permit, and the public document should not be represented as one. The commercial significance is that lower-frequency local access could matter for coverage economics if DobleClick later qualifies and obtains rights; buyers should monitor the actual award record.

Public money therefore raises the standard of evidence. The institution needs a clean legal identity chain, objective selection, conflict management, auditable technical scoring, acceptance by site, payment linked to evidence, and a complete change record. DobleClick’s local reach can be a public-value advantage, but only a disciplined process can distinguish that advantage from vendor dependence.

A regional operator competes on execution

DobleClick competes in at least three markets at once. In households, it faces national fibre and cable brands, local ISPs and wireless providers while using television and mobile bundles to retain customers. In institutional access, it faces carriers and integrators that can bring national transport, formal service catalogues and balance-sheet scale. In public connectivity programmes, it faces other regional operators whose advantage may be a specific municipality, lower mobilisation cost or already-passed homes.

The 2023 Nariño report names IP Technologies, Sinet, ISP Colombia Comunicaciones, ERC Explorer and San Miguel Telecomunicaciones among competing or co-selected proposals in relevant municipalities. A 2025 Universidad del Cauca dedicated-internet procurement response records observations from DobleClick and Media Commerce Partners for a primary channel serving the university and its Santander de Quilichao sites. This is evidence of an active institutional field, not a captive local monopoly.

DobleClick’s structural advantage is the combination of local access, field familiarity and its own ASN. Its disadvantage is that larger upstream carriers can influence its cost and recovery, while national rivals may have deeper capital, broader certifications and more geographically distributed cores. A regional buyer should not decide between “local” and “large” as identities. It should assign each role to the operator best able to make the failure domains independent.

One rational design is DobleClick for the locally difficult primary or access layer and a genuinely independent national or mobile/satellite path for continuity. Another is a national carrier as primary and DobleClick radio or fibre as the locally managed secondary. The Lotería del Cauca example used two fixed ISPs and an alternate DobleClick medium. The correct arrangement depends on route evidence, application tolerance and field-response needs, not brand size.

Switching away is a civil-works programme

Internet access is often procured as if changing provider were a billing event. For an institutional DobleClick deployment, switching may involve a building entry, fibre splice, radio mount, tower permission, ONT, router, public IP addresses, firewall policy, VPN peers, monitoring integration, Wi-Fi design, telephone or television services, and a local support routine. The more DobleClick coordinates, the more operational knowledge accumulates around it.

Some switching costs are productive. A well-installed access path and documented LAN improve the institution. Others are avoidable. Provider-assigned IPv4 space can require renumbering. Leased managed equipment can disappear at termination. Undocumented radio paths, passwords or VLANs can make a successor reconstruct the service. A bundle can turn an internet migration into simultaneous changes to television, voice or mobile accounts. Minimum-term or connection-cost recovery can add a financial exit charge.

The contract should therefore include an exit design on day one. The customer needs current diagrams, an asset and ownership list, configuration export, address plan, log and ticket export, return conditions, porting or renumbering assistance, termination charges, notice periods and a right to run the old and new services in parallel. Critical applications should use portable naming and overlay security rather than bind directly to one access address where feasible.

An annual migration rehearsal need not disconnect the service. The institution can verify that documentation is complete, credentials are controlled, a second path can carry priority traffic, and upstream-dependent addresses are known. Switching discipline also improves bargaining power: DobleClick can be rewarded for performance without becoming irreplaceable by accident.

The dossier DobleClick should be able to produce

The decisive procurement document is not a glossy coverage map. It is a claim-to-evidence dossier that follows the service from legal entity to application traffic.

Identity and authority. The file should contain a current chamber-of-commerce certificate, RUT, NIT verification, RUP where relevant, telecom-provider registration, insurance, bank-account validation and the authority of each signatory. It should reconcile the INGENIERIA legal spelling with the INGENERIA routing name and identify any subcontractor or consortium member. AS264646 and each address block used for the service should be mapped to the party authorised to announce it.

Physical control. DobleClick should identify the access medium and provide a route-level diagram suitable for confidential review. The diagram should mark owned fibre, leased fibre or transport, poles, towers, microwave hops, building entries, aggregation nodes, core sites and carrier hand-offs. It should state who owns each asset, who can repair it, who grants access and where the proposed primary and backup paths share infrastructure.

Capacity and routing. The buyer should receive committed and peak capacity, utilisation history, oversubscription policy, interface headroom and upgrade lead time. The routing appendix should list prefixes, address provenance, upstream ASNs, BGP policy, RPKI status, IRR objects, max-prefix controls and planned changes. For critical sites, DobleClick should show how traffic reaches at least two relevant external destinations under normal and failed conditions.

Power and environment. Every material node needs commercial-power dependency, battery autonomy, generator arrangement, fuel or recharge process, grounding, lightning protection, environmental monitoring and maintenance history. Radio paths require line-of-sight margin, frequency plan, interference handling and wind-rated installation. Fibre routes require restoration stock, splice capability and access to ducts or poles.

Operations and restoration. The NOC schedule, monitoring tools, ticket fields, escalation matrix, maintenance process, spares inventory and field-team coverage should be visible. Historical performance should include availability, latency, loss, incidents, cause categories, acknowledge time and restore time by municipality or comparable route. Where safety can prevent dispatch, the contract should define communication, temporary alternatives and the boundary between force majeure and reasonable preparedness.

Security and privacy. DobleClick should document route filtering, anti-spoofing, DDoS response, CPE hardening, administrator access, logging, vulnerability and patch management, incident notification, subcontractor access and personal-data handling. Certifications should be checked for issuing body, scope, location and expiry rather than accepted as a logo. If there is no certification, the buyer can test the underlying controls directly.

Commercial and exit terms. The price schedule should separate construction, equipment, capacity, managed service, backup, public addresses, support and optional bundles. It should identify subsidies and minimum terms, set chronic-failure remedies, and define ownership at termination. The exit exhibit should promise documentation, configuration and log handover plus a transition window.

Acceptance evidence. Each site should have photographs and labels, route and equipment confirmation, optical or radio measurements, throughput in both directions, latency, jitter, loss, public-address tests, security checks, alarm verification and a witnessed failover. The customer and operator should sign the baseline. Monthly reporting should use the same definitions, making later arguments comparable to the day the service was accepted.

This dossier is demanding, but it favours a capable regional operator. It allows DobleClick to turn local knowledge, number resources, field presence and integrated support into scored evidence rather than asking a committee to trust a smaller brand. It also prevents a larger competitor from winning solely through generic corporate credentials while hiding a weak local delivery chain.

A decision framework for an institutional buyer

The buyer should begin by classifying sites, not suppliers. A low-impact office that can use mobile tethering during a fault does not need the same design as a hospital, payment operation, emergency centre or multi-school aggregation node. For each site, define the applications, maximum tolerable interruption, data sensitivity, minimum degraded capacity and safe manual workaround.

Then score DobleClick on the controls that match that service class.

For ordinary sites, feasibility, price, measured throughput, support responsiveness and reasonable repair may dominate. A single DobleClick GPON or radio path can be proportionate if users have a tested mobile fallback and the contract avoids excessive lock-in.

For important sites, require a documented backup with a different access medium or route, monitored failover, priority traffic policy, power autonomy and monthly performance. If both links come from DobleClick, demand proof that they diverge beyond the local access. If the evidence is weak, buy the secondary path from another operator.

For critical sites, require end-to-end failure-domain diversity. That can mean different building entries, access owners, aggregation sites, long-haul carriers and power sources, plus an independent wireless or satellite option for regional disruption. DobleClick may supply one or more components, but no supplier assertion should replace a witnessed failure test. The institution should retain control of the firewall, overlay encryption, DNS and traffic policy needed to move applications between paths.

A weighted evaluation could assign substantial value to five categories: verified local delivery, end-to-end resilience, operations and restoration, security and governance, and total lifecycle cost. Headline bandwidth should be a threshold, not the majority of the score. Public-project experience earns credit only when supported by references and outcome evidence. Routing resources earn credit for control and transparency, not as a proxy for capacity.

The award should include conditions precedent. DobleClick must deliver route and asset evidence, close material security findings, agree the measurement method, and pass acceptance and failover tests before the full service term begins. If a promised route cannot be made independent, the buyer can revise the architecture rather than discover the convergence during an outage.

What to watch through the next contract cycle

First, watch whether DobleClick updates its public interconnection record. The gap between PeeringDB’s four-IPv4/one-IPv6 declaration and observed routing is not itself a service problem, but current prefixes, an IRR as-set, facility or exchange presence and a public looking glass would improve verifiability. Monitor the ten IPv4 and twelve IPv6 routes observed at the evidence freeze, their RPKI state, and any change in Lumen or Internexa adjacencies.

Second, watch for proof of genuine upstream and geographic diversity. Multiple BGP neighbours are encouraging. What matters to an institution is whether contracted paths use separate entrances, nodes, carrier hand-offs, long-haul routes and power. A new upstream or exchange connection is valuable only if it reduces a relevant failure domain or improves latency and capacity.

Third, follow the Nariño programme from selection to outcomes. Activated homes, sustained service, subsidy transition, disconnections, complaint levels and municipality-level performance would reveal more than the initial award. The same applies to educational and institutional contracts in Cauca: acceptance evidence and restoration history should inform future bids.

Fourth, track the 900 MHz process by permit, not by expression of interest. If DobleClick later obtains local spectrum rights, the band could alter fixed-wireless coverage and cost. Until an award is public, it should not be priced as an existing asset.

Fifth, ask for a current security and incident package each year. RPKI status can change; firmware ages; staff and upstreams change; attack patterns evolve. A privacy policy from 2019 and valid route origins are foundations, not a complete 2026 control environment. Improvement should be visible in route records, vulnerability handling, DDoS tests, CPE practice and post-incident learning.

Finally, measure whether DobleClick’s local coordination advantage survives growth. The company’s opportunity is to make its Popayán-centred control tower more systematic without losing field knowledge: accurate maps, independent power, documented routes, disciplined NOC evidence and repeatable restoration. Its risk is that more municipalities, bundles, address space and public obligations add dependencies faster than operational resilience.

DobleClick should not be judged as a miniature national carrier. Nor should local presence exempt it from carrier-grade evidence. Its strongest proposition is narrower and more valuable: it can coordinate the last, difficult part of regional connectivity and connect that work to a real autonomous network. The institutional buyer’s job is to make that coordination observable, contractible and testable—especially on the day when the road, the radio and the route all matter at once.