ixreport

Atomdata-Center Xelent

AS199860 · Xelent

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

Tools: Where can I peer with Atomdata-Center Xelent? · Where should Atomdata-Center Xelent peer next? · Compare Atomdata-Center Xelent with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Atomdata-Center Xelent's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in Atomdata-Center Xelent's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where Atomdata-Center Xelent'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 40G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands Global-IX Amsterdam, Netherlands 109.239.136.220 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.146 2a03:5f80:4::224:146 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia Website list only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.53
194.226.102.53
2001:7f8:20:201::100:53
2001:7f8:20:202::102:53
2 × 10G Yes Both

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

These exchanges have a switch in a facility where Atomdata-Center Xelent lists itself in PeeringDB, but don't have Atomdata-Center Xelent 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.

Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Bolshaya Morskaya 18; Raduga-2; Miran-1
Russia PITER-IX MoscowMoscow, Russia 243 Bolshaya Morskaya 18; Raduga-2; Miran-1
Russia W-IXMoscow, Russia 66 Bolshaya Morskaya 18
Russia CLOUD-IX MSKMoscow, Russia 52 Bolshaya Morskaya 18; Raduga-2; Miran-1 and 1 more
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Bolshaya Morskaya 18; Raduga-2; Miran-1 and 1 more
Russia PIRIXSt.Petersburg, Russia 6 Bolshaya Morskaya 18; Raduga-2; Miran-1
Facilities (4)

The buildings Atomdata-Center Xelent lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Bolshaya Morskaya 18St. Petersburg 3 of 9
Russia Raduga-2St. Petersburg 3 of 8
Russia Miran-1Санкт-Петербург 0 of 5
Russia XelentSt. Petersburg 0 of 2