Summary

  • The strongest network evidence points to AS212000, an active autonomous system registered to Zeljko Rosic trading as 1337 Hosting Solutions e.U. that originates one IPv4 /24 with a valid route-origin authorisation.
  • AS1337 should not be treated as a second company-operated network merely because it resembles the brand: ARIN records place it within a legacy block registered to Verizon Business, and RIPEstat shows it as unannounced.
  • The company discloses an Austrian owner and registration, German data-centre infrastructure supplied by aurologic, unmanaged server terms and customer-facing support channels, but it does not publish staffing levels or a guaranteed support-response time.

A memorable name creates a verification problem

The number 1337 does a great deal of work in this business. It appears in the trading name, the website and the AS name attached to the network the company demonstrably uses. That consistency makes the offer easy to remember. It also creates an unusually simple trap for anyone doing supplier diligence: a brand string can look like a network identifier even when the underlying registry says otherwise.

The BTW directory entry associates the business with AS1337 and AS212000. Those two references are not equivalent evidence of control. An autonomous system number is useful only when its registry holder, routing activity and originated address space are checked together. On that test, AS212000 is the meaningful operating signal. AS1337 is a naming collision.

This distinction matters beyond one small provider. Hosting customers often see an ASN, a data-centre claim or a protection label and read it as a compact guarantee of independence. In reality, those clues describe separate layers: legal responsibility, route origination, physical placement, upstream connectivity and the contractual limits of support. The public case for 1337 Hosting becomes clearer, not weaker, when those layers are kept apart.

The legal identity is unusually legible

The company's own legal notice identifies 1337 Hosting Solutions e.U. as a registered sole proprietorship owned by Zeljko Rosic, based in Salzburg. It gives company number FN 665783v, VAT identifier ATU82601007, the Regional Court of Salzburg as register court and the City Magistrate of Salzburg as supervisory authority. It also states the business purpose as IT and automated data-processing services, particularly hosting and DDoS protection.

That is valuable accountability evidence. A buyer is not dealing only with a product label or an anonymous checkout page; there is a named proprietor, an Austrian legal form, a registered office and published contact routes. The notice also lists separate addresses for general contact, Digital Services Act contact and abuse reports. Those details create identifiable places to direct contractual, regulatory and network-abuse questions.

The legal form also sets the scale of the assurance. An e.U. is an Austrian registered sole proprietorship, not evidence of a large support organisation or a multi-site engineering department. The public material does not disclose headcount, shift coverage or escalation staffing. The correct conclusion is therefore narrow: responsibility is attributable, but operational depth cannot be inferred from registration alone.

AS212000 is the operating network signal

RIPEstat's AS overview names the holder of AS212000 as “AS-1337HS Zeljko Rosic trading as 1337 Hosting Solutions e.U.” and marks the network as announced. The RIPE RDAP record shows the ASN as active, registered on 15 January 2021, with the same organisation as registrant and Zeljko Rosic in the administrative and technical roles. This is a coherent chain from person and business to a live network identifier.

The visible routing surface is compact. RIPEstat's announced-prefix data shows one originated block, 185.244.28.0/24. That is 256 IPv4 addresses. A route-origin validation check reports a valid authorisation for AS212000 to originate exactly that /24. RPKI validity does not prove service quality, security or ownership of every machine behind the addresses. It does show that the route observed for this small address block is consistent with a cryptographically verifiable authorisation.

Public routing views also show concentration. bgp.tools describes one originated IPv4 prefix and identifies aurologic GmbH as the observed upstream. RIPEstat's neighbour data likewise exposes AS30823, aurologic, as the relevant adjacent network. There is no observed IPv6 origination in the reviewed records. The result looks less like an independently meshed carrier network than a small hosting ASN operating through a larger infrastructure partner.

That is not inherently a defect. A compact provider can use its own ASN and address space while buying transit, facilities and mitigation from specialists. But it changes the due-diligence question. Customers should ask how much routing control remains with 1337 Hosting during an incident, which changes require the upstream, and whether redundancy exists beyond what public route views expose.

AS1337 belongs to a different story

The direct registry evidence for AS1337 breaks the apparent brand connection. ARIN's RDAP record places the number inside the AS1321-AS1340 registration named ANSBB-ASNNET-1. Its registrant handle resolves to Verizon Business. Separately, RIPEstat's overview identifies Verizon Business as the holder and reports the ASN as not announced; its announced-prefix endpoint returns no prefixes.

