• Kaldera’s public catalogue places business internet, managed infrastructure, data-centre housing, cloud backup and archive, and business telephony in one provider relationship for professional clients in Mauritius.
  • PeeringDB identifies AS37722 as Kaldera’s network and lists public peering at JINX, LINX LON1 and MIXP, plus interconnection facilities in Mauritius, Kenya, France and South Africa.
  • RIPEstat observed six IPv4 and two IPv6 prefixes announced for AS37722 from 6 to 20 October 2026; PeeringDB separately shows self-reported totals of 100 IPv4 and 10 IPv6 prefixes.

Kaldera Ltd: What a bundled ISP puts on the line

A professional customer in Mauritius can buy internet access, data-centre space, cloud backup and telephony from separate suppliers, or from one. Kaldera’s public site shows the second route. It describes itself as an ISP based in Mauritius serving professionals, and it lists connectivity, managed infrastructure, data-centre services, cloud and 3CX PBX telephony under one catalogue.

That is convenient until continuity is tested. When internet access, hosted systems, backup and voice run through the same provider and the same operating relationship, a problem at one layer can reach the others. The stakes appear in ordinary operations: a customer trying to call, an employee opening a hosted file, a recovery team restoring a backup. A routing or configuration change may be visible in more than one place at once. The public record does not show that any of this has happened. It shows why buyers should ask how it would be handled.

What the operator lists, and what that means for a buyer

Kaldera says it has more than 12 years of experience and gives an office address at 8th Floor, Nexsky Building, Hotel Avenue, Cybercity, Ebène. Its site lists business internet, IP transit, global IP, managed WAN and SD-WAN, monitoring, business broadband, dual-stack IPv4/IPv6, and a global virtual link. The managed-infrastructure pages add managed LAN and Wi-Fi, security monitoring, data-centre housing and co-location, dedicated and managed servers, cloud storage, backup and archive, and public cloud. The telephony pages list 3CX PBX, on-premises phone systems, hosted PBX and Fanvil IP phones.

These are catalogue entries, not independent service-level measurements. That distinction is not a technicality. For a business, the useful question is which parts Kaldera operates directly, which depend on third parties, and what happens to the rest of the bundle when one service fails. The public pages describe the offer. They do not publish audited availability figures or customer-specific continuity terms.

AS37722: the network behind the name

PeeringDB identifies AS37722 as Kaldera’s autonomous system and describes the network as Cable/DSL/ISP. An autonomous system is the identifier a network uses in global routing. A prefix is a block of IP addresses announced from that network. Peering is a direct interconnection between networks. These definitions matter because they let an outside reader compare the company’s network claims with public records.

PeeringDB lists public peering at JINX, LINX LON1 and MIXP, and interconnection facilities in Mauritius, Kenya, France and South Africa. It also carries self-reported counts of 100 IPv4 prefixes and 10 IPv6 prefixes. Those figures are maintained by the operator. They are not an independent benchmark, and they can lag behind what the network actually announces.

What routing data shows, and why the gap matters

RIPEstat’s announced-prefix query for 6–20 October 2026 returned six IPv4 prefixes and two IPv6 prefixes associated with AS37722. The result records visibility across that two-week window and excludes routes with very low visibility. It is a dated observation, not a permanent inventory.

The difference between those observed prefixes and PeeringDB’s self-reported 100 and 10 is a useful signal, not an alarm. Registry profiles and routing observations answer different questions. One records what an operator says about its network; the other records what route collectors saw. For a buyer, the practical implication is that neither view is a complete guarantee of service continuity. The better approach is to compare both and ask which evidence supports the service being bought.

Why bundling changes the operational question

Bundling can reduce the number of contracts and handoffs. Kaldera’s catalogue suggests a client could place internet access, managed infrastructure, hosting, cloud backup and telephony in the same operating relationship. That is the source-supported mechanism behind the dependency question.

The same bundle can raise switching costs. If access, hosting and telephony are coordinated by one provider, changing supplier may involve more than moving a line. It may require migrating servers, rechecking domain and routing records, and retesting phone systems. The public record does not show how Kaldera contracts those services or what exit terms it offers. The point is not to assume the worst; it is to make the dependency visible before it becomes urgent.

What remains unproven

The available public material does not establish a Kaldera-specific licence entry at the ICTA, a 3CX partner tier, Fanvil exclusivity, a founding year, staff numbers, event sponsorship, peer counts, named upstream carriers or fixed prefix totals. Those claims should not be repeated without direct evidence. Mauritius’s ICT Authority is the national ICT regulator, but its public homepage does not provide a company-specific licence listing in the material available here. AFRINIC’s WHOIS service is a registry lookup for African internet resources, not a company record by itself.

The defensible profile is narrower: a Mauritius-based ISP describing a broad professional catalogue, a named autonomous system with public interconnection, and a dated routing view that differs from self-reported registry counts. For a professional buyer, that is enough to ask better questions about continuity, exit paths and evidence. It is not enough to assume that one provider creates one service level.