ixreport

CJSC Digital Network

AS12695 · tech.ru

Digital Network LLC

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
8Using the route servers
1To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with CJSC Digital Network? · Where should CJSC Digital Network peer next? · Compare CJSC Digital Network with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in CJSC Digital Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on CJSC Digital Network's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G400G
    • In the entry with IPv4 80.81.193.176: set Speed to 400000 (400G) (now 10000).

Exchanges over time

02468Oct 3, 2026Nov 19, 20268
Show as a table
DateExchanges
Nov 19, 20268
Nov 18, 20268
Nov 17, 20268
Nov 16, 20268
Nov 15, 20268
Nov 14, 20268
Nov 13, 20268
Nov 12, 20268
Nov 11, 20268
Nov 10, 20268
Nov 9, 20268
Nov 8, 20268
Nov 7, 20268
Nov 6, 20268
Nov 5, 20268
Nov 4, 20268
Nov 3, 20268
Nov 2, 20268
Nov 1, 20268
Oct 31, 20268
Oct 30, 20268
Oct 29, 20268
Oct 28, 20268
Oct 27, 20268
Oct 26, 20268
Oct 25, 20268
Oct 24, 20268
Oct 23, 20268
Oct 22, 20268
Oct 21, 20268
Oct 20, 20268
Oct 19, 20268
Oct 18, 20268
Oct 17, 20268
Oct 16, 20268
Oct 15, 20268
Oct 14, 20268
Oct 13, 20268
Oct 12, 20268
Oct 11, 20268
Oct 10, 20268
Oct 9, 20268
Oct 8, 20268
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where CJSC Digital Network's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 143G across 8 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.212.185 2001:7f8:1::a501:2695:2 3G 286 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.176 2001:7f8::3197:0:1 10G 303 routes Both Speed differs
Russia Eurasia Peering IX Moscow, Russia 185.232.60.20 10G Yes PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.208.88 2001:7f8:20:101::208:88 40G Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.53 20G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.145 20G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.234 2001:7f8:eb::3197:1 20G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.177 2001:7f8:e6::3197:1 20G Yes PeeringDB

Exchanges in its buildings that it isn't on (5)

These exchanges have a switch in a facility where CJSC Digital Network lists itself in PeeringDB, but don't have CJSC Digital Network as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands GNM-IXAmsterdam, Netherlands 741 Moscow M9; StoreData; DataLine Moscow 1 and 1 more
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; StoreData; IXcellerate MOS1
Russia W-IXMoscow, Russia 66 Moscow M9; DataLine Moscow 1
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; StoreData; DataLine Moscow 1 and 1 more
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (6)

The buildings CJSC Digital Network lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 4 of 9
Russia IXcellerate MOS1Moscow 3 of 6
Russia DataLine Moscow 1Dolgoprudny 1 of 4
Russia StoreDataMoscow 1 of 4
Russia Tech.ru DC2Moscow No exchange
Russia Tech.ru DC4Moscow No exchange