Data Services Pacific: cloud economics in New Caledonia

Summary

What it says: Thesis
Main topic: Cloud service dependency; Local cloud substitution
Context: Internet infrastructure / Company research / Asia-Pacific

Below hyperscale, above the island: Data Services Pacific and the economics of local cloud survival in New Caledonia

Thesis

Data Services Pacific is best understood not as a miniature hyperscaler, nor simply as a local web host, but as a trusted continuity intermediary built around rare local infrastructure in New Caledonia. Its value is produced by three mechanisms unusually visible in small island markets: control of local hosting space, publicly verifiable Internet number resources, and the ability to convert proximity into operational trust. Its constraint is just as clear: it sits below the scale at which cloud economics are dictated by global purchasing power, but above the scale at which a customer can self-host at lower cost.

This middle ground creates a business in which survival depends less on raw computing power than on local credibility, route visibility, vendor relationships, jurisdictional comfort, and customer switching costs.

Public records present Data Services Pacific, often abbreviated as DSP, as a hosting and cloud services operator based in Nouméa and associated with Groupe CIPAC. DSP appears in APNIC records under the organization name ORG-DSP1-AP, an APNIC local Internet registry in New Caledonia, with the same Nouméa address used on its website, legal notices, PeeringDB records, and customer hosting disclosures. Its current routed network identity is AS134405, with three /24 IPv4 and three /48 IPv6 prefixes visible in public routing and RPKI-validated route entities.

Public routing databases identify a single upstream transit provider, the Office des Postes et Télécommunications de Nouvelle-Calédonie (OPT-NC), and DSP is also present at the local exchange point CAN’L IX in Nouméa with two 10G ports. DSP presents itself as the only local player with two data centers and describes a third site for backup replication; PeeringDB independently records its DC1 facility in Nouméa, while Data Center Map and DSP’s own documentation identify both DC1 and DC2.

The economic importance does not lie in DSP having a large Internet footprint. It does not. Public IP intelligence sources count only 768 IPv4 addresses announced by AS134405, and PeeringDB places its traffic level in the 100–1000 Mbit/s band with a heavy outbound ratio. This is small by global hosting standards. But smallness is not economic insignificance.

In New Caledonia, where international connectivity, wholesale access, and local infrastructure are shaped by island geography and by OPT-NC’s historically central role, the ability to host applications locally, provide disaster recovery in the territory, publish an independent network identity, and offer a named local engineering team can be economically valuable, even at a modest scale.

DSP thus reveals a broader rule of infrastructure economics in small markets: below hyperscale, trust can substitute for scale only when customers face real friction in migrating elsewhere. Those frictions are legal, geographical, operational, and psychological. A local business may be able to buy distant cloud in Sydney, Singapore, France, or elsewhere, but that does not eliminate the need for local support, predictable latency to local users, data localization comfort, disaster recovery planning, and a counterparty reachable by phone in Nouméa. DSP monetizes these frictions.

Its risk is that these same frictions are not entirely under its control: upstream transit, electricity, imported hardware, software licensing, submarine cable economics, and the broader financial health of the local market remain external constraints.

The target identity: DSP as a legal enterprise, operational label, and holder of network resources

The canonical target is Data Services Pacific, a Nouméa‑based company using the operational label DSP. APNIC records list “Data Services Pacific” under ORG-DSP1-AP, an APNIC local Internet registry in New Caledonia, with the address 210 Rue Gervolino, Nouméa, and administrative contacts at dsp.nc. The APNIC registration for AS134405 uses the as-name DATASERVICESPACIFIC-AS-AP, describes the holder as Data Services Pacific, and links the network to the same organization record. Abuse‑handling and incident‑response registrations are also at dsp.nc, and the abuse contact was validated in February 2026.

This establishes that Data Services Pacific is not just a brand appearing on a website; it is the public‑registry entity associated with routable Internet number resources.

The legal identity visible in New Caledonian trade registry notices is “DATA SERVICES PACIFIC”, R.C.S. Nouméa 2005 B 759 779, a SARL with its registered office at 210 rue Gervolino. A 2011 registry notice records the company name, trading name, SARL form, capital of 1,000,000 XPF, Nouméa address, and a change of directors. A 2014 notice records the same RCS number and SARL form with different directors. A 2018 registry notice records a formal decision not to dissolve the company after equity fell below half the share capital.

The 2024 electoral list of the Chamber of Commerce and Industry still includes DATA SERVICES PACIFIC with the same RCS/RIDET number in the services category. These records indicate legal entity continuity from at least 2005 through 2024, but they do not by themselves reveal current shareholding or full funding arrangements.

The ownership and operational‑control context is more ambiguous. DSP’s website describes it as “100% private”, based in Nouméa, and dedicated to hosting IT solutions. DSP’s downloadable brochure, however, describes DSP as a subsidiary of Groupe CIPAC. The 2026 CIPAC article also calls DSP a subsidiary of CIPAC, and DSP’s legal notice states that the dsp.nc site is administered by CIPAC SA, a Nouméan company with its own RCS and RIDET identifiers. The most prudent reading is that Data Services Pacific remains the legal/network‑services company and DSP the operational label, while CIPAC is the group or parent‑company context.

Public evidence does not prove the exact current chain of shareholders, but it does prove that the operational identity DSP, the APNIC resource identity, and the Groupe CIPAC context are linked.

This ambiguity matters economically. If DSP is a standalone SARL with limited parent‑company support, its survival depends heavily on its own cash flows and borrowing capacity. If it is backed significantly by Groupe CIPAC, DSP may be able to bear data‑center fixed costs, hardware procurement cycles, and customer collection delays more comfortably than a pure independent hoster. The 2018 non‑dissolution notice is therefore a significant survival signal: at some point the company had experienced enough accounting losses or balance‑sheet deterioration to trigger formal equity‑loss procedures.

Later public evidence of activity, current APNIC validation, data‑center expansion, and CIPAC articles suggest continued operations, but they do not erase the earlier marker of financial stress.

What DSP sells: local continuity, not generic computation

