Summary
- Blue Cloud Networks Limited has a coherent public identity in Ghana: AFRINIC records connect the legal name and AS37647 to Accra contacts using the Ozone domain, while Ozone identifies itself as Blue Cloud's connectivity division at the same street address.
- The operating surface is broader than basic broadband. Public pages advertise business internet, WAN installation, hosting, VPN and security services, plus data-centre capability, but provide little facility, resilience or data-location detail.
- AS37647 is visibly routing three IPv4 announcements through one observed upstream, with no IPv6 announcement, no PeeringDB network entry and no validating route-origin authorisation for the two routes checked. Buyers should treat uptime and support as contract questions, especially because the website publishes 99.5%, 99.9% and 100% promises in different places.
The identity chain leads from Blue Cloud to Ozone
The first task with a generic provider name is to determine whether its public traces belong to the same operator. In this case, the chain is unusually concrete. The BTW directory profile places Blue Cloud Networks Limited in Ghana, describes it as a private company and lists managed network, cloud, data-centre, colocation and hosting services. It also marks those service descriptions as not yet assessed, an important limit: the directory establishes the subject and its claimed surface, not performance.
The strongest independent identifier is AFRINIC's RDAP record for AS37647. The active record names Blue Cloud Networks Limited, gives 20 1st Ringway in Accra, and lists Ghanaian telephone numbers and contacts using ozone.com.gh email addresses. It records the autonomous system as registered on 31 October 2013 and last changed on 4 March 2024. Network registration is not a corporate solvency check, but the legal name, operational contacts and number resource all point in the same direction.
The customer-facing side completes that link. Requests to ozone.com.gh redirect to Ozone Broadband's current site. Its about page calls Ozone the connectivity division of "BlueCloud Network Limited", says the business was established in 2012 and presents the Ozone brand as the public face of the parent company's connectivity work. The page uses "Network" in the singular, whereas AFRINIC uses "Networks". That naming variation deserves confirmation in a contract rather than silent correction. The contact page is more decisive: it repeats the Ringway Estates address and an ozone.com.gh mailbox found in AFRINIC's record.
Together, these records support a measured conclusion. Blue Cloud has a longstanding Ghanaian network identity and a current commercial brand tied to it by address, domain and contact data. They do not establish who owns every advertised facility, which entity signs each service agreement or whether every statement on the Ozone site applies to AS37647.
The catalogue exposes a wide control surface
Ozone's offer reaches beyond a single access line. The internet-service page advertises fibre and wireless connections for homes and businesses, including dedicated business lines and customised enterprise packages. The business page makes the buying sequence more tangible: a prospective customer checks coverage, allows a site survey, signs a contract and proceeds to installation. It advertises download and upload speeds of up to 100 Mbps and unlimited data.
The enterprise boundary broadens from there. A WAN installation page offers fibre-optic, wireless and enterprise network designs for connecting offices. The hosting page names shared hosting, virtual private servers and dedicated servers for websites, applications and databases. A data-centre page promises redundancy, security and scalable infrastructure. Separate pages advertise VPN services for remote access and security services including firewalls, intrusion detection, endpoint protection and encryption.
Those pages are useful because they reveal what Blue Cloud may be asked to control. An access customer depends on last-mile installation and upstream reachability. A WAN customer also depends on branch design and fault isolation. A hosting customer hands over server availability, while a data-centre customer may depend on power, cooling, physical access and recovery procedures. VPN and security customers add identity, key management, monitoring and incident response. The word "cloud" therefore understates the number of operational boundaries involved.
The public proof is less developed than the menu. The pages describe capabilities but do not publish a facility name, network diagram, service-specific support matrix, audit report or measured availability history. The directory lists colocation, yet Ozone's current service navigation does not expose a dedicated colocation page. None of that disproves the services. It means a buyer cannot move from catalogue to assurance without requesting service schedules, architecture and evidence from completed tests.
AS37647 supplies measurable network evidence
Routing data is the clearest evidence that Blue Cloud operates infrastructure rather than only reselling a cloud label. RIPEstat's AS overview showed AS37647 announced on 15 July 2026. Its announced-prefix view showed 196.11.90.0/24, 196.50.24.0/22 and the more-specific 196.50.25.0/24. Because the last route sits inside the /22, the routing-status result counted 1,280 unique announced IPv4 addresses rather than adding the nested block twice.
The same observation showed all 326 available IPv4 RIPE RIS peers seeing the ASN, but no announced IPv6 space. Full collector visibility indicates that the visible IPv4 routes were broadly propagated at that moment; it is not an uptime statistic. The neighbour view recorded one adjacent network, AS37613. A single observed upstream does not rule out private links or arrangements hidden from collectors, but it supplies no public evidence of transit diversity. Customers whose business case depends on failover should ask for current path diagrams and the result of an actual upstream-loss exercise.
Route-origin protection is another open point. RIPEstat returned an unknown RPKI state for both 196.11.90.0/24 and 196.50.24.0/22, with no validating route-origin authorisation in either response. Unknown is not invalid, and these checks do not establish the state of every possible more-specific route. They do show that the two covering announcements checked lacked visible cryptographic origin validation at the observation time.
Public interconnection disclosure is thinner still. The PeeringDB query for AS37647 returned no network entity. That does not prove Blue Cloud has no exchange, facility or private interconnection. It means PeeringDB cannot currently be used to verify any of them.
Ghanaian presence is not a data-location guarantee
The local footprint has practical value. Blue Cloud's AFRINIC contacts and Ozone's head office are in Accra; the commercial site is written for Ghanaian home and business customers; and the application process includes a coverage check and site survey. These signals make local installation and local escalation plausible in a way that a remote-only reseller could not easily match.
They do not identify where hosted workloads, backups, VPN logs or security telemetry reside. The data-centre page describes high-performance infrastructure, redundancy and advanced security, but does not name a facility or publish primary and recovery locations. The hosting page does not state where shared, VPS or dedicated systems are housed. A Ghanaian office address proves an accountable local point of contact, not Ghanaian storage for every byte.
That distinction matters for customers with contractual, regulatory or client-imposed locality requirements. The useful evidence would be service-specific: the address and operator of each facility; the location of replicas and backups; the identity of subcontractors; administrator access locations; encryption and key custody; retention after cancellation; and the recovery site used after a major outage. Locality should appear in the signed service description, not be inferred from the provider's market.
Three uptime promises reveal the support problem
Ozone publishes visible published contact points. The current site gives a head-office address, two telephone numbers, an email address, a contact form, help-centre and ticket-support links. The homepage advertises dedicated 24/7 customer care, while the about page goes further and says support runs 24 hours a day, every day of the year. Those are positive accountability signals, especially for customers who need installation and field work in Ghana.
The promises become less clear when availability is compared across pages. The about page says Ozone guarantees 99.5% uptime. The hosting page advertises 99.9%. The business-internet page says customers receive "100% guaranteed uptime" for uninterrupted browsing. These percentages may refer to different products or measurement methods, but the public copy does not explain the scope. A literal 100% commitment also leaves no outage allowance at all.
An enterprise buyer should therefore ask which document governs, how availability is measured, what is excluded, whether planned maintenance counts, and what remedy follows a miss. Support needs the same precision: staffed hours, severity definitions, acknowledgement and restoration targets, field-dispatch coverage, named escalation owners and the boundary between Blue Cloud's equipment and customer-managed systems. Public phone numbers show reachability; they do not show how enough skilled people are organised around an incident.
A credible operator that still needs service-level proof
Blue Cloud Networks Limited clears the first credibility threshold. The Ozone brand links back to the same Accra address and email domain attached to an active AFRINIC resource, and AS37647 has a visible IPv4 routing footprint. Its public catalogue also names enough services to expose the operational questions a customer should ask.
The remaining gaps are material rather than cosmetic. Current public evidence does not demonstrate IPv6 service, route-origin authorisation for the two checked announcements, observed upstream diversity, a named data-centre location, independent security assurance or a single coherent availability commitment. The website's service breadth raises the need for evidence because each additional managed layer creates another recovery and accountability boundary.
For a prospective customer, the sensible next step is a scoped trial backed by documents: verify the contracting entity, map the path and facility, record data locations, test failover and restoration, and attach one measurable support schedule to the order. Blue Cloud's name and ASN justify that diligence. The result of the diligence, not the name itself, determines whether the service can carry a critical workload.