Summary

  • Registro.br RDAP records identify AS267355 as a Brazilian direct allocation registered on April 4, 2018 to HOSTIDC INTERNET DATACENTER LTDA, CNPJ 12.366.432/0001-08, with related IPv4 block 45.234.92.0/22 and IPv6 block 2804:4c30::/32 visible in NIC.br's public ASN block list.
  • The public service surface is split. The main HostIDC site is a minimal brand page with an abuse contact, while MKCloud presents cloud products for internet providers, names HOSTIDC INTERNET DATACENTER LTDA in its footer and terms, and sells MK-Auth Cloud and IXC Provedor Cloud plans.
  • Routing evidence is unusually checkable. bgp.tools and Hurricane Electric show four originated IPv4 /24s, two originated IPv6 prefixes, AS52925 Ascenty and AS272786 X99 Internet as visible upstreams, and public exchange presence at IX.br Sao Paulo and Fortaleza.
  • The main buyer risk is not whether HostIDC exists. It is whether the customer verifies contract scope, backup responsibility, support escalation, product dependency on third-party software, and the exact location and recovery model behind "cloud" and "datacenter" language.

A real network record, not a full assurance case

HostIDC is the kind of provider name that can look more settled than the evidence initially warrants. "Internet Datacenter" suggests a physical and operational role. The company is also visible in network registries, which gives buyers something better than a marketing page to inspect. But registry visibility is only the first control point. It confirms who is named on internet-number resources; it does not prove how customer systems are operated, how data is backed up, who answers during an outage, or which contractual promises apply to a particular plan.

The strongest primary record is the Brazilian internet-number registration. Registro.br's RDAP record for AS267355 identifies the autonomous system as a direct allocation in Brazil, registered and last changed on April 4, 2018. The registrant is HOSTIDC INTERNET DATACENTER LTDA, with CNPJ 12.366.432/0001-08. The administrative and abuse contact is "Host IDC" at [email protected]. The matching RDAP IP record for 45.234.92.0/22 places the IPv4 range from 45.234.92.0 through 45.234.95.255 under the same registrant, with the same Host IDC contact used for technical and abuse roles.

NIC.br's public ASN block list gives a compact cross-check: AS267355 maps to HOSTIDC INTERNET DATACENTER LTDA, CNPJ 12.366.432/0001-08, 45.234.92.0/22, and 2804:4c30::/32. That turns HostIDC from a generic hosting lead into a network-resource holder with both IPv4 and IPv6 allocations. It also sets the boundary of what the evidence proves. A procurement team can reasonably say HostIDC is named on the network resources. It should not say, from registry data alone, that every customer workload is hosted in a specific facility, protected by a particular backup policy, or covered by a particular recovery commitment.

The corporate trail points to Fortaleza and hosting services

The CNPJ evidence aligns with the network record. A public BrasilAPI mirror for CNPJ 12.366.432/0001-08 returns HOSTIDC INTERNET DATACENTER LTDA as the legal name, HOSTIDC INTERNET DATACENTER as the trade name, active registration status, an activity start date of August 12, 2010, and a business activity description for data processing, application service providers, and internet hosting services. The address shown is Sargento Herminio Sampaio 3100, Sala 201, Presidente Kennedy, Fortaleza, Ceara, CEP 60355512.

That address also appears in PeeringDB's organization page for HOSTIDC INTERNET DATACENTER, which lists the website as https://www.hostidc.com.br, location Fortaleza, Ceara, country code BR, and network AS267355. PeeringDB's separate network page for AS267355 identifies the network as HOSTIDC INTERNET DATACENTER, gives the looking-glass URL https://lg.as267355.net/, and shows public exchange presence at IX.br Sao Paulo with a 20G capacity entry.

These are independent public surfaces, but they do not all carry the same type of authority. Registro.br is the stronger source for number-resource identity. BrasilAPI is useful as a public company-data mirror. PeeringDB is a community-maintained network database that is valuable for peering and contact context. Together they support a clear conclusion: HostIDC is a Brazilian infrastructure company tied to AS267355 and Fortaleza corporate information. They do not eliminate the need to read the customer-facing service pages and terms.