DSP’s website frames its offer around hosting, cloud services, security, reliability, proximity, and performance. It describes rack rental, power, redundant Internet connectivity, cooling, and physical security as core colocation functions, while the customer retains ownership of its hardware and software. The same site stresses the benefits of local hosting: infrastructure outsourcing, proximity, security, simpler relationships, a French and European legal framework, bandwidth costs, network performance, resilience, and an ecosystem of local partners and Internet service providers.

In economic terms, this is a bundle of physical hosting, local network access, managed operations, and jurisdictional comfort.

The service catalogue goes beyond colocation. DSP’s brochure and CIPAC documents describe IaaS, BaaS, DRaaS, private cloud, application hosting, backup, supervision, platform operations, disaster recovery planning, business continuity planning, Microsoft licensing, and support. The 2026 CIPAC article on GPUaaS adds a more recent layer: DSP had acquired two dedicated AI servers and planned to offer computing capacity on a monthly rental, positioned as a New Caledonian sovereign‑cloud extension. This GPUaaS move is economically revealing. It is not a hyperscale AI build‑out; it is a local capacity experiment.

The question is whether there is enough local demand for GPU‑hours from public institutions, healthcare establishments, local government, digital players, and businesses to justify the immobilised‑capital risk of specialised servers.

The brochure describes DSP’s value chain as “end‑to‑end” and emphasises a single point of contact, 24/7 support, 30‑minute intervention, monitoring and supervision, backup operations, hardware vendor relationships, and provider coordination. Its SLA document mentions 99.98% annual availability for the data‑centre hosting environment, 99.8% annual availability for hosted services, a 30‑minute response commitment, a 4‑hour restoration objective, and disaster‑recovery objectives of RTO two hours and RPO 24 hours.

These are self‑stated commercial commitments, not third‑party certification results, but they show the shape of the product: DSP sells operational assurance more than raw computing.

The brochure also claims about 100 customers on a resilient and proven platform. The public sample of customers is smaller but economically significant. Nespresso New Caledonia’s legal notice identifies DSP as the host. MDF, a local medical and dental services group, identifies Data Services Pacific as the host of its website. ISEE, the official statistical institute of New Caledonia, lists DSP as the host of its website. This does not prove the entire client base, and website hosting does not necessarily mean full IaaS or disaster recovery.

But the visible sample covers retail/e‑commerce, healthcare‑adjacent services, and public/statistical presence, which are exactly the categories where local trust, continuity, and data‑localization comfort can matter.

DSP’s LinkedIn profile gives an additional channel signal. It describes the company as a private New Caledonian firm specialising in outsourcing and hosting, with over ten years’ experience, two interconnected data centres, fallback rooms for business continuity, and specialities including datacentre, hosting, VPS, IaaS, PaaS, SaaS, networking, Microsoft SPLA, Veeam, backup, replication, storage, disaster recovery, business continuity, BaaS, DRaaS, IXP, private cloud, and sovereign cloud.

LinkedIn is not an audited source, and several terms, including ISO27001 and HDS, appear as profile keywords rather than certifications verified in the public registry examined here. Nevertheless, it is useful as market‑channel material: DSP wants buyers to perceive it as a local sovereign‑cloud and continuity provider, not as a low‑end shared hoster.

Geography and facilities: the scarcity of local hosting space

The physical footprint is central to DSP’s economics. DSP’s website and brochure place the business at 210 rue Gervolino in Nouméa. PeeringDB records the DSP DC1 facility at the same address and lists Data Services Pacific as the underlying organisation. PeeringDB also records two networks in the facility: Data Services Pacific AS134405 and THEMIS AS149520, and identifies CAN’L IX as present there. This matters because recognition of a facility in PeeringDB is a form of industry‑readable infrastructure evidence. It tells network operators that DSP DC1 is not just a building with servers but a place where networks can interconnect.

DSP’s own documentation claims a second data centre, DC2‑GAL, used for disaster recovery and business continuity, and indicates that backups are copied to a third site. Its infrastructure diagram shows production, disaster‑recovery, and off‑site backup sites, with links to OPT, CAN’L, Lagoon, and the local exchange point. Data Center Map independently lists two DSP facilities in Nouméa: DSP‑DC1 at 210 rue Gervolino with 20 racks and DSP‑DC2 at 34 rue du général Gallieni with 6 racks. This confirms the existence of two DSP data‑centre locations, while also showing their small absolute scale.

A 20‑rack and 6‑rack footprint is not hyperscale infrastructure; it is a local resilience platform.

The March 2025 CIPAC article indicated that DSP was expanding its second data centre to support economic activity and growing digital needs in New Caledonia, with an emphasis on resilience in the face of socio‑political challenges and cybersecurity risk. The expansion included additional hosting space, access control, a new security vestibule, and a preparation area. This is useful because it is a recent group‑level signal that DSP was still investing in physical infrastructure after the 2018 financial‑stress marker.

It also implies that the local‑demand thesis had not disappeared: CIPAC and DSP saw sufficient market need to justify capacity and security work on the second site.

The unresolved point is the independent status of the third site. DSP’s brochure states that backups are copied to a third site and that data is secured in three tier‑one data centres in New Caledonia. The public facility directories and PeeringDB records examined here do not independently identify a third data centre operated by DSP. The economic interpretation must therefore distinguish between “two named DSP data centres” and “a third backup site claimed in DSP documentation”. If the third site is a contractually robust, geographically separate, controlled data centre, DSP’s disaster‑recovery value is stronger.

If it is a smaller backup location or a partner site, the product may still be valuable, but the resilience claim depends more on contractual detail and operational execution than on owned physical infrastructure.

Small local data centres have a different cost curve from hyperscale sites. They do not enjoy the same purchasing power over energy systems, servers, cooling equipment, optical transport, security systems, or software licences. Their advantage is not lower unit computing cost; it is lower transaction cost for local continuity. For a New Caledonian buyer, moving a workload to DSP can avoid capital expenditure on an on‑premises server room, reduce the local operational burden, and keep support relationships in Nouméa.

DSP’s brochure itself makes this explicit by selling outsourcing, support, backup, supervision, and energy savings, including an estimate of up to 118,000 XPF excluding tax per 42U rack per month in energy savings over customer premises. That figure is a marketing claim, but it illustrates the business logic: DSP converts the hidden cost of small corporate server rooms into recurring infrastructure revenue.

