IP TRANSIT
1G and 10G ports, full view or default, IPv4 + IPv6.
- 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
PACKETLOSSLTD — AS202831
Named after the one metric we keep at zero. Everything else — transit, peering, tunnels and racks — simply works.
202831
3
3
9
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.
- AS202831
- Packet Loss LTD
- RIPE NCC
- 202240-203263
- OPEN
- BIRD 3.2
- RADb / RIPE · ROA signed
| AS | ORGANISATION | AF | TYPE |
|---|---|---|---|
| AS31500 | Global Network Management | v4 · v6 | TRANSIT |
| AS30823 | aurologic GmbH | v4 · v6 | TRANSIT |
| AS50952 | DATA-IX | v4 · v6 | IX |
| AS49869 | Piter-IX Moscow | v4 · v6 | IX |
| AS50817 | Piter-IX St. Petersburg | v4 · v6 | IX |
| AS13335 | Cloudflare | v4 · v6 | PEER |
| AS6939 | Hurricane Electric | v4 · v6 | PEER |
| AS214745 | NET67X Networks | v4 · v6 | DOWNSTREAM |
| AS219431 | MANEKO | v4 · v6 | DOWNSTREAM |
- RouteViews · AS6447
- Hurricane Electric · AS393338
- bgp.tools · AS212232
WHAT WE SELL
Six items. None of them is called a next-generation cloud ecosystem.
L2 / L3 TUNNELS
GRE, WireGuard, IP-in-IP and IPsec between your sites and our core.
- 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
IPv6
Native dual-stack at every site, no NAT.
- A /64 per customer by default, wider on request
- Dual-stack from day one, not eventually
- PTR delegation and RIPE DB objects
- No CGNAT sold as a feature
COLOCATION MOSCOW
Units and 42U racks on our own platform in Moscow.
- Network present at MMTS-9 — direct interconnects with RU carriers
- Servers live on a platform we run ourselves
- A properly built cold aisle
- In-rack cross-connects and remote hands on a NOC ticket
RTBH / L3-L4 MITIGATION
Blackhole triggered by your own announcement. No phone calls.
- 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
LIR / RIPE NCC
Our own RIPE NCC LIR — pl.packetloss (ORG-AL1127-RIPE). ASN registration and sponsorship of independent resources, handled directly, with no chain of resellers.
- ASN registration — €100 / year
- ASN transfer from another LIR — €100 / year
- PI IPv4 sponsorship — €150 / year
- PI IPv6 sponsorship — €150 / year
- Legacy resource sponsorship — €150 / year
- Service area: PL, DE, NL, CZ, FR, GB, CH, SE, FI, LT, LV, RU, UA, BY, MD, KZ
Send your AS number, the bandwidth you want and the site — that is enough for a first reply.
OPEN POLICY
We peer with anyone holding an ASN and an interest in fewer hops. No NDA required for that.
- A registered ASN with correct IRR objects (RADb / RIPE)
- Signed ROAs for every announced prefix
- A max-prefix limit agreed during turn-up
- A working NOC contact that answers
- No transit announcements through our session without prior agreement
| COMMUNITY | ACTION |
|---|---|
| 202831:666:0 | BLACKHOLE — drop here, at every upstream and IX (/48–/128 within your ROAs) |
| 202831:911:0 | BLACKHOLE — transits only, stays reachable here and at IXes |
| 202831:100:N | PREPEND ×N (1–3) to transits |
| 202831:101:N | PREPEND ×N (1–3) to IXes and peers |
| 202831:300:0 | DO NOT ANNOUNCE to transits (IXes and peers only) |
| 202831:301:0 | DO NOT ANNOUNCE to IXes and peers (transits only) |
| 202831:2:ASN | INFO — 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.
- BIRD 3.x on the MSK and FRA cores
- prefix-list or origin + RPKI ROV, invalids dropped
- MD5 on request, BFD where it earns its keep
- MP-BGP, IPv4 and IPv6 in one session or separately
- flow accounting and alerts on session state change
WHERE THE HARDWARE LIVES
Three points of presence. The network plugs into carrier-neutral hubs; the servers sit on platforms we run ourselves.
Moscow
Own platform · network present at MMTS-9
CORE + COLOCATION
Warsaw
LIM Warszawa
EU GATEWAY
Frankfurt am Main
Tornado DC / aurologic
TRANSIT + DDoS SCRUBBING
WHOSE NETWORK THIS IS
AS202831 was built for our own hosting projects. Below: who owns it and what runs on it.
CUSTOMERS
Third-party projects taking addressing and transit from us.
| PROJECT | SITE |
|---|---|
| kremen.host | FRA |
| endcore.cloud | MSK |
TWO APPROACHES TO CABLING
Above: what we sometimes find when a customer migrates to us. Below: what it looks like afterwards. The difference is usually measured in downtime, not money.
A rack assembled from whatever was in the room
Cabling done on a we-will-sort-it-later basis
Machine room: closed cabinets in rows, a dedicated cold aisle
- Every patch cord labelled at both ends, length cut to the run
- Two power feeds per rack, separate PDUs, separate breakers
- Fibre in organisers, bend radius respected, slack coiled in the tray
- The rack diagram is updated the same day, not eventually
WHO ANSWERS THE TICKET
A small team with no management layer in between. Your ticket lands directly with whoever can fix it.
LEAD NETWORK ENGINEER
Owns the BIRD configuration, plans addressing, and decides what to do with a flapping session at three in the morning.
L1 / L2 SUPPORT
Works the ticket queue, builds tunnels, and explains why MTU 1500 inside GRE is a bad idea.
PEERING COORDINATOR
Negotiates interconnects, maintains IRR objects, and keeps the ROAs from expiring.
CUSTOMER NOTES
This section is inherited from the previous version of the site. We kept the format and fixed the spelling.
- > vovan_hacker99
Took a rack for my project. BGP session was up two hours after the request, max-prefix negotiation included. Support answers to the point and without scripts. Ten out of ten.
- > sysadmin_oleg
Left my previous transit provider over price. Ping to Europe via Warsaw is 30 ms, and in a year monitoring has not caught a single outage. Invoices match the contract.
- > darkl0rd_kazan
Tried to run something on a VDS that should not have been run. The VM was pulled in four minutes with an explanation citing the contract. No complaints, still a customer.
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.
0.0.0.0/0 AND ::/0A default from a customer is not an announcement, it is an outage
BOGON / RFC1918 / RFC6598Private space does not travel in the global table
RPKI INVALIDDropped automatically, no discussion
PREFIXES LONGER THAN /24 AND /48We will not pollute other people's tables
ANNOUNCEMENTS WITH NO IRR OBJECTUpstreams filter on AS202831:AS-ALL — without a route object it goes nowhere past us
A FULL VIEW INTO A /24 SESSIONmax-prefix is not decorative
GET IN TOUCH
Three addresses and one messenger. There is no eight-item phone menu.
Send your AS number, the bandwidth you want and the site — that is enough for a first reply.