Summary

  • CraftLands Hosting S.R.L. can be tied across Romanian company information, its own legal pages and a current RIPE registration, giving the brand a more traceable identity than a domain name alone.
  • Its website, client portal, documentation, status page and product catalogue are credible signs of an operating retail service, but specifications and location claims remain supplier statements rather than independent measurements.
  • AS212854 is registered to CraftLands, yet RIPE observed no current route announcements from that ASN on July 15, 2026. Publicly exposed service hostnames instead resolved into several third-party networks, making infrastructure responsibility more layered than the company name suggests.
  • The visible support and refund paths are useful, but the SLA, retention language and outage-claim process put material obligations on the customer. Buyers should verify escalation, backup, location and data-processing terms in writing.

A verifiable name is the start, not the conclusion

Small hosting companies are often judged from the retail surface: a fast website, an attractive processor name, a list of cities and a Discord invitation. Those signals matter, but they answer only whether a business is trying to sell hosting. They do not establish who signs the contract, who controls the network, who owns or leases the server, where customer data can move, or who has authority to restore service.

CraftLands is a useful case because its public footprint is neither empty nor simple. The company's own description says the service is operated by CraftLands Hosting S.R.L., a Romanian company. A Romanian company-information page records the same legal name, unique registration code 50929471, registration number J2024043623000 and a formation date of November 22, 2024. The listed Bucharest address also appears in the current RIPE registration and on CraftLands' Trustpilot profile. Those repeated identifiers make it reasonable to connect the storefront to the Romanian legal entity.

That is identity evidence, not performance evidence. The Romanian listing describes the company's principal activity under CAEN 6201, custom software development. A principal activity code can be broad and does not prevent a company from selling hosting, but it does not independently verify the scale or architecture of that hosting business. The same listing shows zero turnover and zero employees for 2024. Because the company was formed near the end of that year, those figures say little about operations in 2025 or 2026 and should not be recycled as a current size estimate.

The more defensible reading is narrow: there is a named Romanian counterparty, and several public surfaces converge on it. A buyer can therefore ask for an invoice, contract and data-processing commitment from a specific company rather than from an unexplained trading name. Whether those documents actually name CraftLands Hosting S.R.L. remains something to confirm during purchase.

The retail service leaves operational footprints

CraftLands' service claim goes beyond a single sales page. The main site advertises game servers for Minecraft, Hytale, Rust, Palworld and Satisfactory, as well as dedicated servers. It gives plan-level RAM, NVMe storage, backup and processor specifications. The dedicated-server page advertises Ryzen 9 9950X systems, 128GB or 256GB of RAM, up to two 4TB NVMe drives and 10Gbps links. The about page names six locations: Singapore, Los Angeles, Dallas, New York, Amsterdam and Frankfurt.

There is also a functioning client area, a documentation site and a separate status hostname. The documentation index covers panel access, setup, SFTP, plugins, console use, performance and domain configuration. A backup guide describes creating, restoring and downloading backups from the server dashboard. These are modest but meaningful service-proof records: they describe actions a customer would perform after purchase, not merely features used to attract one.

The distinction still matters. Product pages are supplier claims. Processor models, backup allowances, port speeds and city names were not independently benchmarked for this review. Phrases such as "worldwide hardware," "no downtime during floods" and a median support reply of about 15 minutes are assertions from CraftLands, not audited service statistics. Even the location picker shown on product pages displayed a testing or checking state during the research capture rather than public latency results.

Documentation proves that a supportable workflow has been described; it does not prove that every plan receives the same implementation, that backups sit outside the failure domain, or that a restore has recently succeeded. The public footprint is therefore stronger than a bare landing page, but weaker than a customer-specific architecture, test result or incident history.

The ASN is real, but it is not current traffic proof

The most technical identity clue is AS212854. RIPE RDAP identifies the autonomous system as CraftLands-Hosting, names CraftLands Hosting S.R.L. as the registrant and provides an abuse contact at the company's domain. The registration event is dated November 10, 2025. RIPE also records the CraftLands maintainer and an assigned status. This is useful evidence that the company has taken a step toward a recognisable network identity and has published a route-policy and abuse-handling surface.

It should not be overstated. RIPE's routing-status view, queried on July 15, 2026, showed zero IPv4 prefixes, zero IPv6 prefixes and no visibility among the monitored peers. In other words, the registry assignment existed, but RIPE did not see AS212854 originating address space at that time.

There is a historical wrinkle. The same routing view reports an earlier IPv6 announcement in May and June 2023. That observation predates the November 2025 CraftLands registration and reflects an earlier use of the ASN; it cannot be credited to the present company. ASN history follows the number, not automatically the current holder. This is why an ASN badge, detached from dates and live routing, can create more confidence than the evidence supports.