ASN, addresses, and route visibility as economic assets

AS134405 is the current public network identity of Data Services Pacific. BGP.tools identifies AS134405 as registered in October 2018, allocated under APNIC, and announcing three IPv4 and three IPv6 prefixes: 103.123.232.0/24, 103.123.233.0/24, 203.34.36.0/24, 2404:e9c0::/48, 2404:e9c0:1::/48, and 2404:e9c0:2::/48. BGP.tools marks the listed routes as RPKI‑valid. IPinfo similarly counts 768 IPv4 addresses and identifies the three /24 IPv4 prefixes as RPKI‑valid, while WhatIsMyIP lists the same six IP ranges in New Caledonia.

The address block 203.34.36.0/24 is particularly interesting because APNIC lists it as “ASSIGNED PORTABLE”, with the network name DATASERVICESPACIFIC-NC. Portable address space can be more valuable than provider‑assigned space in a small hosting economy because it gives the operator greater continuity across upstream‑provider changes and supports a more independent routing identity. DSP’s 103.123.232.0/24 block is listed as DATA-SERVICES-PACIFIC-DC1, with the description “Data Services Pacific DC 1 Noumea”, while APNIC also records the IPv6 allocation 2404:e9c0::/32 to Data Services Pacific.

The blocks are not large, but they are sufficient to support a local hosting and cloud platform with publicly visible routing and reputation.

DSP also holds a historical ASN, AS24053. APNIC and BGP.tools identify AS24053 as Data Services Pacific, registered in 2005, but BGP.tools indicates it is not currently in the global routing table and announces no IPv4 or IPv6 prefixes. The likely economic interpretation is a network‑identity transition: AS24053 reflects an older history of DSP Internet resources, while AS134405 is the current routed identity. The public record does not explain why AS24053 remains allocated but not routed. This unresolved fact is not trivial.

A retained but inactive ASN can be an administrative leftover, a standby asset, a historical migration artefact, or a sign of earlier routing arrangements later replaced.

Route visibility is commercially important because it turns an otherwise opaque local infrastructure provider into a verifiable network peer. Customers, suppliers, and operators can observe that DSP has an APNIC record, validated abuse contacts, routable prefixes, RPKI‑valid announcements, a PeeringDB presence, and visible interconnection at CAN’L IX. In a small market, this is a reputation asset. It lowers due‑diligence costs for buyers who need evidence that the provider is not merely reselling anonymous hosting, and it creates accountability via the abuse mailbox, route‑entity, and peering records.

The same visibility also exposes DSP’s limits. IPinfo labels AS134405 as a stub AS, lists one peer and one upstream, and shows no downstream. Its observed traceroute from Nouméa passes through AS18200 before reaching AS134405. PeeringDB gives DSP’s traffic level as 100–1000 Mbit/s and its traffic ratio as heavily outbound. These signals are consistent with a hosting/cloud operator that serves local customers and sends hosted content or application traffic outward, not with a carrier‑scale network or a transit provider. Public visibility thus creates trust, but it also prevents DSP from pretending to be larger than it is.

Upstream dependency: the invisible price‑setter

The central external dependency in DSP’s economics is OPT-NC. BGP.tools identifies AS18200, Office des Postes et Télécommunications de Nouvelle-Calédonie, as DSP’s upstream provider for both IPv4 and IPv6. IPinfo also lists AS18200 as DSP’s sole upstream. PeeringDB records DSP at CAN’L IX, but BGP.tools and IPinfo still show the upstream graph as dependent on OPT. This combination is economically important: local peering can reduce cost and latency for local traffic, but it does not eliminate dependence on the territory’s dominant infrastructure provider for wider reach.

The regulatory context reinforces this. The New Caledonian Competition Authority indicates that OPT-NC holds a monopoly over public telecommunications services, while the Internet access market is open to competition. The same summary warns about the relationship between OPT-NC’s monopoly missions and competitive markets, including cross‑subsidy risks, and recommends a declaratory rather than a restrictive authorisation regime for Internet service providers and service operators.

Another market summary describes OPT-NC as dominating the telecommunications sector, including fixed and mobile voice, mobile Internet, fixed broadband, and wholesale services to ISPs.

The submarine‑cable layer is also relevant. OPT-NC’s own document describes Gondwana-1 as the cable connecting Nouméa to Sydney since 2008 and indicates that a second cable project has been launched to provide additional capacity and resilience. SubmarineNetworks identifies Gondwana-1 as a 2,151 km system linking New Caledonia and Australia, ready for service in September 2008 and owned/operated by the public OPT. For DSP, this means that the cost and resilience of international access are not simply a procurement item; they are structural determinants of the local hosting market.

If international bandwidth is expensive or fragile, local hosting is more valuable. If international capacity becomes cheaper, more resilient, and more competitive, distant‑cloud substitutes become stronger.

DSP’s brochure shows this dependency indirectly. Its network diagram references OPT links across multiple sites and also mentions CAN’L, Lagoon, and local interconnection. It argues that local hosting can improve performance and resilience and reduce the cost of local and international bandwidth. The economic mechanism is clear: DSP does not need to own international cables to benefit from their scarcity. It needs to sit at the point where local customers experience that scarcity as risk, latency, price, or complexity, and then sell a locally managed alternative for workloads that can stay in New Caledonia.

This also defines DSP’s bargaining problem. A small hosting operator with a single publicly visible upstream does not have strong supplier diversification. Its margins can be squeezed by upstream transit pricing, electricity costs, equipment import costs, maintenance contracts, and software licence fees. Its pricing power vis‐à‐vis buyers must come from service differentiation, not from procurement scale. The two CAN’L IX 10G ports are useful, but they do not by themselves create wholesale bargaining parity with OPT-NC. They create local network legitimacy and local traffic efficiency.

CAN’L IX and the local interconnection layer

DSP’s interconnection position is visible at CAN’L IX. PeeringDB records CAN’L IX in Nouméa with five peers, seven connections, and a total capacity of 60G. DSP appears there with two 10G connections, IPv4 addresses 103.23.55.9 and 103.23.55.10, IPv6 addresses 2401:c00:1:4::9 and 2401:c00:1:4::10, and an open peering policy. PeeringDB also records DSP’s network profile as open peering, with no contract requirement, no traffic‑ratio requirement, and no multi‑site requirement.

