cryptoservers.io

A privacy-first
offshore backbone

1 Tbps of anycast DDoS scrubbing, 150+ Gbps of blended Tier-1 transit, peering with the major European IXs — all terminated in jurisdictions chosen for free-speech precedent. Every IP on every plan is dual-stack, DDoS-shielded, and ready for BYOIP.

5 Tier-1 carriers 6 IX memberships IPv6-first Anycast scrubbing
Cryptoservers offshore network backbone

Network at a glance

What the pipes and the scrubbers actually look like — numbers, not marketing.

1 Tbps
Anycast DDoS

L3/L4 scrubbing capacity across four PoPs. L7 rules available on demand.

150+ Gbps
Blended transit

Tier-1 IP transit aggregated across five diverse upstream carriers.

6
IX memberships

Direct peering at AMS-IX, DE-CIX, LINX, FICIX, BIX and SwissIX.

/48 IPv6
Routed block

Every box ships dual-stack. /64 by default, /48 on flagship Citadel.

Tier-1 transit. Real peering.

Blended upstreams chosen for diversity — five different ASNs carry traffic for each location, with automatic failover if one degrades.

IP transit providers

Carrier-diverse Tier-1 transit with BGP weighting tuned for latency-first on our side and price on upstream overflow. Every DC has ≥ 3 of these active.

  • GTTAS3257
  • NTTAS2914
  • CogentAS174
  • LumenAS3356
  • TeliaAS1299
  • ArelionAS1299

Internet Exchange peers

We peer directly at the European Tier-1 IXs — traffic to/from Netflix, Cloudflare, Google, Hetzner, OVH, and most hyperscalers stays off paid transit entirely.

  • AMS-IXNL
  • DE-CIXDE
  • LINXUK
  • FICIXFI
  • BIXHU
  • SwissIXCH

DDoS protection, every layer

Volumetric, protocol and application-layer attacks are absorbed at the edge before they ever reach your server. No opt-in, no per-incident fee, no "fair-use" fine print.

Layer 3 / 4 · Volumetric

Anycast scrubbing

Anycast absorption at every PoP. Automatic detection inside 2 seconds for SYN, UDP-flood, amplification (NTP, DNS, Memcached) and reflection attacks.

Capacity
1 Tbps
Detection
< 2 s
Fair-use
none

Layer 7 · Application

HTTP / HTTPS / WS

Optional L7 rules on Bastion and up — rate-limits, JS challenges, captcha flows and bot-fingerprint filtering. Templates ready for auth, checkout and game lobbies.

Tiers
Bastion+
Templates
6 preset
Challenge
JS · hCaptcha

Geo-fencing & ACL

Per-service

Drop or rate-limit by country, ASN, known-bad IP list, or a custom prefix list you upload via API. Every rule is pushed to the edge in < 60 s.

Scope
Global
Push
< 60 s
API
REST · TF

IP & BGP policies

Control over your prefix, your announcements and your reverse DNS — without tickets.

IPv6-first, dual-stack everywhere

Every server ships with a routed /64 by default and a full /48 on Citadel. Reverse DNS editable per host from the dashboard.

BYOIP & ASN announcement

On Fortress and Citadel we accept BGP sessions from your ASN for IPv4 /24 or longer and any IPv6 prefix. Send LOA + IRR object, go live in 2 – 3 days.

Traffic-engineering communities

Well-known BGP communities: prepend by region, de-preference a carrier, blackhole a prefix, steer away from transit during IX congestion. Full list in docs/bgp.

RPKI ROV & IRR-filtered

All upstream and peer sessions are RPKI-validated and IRR-filtered. Route leaks from your AS are caught before they leave us; hijacks directed at you are dropped.

Check the routes yourself

No marketing between you and our network — run traceroutes, BGP lookups and ping tests directly from our PoPs.

Public looking-glass

Traceroute, ping, MTR and BGP show ip bgp from each of our 4 PoPs. IPv4 and IPv6. No login required, no rate-limit for interactive use.

Open looking-glass BGP docs

Network questions

What's the actual DDoS capacity — and what's the fine print?
1 Tbps of anycast L3/L4 scrubbing, split across 4 PoPs with each one able to absorb up to ~300 Gbps on its own. No per-incident charge, no traffic-tier "fair-use" quota, no handoff to a third-party scrubber like Voxility or Path. L7 filtering (HTTP rate-limits, bot challenges) is included on Bastion tier and above.
Can I bring my own IPs (BYOIP)?
Yes on Fortress and Citadel tiers. Send us a Letter of Authorization, your IRR route / route6 objects, and the origin ASN. We'll provision a BGP session, accept your prefix (minimum /24 IPv4, any IPv6) and announce it from our edge. Typical turn-up is 2 – 3 business days.
Which BGP communities do you support?
Inbound: per-carrier de-preference (cs:100:carrier), regional prepend (cs:200:region), selective blackhole (cs:666:prefix). Outbound: no-export, do-not-advertise-to-$peer, and geographic steering. Full reference in docs/bgp.
Do you support IPv6 only?
Yes — if you don't need IPv4 (or want to save on IP cost), you can opt out of the IPv4 allocation at checkout and run pure IPv6 with a routed /48. We'll provide a NAT64/DNS64 endpoint you can point resolvers at, so legacy v4-only services still resolve.
What's your reverse-DNS policy?
Fully self-serve. Every IPv4 and IPv6 address has editable PTR records in the dashboard and the API — we don't force a default cryptoservers. suffix. Changes propagate globally in under 5 minutes. The API accepts up to 1000 PTR updates per request for bulk deployments.
Will you publish a warrant canary for network-layer requests?
Yes — signed weekly with our PGP key. It specifically covers upstream takedown orders, BGP-route-injection orders, NSL-equivalents in each jurisdiction, and national-security letters. See /canary for the current signed statement.

Need this infrastructure under your own ASN?

BYOIP, cross-connects, private VLANs, ASN setup, transit-only deals — all quoted per project.