S-05

RTBH / L3-L4 MITIGATION

Blackhole triggered by your own announcement. No phone calls.

RTBH lets you survive a volumetric attack without losing the whole link: announce the target address with a blackhole community and traffic to it is dropped before it reaches your port.

202831:666:0 drops here, at every upstream and at exchange points. 202831:911:0 drops at transits only, so the address stays reachable here and over IXes. For IPv6 we accept prefixes down to /128 within your ROAs.

No calls and no tickets — the blackhole is triggered by your own announcement. A post-incident review is mandatory.

WHAT'S INCLUDED
  • 202831:666:0 — dropped here, at every upstream and at IXes
  • Up to /128 within your ROA prefixes (IPv6)
  • Isolate the target, not the whole uplink
  • A written post-incident review is mandatory
PRICEINCLUDED WITH TRANSIT
REQUEST A PORT
03 / PEERING

OPEN POLICY

We peer with anyone holding an ASN and an interest in fewer hops. No NDA required for that.

REQUIREMENTS
  1. 01A registered ASN with correct IRR objects (RADb / RIPE)
  2. 02Signed ROAs for every announced prefix
  3. 03A max-prefix limit agreed during turn-up
  4. 04A working NOC contact that answers
  5. 05No transit announcements through our session without prior agreement
EMAIL PEERING
BGP COMMUNITIES
COMMUNITYACTION
202831:666:0BLACKHOLE — drop here, at every upstream and IX (/48–/128 within your ROAs)
202831:911:0BLACKHOLE — transits only, stays reachable here and at IXes
202831:100:NPREPEND ×N (1–3) to transits
202831:101:NPREPEND ×N (1–3) to IXes and peers
202831:300:0DO NOT ANNOUNCE to transits (IXes and peers only)
202831:301:0DO NOT ANNOUNCE to IXes and peers (transits only)
202831:2:ASNINFO — set by us: route learned from customer ASN

Large communities only (RFC 8092): AS202831 is a 32-bit ASN, classic 202831:666 cannot exist. Transits are GlobalNet and HE; IXes are DATA-IX, Piter-IX and Cloudflare. By default customer routes go to GlobalNet and DATA-IX with a ×2 prepend. Honoured on customer IPv6 tunnel sessions.

WHAT RUNS THE CORE
ROUTING
BIRD 3.x on the MSK and FRA cores
FILTERING
prefix-list or origin + RPKI ROV, invalids dropped
AUTHENTICATION
MD5 on request, BFD where it earns its keep
PROTOCOL
MP-BGP, IPv4 and IPv6 in one session or separately
MONITORING
flow accounting and alerts on session state change
10 / FILTERS

WHAT WE REFUSE TO ACCEPT

The old site had a list of surnames here. We replaced it with a list of prefixes — more useful, and unlike politics it is actually enforced at the edge.

010.0.0.0/0 AND ::/0A default from a customer is not an announcement, it is an outage
02BOGON / RFC1918 / RFC6598Private space does not travel in the global table
03RPKI INVALIDDropped automatically, no discussion
04PREFIXES LONGER THAN /24 AND /48We will not pollute other people's tables
05ANNOUNCEMENTS WITH NO IRR OBJECTUpstreams filter on AS202831:AS-ALL — without a route object it goes nowhere past us
06A FULL VIEW INTO A /24 SESSIONmax-prefix is not decorative
11 / CONTACT

GET IN TOUCH

Three addresses and one messenger. There is no eight-item phone menu.

EMAIL
TECHNICAL SUPPORT (NOC)
support@as202831.network
PEERING AND INTERCONNECTS
peering@as202831.network
TELEGRAM

Abuse reports are handled in order. A substantiated complaint with logs gets an answer; a template blast without detail does not.

CONNECTION REQUEST

Send your AS number, the bandwidth you want and the site — that is enough for a first reply.

The button opens your mail client with a pre-filled message to peering@as202831.network. Nothing is sent in the background.