Summary

  • GK2 CLOUD LTDA has a visible Brazilian identity: BTW's directory page places it in Brazil with five service labels, Casa dos Dados reports an active CNPJ in Maringa, Parana, and Registro.br lists AS271435 under GK2 CLOUD LTDA.
  • The company's own site presents GK2.CLOUD as a hosting, VPS, dedicated server, email, DNS, SSL, backup and support provider, with 24/7/365 support language, a client area, ticketing, a knowledge base and a public uptime link.
  • Network evidence is real but bounded: AS271435 originates 170.247.60.0/22 and 2804:7b7c::/32, with public routing views showing Ascenty Data Centers e Telecomunicacoes S/A as the observed upstream or peer.
  • The evidence does not prove audited facility certification, measured uptime, latency, restoration performance, staffing depth, security controls, support response speed or the exact contract boundary for customer workloads.

GK2 CLOUD LTDA is not a name that should be accepted or dismissed from the word "cloud" alone. It is a Brazilian company with a public hosting brand, public service pages, public support entry points and public internet-number records. That combination is enough to make the company visible to infrastructure, procurement and governance readers. It is not enough to make the operating risk disappear.

The public record starts with identity. BTW's directory page identifies GK2 CLOUD LTDA as an organisation in Brazil, gives it a private-company legal type, and lists five service categories: managed network, cloud service, data center, colocation and hosting. The directory's visible summary says GK2 CLOUD LTDA appears in the LACNIC member directory for Brazil and marks the profile as fresh to July 5, 2026.

That directory view is not a replacement for a contract file, but it sets a useful boundary: the subject is not merely a domain string; it is a named Brazilian infrastructure provider with a service surface that touches hosting and network operations.

Company-register mirrors add a second identity layer. Casa dos Dados reports GK2 CLOUD LTDA under CNPJ 14.322.136/0001-22, with the trade name GK2.CLOUD, active registration status, opening date of August 25, 2011, and address on Avenida XV de Novembro, Sala 302, in Maringa, Parana. It also reports a limited-liability company form, capital of R$115,000, Anderson Thiago Ouverney as managing partner, and a set of business activities that include computer equipment retail, custom software development, customizable software licensing, technical support and internet information services.

Those details matter because cloud assurance often begins with the simplest question: who is the accountable local party?

The legal and commercial names line up closely enough to support a serious diligence path. The company site uses GK2.CLOUD as the public brand. The CNPJ mirror reports GK2.CLOUD as the trade name. Registro.br's WHOIS output for AS271435 names GK2 CLOUD LTDA as the owner and Anderson Ouverney as the responsible contact. Host.io associates gk2.cloud with AS271435, shows an A record at 170.247.60.2, an IPv6 record at 2804:7b7c::3, MX at mail.gk2.cloud, and name servers under the br53 family. The result is a coherent public chain from legal name to brand to domain to autonomous-system record.

A buyer would still need signed documents, invoices, support terms and data-processing language, but the public identity is not floating in isolation.

The service surface is broader than a simple shared-hosting storefront. GK2's home page presents hosting, VPS, dedicated servers and SSL certificates as core offers, with additional navigation for domain registration, cPanel and DirectAdmin licences, remote backup, WordPress maintenance, enterprise hosting, DNS hosting, email hosting and hosting for law firms. The same page claims 24/7/365 support and says site availability is a priority, with a public uptime link in the footer. It also points users to support, contact, a knowledge base and login. That is a commercial operating surface, not just a brochure.

The VPS page gives the clearest picture of how GK2 wants buyers to understand its cloud product. It advertises a high-performance VPS with a 99.9 percent uptime claim, SSL, application installation, multiple operating systems and common control panels or applications. The page names Debian, CoreOS, FreeBSD, Fedora, OpenBSD, Ubuntu, Windows, Archlinux, openSUSE and AlmaLinux, and it displays cPanel, CyberPanel, Docker, Plesk, Webmin, Drupal, Magento, PrestaShop, WordPress, Joomla and CWP as examples of supported software or stacks.

It also describes dedicated RAM, CPU and storage, root access, firewall management, DDoS protection, SSL encryption, simple upgrades and migration help.

Those claims are useful because they define the buyer workflow. A VPS customer is not only buying a virtual machine. They are buying provisioning, operating-system choice, account control, access management, backups, upgrade paths, billing, monitoring, software support boundaries and incident escalation. The public page says GK2 will provide flexibility and support. It does not show how the provider isolates tenants, tests backup integrity, handles kernel vulnerabilities, logs administrative access, or proves recovery after a failed upgrade.