The customer-facing surface is MKCloud more than HostIDC

The main HostIDC website is minimal. It shows a Grupo HostIDC logo and an abuse contact written as abuse at hostidc.com.br, but it does not explain plan scope, datacenter design, uptime, service levels, backup policy, or customer onboarding. A sparse corporate site is not unusual for an infrastructure operator, especially where separate brands handle retail offers, but it leaves buyers with a question: where is the actual service contract and support surface?

The visible service surface is MKCloud. Its footer names HOSTIDC INTERNET DATACENTER LTDA and CNPJ 12.366.432/0001-08, and the site markets cloud services for internet providers. The homepage describes MKCloud as a way for providers to run management systems in a high-performance platform, with products for MK-Auth Cloud, IXC Provedor Cloud, and a future Gesprov Cloud offer. It says products are provisioned automatically after payment, offers a customer area through app.speedcloud.sh, and points prospects to WhatsApp.

That makes the HostIDC assessment more specific. This is not a broad hyperscale cloud profile. The public evidence describes a provider selling cloud-hosted versions of operational systems used by internet service providers. The target customer is not only a generic website owner; it is the small or regional ISP that wants to move billing, authentication, subscriber management, or provider operations software out of local infrastructure and into a managed hosting environment.

That specialization can be useful. It means the service speaks to concrete ISP workflows rather than abstract compute. It also means customers should not confuse infrastructure hosting with software support. MKCloud's product pages repeatedly state that MKCloud provides the cloud infrastructure for the systems and that support or demands related to the systems themselves should be handled directly with the software developers.

In practice, that splits responsibility: HostIDC/MKCloud may keep the virtual environment available, while the application vendor or customer remains responsible for application behavior, configuration, licensing, and some operational incidents.

The product promise is automation, not hands-off operations

The MK-Auth Cloud Brasil product page sells five plans from Nano to Large, starting at R$60 per month. It describes a certified datacenter in Brazil, ECC DDR4 RAM allocations from 1 GB to 6 GB, activation in 60 seconds, VPN via PPTPD, and a first Mikrotik integration included. The page says the product will be delivered after invoice payment is detected, with access data sent by email, including PPTP connection data for Radius integration between the server and the customer's concentrator. If a customer struggles with integration, the team can schedule the first integration at no additional charge.

The IXC Provedor Cloud Brasil page is aimed at larger provider-management workloads. Its Nano plan starts at R$250 per month and lists up to 1,000 subscribers, 8 GB RAM, 4 vCPUs, two 120 GB SSD volumes, unlimited traffic, IPv4 plus IPv6, and instant activation. Higher plans advertise more subscribers, RAM, CPU, and SSD capacity. The page frames IXC Cloud Brasil as a cloud solution for sales, support, implementation, cancellation, standardized service processes, mobile access, and geolocation of customers through Google Earth integration.

The marketing language is energetic, but the operational model is not mysterious. MKCloud is selling automated provisioning of pre-sized environments for known ISP management tools. That can replace local server maintenance, reduce the need for physical hardware, and make remote access easier. It also creates new supervision work: customers must track whether the plan size matches subscriber count, whether the license is included, how Radius/VPN integration is secured, who monitors availability, and who owns application incidents when the software and the infrastructure are not the same support domain.

The right buyer question is therefore not "is this cloud?" but "which tasks have actually moved from the customer to the provider?" The public pages support a claim that infrastructure provisioning, hosting location, and a customer panel are part of the service. They do not support assuming that application-level support, business-process configuration, or customer-data recovery is fully outsourced.

Routing evidence is compact, dual-stack, and inspectable

The network layer gives HostIDC a stronger public footprint than many small cloud-service names. bgp.tools for AS267355 lists the network as active and allocated under NIC.BR, registered on April 4, 2018, with network type "Content." It shows four originated IPv4 prefixes, two originated IPv6 prefixes, four /24s of IPv4 addresses, and 32,768 /48s of IPv6. The listed IPv4 prefixes are 45.234.92.0/24, 45.234.93.0/24, 45.234.94.0/24, and 45.234.95.0/24. The IPv6 side includes 2804:4c30:8000::/33 and 2804:4c30:c000::/34.

