Neue Funktion

Meistern Sie Ihre E-Mail-Zustellung mit dem Mail Delivery CenterNeu: Mail Delivery Center für intelligentere E-Mail-Zustellung Mehr erfahren >

Network services

The network your sites actually run on

Six datacenter locations across four regions, carrier-diverse transit at every one, and always-on DDoS filtering in front of every port. Pick where your service lives; we handle everything between it and your visitors.

  • 6Datacenter locations
  • 100 Gbit/sUpstream capacity
  • Multi-carrierTransit at every site
  • 99.9%Uptime SLA

Sechs Rechenzentrumsstandorte

Hosten Sie Ihre Website dort, wo Ihre Leser sind

Entfernung ist Latenz, die sich nicht wegoptimieren lässt. Wählen Sie bei der Bestellung den Standort, der Ihrem Publikum am nächsten liegt — oder lassen Sie eine bestehende Website kostenlos umziehen, wenn sich Ihr Traffic verlagert.

  • Sofia, Bulgarien

    Europa

    Ideal für: Europäisches Publikum und Daten mit EU-Residenz

  • Los Angeles, USA

    Nordamerika

    Ideal für: Die US-Westküste und den kürzesten US-Hop nach Asien-Pazifik

  • Dallas, USA

    Nordamerika

    Ideal für: Ausgewogene Latenz über die gesamten kontinentalen USA

  • Singapur, Singapur

    Asien-Pazifik

    Ideal für: Südostasien, Australien und den indischen Subkontinent

  • Saudi-Arabien

    Naher Osten

    Ideal für: Golf-Traffic und Unternehmen, deren Daten im Königreich bleiben müssen

  • Kairo, Ägypten

    Naher Osten und Nordafrika

    Ideal für: Ägypten und Nordafrika, ohne Umweg über Europa

Alle Standorte fahren denselben Stack: LiteSpeed, NVMe-Speicher, kostenloses SSL, tägliche Backups und dauerhaft aktive DDoS-Filterung.

Under every port

What you get on the network side, everywhere

The same connectivity standard applies in Sofia, Los Angeles, Dallas, Singapore, Saudi Arabia, and Cairo. No location is the cheap one.

  • Carrier-diverse transit

    Every facility is fed by multiple upstream providers rather than a single carrier. When one upstream has a bad afternoon, your traffic takes a different path instead of a support ticket.

  • 100 Gbit/s upstream capacity

    Headroom is what keeps a busy neighbour from becoming your problem. Capacity is provisioned well ahead of committed traffic, so a spike somewhere on the platform does not surface as latency on your site.

  • 1 Gbps ports, 10 Gbps on request

    Standard uplinks run at 1 Gbps with an unthrottled path. Dedicated and custom deployments can be provisioned on 10 Gbps ports when your workload genuinely needs them.

  • Always-on DDoS filtering

    Attack traffic is scrubbed upstream before it reaches your port — in every location, on every plan, with nothing to switch on and no surcharge.

  • No single path, no single feed

    Redundant routing, redundant power, and carrier-neutral facilities. A failure has to happen in more than one place at once before it reaches you.

  • Fast, resilient DNS

    Authoritative DNS runs on Google-backed infrastructure, so the very first lookup a visitor makes is answered from a nearby node instead of across an ocean.

Choosing a location

Put the server near the audience, not near yourself

Latency is mostly distance, and distance is the one thing no amount of caching, tuning, or faster hardware will give back. Three questions settle it.

  1. Where do your visitors actually load the page?

    Check your analytics by country, not by where your business is registered. An agency in London serving Gulf clients belongs in Saudi Arabia or Cairo, not in Europe.

  2. Does the data have to stay somewhere?

    If you are bound by EU data residency, Sofia keeps your data inside the union. If you need records kept in-Kingdom, Saudi Arabia does that. Pick the constraint first, then optimise inside it.

  3. Is your audience split across regions?

    Host where the largest share of your revenue is and let caching serve the rest, or talk to us about running separate deployments per region. Splitting a small audience usually costs more than it saves.

Picked wrong, or your traffic moved? Migration between our locations is free and handled by our team — you do not pay for changing your mind.

Backed by a written SLA, not a promise

Network and power availability are covered by a service level agreement with defined credits. If we miss the target, you claim — no goodwill negotiation required.

Read the full SLA
  • 99.9% availability on standard services
  • 99.95% on premium infrastructure
  • Service credits defined in advance, not case by case
  • 24/7 monitoring, with engineers on call rather than on a rota of one

Network questions, answered plainly

  • Which locations can I choose from?

    Sofia (Bulgaria), Los Angeles (USA), Dallas (USA), Singapore, Saudi Arabia, and Cairo (Egypt). Availability varies by product — shared and WordPress plans, cloud servers, and dedicated hardware do not all exist in every site, so check the product page or ask us before you order.

  • Can I move to a different location later?

    Yes, and we do the move for you at no charge. Tell support where you want to land and we will schedule it, usually inside a maintenance window you choose.

  • What uplink speed does my service get?

    Standard services run on 1 Gbps ports with no artificial throttling. Dedicated servers and custom builds can be provisioned on 10 Gbps ports on request.

  • Do you run your own autonomous system?

    No. We deploy into carrier-neutral facilities and buy transit from multiple upstream providers at each site, rather than announcing our own AS. In practice that means your routing is handled by networks that do it at far larger scale than a hosting provider our size could.

  • Is DDoS protection extra?

    No. Filtering is always on, included on every plan in every location, and there is nothing to activate.

  • How do I test latency from my own network before committing?

    Start a trial on the location you are considering and measure it yourself from the networks your visitors actually use. If the numbers disappoint, move to another location free or cancel within the refund window.

Pick a location and deploy on it

Same stack, same SLA, same filtering in all six. The only decision left is which one sits closest to the people you are trying to reach.