Summary

  • Ecxon Datacenter LTDA presents a real public operating surface: a Brazilian legal identity, Ecxon-branded VPS and dedicated-server pages, customer-area support routes, terms of service, published contact points, geofeed records and an independently visible AS270764 routing footprint.
  • The evidence also sets clear limits. Ecxon publishes strong claims around DDoS capacity, Brazilian infrastructure, KVM VPS, bare metal, network capacity and support, while its terms place important responsibility on the customer for backups, account state, payment discipline and incident reimbursement requests.

A Datacenter Name Is Only the First Claim

Ecxon Datacenter LTDA sits in the awkward but important middle of the infrastructure market. It is not presented like a global hyperscaler, and it is not merely a domain-name storefront. Its public materials describe Brazilian infrastructure, VPS hosting, dedicated servers, game hosting, DDoS protection, customer accounts, ticket support and a routed network identity. That combination makes it relevant to buyers who want local infrastructure capacity without taking on the full work of owning servers, transit, mitigation, billing systems and support workflow themselves.

The risk is that the word "datacenter" can carry more confidence than the evidence supports. For a buyer, the operational product is not the name on the footer. It is the record that connects the contracted machine, the address block, the network path, the mitigation promise, the login account, the support ticket, the payment status and the backup practice. If that record is clear, Ecxon can be assessed as a practical infrastructure supplier. If it is scattered, the customer is not buying assurance; it is buying a collection of promises that still have to be reconciled during an outage.

Ecxon's public identity is more concrete than many small hosting brands. The site metadata identifies Ecxon Datacenter LTDA and describes "Infraestrutura no Brasil." The footer displays CNPJ 33.162.811/0001-48, and the terms PDF ties that CNPJ to the legal name ECXON DATACENTER LTDA, the Ecxon trading name and a base in Bento Goncalves, Rio Grande do Sul. Public company-record pages cross-check the same CNPJ, active status, March 27, 2019 opening date, corporate form and telecom-related activity classification.

Those records do not prove service quality, but they reduce the identity ambiguity that often surrounds smaller hosting providers.

That identity still needs to be read with care. Ecxon is the supplier surface, not every workload that may run on it and not every reseller or customer that appears in routing or support records. Its value has to be tested through what it makes visible: the product pages, the customer-area routes, the service terms and the network records. Those are enough to form a picture of the operating model. They are not enough to infer private uptime, current customer count, revenue, support speed, audited facility status or actual recovery outcomes.

What Ecxon Says It Sells

Ecxon's visible product framing is concentrated around hosting and infrastructure. The home route offers "hospedagem de alto desempenho" and points users toward VPS and dedicated servers. The navigation and customer-area pages expose VPS Linux in Brazil, VPS Linux in Canada, VPS Windows in Brazil, dedicated servers in Brazil and Canada, site hosting, SA:MP, MTA-SA and Minecraft hosting, and DDoS protection. The newer React site routes narrow the public offer to VPS, dedicated servers, network and anti-DDoS pages, with login and registration links to the customer area.

The VPS page is the clearest self-service infrastructure offer. It describes high-performance VPS hosting powered by NVMe storage, KVM virtualization and customer management control. Its plan list includes four named VPS tiers from R$250 to R$800, with stated CPU cores, DDR4 RAM, NVMe storage, 1 Gbps networking and 20 TB traffic. The page names AMD Ryzen 9 3950X processors and claims boost speeds up to 4.70 GHz. It also presents DDoS protection, a 1 Gbps network and optimized routes as part of the VPS value proposition.

The dedicated-server page moves from virtual capacity to bare metal. It lists DDR4 and DDR5 server options using Ryzen processors, NVMe storage and network allocations that range from 1 Gbps to as much as 20 Gbps depending on the plan class. It describes the servers as hosted in Ecxon's own Brazilian infrastructure and makes a support claim around direct access to senior technical specialists.

Some purchase flow appears to move through WhatsApp rather than a purely automated checkout, which matters: for dedicated servers, the accepted operating record may be partly commercial conversation, partly ticket, partly invoice and partly technical handover.

The network and anti-DDoS pages are more ambitious. Ecxon claims more than 500 Gbps of network capacity, multiple 100GE uplinks, optimized global routes and direct peering with major networks. Its DDoS material claims 348 Tbps of mitigation capacity, Cloudflare Magic Transit integration, game-server-oriented UDP flood mitigation, TCP protection for business applications and a mitigation-time claim under 500 milliseconds. Those claims should be treated as provider claims unless a buyer receives contractual detail or test evidence.