The IX footprint has two economic effects. First, it supports local performance. If local ISPs, hosting providers, or utility networks exchange traffic at CAN’L IX, customer applications hosted at DSP can be reached via shorter local paths instead of taking a detour through distant transit. Second, it supports market trust. In small markets, the ability to say “we are present at the local exchange point” signals that a hosting provider is part of the local operator ecosystem rather than a pure reseller or a desktop IT shop.

The limitation is that CAN’L IX is itself small. Five peers and seven connections are useful but not transformative in a global routing sense. The peer list includes local actors, and DSP’s PeeringDB profile places its scope in Asia‑Pacific, not global. This is the classic island‑interconnection trade‑off: the local exchange point can save on local traffic and make local hosting more attractive, while the island still depends on upstream international capacity for outside reach.

The IX location inside DSP DC1 or associated with the DSP DC1 facility raises DSP’s strategic value. PeeringDB records CAN’L IX at DSP DC1, and the DSP facility record lists both CAN’L IX and the networks present on site. This means DSP is not just a user of interconnection; it is also a physical host of part of the local interconnection fabric. This is an important distinction. A small data‑center operator with an IX presence can monetize colocation, cross‑connects, network adjacency, and reputational centrality even when raw compute demand is limited.

Address scarcity, reputation, and the trust premium

DSP’s public address pool is small: 768 IPv4 addresses spread across three /24s. In a large cloud, that would be trivial. In a small island hosting market, it is enough to create a scarce, reputation‑bearing asset. IPv4 addresses can be allocated to hosted services, customer VMs, NAT pools, DNS, VPN, email, monitoring, and management systems. Because address reputation is cumulative, every abuse event or misconfigured customer can impose a cost on the whole operator. A small operator therefore has less room for noisy tenants than a hyperscaler.

IPinfo reports 35 domains hosted on AS134405 and labels at least one IP as associated with VPN usage. That VPN label should not be over‑interpreted: it is a third‑party classification signal, not proof of abuse or misconduct. But it illustrates why resource visibility matters. Hosting companies are judged on the cleanliness, responsiveness, and traceability of their IP space. DSP’s APNIC abuse‑contact validation in 2026 and its visible RPKI‑valid routes are therefore part of the trust product. They tell counterparties that the operator can be identified, contacted, and held accountable within the normal Internet‑governance stack.

For enterprise and public‑sector customers, this matters more than it may appear. A small local cloud provider cannot compete with hyperscalers on service breadth or base compute price. It can compete on reducing operational uncertainty. A buyer can verify the provider’s address resources, inquire about local routing, inspect other local customers’ legal notices, visit the facility or meet the team, and escalate problems through local relationships. This bundle of checks is a trust premium. It is also difficult to scale beyond the territory.

The same local anchoring that makes DSP credible in Nouméa may not travel well to a broader regional market.

Address‑resource visibility also affects switching costs. If a customer uses DSP‑provided IP addresses, hosted DNS, backups, VPNs, or firewall rules, migration is not just about copying VMs. It involves re‑addressing, DNS cutovers, firewall changes, backup‑chain migration, compliance review, operational testing, and user retraining. For a customer with disaster‑recovery or managed backups at DSP, the switching cost is even higher because the historical backup set and recovery procedures are part of the service. DSP’s brochure emphasizes backup, replication, supervision, and BCP/DRP precisely because these are sticky products.

Revenue logic: recurring services on scarce local assurance

DSP’s revenue model is not disclosed in detail in public prices. The website says that offers are tailored to customer requirements and invites buyers to contact the company for availability, terms, and pricing. This absence of posted prices is itself informative. In small enterprise‑infrastructure markets, pricing is often configured around rack space, power density, bandwidth commitments, VM sizing, backup retention, recovery objectives, Microsoft or other software licensing, managed‑service hours, and support commitments. Public price menus are less useful when the product is a risk bundle rather than a standardised server.

Likely recurring revenue streams are colocation or rack rental, virtual infrastructure, hosted applications, private cloud, backup, disaster recovery, monitoring, support, licence pass‑through, and, more recently, GPU capacity on monthly rental. The CIPAC GPUaaS article explicitly states that the AI servers would be offered on a monthly rental and describes DSP’s broader service lines as IaaS, BaaS, DRaaS, private hosting/cloud, and GPUaaS. These are recurring or quasi‑recurring services, which is economically attractive because data‑centre fixed costs are high and utilization counts.

Pricing power comes from five sources. The first is local scarcity: DSP claims to be the only player with two data centres, and facility directories show only a small number of listed data centres in New Caledonia. The second is operational proximity: DSP advertises local support, simplified relationships, and a local team. The third is legal and data‑localization comfort: its own documentation sells a French and European legal framework and local data security. The fourth is interconnection: DSP has a visible ASN, RPKI presence, and CAN’L IX presence.

The fifth is switching cost: backup, disaster recovery, and managed infrastructure are harder to migrate than a static website.

Margin pressure comes from the other side of the balance sheet. DSP must pay for electricity, cooling, facility maintenance, security systems, battery or generator resilience, imported hardware, vendor support, software licensing, staff, and upstream connectivity. Its brochure displays logos of technology partners, including APC, VMware, Microsoft SPLA Partner, Veeam, Dell EMC, Synology, Cisco, and related infrastructure vendors. These relationships help DSP deliver enterprise‑grade services, but they also expose it to foreign‑currency constraints, licensing, support, and procurement constraints.

A small operator cannot dictate terms to Microsoft, VMware, Veeam, Cisco, or Dell EMC.

The most delicate margin question is utilization. A local data centre must bear high fixed costs whether racks are full or empty. Adding GPU servers raises the utilization risk because specialised computing depreciates quickly and depends on workload adoption. If local businesses, public institutions, healthcare entities, and digital players consume GPU regularly, DSP can build a differentiated sovereign‑compute niche. If demand is episodic, the GPUaaS becomes a capital outlay that is symbolically useful but financially weak.

This is the same below‑hyperscale problem in a more acute form: local control has value, but hardware economics still punish under‑utilization.