That distinction is the heart of the diligence issue: public service pages can describe the product boundary, but they do not prove how the boundary behaves under stress.

Dedicated servers add another accountability layer. GK2's dedicated-server page claims hardware performance, Linux or Windows installation, virtualizer support, cPanel or DirectAdmin management, high-performance networking, many dedicated servers with unlimited transfer, SSL certificates, migration help, DDoS mitigation, 1G and 10G uplinks, firewall configuration, RAID monitoring, advanced graphs and DNS through br53. It also uses a 99.95 percent SLA claim for hardware availability. For a procurement team, those are not merely features.

Each one creates a follow-up question: which terms are contractual, which are best-effort, which are included in the base plan, and which require a managed-service agreement?

The hosting and email pages widen the control surface. Enterprise hosting lists cPanel or DirectAdmin, daily, weekly and monthly backups, free SSL certificates, Cluster DNS, 24/7/365 support and professional webmail across several packages. The email page presents CrossBox Mail with email, chat, video calls and file sharing, and claims high deliverability, monthly backups and premium support across plan tiers. That makes GK2 relevant not only as raw infrastructure but as an operator of communication and business-continuity layers.

Email, DNS and backup services carry different risk from a standalone VPS: mistakes can affect domain reputation, message delivery, incident communications and restore confidence.

The network-resource evidence is the most concrete operating clue. Registro.br's WHOIS for AS271435 lists GK2 CLOUD LTDA as the owner, Anderson Ouverney as responsible contact, creation and change date of October 9, 2020, and two resources: IPv6 prefix 2804:7b7c::/32 and IPv4 prefix 170.247.60.0/22. BGP.tools shows the same autonomous system as active and allocated under NIC.BR, with one IPv4 and one IPv6 prefix originated. IP2Location also associates AS271435 with GK2 Cloud Ltda in Brazil, the domain gk2.net.br, 170.247.60.0/22 and 2804:7b7c::/32, and says there are no downstreams listed for the ASN.

That is strong evidence that GK2 has its own visible routing identity. It is not, by itself, evidence that every customer service runs on those resources, that every server is local, or that every offer is delivered from facilities controlled by GK2. A provider may mix owned address space, partner datacenters, software licences, support labour and third-party dependencies. The public routing record answers one question: GK2 is not only reselling a website under someone else's name; there is an AS271435 resource record tied to the legal entity.

It leaves open the architecture question: which services use which infrastructure, in which facilities, with which upstreams and recovery paths?

The upstream picture is narrow. IP2Location lists AS52925, Ascenty Data Centers e Telecomunicacoes S/A, as the upstream. BGP.tools also shows Ascenty as an upstream and peer for both IPv4 and IPv6. Hurricane Electric's BGP Toolkit reports Brazil as the country of origin, two originated and announced prefixes, 1,024 IPv4 addresses originated, and one observed IPv4 and IPv6 peer, again Ascenty. IPinfo's prefix page for 170.247.60.0/22 places the range in LACNIC context and shows a recent traceroute reaching AS271435 after AS52925.

The picture is coherent: GK2's public network view appears concentrated around one visible upstream relationship.

That concentration is neither automatically bad nor automatically safe. Ascenty is a recognizable Brazilian datacenter and connectivity operator, and a small infrastructure provider may reasonably build around a primary datacenter relationship. But single-upstream visibility is a dependency that should be understood. Buyers should ask whether GK2 has redundant circuits not visible in the public snapshot, whether failover is contracted and tested, whether IPv4 and IPv6 paths fail together, how route changes are approved, and how customers are notified when upstream maintenance affects reachability.

The public routing view gives procurement a map of what to ask, not a guarantee of survivability.

The address-space footprint also needs a sober reading. A /22 gives 1,024 IPv4 addresses, and the IPv6 /32 is a large allocation by design. IPinfo reports many hosted domains across the AS271435 range and lists pingable addresses in recent scans. Host.io shows gk2.cloud co-hosted with related domains such as gk2.net.br, gk2.com.br, gk2.host, hospedagem.maringa.br, clusterdns.io and sender25 domains on 170.247.60.2. Those clues suggest an active hosting environment, DNS and mail-adjacent services rather than an unused resource record.

They also raise operational questions: how are shared IPs managed, how is email reputation separated between customers, how are DNS changes audited, and how does GK2 handle abuse complaints?

Data locality is where GK2's Brazilian footprint may have practical value. The legal identity is Brazilian, the contact address is in Maringa, the website and CNPJ mirror point to Parana, the AS is under NIC.BR/LACNIC context, and the site is written primarily for Portuguese-speaking customers with Brazilian payment and support assumptions. For a small or mid-sized Brazilian company, that can matter. Local billing, local support, local language, familiar legal process and regional hosting can reduce day-to-day friction compared with a distant hyperscale account or an anonymous offshore host.