They are still useful because they identify the technical area Ecxon wants to own: not only compute, but reachability under hostile or unstable traffic conditions.

Network Records Turn the Claim Into a Map

The strongest independent evidence for Ecxon is AS270764. PeeringDB lists the organization as Ecxon Datacenter, with the long name Ecxon Datacenter LTDA, the website ecxon.com.br, ASN 270764, network type "Content," a global geographic scope and a heavy-outbound traffic ratio. BGP.Tools identifies AS270764 as Ecxon Datacenter LTDA, registered on May 29, 2020, active under NIC.br, with 8 IPv4 and 5 IPv6 prefixes originated. It lists upstreams including Cloudflare, Cogent, Lumen, Hurricane Electric and Datacamp, and shows IX.br presence in Sao Paulo and Porto Alegre.

IPinfo also lists Ecxon Datacenter LTDA for AS270764, records five upstreams, one downstream and IP ranges associated with the ASN.

This does not make Ecxon a global cloud platform. It does show a visible routed network rather than a purely anonymous hosting brand. Prefixes such as 45.40.99.0/24, 104.234.119.0/24, 181.215.236.0/24, 181.215.253.0/24, 181.215.254.0/24, 189.127.164.0/24 and 189.127.165.0/24 appear in independent ASN records, with BGP.Tools marking the listed prefixes as RPKI-valid at the time of collection. IPinfo also reports recent pingable addresses in Brazil, including Sao Paulo and Osasco observations, while Ecxon's own IPv6 geofeed places multiple 2804:7110 prefixes in Osasco, Sao Paulo state.

For procurement readers, this is not trivia. If a workload is hosted on Ecxon, the routing record determines how users, upstream networks, mitigators and other services reach it. A VPS can be correctly provisioned and still fail the customer if the route is unstable, the prefix is filtered, DDoS mitigation changes the path unexpectedly, or a customer misunderstands which IP range is attached to which service.

Conversely, a well-documented network footprint helps a customer ask better questions: which ASN originates the service address, which upstreams are used, which exchange points matter, how DDoS traffic is steered, whether RPKI is maintained and which support channel owns route incidents.

The network record also complicates a simple "locality" story. Ecxon is a Brazilian legal entity and markets Brazilian infrastructure, yet its product navigation includes Canada options and its DDoS terms discuss both Canada and Brazil. That can be commercially sensible: some customers may want lower-cost or different-protection capacity outside Brazil. But locality cannot be assumed from the brand alone.

A buyer with data-sovereignty, latency, public-sector, gaming-community or compliance requirements should verify where the server is provisioned, which jurisdiction applies, which provider supplies protection and whether the billing and support record clearly distinguishes Brazil-hosted and Canada-hosted services.

Support Is Visible, but the Boundary Matters

Ecxon publishes several support signals. The customer-area pages expose login, registration, contact, ticket and support-ticket routes. The contact page shows sales and support email addresses and a WhatsApp published contact points. The footer and header provide WhatsApp links, contact email, a customer-area login and registration path. The terms say Ecxon offers customer support 24 hours a day, 365 days a year through site tickets and official contact emails, while also stating that it does not define a response deadline and that commercial service hours are Monday to Friday from 12:00 to 20:00.

That distinction is central. A 24/7 support intake channel is not the same as a 24/7 response-time obligation. For a small business site or game server, the difference may be acceptable if expectations are clear. For a production service, the buyer needs a sharper support record: what classifies an emergency, which channel is authoritative, how a DDoS event is escalated, who can approve service changes, when dedicated-server hands-on work happens, and whether a service credit or refund requires the customer to file a request after the incident.

The terms make that last point explicit. Ecxon describes a downtime reimbursement rule based on 5 percent of the next invoice for every 10 minutes of unavailability, limited to 100 percent of the invoice. It then lists exceptions, including packet loss where the network remains minimally available, routing errors affecting a portion of users, routing errors up to the datacenter when Ecxon says the problem is not its own, and user-caused human error. After unavailability is detected, the customer must contact Ecxon requesting the SLA reimbursement.

