ixreport

UpiterTelecom

AS208954

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with UpiterTelecom? · Where should UpiterTelecom peer next? · Compare UpiterTelecom 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 UpiterTelecom's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on UpiterTelecom'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:234
    Port speed differs10G20G
    • In the entry with IPv4 178.18.225.234: set IPv6 to 2a03:5f80:4::225:234 (now empty); set Speed to 20000 (20G) (now 10000).

    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

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, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where UpiterTelecom'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 across 4 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.137.147 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.234 10G Yes Both IPv6 not in PeeringDBSpeed differs
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.17 10G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.112.153 10G Yes PeeringDB

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

These exchanges have a switch in a facility where UpiterTelecom lists itself in PeeringDB, but don't have UpiterTelecom 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 MoscowMoscow, Russia 243 Tsvetochnaya Data Center
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Tsvetochnaya Data Center
Russia CLOUD-IX MSKMoscow, Russia 52 Tsvetochnaya Data Center
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Tsvetochnaya Data Center
Russia PIRIXSt.Petersburg, Russia 6 Tsvetochnaya Data Center
Facilities (2)

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

Russia Tsvetochnaya Data CenterSt. Petersburg 3 of 8
Russia COD BM-18St.Petersburg No exchange