ixreport

OTS Network

AS47286 · OTS

OTS Ltd.

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on OTS 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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:119 2a03:5f80:4::226:120
    Port speed differs2 × 10G10G
    • In the entry with IPv4 178.18.226.119: set IPv6 to 2a03:5f80:4::226:119 (now empty).
    • In the entry with IPv4 178.18.226.120: set IPv6 to 2a03:5f80:4::226:120 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where OTS 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 40G across 2 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.119
178.18.226.120
2 × 10G Yes Both IPv6 not in PeeringDBSpeed differs
Russia PITER-IX Moscow Moscow, Russia 185.0.13.249
185.0.13.250
2 × 10G Yes PeeringDB

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

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

Russia MSK-IX MoscowMoscow, Russia 638 Moscow M9
Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (1)

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

Russia Moscow M9Moscow 2 of 9