Network and backbone

Anycast DDoS, dual-stack, editable PTR, BGP communities on request. Same edge whether you pay the invoice in BTC or USDT.

DDoS

L3/L4 always on at ~1 Tbps class edge capacity. Optional L7 for HTTP. Included, not an upsell SKU. A $6.80 VPS paid in Bitcoin or Monero gets the same scrubbing class as a dedicated box paid in USDT. We do not sell 'DDoS protection' as a second invoice. Indicative RTT: looking glass.

IP and DNS

1x IPv4 + /64 IPv6 on VPS. Editable reverse DNS from the panel after provision. /48 on request for dedicated. PTR is part of mail and VPN hygiene; it is not a KYC field. We do not sell domains.

Transit

Amsterdam is AMS-IX / DE-CIX. Zurich is SwissIX / DE-CIX. Reykjavik is FICIX. Bucharest is BIX. Singapore is SGIX. Uplink numbers are on each location page. BYOIP is Dedicated Pro+ and Ultra: LOA plus ASN, a few days, not a checkout toggle.

BGP, communities, and routing hygiene

Every VPS talks to a routed edge that a network team maintains: prefix filters, RPKI-aware upstreams, and peering at the exchanges listed above. You do not run BGP on a VPS — but you inherit the hygiene of those who do. Concretely, what you get by default:

• Filtered routes — upstream prefixes are IRR-filtered; hijacked prefixes do not casually ride our ASNs.
• Stable egress identity — your IPv4 leaves via the location's ASN, which receivers can score; a clean pin stays clean if your mail and scripts behave.
• Communities on request — dedicated-tier customers can request BGP community tagging for traffic engineering; VPS gets the default policy, which is the same one the dedicated boxes use.

The peering fabric itself is public knowledge — AMS-IX and DE-CIX publish their member and traffic statistics, and the looking glass shows the route you actually get.

What payment does not change

Coin choice does not change the ASN, the scrubber, or the IPv4 you receive. It only changes how the USD total is settled. Send the asset named on the invoice, on the named network.

The edge, location by location

Uplink and scrubbing class are identical across the fleet; what changes by city is the peer set. A practical map:

The full 21-location table with per-city latency anchors lives on each location page; the looking glass carries live RTTs.

Traffic model: unmetered, with one honest line

• VPS and storage: unmetered — no per-GB invoice exists in the catalog.
• Ports: 1 to 10 Gbps by plan tier, not by geography.
• The honest line: unmetered is not unfiltered — attack traffic hits the scrubber, AUP-banned abuse (spam floods, paid attacks) hits the contract.
• What you never see: bandwidth overage fees, regional surcharges, or a 'premium bandwidth' upsell on the same rack.

Reverse DNS and mail deliverability

1. Provision the VPS; the IPv4 appears in the panel.
2. Set PTR from the panel to a hostname you control — mail receivers check forward-confirmed reverse DNS before they read your content.
3. Match the A record of that hostname back to the IP.
4. For mail-serving boxes, add SPF/DKIM in your application stack; the PTR is the entry ticket, not the whole meal.

What the scrubber actually does during an attack

When volumetric traffic arrives, it terminates at the scrubbing edge before it reaches your rack. Clean traffic is forwarded; the attack suffix is dropped. The practical facts, without the brochure adjectives:

• Always-on L3/L4 — no BGP re-routing delay, no 'protection activation' window. The filter is in the path from the first packet.
• L7 for HTTP is optional — application-layer filtering needs to read your traffic, so it is a per-service toggle, not a default.
• No blackhole-by-default — a small attack does not get your IP null-routed while you open a ticket.
• Shared edge, honest capacity — ~1 Tbps class is fleet capacity, and it is not for resale as a per-customer upsell.

What an attack does not do: change your IP, suspend your box, or start an invoice. Abuse that originates from your box is a different matter — that is the AUP, and it applies in both directions.

IPv6 on every box

Dual-stack is the default, not a checkbox: each VPS ships one IPv4 and a routed /64, dedicated gets a /48 on request. That is 18 quintillion addresses for the price of none — no 'IPv6 enabled' surcharge exists in the catalog. Practical notes:

• Applications bind to v6 independently; the firewall is yours to configure, same as v4.
• rDNS works for v6 too — set it from the panel per address.
• Outbound v6 is useful for sources that rate-limit by IP: one more clean identity on the same box.