S-01

IP TRANSIT

1G and 10G ports, full view or default, IPv4 + IPv6.

Transit is sold as a BGP session off our core: a 1G or 10G port with full view, a partial table or just a default route. IPv4 and IPv6 run in one MP-BGP session or separately, whichever you prefer.

Upstream traffic leaves through GlobalNet (AS31500) in Moscow and aurologic (AS30823) in Frankfurt. The network is also on DATA-IX, Piter-IX Moscow and Piter-IX St. Petersburg and peers directly with Cloudflare and Hurricane Electric — all visible in the session table below.

Announcements are filtered on IRR and RPKI: invalids are dropped, route objects must exist in RADb or the RIPE DB. You steer your own routes with large communities for prepends, selective announcement and blackholing.

WHAT'S INCLUDED
  • 1000BASE-T / BX and 10GBASE-LR / SR
  • Full view, partial or default route — your call
  • BGP communities to steer your announcements
  • Trial connection before any contract
PRICEON REQUEST
REQUEST A PORT
01 / TELEMETRY

NETWORK

Registry data comes from RIPE, the session list comes off our own routers. None of it was invented by a marketing department, and nearly all of it is externally verifiable.

REGISTRY RECORD
AS NUMBER
AS202831
HOLDER
Packet Loss LTD
REGISTRY
RIPE NCC
AS BLOCK
202240-203263
PEERING POLICY
OPEN
ROUTING DAEMON
BIRD 3.2
IRR / RPKI
RADb / RIPE · ROA signed
LIVE QUERY
QUERYING RIPESTAT…
IPv4 PREFIXES
10
IPv6 PREFIXES
264

Pulled straight from stat.ripe.net when the page loads.

VERIFY ON RIPESTAT
BGP SESSIONS
ASORGANISATIONAFTYPE
AS31500Global Network Managementv4 · v6TRANSIT
AS30823aurologic GmbHv4 · v6TRANSIT
AS50952DATA-IXv4 · v6IX
AS49869Piter-IX Moscowv4 · v6IX
AS50817Piter-IX St. Petersburgv4 · v6IX
AS13335Cloudflarev4 · v6PEER
AS6939Hurricane Electricv4 · v6PEER
AS214745NET67X Networksv4 · v6DOWNSTREAM
AS219431MANEKOv4 · v6DOWNSTREAM
WE FEED THESE COLLECTORS
  • RouteViews · AS6447
  • Hurricane Electric · AS393338
  • bgp.tools · AS212232
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
04 / SITES

WHERE THE HARDWARE LIVES

Three points of presence. The network plugs into carrier-neutral hubs; the servers sit on platforms we run ourselves.

MSKRU

Moscow

FACILITY
Own platform · network present at MMTS-9
ROLE
CORE + COLOCATION
WAWPL

Warsaw

FACILITY
LIM Warszawa
ROLE
EU GATEWAY
FRADE

Frankfurt am Main

FACILITY
Tornado DC / aurologic
ROLE
TRANSIT + DDoS SCRUBBING
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.