ixreport

ICEWOOD

AS201119 · Icewood

Icewood

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

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

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

PeeringDB fix list Printable page · CSV

6 things to fix in ICEWOOD's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 4 to check. As of 2026-11-19 12:40 UTC.

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

  1. Netherlands Speed-IX Dronten, Netherlands · PeeringDB 1842From its IX-F export
    IPv4185.1.222.220
    IPv62001:7f8:b7::a520:1119:1
    Speed10000 Mbps (10G)
    RS peerYes

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

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.227.0 178.18.227.1178.18.224.117 178.18.227.0 178.18.227.1
    IPv6 address missing from PeeringDB2a03:5f80:4::227:0 2a03:5f80:4::227:12a03:5f80:4::224:117 2a03:5f80:4::227:0 2a03:5f80:4::227:1
    • Add an entry: IPv4 178.18.224.117, IPv6 2a03:5f80:4::224:117, speed 10000 (10G), 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.

Check these entries (4)

In PeeringDB, but on none of the exchange's own lists. If ICEWOOD has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350Not on its IX-F export
    IPv4194.85.107.159
    IPv6–
    Speed10000 Mbps (10G)
    IPv4194.85.107.70
    IPv6–
    Speed10000 Mbps (10G)
  2. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223Not on its IX-F export
    IPv4193.232.87.159
    IPv6–
    Speed10000 Mbps (10G)
    IPv4193.232.87.69
    IPv6–
    Speed10000 Mbps (10G)
  3. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380Not on its IX-F export
    IPv4193.232.140.59
    IPv6–
    Speed10000 Mbps (10G)
  4. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.159
    IPv62001:7f8:20:201::100:159
    Speed10000 Mbps (10G)
    IPv4194.226.102.159
    IPv62001:7f8:20:202::102:159
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where ICEWOOD'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 310G across 19 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.85
31.28.19.87
2a00:13c0:3:1::1f1c:1355
2a00:13c0:3:1::1f1c:1357
2 × 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.178 2a0d:e180::60:178 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.58
109.239.136.68
2001:b28:3ff::3119:0:1
2001:b28:3ff::3119:0:2
2 × 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.0
178.18.227.1
2a03:5f80:4::227:0
2a03:5f80:4::227:1
2 × 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.70
194.85.107.159
2 × 10G Yes PeeringDB only
Russia MSK-IX Moscow Moscow, Russia 195.208.209.159
195.208.210.159
2001:7f8:20:101::209:159
2001:7f8:20:101::210:159
2 × 10G Yes Both
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.69
193.232.87.159
2 × 10G Yes PeeringDB only
Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia 193.232.140.59 10G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.159
194.226.102.159
2001:7f8:20:201::100:159
2001:7f8:20:202::102:159
2 × 10G Yes PeeringDB only
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.164 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.226 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.17
185.0.13.67
2001:7f8:eb::3:119f:1
2001:7f8:eb::3:119f:2
2 × 10G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.101
193.27.39.116
2 × 10G Yes PeeringDB
Russia PITER-IX Rostov Rostov, Russia 193.27.38.46 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.19
185.1.153.41
2001:7f8:e6::3:119f:1
2001:7f8:e6::3:119f:2
2 × 10G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.59
37.9.49.75
2 × 10G Yes PeeringDB
Russia Sea-IX Krasnodar, Russia 91.240.225.196 10G Yes PeeringDB
Netherlands Speed-IX Dronten, Netherlands 185.1.222.220 2001:7f8:b7::a520:1119:1 10G Yes Not in PeeringDB
Russia W-IX Moscow, Russia 193.106.113.15
193.106.113.58
2a00:1b30::a15
2a00:1b30::a58
2 × 10G Yes PeeringDB

ICEWOOD lists no facilities in PeeringDB.