Optimized Cloud Compute

Volumetric floods (e.g. UDP, ICMP and TCP floods) as well as reflection/amplification attacks (e.g. DNS, NTP, memcached etc.) and protocol based attacks (e.g. SYN floods, ACK floods etc. as well as fragmentation and malformed packet attacks). We also absorb multi-vector attacks.

In case the incoming traffic load (DDoS attack) is bigger than the traffic that can be filtered by us, then the targeted IP will be black-holed.

Dedicated DDoS Protection is automatically enabled for all relevant services such as Cloud Compute, Colocation, Bare Metal servers and GPU servers. No activation is required. The protection starts as soon as the related resource goes online.

No, Netrouting DDoS Protection is a network-layer attack mitigation service, it is designed to protect against volumetric traffic attacks (so called floods) at network-layer (so called Layer 3/4). For application-layer attacks (so called Layer 7 attacks) like HTTP floods, slowloris, etc. you would use a Web Application Firewall (WAF) or layer 7 packet processing, edge caching services like Cloudflare or Akamai.

Flex Cloud is an shared-CPU pool (oversubscribed by reasonable ratios, not like those super cheap providers that want to sell you super cheap and then make up for it in other ways). It's very cost efficient for vCPUs. Flex Cloud is meant for general workloads, dev / test, web tier, etc. while Dedicated Cloud is meant for very specific workloads, like database, real-time services, etc. where p99 latency matters and the customer doesn't want to manage physical servers.

Our cloud runs KVM directly on our own bare metal servers. We do not use any form of nested virtualization, co-hosted shared-tenant kernels or other hypervisor layers on top of other providers' kernels. The VMs on our cloud are managed through our own control plane (the same that our API talks to), which enables us to have VMs up and running within sub-1 minute and to perform live migration of VMs to other hosts should we need to perform maintenance on the underlying hypervisor.

No. All cloud plans include a fixed transfer quota for the uplink speed of your choice (1G or 10G) up to 100 TB per month. Thereafter we bill on a per-TB basis at the same low rate. This means no surprise egress charges, no charges for inter-AZ traffic, no charges for inter-region traffic within Europe and many other "hidden" charges that can turn a cheap €200/mo cloud work load into a €2,000/mo work load on AWS. Use our cloud for an egress-heavy CDN origin or video streamer and you will see the savings on your first month bill.

Yes - the cloud control plane is multi-region by design and the same image / template you launch in Amsterdam will launch unchanged in Frankfurt, Miami or Singapore. Snapshot in one region, restore in another. Inter-region private networking rides our backbone (AS6206) at backbone speed; you do not need to spin up site-to-site VPNs to mesh your VMs across PoPs.

Gaming / DDoS | Netrouting DDoS Protection - free, always-on service protecting all Netrouting infrastructure (Cloud Compute, Colocation, Bare Metal servers, GPU servers) from network-layer (L3/L4) DDoS attacks. No setup required.

While we don't have managed Kubernetes yet (it's on our roadmap though), the vast majority of our customers are running their own K8s clusters - on our bare metal servers or in our cloud (flex or dedicated). Often 3 node clusters for k3s or larger for full blown kubeadm controlled clusters (where we also provide Cluster API for KVM to run against our control plane to manage those for them).

Every city page now includes the public test IP address for that location, as well as a link to 100 MB, 1 GB and 10 GB test files. You can download these files from the location nearest to you with curl or wget, or download them from your browser.