Other public clues point toward a supplier-based delivery model. Hostnames exposed by the CraftLands website for Los Angeles, New York and European service endpoints resolved during the research pass to addresses originated by networks including ReliableSite, Telic Technologies, Royale and Hetzner. The company itself says its DDoS mitigation comes from GlobalSecureLayer or Royale. Together, those observations support an inference that CraftLands assembles its offer across third-party facilities or network providers rather than delivering every location from address space announced by AS212854.

That model is common in hosting and is not, by itself, a weakness. Leasing servers, rack capacity, transit or mitigation can give a small operator broad geographic reach. The assurance question is allocation of responsibility: which provider controls a given machine and route, what CraftLands can change directly, what must be escalated to an upstream, and which party communicates during a regional failure. The public record shows layers; it does not publish a customer-by-customer map of those layers.

Location choice is not yet a data-sovereignty map

Six advertised server locations give customers a useful placement choice, especially for games where latency is visible. They do not answer every locality question. A server selected in Frankfurt may keep the primary game files there while account details, billing records, support conversations, analytics, backups or abuse evidence are handled elsewhere.

CraftLands' privacy policy says account and order information may be collected through WHMCS, and that integrated processors include Stripe and PayPal. It says data is used to provide the service, enforce terms and prevent abuse; it also says users can request erasure through a support ticket. The retention wording combines two tests: data remains until deletion is requested or until it is no longer needed to prevent fraud.

Those statements create a route for a user, but they are not a complete enterprise data map. The public policy does not set out a location-by-data-type matrix, a detailed subprocessor list, backup retention periods, cross-border transfer arrangements or a response timetable for data requests. Nor does the public backup guide state whether scheduled copies stay in the same facility as the active server.

For a casual game world, that may be an acceptable gap. For a commercial community, an educational deployment or any customer carrying personal data, it changes the diligence required. The buyer should establish where account records and server content reside, whether backups cross regions, who can access console and file data, and how deletion propagates through backup copies. A city label on the order form should be treated as a placement claim for the purchased server, not as a blanket sovereignty guarantee for every record connected to the account.

Support is visible; accountability lives in the conditions

CraftLands puts human support at the centre of its offer. Its about page advertises 24-hour coverage through live chat, tickets and Discord, with a median response of about 15 minutes. The Trustpilot profile showed a 4.8 score across 87 reviews during the research pass, including recent comments about activation, support and problem resolution. Trustpilot also marked some reviews as verified and said the company typically replied to negative reviews within 24 hours.

Customer reviews are useful directional evidence, particularly when they describe concrete interactions rather than repeat product slogans. They are not a substitute for support metrics: the review population is self-selecting, CraftLands invites reviews, and public comments cannot show the full distribution of response or resolution times. A quick first reply is also different from a restored server or a completed refund.

The binding conditions are more revealing. CraftLands' terms of service require refund requests through an authenticated ticket or Discord process and offer a 72-hour refund window for a new service, with stated limits. The terms provide a one-day payment grace period and say files may be deleted when payment remains outstanding for seven days. They also reserve broad suspension and termination rights, including consequences for disputes and chargebacks.

The service-level agreement promises 99.9% yearly network availability for covered game and dedicated services and offers service credits worth five times the outage duration when that level is missed. But customers must file a claim within seven days, from an authorised account, and the company says it investigates and determines outcomes at its discretion. Planned maintenance, software failures, customer actions, excess resource use and events beyond the company's control are excluded; reseller downtime is outside coverage.

This is a real remedy path, but a bounded one. It protects a direct customer who notices an eligible network outage, documents it and submits promptly. It offers less protection for application failures, supplier disputes, ambiguous degradation or a customer who assumes compensation is automatic. The best pre-purchase support test is therefore not simply asking whether help is available. It is asking who owns an incident, how escalation works across upstream providers, what evidence the customer must preserve and when the clock starts for claims and data deletion.

What should be verified before the name carries assurance

The public evidence supports treating CraftLands as an identifiable young hosting business with a live retail operation, documented customer controls and a visible support culture. It does not support treating every marketing claim as independently verified, or AS212854 as proof that CraftLands currently originates the networks serving its customers.

A buyer can close much of that gap with a short set of written answers. The order and invoice should name CraftLands Hosting S.R.L. and state the governing service terms. The selected city should be tied to a named facility or infrastructure provider, with an explanation of who owns the server and who can replace hardware. The company should identify the origin network used for the ordered service, even if it differs from AS212854, and explain which party supplies DDoS mitigation.

Backups deserve their own questions: how many copies exist, where they reside, how long they are retained, whether the customer can export them, and when the last restore path was tested. Support terms should identify the channel for urgent incidents, the escalation route when an upstream is involved and the difference between response and resolution targets. Customers with locality obligations should request the account, billing, support and backup data map rather than rely on the game-server location alone.

None of those questions assumes that CraftLands is failing. They turn a promising public footprint into a decision that can survive a real outage. The company name is traceable, the service surface is visible and the support story has outside corroboration. Operating assurance begins where those signals are converted into customer-specific commitments about control, place, evidence and remedy.