S-02

L2 / L3 TUNNELS

GRE, WireGuard, IP-in-IP and IPsec between your sites and our core.

If your hardware is not with us, reach the AS202831 core over a tunnel: GRE, IP-in-IP, IPsec or WireGuard. MTU and MSS clamping are agreed during setup, so nothing gets silently truncated inside GRE.

We run a BGP session inside the tunnel — that is how our downstreams announce their IPv6 prefixes through AS202831. The same large communities as on transit work there, blackholing included.

IPsec when traffic crosses untrusted networks. Transparent L2 over L3 for segments split between sites. Turn-up usually fits into one business day.

WHAT'S INCLUDED
  • GRE / IPIP with agreed MTU and MSS clamping
  • IPsec whenever traffic leaves the trusted path
  • Transparent L2 over L3 for split segments
  • Turn-up within one business day
PRICEON REQUEST
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
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.