But data locality is not proven by an address, a country code or a Portuguese support page. A workload may use off-site backup, external email filtering, third-party DNS, partner datacenters, remote support tooling, software vendors or payment processors. The right procurement question is not "is GK2 Brazilian?" The public answer to that appears yes. The better question is: where does the primary data sit, where do backups sit, who can access management consoles, what vendors can touch the environment, what logging proves access, and what happens if a customer needs export, deletion or migration evidence?

Support is central to the offer. GK2's contact page says it has premium 24/7/365 support, offers ticket opening, links to a knowledge base and a client area, and publishes a phone number and social channels. Its footer repeats the Maringa address and links to client area, support, public uptime, monitoring, backup and security pages. The about page presents the company as a partner for secure, fast and reliable storage and data traffic, names Anderson Ouverney as CEO, and shows team roles in development, support, finance and marketing. This is the labour layer behind the infrastructure brand.

For customers, labour is often the difference between a usable local provider and a fragile dependency. A support team that knows the customer's environment can reduce recovery time, migration confusion and billing friction. But support must create records. The public site shows entry points; it does not show ticket retention, escalation rules, named on-call roles, incident-report templates, support authority, root-access approval, after-hours staffing depth or customer audit exports. A buyer should treat the support channel as a product that needs testing. Open a non-urgent ticket before production. Ask a technical question.

Ask how emergency changes are approved. Ask for a sample post-incident report. Ask whether restore tests are recorded.

Enterprise software is another place where GK2's offer can be valuable if the operating surface is real. VPS, dedicated servers, email, DNS and backup are not isolated commodities when a customer runs an ERP, online store, law-firm site or regional business system. The provider's automation has to keep accounts, domains, certificates, storage, mailboxes, backups, invoices, support cases and monitoring aligned. GK2's site advertises control panels and client-area management. That suggests a standardized hosting stack.

It does not show whether infrastructure changes are repeatable, whether customers can export configuration state, whether backups are application-consistent, or whether support actions are tied to approval records.

The buyer test should therefore be practical. Before treating GK2 as operating assurance, run a workload through the whole path: purchase, provision, configure DNS, set up mail, assign users, install software, test backups, change a firewall rule, request a migration, simulate a restore, open a ticket, review logs and ask for exit steps. If the records stay coherent, the local-provider value becomes concrete. If the records fragment across chat messages, emails, panel screens and unlogged engineer actions, the risk is not the size of the company; the risk is the absence of durable operational evidence.

There is also a difference between uptime claims and uptime proof. GK2's pages use 99.9 percent and 99.95 percent availability language in different contexts, and the site links to a public uptime page. Those are useful signals because they show the company expects buyers to care about availability. They are not enough to prove service history.

A serious buyer should ask which service each SLA covers, how downtime is measured, which maintenance is excluded, whether credits are automatic or requested, whether incidents are published, and whether the customer's own environment has separate dependencies that fall outside the advertised target.

The same caution applies to DDoS, firewall, RAID monitoring, DNS and backup language. These are important controls, but each one can mean very different things in practice. DDoS mitigation may be upstream filtering, an appliance, a scrubbing partner or a best-effort traffic policy. Firewall management may be customer-controlled or provider-controlled. RAID monitoring may alert only hardware staff, or it may feed a customer-visible incident process. Backups may exist but still fail if restore procedures are untested. DNS may be robust but still vulnerable to poor account hygiene. Public feature lists should be converted into evidence requests.

GK2's strongest public posture is therefore not scale. It is traceability. The public evidence links a Brazilian legal identity, a Maringa address, a GK2.CLOUD brand, a support site, a knowledge base, a client area, an AS number, a concrete IPv4 and IPv6 prefix set, and an observable upstream relationship. That is enough to make the company more than a generic "cloud" name. It is also enough to identify the questions that remain unanswered: architecture, resilience, support records, data location, customer isolation, recovery testing and contract accountability.

For BTW readers, the final assessment is deliberately bounded. GK2 CLOUD LTDA appears to be a real Brazilian hosting and cloud operator with public identity, service pages and network-resource evidence. It should not be treated as fully assured until the operating records behind those public signals are reviewed. The next diligence step is not another search result. It is a document and workload test: legal party, service schedule, upstream and facility map, access-control process, backup and restore evidence, incident procedure, export plan and support-response proof.

If those records are strong, GK2's local support and Brazilian network presence may be meaningful operating advantages. If they are weak, the cloud name will have done more work than the evidence.