This is a practical warning, not a disqualifier. Many infrastructure contracts work this way: service credits depend on definitions, exclusions and customer action. But it means the customer cannot treat a marketing uptime assumption as the operational truth. The accepted record should say what "unavailable" means, what monitoring source is accepted, what evidence the customer must preserve, which invoice receives credit and which routing failures fall outside Ecxon's responsibility. Without that record, a service-credit policy can become a post-incident dispute rather than a protection.

Automation Reduces Labour Only When Records Stay Aligned

Ecxon appears to use a conventional hosting automation stack for customer accounts, carts, tickets and service activation. The site links VPS plans to cart URLs, exposes client-area login and registration, and routes support through ticket pages. The terms say all services except dedicated servers are activated and sent automatically immediately after payment confirmation, while dedicated servers have a delivery period of up to 72 business hours, after which the customer may request a full refund if the service has not been delivered.

That automation is a real customer benefit when the workflow is simple. A VPS buyer can choose a plan, pay, receive credentials and start work faster than it could buy hardware or negotiate a custom environment. For teams running game servers, small web applications, test environments, bots, community infrastructure or regional workloads, the reduction in provisioning labour can matter more than a large feature catalogue. The product is not just CPU and memory; it is the conversion of payment into usable server state.

The same automation creates supervision costs. The customer must know which service was ordered, which location was selected, which virtualization mode applies, what bandwidth policy is attached, what login details were sent, what billing date governs suspension, whether the service is shared or dedicated, and which backup obligation remains with the customer. If the account email is wrong, if an invoice lapses, if a server is provisioned in the wrong region, or if a support request lacks the necessary identifier, the automated path may not rescue the customer quickly.

Ecxon's terms are unusually direct about this boundary. They state that VPS customers are acquiring OpenVZ or KVM service, and that resources are controlled by the virtualization software. They say Minecraft and TeamSpeak hosting are shared placements on dedicated servers, with bandwidth restricted to a portion of the underlying server capacity. For backups, the terms say Ecxon is not responsible for loss of any file allocated on a contracted service and that the customer is responsible for keeping backups current.

Ecxon says it performs periodic backups for security only for OpenVZ servers, but presents those backups as a courtesy that may not be available and may involve a service fee to recover a file.

That language is important because it cuts through generic cloud comfort. If a customer wants recoverability, it must not stop at the word "cloud" or "datacenter." It needs a backup design: what is backed up, how often, where it is stored, whether the service type is included, who can restore it, how long restoration takes and whether a restore has been tested. Ecxon's public terms place much of that burden on the customer. A serious buyer should accept that boundary before moving production data.

DDoS Protection Needs a Contractual Reading

DDoS protection is one of Ecxon's headline claims, and it is likely part of the company's appeal to game-server and hosting customers. The homepage, VPS page, dedicated-server page, network page and anti-DDoS page all reinforce the protection story. Ecxon claims 348 Tbps of mitigation capacity, Cloudflare Magic Transit integration and specialized handling for UDP floods and gaming traffic. For a customer whose normal failure mode is hostile traffic, that is not a decorative feature. It can be the reason to choose one provider over another.

The terms, however, add operational boundaries. For Canada, Ecxon says it offers anti-DDoS as a free courtesy and does not guarantee full operation or that every attack will be mitigated, while noting that the outside-Brazil structure belongs to OVH for DDoS protection. For Brazil, Ecxon says anti-DDoS is also offered as a free courtesy within a fair-use price policy.

It states that attack size, duration and repeated attacks within the same 24-hour period can be considered, that constant attack targets may be evaluated case by case, and that after three hours of daily use of layer-7 protection the service may have to carry that protection as a mandatory paid add-on. It also reserves the right to cancel services with at least six hours' advance notice in cases of massive attacks or attacks outside the fair-use value policy.

Those terms are not unusual in the hosting market, but they are decisive for high-risk workloads. A customer running a gaming community, public API, contentious forum, campaign site or other attack-prone service should not assume that the advertised mitigation headline equals unlimited protection. The better question is: what type of attack is included, what traffic volume or duration changes the commercial terms, whether layer-7 protection is in scope, how fast the path changes, whether customer-originated misconfiguration is excluded, and what notice period applies if the provider decides the risk is outside acceptable use.

In other words, DDoS protection should be evaluated as an operating procedure, not a number. Ecxon's number may describe the capacity of an upstream mitigation ecosystem, but the customer's practical protection depends on routing, prefix state, customer configuration, application design, fair-use policy, support response and escalation authority. For game-server operators, this is especially important because a service can be technically online while player experience collapses through jitter, packet loss or routing instability.

