DDoS operator · AS208355 · Sofia

DDoS attacks stop at AS208355.

We see every attack on your prefixes as it starts, filter it on our own network, and read it with you. People in our NOC, around the clock.

noise stays on top80/tcp443/tcp53/udp123/udpdelivered, one queue per service
Noise stays on top. Your traffic has a shape; it passes.
What we do

Three things, on one network.

  1. 01

    DDoS detection — YAM Watch

    Your routers already export sFlow. We read it and name every attack as it starts: vector, target, peak. Nothing to install.

  2. 02

    Filtering — On-demand · Always-on

    Attacks are filtered on our own network in Sofia, by shape rather than size. On demand, when you call for it, or always on.

  3. 03

    Our NOC, 24/7 — YAM Respond

    A person reads every attack with you, tells you what to change on your network, and writes it down.

Product

How it works

Connect once. The loop runs.

Connect
sFlow from your routers for detection. One BGP session and a link for filtering: a cross-connect at our site, or delivery to your data centre.
The loop
Detect, filter, read, report. What we learn from each attack re-cuts the sieve for the next one.
Honest status
Every status in your panel is backed by a counter. If we can't measure it, it says unknown, never green.

How it works

Who runs it

A small operator with its own network.

Network
AS208355, one site in Sofia, our own filtering hardware and software. IPv4 today.
People
Engineers in the NOC, around the clock. The first 30 days of filtering actions on your network are approved by a person.
Words
We say observed, not guaranteed. Numbers come with a date and a counter.

Start with a conversation, or with detection alone.

Tell us your ASN and your prefixes. We answer within one working day, in writing.

hello@yam.network · we answer in writing