The upstream picture is also visible. bgp.tools shows AS52925 Ascenty Data Centers e Telecomunicacoes S/A and AS272786 X99 Internet as upstreams, with both IPv4 and IPv6 marked for each in the live table captured during this pass. Hurricane Electric's BGP Toolkit page for AS267355 independently shows six total announced prefixes, four IPv4 and two IPv6, 1,024 originated IPv4 addresses, and observed peers including X99 Internet, Ascenty, Hurricane Electric, and EdgeUno among the more visible paths.

Two public exchange points matter for the locality story. bgp.tools reports IX.br Sao Paulo and IX.br Fortaleza entries for AS267355, with Sao Paulo showing IPv4 187.16.210.71, IPv6 2001:12f8::210:71, and 20 gbps link speed, and Fortaleza showing IPv4 45.68.72.183 and IPv6 2001:12f8:0:9::183. The IX.br Fortaleza peer list visible through bgp.tools also includes AS267355 at those Fortaleza addresses. This does not prove every customer server is in Fortaleza or Sao Paulo, but it does show a Brazilian exchange footprint that customers can test through traceroute, latency checks, route monitoring, and maintenance notices.

For a serious workload, this routing profile raises precise questions. Are MKCloud customer environments hosted behind the AS267355 prefixes, or do some products sit on third-party infrastructure? Which products use Ascenty FTZ1, Equinix SP4, or both? Is route failover tested across Ascenty and X99 paths? Are IPv6 commitments offered on every plan or only certain products? Does the looking glass at lg.as267355.net provide usable diagnostics during incidents? The public record is good enough to ask those questions without guessing.

Locality is a signal, not a complete sovereignty proof

HostIDC's public materials make Brazil central to the service. The company record points to Fortaleza. PeeringDB locates the organization in Fortaleza. MKCloud's homepage says its servers are located in Fortaleza and Sao Paulo and states that it operates its own infrastructure in Tier III datacenters, naming Ascenty FTZ1 and Equinix SP4. The product pages describe "Cloud Brasil" products, and the IXC page advertises IPv4 plus IPv6 on the listed plans.

For Brazilian internet providers, that local posture can matter. Provider-management systems are operationally sensitive: they may contain subscriber records, support workflow data, authentication links, geolocation, billing state, and network operations context. Keeping those systems close to a customer's user base and support team can improve latency, language fit, and escalation practicality. It can also help customers avoid the mismatch of running local ISP operations on distant commodity hosting without a clear support path.

But locality should be handled with discipline. A page that says infrastructure is in Brazil does not, by itself, document where backups are stored, where support tools run, which subcontractors can access systems, which datacenter houses a given customer, or whether a failover environment crosses regions. The public evidence supports Brazilian corporate, network, and service-location signals. It does not replace a data-location statement, backup-location statement, access-control description, or incident notification process for customers with regulatory or contractual obligations.

The clean conclusion is narrower and stronger: HostIDC/MKCloud has public Brazilian locality evidence that is relevant to procurement. Buyers should convert that evidence into contract language and operational tests instead of treating it as a slogan.

Backup and cancellation terms are the sharpest risk

The most consequential public text is in MKCloud's terms of service. The terms identify the contracted party as HOSTIDC INTERNET DATACENTER, located in Fortaleza at Av. Sargento Herminio 3100, CNPJ 12.366.432/0001-08, and refer to customer accounts across central.mkcloud.com.br, mkcloud.com.br, and core.hostidc.com.br. They say services are activated only after the first payment is confirmed and that service suspension follows payment delay.

For continuity, the harsher clauses are about cancellation, nonpayment, and backups. The terms say cancellation can trigger immediate account deletion for the cancelled plan and describe that operation as irreversible, advising customers to perform backups before requesting cancellation. They also state that services are suspended after more than three days of nonpayment and fully finalized after more than seven days, with data permanently deleted and not recoverable after finalization.

