Network and backbone

One edge for every plan: L3/L4 scrubbing, IPv6 /64, editable PTR, BGP communities on request. BTC, XMR or USDT settle the same invoice.

Uzun makale metni İngilizce. Üst çubuk, katalog ve ödeme çevrildi.

DDoS

Layer 3/4 filtering runs continuously at roughly 1 Tbps of edge capacity; an optional L7 profile exists for HTTP floods. Both ship inside the plan price - protection here is not a second line item. A $3 Scout paid in Monero and a dual-EPYC box paid in USDT ride the same scrubbing path. Selling "DDoS protection" as an upsell is a business model we declined. Indicative round-trip times live in the looking glass.

What filtering does and does not stop

Volumetric floods - SYN, UDP amplification, reflection - are absorbed at the edge before they reach your port. Application-layer exhaustion (HTTP request floods, slowloris) needs the L7 profile plus your own rate limits; no scrubber replaces sane nginx or game-server limits. During an attack, traffic is announced, cleaned and forwarded; legitimate packets occasionally pay a latency tax measured in milliseconds. The looking-glass probes stay live throughout, so you can watch what an incident actually does to RTT instead of reading a status rhyme.

IP and DNS

Every KVM instance carries one IPv4 plus a /64 of IPv6. Reverse DNS is yours to edit from the panel the moment provisioning finishes. Metal can request a /48. PTR records are mail and VPN hygiene, not an identity field, and we are not in the domain business.

BYOIP

Bring-your-own space mounts on the top two dedicated SKUs, Fortress and Citadel. The mechanics are an LOA plus your ASN and a few days of coordination with the facility - it is a routing change, not a checkbox in the cart.

Transit and peering

Amsterdam terminates on AMS-IX and DE-CIX. Zurich on SwissIX and DE-CIX. Reykjavik on FICIX, Bucharest on BIX, Singapore on SGIX, Frankfurt on DE-CIX, Riga on RIX and GEANT. The Americas rack at IX.br and PTT.br in Sao Paulo, DE-CIX Dallas and Equinix in the US, MXIX in Mexico City. Africa peers at CINX and NAPAfrica (Cape Town) and NAPAfrica (Johannesburg); Asia closes the ring at HKIX, UAE-IX, KazIX and BKNIX; Russia at MSK-IX and SPB-IX. Per-facility uplink figures sit on each location page, because that is where they are contractually true.

Latency, honestly measured

Indicative RTT to Amsterdam from our own probes: sub-millisecond in Amsterdam itself, roughly 8 ms from Frankfurt, 9 ms from Zurich, 18 ms from Reykjavik, 25 ms from Riga, 30 ms from Bucharest. The long legs are physics: about 80-90 ms to Almaty, Ashburn and Dubai, 110 ms to Dallas, 140-160 ms to Sao Paulo, Johannesburg and Mexico City, 170-180 ms to Cape Town and Singapore, 200-240 ms to Bangkok, Hong Kong, Tokyo and Shanghai. Moscow and Saint Petersburg land at 40 ms and 35 ms. Numbers are indicative, not an SLA - measure from your own users with the looking glass.

Facility grade

All twenty-one sites are Tier III or Tier III+ with 2N power, spanning four continents. Uplinks run from 10 Gbps in Reykjavik and Bucharest through 40 Gbps in most markets to 100 Gbps in Zurich, Frankfurt, Singapore, Tokyo, Dallas and Ashburn. Facility tier and law per city are laid out in the location table on the locations index.

Port sizes: set by the SKU, not the city

The port you get follows the plan, and the plan prices the same in every facility. KVM VPS lines run unmetered from 1 Gbps at the floor to 10 Gbps at the top of the ladder. The storage line steps from 2.5 Gbps at 1 TB to 10 Gbps at 5 TB, because moving archives is the entire job of those boxes. Bare metal starts at 1 Gbps on the entry Xeon and reaches 25 Gbps on the dual-EPYC Citadel, IPMI included at every rung. None of these are burst ratings that evaporate after five minutes; the meter sits on the uplink and the same table applies in Reykjavik as in Dubai. When a workload outgrows the port, the honest fix is the next SKU, not a faster billing tier.

Choosing a city without superstition

Pick the rack for two measurable things: distance to your users and the law that governs the building. Everything else - the flag, the fiat currency, the coin at checkout - changes nothing about the packet path. A storage box filling 5 TB over a weekend wants a short hop to the machines that feed it. A Monero node or a wireguard endpoint wants jurisdictional separation from the people it inconveniences, which is what dedicated servers with out-of-band IPMI are for. Both orders land on the same invoice page and settle in the same sixteen coins, so geography and payment stay independent decisions.

Redundancy across facilities

Twenty-one sites on four continents also mean you can run hot spares without a second vendor. Panel snapshots and a Borg or Restic target replicate cleanly between facilities; a DNS TTL is the only dial that decides how fast a failover becomes visible to users. The locations index publishes the facility tier, uplink class and governing law per city, so a redundancy plan can be written from numbers instead of sales adjectives - and re-checked after every refresh of that table.

What the coin does not change

Paying in XMR, BTC or USDT does not reroute your traffic. ASN, scrubber profile, IPv4 and port speed are properties of the plan; the coin only settles the USD figure. Send the asset the invoice names, on the network it names.