ixreport

Uniontel

AS48293 · iFlat

Uniontel LCC

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

Tools: Where can I peer with Uniontel? · Where should Uniontel peer next? · Compare Uniontel with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Uniontel'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 Uniontel's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.227.140
    IPv6–
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

In the last 30 days Uniontel joined 1 exchange and left 0. Growing networks

Joined

Map

Where Uniontel'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 420G across 7 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.99 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.126 2a0d:e180::60:126 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.140 100G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.209.135
195.208.210.142
2001:7f8:20:101::209:135
2001:7f8:20:101::210:142
2 × 40G Yes Both
Russia PITER-IX Moscow Moscow, Russia 185.0.12.50 2001:7f8:eb::bca5:1 100G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.0.44.133 2001:7f8:e6::bca5:1 100G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.112.129 20G Yes PeeringDB

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

These exchanges have a switch in a facility where Uniontel lists itself in PeeringDB, but don't have Uniontel 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 Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (2)

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

Russia Moscow M9Moscow 7 of 9
Russia DataHouse MoscowMoscow 1 of 1

Recent changes Search them

  • Nov 18, 2026 [IXF] AS48293 Uniontel added to GNM-IX
  • Oct 15, 2026 [PDB] AS48293 Uniontel left PITER-IX Tallinn
  • Oct 15, 2026 [PDB] AS48293 Uniontel left PITER-IX Helsinki
  • Oct 15, 2026 [PDB] AS48293 Uniontel left PITER-IX Frankfurt