The backup section is even clearer. MKCloud says it is not responsible for files or other data stored in the account, that the plan does not guarantee recovery of lost information, that the customer must keep backup copies outside the server, and that the provider does not perform backups of the offered services. For a low-risk test system, that may be acceptable. For an ISP's subscriber-management or authentication environment, it is a major operating constraint.

This does not make the service unusable. It means the customer must bring a recovery design. Before moving MK-Auth or IXC operations into MKCloud, a provider should test exports, snapshots, database recovery, DNS and Radius restoration, credential rotation, and a clean rebuild outside the account. The most important service metric may not be monthly price or activation speed. It may be whether the customer can restore the provider-management system without waiting for an unavailable backup that the terms never promised.

Support is visible, but responsibility is split

MKCloud's public pages provide several support entry points. The homepage and navigation point to WhatsApp, a customer area, and product pages that mention WhatsApp, chat, and ticket support. The MK-Auth page says support is available for service-related difficulties through those channels and describes a first Mikrotik integration. The IXC page says the team is available through WhatsApp, chat, and ticket, while also saying MKCloud's service is limited to keeping the system available and that support related to the system should be handled with the software developers.

That distinction is exactly where buyers should focus. A local support channel is valuable only if it maps to authority during an incident. If a provider's billing platform is unreachable, the incident could involve virtual machine health, storage, network routing, DNS, software licensing, database state, or an application bug. HostIDC/MKCloud may control some of those layers and not others. The public pages suggest the infrastructure layer is theirs, while application behavior can sit with MK-Auth, IXC, or the customer.

The practical support checklist should separate channels from responsibilities. Who can restart or rebuild the server? Who can diagnose Radius connectivity? Who controls firewall and VPN settings? Who is responsible for operating-system updates? Who restores data after customer error? Who escalates network issues on AS267355? Who handles abuse mail sent to [email protected] or abuse at hostidc.com.br? The public evidence identifies doors into the support system. It does not prove the authority behind every door.

What HostIDC can credibly claim, and what buyers still need

HostIDC can credibly be treated as a real Brazilian network and cloud-service operator with a focused ISP-management hosting offer. The public record supports the legal identity, CNPJ, Fortaleza address, AS267355, IPv4 and IPv6 resources, IX.br presence, visible upstreams, MKCloud product pages, customer account surfaces, and terms naming HostIDC as the contracted party. That is more than enough to move the conversation from "who is this?" to "what exactly is being bought?"

The second question is harder. The evidence does not support assuming hyperscale resilience, broad managed-service coverage, included backups, or single-party responsibility for the application stack. MKCloud's own pages make the business model more precise: automated cloud infrastructure for ISP management systems, with support channels and fast provisioning, but with application support split toward software developers and backup responsibility pushed strongly toward the customer.

For some regional providers, that may be the right bargain. Running MK-Auth or IXC locally can mean hardware care, power risk, manual upgrades, limited remote access, and fragile backups. A cloud-hosted environment with Brazilian infrastructure, local support channels, and visible network resources may improve day-to-day operations. But the improvement is not automatic. It has to be measured by tested recovery, documented support boundaries, and route and locality evidence that matches the actual plan.

The governance rule is simple: treat the HostIDC name as an invitation to verify, not as assurance by itself. Confirm the contracting entity and CNPJ. Confirm the plan's datacenter and route path. Confirm whether AS267355 carries the customer environment. Confirm IPv6 availability and monitoring. Confirm what "system availability" covers and what it excludes. Confirm how cancellation, late payment, and data deletion work. Confirm backup ownership and perform a restore before production dependence.

HostIDC's public footprint is useful because it is specific. It gives buyers enough to ask exact questions about network resources, locality, support, and customer responsibility. The risk is stopping at the datacenter label. In this case, the real operating story is not the name on the page. It is the alignment between a Fortaleza company, AS267355, MKCloud's provider-management products, the terms that govern data recovery, and the people who can act when the customer's own customers are waiting.