Customer trust: why local evidence can beat global scale for some workloads

The public evidence suggests that DSP serves customers for whom local trust matters. The ISEE website identifies DSP as the host; MDF’s legal notice identifies Data Services Pacific as the host; Nespresso New Caledonia’s legal notice identifies DSP as the host. These are visible examples rather than a full account list, but they cover public information, healthcare‑adjacent services, and consumer retail. In each case, the commercial significance lies less in the complexity of the web hosting than in the reputation signal: local institutions and recognisable brands are willing to disclose DSP as an infrastructure counterparty.

Trust in local infrastructure has several layers. The first is physical trust: customers can know where the servers are and, in some cases, visit or audit the facility. The second is legal trust: DSP sells local hosting under a French and European legal framework. The third is operational trust: DSP names support commitments, monitoring, restoration objectives, and local intervention. The fourth is social trust: in a small market, reputation travels through business networks, integrators, ISPs, and group relationships. DSP’s website itself says it is positioned at the centre of the local digital ecosystem and relies on a partner network.

This trust premium is economically rational when the alternative is not simply “AWS vs. DSP”, but a more complex choice among on‑premises server rooms, local ISP services, regional cloud reachable via international links, and managed‑service providers. A Nouméan customer may prefer distant cloud for elasticity, service breadth, or global tooling. But if the workload is local, latency‑sensitive, politically or legally sensitive, or operationally dependent on local technicians, DSP’s smaller scale can be offset by proximity and accountability.

The trade‑off is concentration. A customer that outsources core hosting, backup, and disaster recovery to the same local provider may reduce internal complexity while increasing counterparty dependence. DSP’s “single point of contact” promise is commercially attractive because it lowers coordination cost. It is also a lock‑in mechanism. The more DSP manages, the more expensive it becomes for the customer to split colocation, backup, licensing, monitoring, disaster recovery, and support across multiple providers.

Competitive landscape: local ISPs, on‑premises rooms, and distant cloud

New Caledonia’s connectivity market is shaped by the interaction of OPT-NC, local ISPs, and service operators. The APNIC blog notes that despite OPT-NC’s historical infrastructure monopoly, CAN’L was created as an ISP in 1995 with the involvement of Groupe CIPAC, followed by MLS in 1997 and later Telenet and Nautile. The HE.net New Caledonia network list shows local ASNs including OPT-NC, Micro Logic Systems, OFFRATEL, Nautile, TeleNet, CAN’L, and DSP, with OPT-NC much larger in terms of adjacencies and routes.

The DB-IP country allocation table similarly shows OPT, OFFRATEL, CAN’L, Micro Logic, Nautile, and TeleNet with larger IPv4 allocations than DSP.

DSP’s competition must therefore be separated by layer. At the access level, ISPs and telecom operators control customer connectivity and can bundle adjacent services. At the hosting level, on‑premises server rooms remain a substitute for small businesses, especially when budgets are tight or legacy systems hard to move. At the cloud level, distant hyperscalers and regional data centres can offer lower unit compute costs and wider service catalogues. At the managed‑services level, local integrators can compete for customer relationships even if they do not own data centres.

DSP’s defensible zone is where local hosting, network presence, and managed continuity need to be bought together.

Buyer power is probably mixed. Large public institutions, telecom‑affiliated buyers, banks, healthcare entities, and larger enterprises can demand service guarantees and negotiate on price because their contracts matter to a small provider. Small businesses have less bargaining leverage but can still choose on‑premises equipment, ISP bundles, or distant cloud. DSP’s ability to maintain pricing depends on whether customers see local resilience and support as mission‑critical or as optional insurance.

Supplier power is structurally high. OPT-NC’s wholesale and infrastructure role gives it influence over the economics of local and international connectivity. Electricity and facility inputs are local constraints. Hardware and software vendors are external. In this context, DSP’s best procurement advantage may be its Groupe CIPAC affiliation and its relationships with local ISPs and partners, rather than its own scale. CIPAC’s wider digital ecosystem references CAN’L, DSP, Satnet, Le Cube, and related services, indicating a channel environment where group relationships can count commercially.

Regulatory change could be double‑edged. A more open and competitive wholesale environment could reduce DSP’s upstream costs and improve redundancy options. It could also make it easier for other service operators to enter hosting, interconnection, or cloud‑adjacent services. The Competition Authority’s preference for a declaratory regime over administrative authorisation would generally lower entry barriers for service operators, which is good for market dynamism but not automatically good for DSP’s pricing power.

Corporate control context and survival below scale

The most important corporate‑control fact is the CIPAC connection. DSP’s brochure calls it a Groupe CIPAC subsidiary, CIPAC articles call it a subsidiary, and the dsp.nc legal notice identifies CIPAC SA as the website administrator. CIPAC’s public communications position DSP as part of a broader local digital infrastructure offering, with services for businesses, public institutions, local government, healthcare establishments, and digital players. This parent‑ or group‑company context probably gives DSP a commercial reach that a standalone technical hoster would lack.

The 2026 CIPAC article describes DSP’s infrastructure as “invisible” but essential for local organizations, with IaaS providing locally hosted, backed‑up, monitored, and operated virtualised servers. This framing is commercially useful: it recasts hosting from a commodity into a continuity layer for New Caledonia’s economy. The 2025 CIPAC article on second‑data‑centre expansion similarly places DSP in the context of economic continuity, local digital needs, socio‑political risk, and cybersecurity.

These are not neutral third‑party assessments, but they reveal how the group wants to sell DSP internally to the market: as a resilience platform, not as a hosting workshop.

The 2018 non‑dissolution notice complicates the narrative. A company whose equity fell below half the share capital had experienced significant accumulated losses or balance‑sheet impairment. For a small infrastructure operator, that could reflect the high fixed costs of data‑centre investment, under‑utilization, price pressure, slow customer adoption, or group‑level restructuring. The public record does not reveal which. Later evidence of the 2018 AS134405 allocation, active APNIC records, data‑centre expansion, and new GPU services suggests that DSP survived and continued to invest.

But the survival may have required group support, recapitalisation, creditor patience, or higher utilization.