The Locality Case Is Useful but Conditional

Ecxon's Brazilian identity and Brazilian infrastructure positioning give it a plausible locality advantage. Brazilian buyers may value Portuguese-language support, local payment and published contact points, lower domestic latency for some users, a Brazilian legal counterparty, and infrastructure references that can be mapped to Brazilian routing records. For customers that do not need a hyperscale managed-service catalogue, a regional provider can be easier to understand and easier to hold accountable.

But locality is not a substitute for evidence. The site also markets Canada options, the terms distinguish Brazil and Canada protection models, and independent routing records show a mixture of prefix histories and upstream relationships. That does not make the offer suspect; it makes verification necessary. A customer should ask where a given plan will run, which IP range it will receive, what geofeed or location data applies, which DDoS provider or transit path is used and whether support has authority over the actual facility or upstream dependency involved.

For data-sovereignty and locality-sensitive work, the minimum record should include server location, legal counterparty, billing entity, support jurisdiction, data backup location, DDoS steering method and incident access path. Ecxon provides enough public information to begin that conversation. It does not, from public evidence alone, prove that every service selected by a customer remains in Brazil or that every copy of data, backup or traffic path stays within a preferred jurisdiction.

That is why Ecxon is best treated as a provider to diligence, not a label to accept. The same is true of larger clouds, but the burden is different. Hyperscalers usually publish extensive region, compliance and architecture documentation. Regional providers may offer more direct support and simpler products, but less public audit depth. The buyer should not punish Ecxon for being regional; it should ask regional-provider questions: who answers, where is the server, which network announces it, what is included, what is excluded and what proof is available when something fails.

Practical Buyer Questions

The first buyer question is identity: is the contracted party Ecxon Datacenter LTDA under CNPJ 33.162.811/0001-48, and does the invoice, customer account and terms link to that entity? The second is product boundary: is the workload on VPS, dedicated server, site hosting, game hosting or another service type, and is it hosted in Brazil or Canada? The third is network evidence: which IP prefix and ASN will be used, which location is advertised, and what happens if the address or route changes?

The fourth question is support scope. The customer should know whether tickets, email, WhatsApp or client-area messages are authoritative for incidents; whether response time is contractual; whether commercial hours differ from emergency support; and which evidence is needed to request a downtime credit. The fifth question is backup responsibility. Ecxon's terms put primary responsibility on the customer, so a buyer should either create its own backup process or contract a separate managed backup arrangement with tested restore steps.

The sixth question is DDoS scope. If protection is material to the purchase, the customer should ask which attack types are covered, whether protection is a courtesy or paid service, which thresholds trigger extra charges, whether layer-7 protection is included, what fair-use policy applies and what cancellation notice could apply under attack pressure. The seventh is payment-state risk. Since terms connect non-payment to suspension and cancellation rules, the buyer should make sure billing contacts, invoice dates and payment methods are actively maintained.

Those questions may feel basic, but they are the difference between buying infrastructure and buying a surprise. Ecxon has a public operating surface that makes the questions answerable in principle. The buyer's job is to force the answers into a record before the first outage, attack, migration, restore or billing dispute.

The Practical Verdict

Ecxon Datacenter LTDA should be read as a real Brazilian hosting and infrastructure provider with a visible legal identity, service catalogue, customer-area workflow, public terms and independently observable network footprint. Its AS270764 records, PeeringDB entry, BGP.Tools view, IPinfo ranges and own geofeed give the name more substance than a generic hosting label. Its website also exposes concrete service categories: VPS, dedicated servers, site hosting, game hosting, DDoS protection, support tickets and client accounts.

The same evidence keeps the verdict bounded. Ecxon publishes claims that need contractual or operational confirmation before production reliance: mitigation capacity, senior support, network capacity, Brazilian infrastructure ownership, rapid deployment and route quality. Its terms also place meaningful burdens on the customer for backups, account state, payment discipline and reimbursement requests. The result is not a warning away from Ecxon. It is a warning against lazy assurance.

For infrastructure, procurement and governance readers, the right posture is simple: treat Ecxon as a provider whose public record is strong enough to evaluate, but not strong enough to skip evaluation. Ask for the server location, prefix, support path, backup model, DDoS limits, billing rules and incident evidence. If those pieces align, Ecxon may be a practical regional infrastructure choice. If they do not, the customer has only bought a datacenter name, and a datacenter name is not the same thing as operational control.