S-04

COLOCATION MOSCOW

Units and 42U racks on our own platform in Moscow.

We host servers on our own platform in Moscow — from a single unit to a whole 42U rack. AS202831 is present at MMTS-9, so Russian carriers are reached over direct interconnects rather than a chain of resellers.

The hall has a dedicated cold aisle. Each rack gets two power feeds from different PDUs and different breakers, patch cords are labelled at both ends, and the rack diagram is updated the same day.

In-rack cross-connects and remote hands are a NOC ticket away. Hosted equipment can be connected to AS202831 transit together with IPv6 and RTBH.

WHAT'S INCLUDED
  • 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
PRICEFROM 1U
REQUEST A PORT
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
07 / FIELD NOTES

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
DO NOT
A rack assembled from whatever was in the room
Cabling done on a we-will-sort-it-later basis
DO NOT
Cabling done on a we-will-sort-it-later basis
Machine room: closed cabinets in rows, a dedicated cold aisle
DO
Machine room: closed cabinets in rows, a dedicated cold aisle
CABLING STANDARD
  1. R-01Every patch cord labelled at both ends, length cut to the run
  2. R-02Two power feeds per rack, separate PDUs, separate breakers
  3. R-03Fibre in organisers, bend radius respected, slack coiled in the tray
  4. R-04The rack diagram is updated the same day, not eventually
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.