This is the central below‑hyperscale survival problem. Data‑centre economics reward high utilization and procurement scale. Small‑market trust economics reward proximity, redundancy, and customised support. DSP sits between the two. If utilization is high enough and customers pay a premium for local continuity, the business can survive despite limited scale. If customers treat local hosting as a commodity, DSP is exposed to margin compression from upstream suppliers and downstream buyers.

The public evidence points to an operator that has chosen to deepen differentiation—two data centres, backup replication, DRaaS, sovereign cloud, GPUaaS—rather than compete on generic server price.

The economic significance of two data centres

DSP’s claim to be the only local player with two data centres is not just a marketing argument; it is a pricing argument. A single‑site hoster sells availability within one facility. A dual‑site hoster can sell continuity, replication, failover, backup separation, and disaster‑recovery planning. DSP’s brochure explicitly describes DC1‑MGTA as the first production site and DC2‑GAL as the second site used for disaster recovery and business continuity, with backups copied to a third site. Its SLA document includes RTO and RPO objectives, which are commercially credible only when the provider can point to geographically separated infrastructure.

The small physical scale does not invalidate the strategy. In a territory with limited listed data‑centre capacity, a 20‑rack production facility and a 6‑rack secondary site can be significant. The unit economics, however, are fragile. A second site increases fixed costs before it increases revenue. It requires space, power, cooling, access control, networking, replication equipment, monitoring, and staff procedures. The 2025 CIPAC expansion article shows precisely those investments: hosting space, access control, a new security vestibule, and a preparation area.

The dual‑site strategy creates an insurance‑like revenue model. Customers pay recurring fees for an event they hope not to experience: an outage, a cyberattack, a hardware failure, a disaster, or the loss of a site. The provider must maintain readiness even when no incident occurs. This makes trust central. A customer does not buy DRaaS just because it is cheap; they buy because they believe the provider will be there when failure happens. DSP’s local address, named team, facility visibility, APNIC identity, and public customer disclosures all contribute to sustaining that belief.

The unresolved economic question is whether DSP’s dual‑site capability is sold mainly as high‑margin insurance to many customers, or as bespoke infrastructure to a smaller number of large accounts. The claim of about 100 customers in the brochure suggests a relatively broad base, but public evidence does not reveal revenue concentration. If a few large customers anchor the data centres, DSP’s economics are sensitive to contract renewal. If many mid‑sized customers buy backup and hosting services, DSP has more diversified recurring revenue but may face higher support complexity.

DNS, hosted domains, and the visible edge of the customer base

Public IP intelligence shows only a partial view of DSP’s customer base. IPinfo reports 35 domains hosted on 11 IPs within AS134405. This is not a complete account count because many customers may use private addressing, customer‑owned domains, remote DNS, VPN‑only services, colocation without public IP disclosure, or IPs not easily attributable through reverse domain collection. Nonetheless, the domain count supports the picture that DSP is a modest‑sized hosting operator rather than a mass‑shared hosting platform.

The visible legal notices matter because they are deliberate disclosures. ISEE, MDF, and Nespresso New Caledonia identify DSP as the host in their own public documents. In French and European legal‑notice culture, host disclosure is a compliance and accountability practice. That makes DSP part of the public trust chain for those sites. The commercial implication is that DSP’s name appears where end‑users, regulators, suppliers, or litigants might find it. A hoster willing to be named by public organisations must maintain basic reputation hygiene.

The customer evidence also suggests a channel model. DSP’s website emphasises partners and a local digital ecosystem, while ISEE’s legal notice names SKAZY as the site creator and maintainer but DSP as the host. This is a common infrastructure division: web agencies or integrators own the application relationship, while DSP supplies hosting, backup, networking, and facility services. For DSP, channel relationships with agencies, ISPs, integrators, and CIPAC affiliates may be as important as direct sales.

This channel model affects margins and bargaining. If DSP reaches customers via integrators, it can gain volume without heavy sales overhead, but it may also share margin or lose direct control of customer perception. If it sells directly to large accounts, it can price risk more fully but must bear enterprise sales and support costs. The evidence suggests both moves: DSP has named sales and support contacts, while ecosystem language and third‑party site creators point to indirect channels.

Security, abuse handling, and reputation signals

The public records consulted for this report do not show any major DSP‑specific incident of outage, breach disclosure, litigation, procurement challenge, licence sanction, or public abuse controversy. This absence must be treated with caution. Incidents in small markets can be handled privately, reported in local French channels not widely indexed, or disclosed only to customers. Absence of public evidence is not evidence of absence. It does mean, however, that no obvious public‑scandal discount is visible in the records examined here.

Positive security signals are operational rather than forensic. APNIC records show a validated abuse contact in 2026. RPKI status appears valid on currently visible prefixes. DSP’s brochure promises monitoring, backup, supervision, hardware‑vendor relationships, provider coordination, 24/7 support, GTI and GTR commitments, and disaster‑recovery objectives. Recent CIPAC articles explicitly frame DSP in relation to cybersecurity risk and continuity. These are not independent security audits, but they show that security and continuity are central to the commercial proposition.

The weakest signal is certification ambiguity. DSP’s LinkedIn profile includes ISO27001 and HDS among specialities or keywords, but the public evidence examined here does not verify certification status. This matters because a verified ISO 27001 certification or French HDS health‑data‑hosting certification would substantially broaden DSP’s credibility for public‑sector, healthcare, and regulated workloads. A keyword on a profile is not enough. Buyers must distinguish between “security‑oriented services”, “certification‑aligned practices”, and “audited certification”.

IP reputation appears manageable in the examined public sources, but not invisible. IPinfo identifies at least one IP associated with VPN usage, while showing a small set of hosted domains, pingable infrastructure, and visible traceroute paths. In a small hosting network based on /24s, even minor reputation issues can have disproportionate effects because address pools are limited. The economically important point is not whether the VPN label is harmful; it is that DSP’s address space is small enough that reputation management must be operationally active.

Alternative hypotheses and which unresolved facts would change the picture

One hypothesis is that DSP is primarily a local sovereign‑cloud and business‑continuity platform. The supporting evidence is strong: the website and brochure emphasise local hosting, legal comfort, proximity, two data centres, backup, DRaaS, BaaS, and SLA commitments; CIPAC articles frame DSP around sovereignty, continuity, and local organisations; APNIC and PeeringDB records show an independent network identity and exchange‑point presence. Under this hypothesis, DSP’s value comes from local trust and infrastructure control, and the central financial question is fixed‑asset utilization.

