About us

We were the ones getting attacked.

WipZen started because a Friday-night raid took down a server we ran, and every product we could afford either did not work or wanted a percentage of our store revenue to try. So we built the thing we had wanted to buy.

What we are for

Protection should not be a luxury tier.

The economics of this industry are backwards. The networks most likely to be attacked — small communities, new servers, anyone who annoyed the wrong person — are the ones least able to pay enterprise rates for it.

So we made one decision early and have not moved from it: the mitigation itself is identical on every plan. A $25 network sits behind the same filtering stack, the same edge capacity and the same engineers as a $250 one. Higher tiers buy scale, headroom and response times. They do not buy a better shield, because there is only one shield.

See how the plans actually differ

One shield, every plan

Mitigation is never the upsell. It is the product.

Priced on capacity

Never on player counts, and never on what your store earns.

Answered by engineers

The emergency line reaches someone who can change routing.

Honest about limits

We will tell you when a cheaper plan is the right answer.

Our story

From one bad weekend to 31 points of presence.

We have never taken outside investment, which is why the network grew in the order it did — capacity first, features second, marketing somewhere well after that.

  1. 2019

    A server goes down for eleven hours

    Two of us were running a mid-sized community. A sustained UDP flood took it offline through the busiest weekend of the year, and the host's answer was to null-route us until it stopped.

  2. 2020

    The first proxy, for our own network

    A single filtered box in Amsterdam, forwarding traffic to an origin nobody could see. It was held together with scripts, and it worked. Friends started asking to be put behind it.

  3. 2022

    Anycast, and a real company

    WipZen SAS was registered in Hyères. We moved from forwarding boxes to a proper anycast edge, so players reached the nearest location instead of all reaching the Netherlands.

  4. 2024

    Voice chat, treated as a first-class protocol

    Simple Voice Chat and Plasmo Voice were breaking behind every proxy on the market, ours included. We stopped filtering their UDP as unknown traffic and started routing it deliberately.

  5. 2026

    4,200 networks and 64 Tbps

    Thirty-one points of presence across five continents, with Frankfurt and São Paulo the most recent. Still no investors, and still the same rule about the shield.

4,200

Networks protected

64 Tbps

Edge capacity

31

Points of presence

18

People, all told

The network

How the edge is actually built.

Every location below runs the same filtering stack on our own hardware. We do not resell someone else's scrubbing centre, which is why we can tell you exactly where your traffic was dropped.

  • Amsterdam AMS1
  • Frankfurt FRA2
  • London LHR1
  • Paris CDG1
  • Warsaw WAW1
  • Stockholm ARN1
  • Ashburn IAD1
  • Dallas DFW1
  • Los Angeles LAX1
  • Toronto YYZ1
  • São Paulo GRU1
  • Singapore SIN1
  • Tokyo NRT1
  • Sydney SYD1
  • Johannesburg JNB1

Our own hardware

Filtering runs on machines we specified and own, in facilities we hold contracts with. Nothing about your traffic is subcontracted.

Multi-homed transit

Every site takes transit from at least three carriers plus local peering, so losing one upstream is a routing event rather than an outage.

Capacity kept ahead

We hold headroom well above the largest attack we have absorbed. The point of the number is that you never get near it.

How we work

Four things we will not trade away.

Say what happened

When we cause an outage we publish what broke, how long it lasted and what changed afterwards. Status pages that only ever show green are marketing, not monitoring.

Keep the minimum

Traffic metadata is what lets us filter attacks, so we keep it briefly and narrowly. We do not read the contents of your players' sessions, and we do not sell anything about them.

No revenue share, ever

Several competitors price against your store income. We think charging more because your community succeeded is a bad deal dressed up as a partnership.

Sell you the smaller plan

If your numbers fit Pro, sales will tell you they fit Pro. Upgrading during an attack takes about a minute, so there is no reason to overbuy in advance.

The team

Eighteen people, mostly on call.

Network engineers, a support team that has run game servers themselves, and nobody whose job title contains the word "growth".

R. Mägi

Co-founder, network

T. Kask

Co-founder, platform

J. Vaher

Head of mitigation

A. Ojala

Support lead

Find us

Where WipZen actually is.

The network runs from thirty-one places. The people run from one — Tashkent, where support and engineering sit.

WipZen 50B Ziyovuddin Bobokhonov Street
Tashkent 100069
Uzbekistan

We are hiring network engineers.

Remote across EU time zones, on-call rotation included and honestly described. If you have run infrastructure that people shout at you about, we would like to talk.