Nothing in those records supports treating AS1337 as a second autonomous system operated by 1337 Hosting. The safer reading is that the company's brand and AS212000's name use “1337”, while the actual integer AS1337 remains part of an older allocation to another organisation. This is precisely why network-resource evidence should be joined by registry identity and live routing, not matched by digits or text alone.

For buyers and researchers, the practical rule is simple: use AS212000 when assessing this provider's public routing footprint. Treat references to AS1337 as unresolved unless fresh primary evidence establishes a transfer or operational relationship.

The service is automated, shared and partner-dependent

The commercial surface is more developed than the small routing footprint might suggest. The customer portal offers standard VPS plans and an advanced DDoS “Shield” range. Both advertise AMD Ryzen compute, NVMe storage, one IPv4 address and a shared 25 Gbps uplink across several resource tiers. The portal also exposes account management, payments, service management, tickets and network-status functions.

The terms of service put important boundaries around that presentation. VPS and dedicated servers are unmanaged unless separately agreed. Customers are responsible for operating-system installation, configuration, patching, application security and off-platform backups. Support covers the underlying network, hardware and power rather than customer software. VPS compute can be shared or overprovisioned, and stated CPU counts are maximum allocations rather than a promise of continuously dedicated performance unless a product explicitly says otherwise.

DDoS protection is also an automated dependency. The terms say aurologic's specialised system analyses and filters traffic, with thresholds and traffic patterns used to detect attacks. Legitimate high-throughput traffic, UDP, backups or long transfers may be misclassified, filtered or rate-limited. Always-on protection can apply lower detection thresholds, while an attack against the shared /24 may affect more than one customer. Automation expands the service a small operator can offer, but it also introduces a control boundary: some outcomes depend on the partner's detection system rather than an intervention performed solely by 1337 Hosting.

Data locality is strong but not absolute

The company's privacy policy says its server infrastructure is exclusively in the European Union, in German data centres operated by aurologic. That is a specific and useful workload-locality claim. The same policy names aurologic for server and data-centre infrastructure and describes 1337 Hosting as a processor when customers place personal data on VPS or dedicated servers.

Yet “EU servers” does not mean every customer-related data flow remains in one German facility. The policy says the client area uses WHMCS for accounts, billing and tickets, while payment and anti-bot functions can involve Stripe, PayPal and hCaptcha, including transfers to the United States under stated safeguards. A self-hosted BTCPay Server is presented as an EU-based alternative for Bitcoin processing, although blockchain transaction data is globally replicated by design.

The useful procurement distinction is between hosted workload data and commercial-account data. The reviewed disclosure supports German placement for server infrastructure. It does not support a blanket claim that every identity, payment, security or support record stays only in Germany. Buyers with strict sovereignty requirements should map each of those flows separately and request the available data-processing agreement.

Support accountability is visible, but capacity is not

Customers can submit tickets, view service status, consult a knowledge base and use published office and abuse addresses. The privacy notice explains that ticket histories and timestamps are retained for service and quality purposes. The terms target 99.9% annual availability for network reachability and power, but call it a target rather than a general guarantee; a different binding commitment requires an individual written SLA. Several events, including upstream failures, planned maintenance and certain DDoS-protection effects, are excluded from downtime calculations.

What is absent is just as relevant. The reviewed pages do not state a guaranteed first-response time, a restoration target, support hours or the number of people available for escalation. A named proprietor can make accountability direct, but it does not establish around-the-clock labour capacity. Workloads that require rapid human intervention should therefore price the support contract, not just the virtual machine.

A credible small-provider case, with narrow proof

1337 Hosting's public evidence supports a real, attributable and technically active hosting business: Austrian registration, a named owner, an orderable product range, an active ASN, one authorised IPv4 route and disclosed German infrastructure. It also shows where assurance ends. The routed footprint is small, the visible upstream path is concentrated, protection depends on automation supplied by a partner, server management and backups usually remain with the customer, and public support commitments stop short of response-time guarantees.

The right verdict is neither “just a name” nor “fully assured by an ASN”. It is a narrower proposition: 1337 Hosting has enough public identity and network evidence to be evaluated seriously, provided buyers test the specific controls their workload needs. The most useful next questions concern upstream redundancy, IPv6 plans, mitigation ownership, incident escalation, backup design and a written SLA. Those answers, rather than the memorable number, determine whether the service is fit for a particular risk profile.