A second hypothesis is that DSP is in part an infrastructure utility for the CIPAC group. The evidence is suggestive: DSP is described as a CIPAC subsidiary, CIPAC administers the website, and CIPAC’s wider digital ecosystem includes related connectivity and digital services. If this is true, DSP may not need to maximise standalone hosting margins in each service line; it can support group offerings, strengthen customer retention, and provide infrastructure depth to affiliated channels. The economic implication would be lower standalone fragility but higher dependence on group strategy.

A third hypothesis is that DSP is a technically credible but financially constrained niche operator. The 2018 non‑dissolution notice supports the possibility of earlier financial strain. The small IP footprint, small LinkedIn staff signal, limited traffic scale, and single visible upstream all point to an operator below scale. Subsequent expansion and GPUaaS investment suggest resilience, but do not prove strong profitability. Under this hypothesis, DSP survives because it has a defensible local niche, but its margins remain exposed to utilization swings and supplier pricing.

A fourth hypothesis is that DSP’s strategic value lies more in local interconnection and facility control than in cloud services. The evidence is partial. PeeringDB records DSP DC1 as a facility, CAN’L IX is present there, and DSP has two 10G ports at the exchange. This gives DSP a role in the local network graph. But the service documents emphasise hosting, cloud, backup, and disaster recovery more than carrier‑neutral colocation or telecom‑hotel economics. The likely reality is hybrid: the facility and exchange‑point presence supports the cloud product rather than replacing it.

A fifth hypothesis is that DSP’s future depends on whether local sovereign‑compute demand grows faster than substitution by distant cloud. The GPUaaS announcement is the test case. If New Caledonian public institutions, healthcare entities, and businesses need local AI or data‑processing capacity for sovereignty, latency, or compliance reasons, DSP can capture a premium. If workloads are sporadic or better served by distant clouds, local specialised compute can depress returns. Public evidence proves investment intent; it does not prove demand depth.

What DSP reveals about small‑scale hosting economics in New Caledonia

DSP shows that in small island markets, address‑resource visibility is not a technical footnote. It is part of the commercial product. An ASN, an APNIC organization record, a portable IPv4 block, an IPv6 allocation, RPKI‑valid routes, an abuse contact, a PeeringDB profile, and an exchange‑point presence collectively make a local hoster legible to customers and counterparties. This legibility supports trust, and trust supports pricing power.

DSP also shows that upstream dependency is the hidden regulator of local cloud economics. The company may own racks, servers, and IP resources, but it cannot escape the economics of wholesale connectivity and international reach. Public routing data showing a single upstream via OPT‑NC, combined with regulatory evidence of OPT‑NC’s monopoly role in public telecommunications services, places DSP in a constrained supplier structure. Local exchange‑point participation improves the position; it does not remove the dependency.

The company further demonstrates how customer trust becomes a substitute for hyperscale breadth. DSP cannot offer the global service catalogue of a hyperscaler. It can offer proximity, a local legal framing, a named support team, visible data‑centre locations, disaster recovery in New Caledonia, and local customer references. For some workloads, these attributes are worth more than the marginal cost advantage of distant cloud. For others, they are not. DSP’s survival depends on segmenting the market correctly.

Finally, DSP shows that survival below hyperscale is path‑dependent. The company’s early legal continuity, the older ASN, the newer AS134405 routing identity, the CIPAC affiliation, the data‑centre investments, the 2018 balance‑sheet stress signal, and the later expansion all matter. Small infrastructure businesses survive not by reaching global scale, but by accumulating enough local evidence points that customers hesitate to switch: known address, known engineers, known facility, known routes, known backups, known legal notices, known parent‑company context. Each evidence point is small. Together they create a local infrastructure moat.

The moat is not permanent. It can be eroded by cheaper international capacity, stronger distant‑cloud adoption, regulatory liberalisation, new local facilities, supplier price shocks, electricity instability, cyber incidents, loss of key staff, or customer concentration. But on the public evidence examined here, DSP remains a visible and active local infrastructure operator whose economic significance exceeds the raw count of its addresses.

Evidence register

