ixreport

Team Host

AS202984 · TEAM-HOST

Chernyshov Aleksandr Aleksandrovich

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

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

Make the changes on Team Host'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
    IPv4 address missing from PeeringDB178.18.225.245178.18.225.245 178.18.225.246
    IPv6 address missing from PeeringDB2a03:5f80:4::225:2452a03:5f80:4::225:245 2a03:5f80:4::225:246
    • Add an entry: IPv4 178.18.225.246, IPv6 2a03:5f80:4::225:246, speed 200000 (200G), RS peer yes.

    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

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

Map

Where Team Host'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 100G, at the 1 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.215
185.232.60.216
2a0d:e180::60:215
2a0d:e180::60:216
Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.154 2001:b28:3ff::3:18e8:2 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.245 2a03:5f80:4::225:245 Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.208.176
195.208.210.59
195.208.210.149
2001:7f8:20:101::208:176
2001:7f8:20:101::210:149
Yes Both
Russia PITER-IX Moscow Moscow, Russia 185.0.13.57
185.0.13.60
Yes PeeringDB

Team Host lists no facilities in PeeringDB.