APNIC organization record ORG-DSP1-AP: identifies Data Services Pacific as an APNIC local Internet registry in New Caledonia, with the Nouméa address and dsp.nc contacts.
APNIC record AS134405: identifies DATASERVICESPACIFIC-AS-AP, Data Services Pacific, country NC, organization ORG-DSP1-AP, and validated abuse/IRT contact information.
APNIC record 203.34.36.0/24: identifies DATASERVICESPACIFIC-NC as a portable assigned IPv4 block and names Glenn Penin as the network contact.
APNIC record 103.123.232.0/24: identifies DATA-SERVICES-PACIFIC-DC1 and describes the block as Data Services Pacific DC1 Nouméa.
APNIC IPv6 allocation record: identifies 2404:e9c0::/32 as an IPv6 allocation for Data Services Pacific.
BGP.tools AS134405: provides the set of routed prefixes, RPKI‑valid status, registration date, upstream/peer data, and CAN’L IX participation.
BGP.tools AS24053: shows the historical ASN for Data Services Pacific, registered in 2005 and currently not present in the global routing table.
APNIC record AS24053: confirms AS24053 as DATASERVICESPACIFIC-AS-AP with the Data Services Pacific organization reference.
IPinfo AS134405: provides address count, RPKI status, hosted‑domain count, upstream/peer summary, traceroute observations, and stub‑AS characterisation.
WhatIsMyIP record AS134405: corroborates the six IP ranges of Data Services Pacific in New Caledonia.
PeeringDB network profile Data Services Pacific: identifies ASN 134405, website, open peering policy, traffic band, heavy outbound ratio, and CAN’L IX entries.
PeeringDB organization profile Data Services Pacific: identifies DSP, the address at 210 Rue Roger Gervolino, and the associated facility/network.
PeeringDB facility profile DSP DC1: records DSP DC1 in Nouméa, support and sales contacts, CAN’L IX presence, and on‑site networks.
PeeringDB CAN’L IX profile: records the Nouméa exchange point, five peers, seven connections, capacity, local facility, and DSP’s two 10G connections.
Data Center Map Nouméa listing: lists DSP‑DC1 and DSP‑DC2 with addresses and rack counts.
DSP official website: describes DSP as Nouméa‑based, 100% private, a hosting/cloud player with two data centres, and lists services, arguments for local hosting, team, and contact details.
DSP legal notice: identifies CIPAC SA as the site administrator, gives CIPAC company details, and states that the site is hosted by D.S.P. in a New Caledonian data centre.
DSP PDF brochure: describes DSP as a Groupe CIPAC subsidiary, presents services, two data centres, third backup site, SLA commitments, customer‑count claim, support model, and service lines.
Screenshot of DSP brochure infrastructure diagram: shows production, disaster‑recovery, and off‑site backup topology with OPT, CAN’L, Lagoon, and IXP connectivity references.
Screenshot of DSP brochure technology partners: shows APC, VMware, Microsoft SPLA, Veeam, Dell EMC, Synology, Cisco, and related vendor ecosystem.
CIPAC article, June 2026: describes DSP as a CIPAC subsidiary providing IaaS that is locally hosted, backed up, monitored, and operated for local businesses, public services, and organisations.
CIPAC article, March 2025: describes the expansion of DSP’s second data centre and frames it around resilience, cybersecurity, and local economic continuity.
CIPAC article on GPUaaS: indicates that DSP acquired two dedicated AI servers, planned a monthly‑rental GPUaaS, and lists IaaS, BaaS, DRaaS, and private cloud service lines.
DSP LinkedIn company profile: provides a market‑channel description, company‑size signal, founding date, specialities, locations, and employee names.
New Caledonia trade registry notice, 2011: records DATA SERVICES PACIFIC SARL, RCS Nouméa B 759 779, capital, address, and directors.
New Caledonia trade registry notice, 2014: records DATA SERVICES PACIFIC, the same RCS identity, and a change of management.
New Caledonia trade registry notice, 2018: records the non‑dissolution after equity fell below half the share capital.
CCI 2024 electoral list: records DATA SERVICES PACIFIC as a current legal person in the services category.
Nespresso New Caledonia legal notice: identifies DSP as the website host.
MDF legal notice: identifies Data Services Pacific as the host.
ISEE legal notice: identifies Data Services Pacific as the host of the official statistical institute’s website.
New Caledonian Competition Authority English summary: describes OPT-NC’s monopoly on public telecommunications services, the open Internet access market, and competition regulatory concerns.
Market summary on New Caledonia telecommunications: describes OPT-NC’s dominant role in telecommunications and wholesale services to ISPs.
OPT-NC submarine‑cable article: describes Gondwana-1 and the second cable project for capacity and resilience.
SubmarineNetworks Gondwana-1 profile: identifies Gondwana-1 as a 2,151 km system linking New Caledonia and Australia, owned and operated by the public OPT.
APNIC blog on New Caledonia: provides the history of local ISPs, including CAN’L, Groupe CIPAC involvement, MLS, Telenet, and Nautile.
DB-IP allocation table for New Caledonia: provides the relative scale of IPv4 allocations among OPT, OFFRATEL, CAN’L, Micro Logic, Nautile, TeleNet, and DSP.
HE.net New Caledonia network list: provides comparative ASN adjacency and route counts for New Caledonian networks, including DSP and local competitors.

Watchpoints

A second upstream provider or non‑OPT transit path. If AS134405 gains another upstream beyond AS18200, DSP’s supplier dependency and resilience profile would improve markedly. If it remains single‑homed, local exchange‑point participation remains useful but not sufficient to change the international‑connectivity bargaining structure.
Changes in OPT-NC wholesale pricing, cable capacity, or regulatory obligations. Cheaper international bandwidth could reduce the local‑hosting premium by making distant cloud more attractive. Greater wholesale competition could also improve DSP’s margins and redundancy options. The direction depends on whether cheaper connectivity benefits DSP more as a buyer or hyperscalers more as substitutes.
Public verification of ISO 27001, HDS, or equivalent certifications. A verified certification would materially change DSP’s addressable market for public‑sector, healthcare, and regulated workloads. Marketing keywords alone do not have the same economic effect.
Transparency of DC2 and the third site. Independent facility records, certifications, customer references, or peering entries for DC2 would strengthen the disaster‑recovery thesis. Evidence that the third site is a limited backup location would reduce the resilience premium.
RPKI or APNIC contact drift. Invalid ROAs, expired abuse contacts, or inconsistent registry data would damage the trust value created by DSP’s public resource identity. Continuing validation supports counterparty confidence.
GPUaaS utilisation. Sustained customers for local GPU compute would signal a new sovereign‑compute niche. Low utilisation would turn the servers into rapidly depreciating investments and reveal the limits of local AI demand.
Customer concentration disclosures or major public‑sector wins. A large anchor customer would improve utilisation but raise renewal risk. A diverse set of mid‑tier backup, DRaaS, and IaaS customers would build more resilient recurring revenue.
CIPAC ownership or funding changes. Formal confirmation of shareholder support, recapitalisation, or integration into a broader CIPAC digital platform would reduce standalone survival risk. A separation from group support would expose DSP’s fixed‑cost structure more.
New local data‑centre entry. A rival facility with carrier‑neutral positioning, public‑sector certification, or stronger upstream diversity would pressure DSP’s scarcity premium. If no rival emerges, DSP’s dual‑site claim remains commercially powerful.
Hyperscaler edge, CDN, or private connectivity expansion closer to New Caledonia. Better regional cloud accessibility could erode DSP’s generic compute demand. It could also increase demand for local hybrid hosting if DSP becomes the local continuity and interconnection partner.
Public incident record. A major outage, cyber incident, or abuse event would be more damaging for DSP than for a hyperscaler because the trust premium is central to its economics and its address pool is small.
Post‑crisis local enterprise IT spending. DSP’s business improves if New Caledonian organisations prioritise continuity, backup, and outsourced infrastructure. It weakens if fiscal pressure pushes buyers toward deferred upgrades, low‑cost distant SaaS, or minimally maintained on‑premises systems.