ixreport

IP-Home

AS47914

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
1Facility in PeeringDB

Tools: Where can I peer with IP-Home? · Where should IP-Home peer next? · Compare IP-Home with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on IP-Home'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.224.196 178.18.225.56178.18.224.196 178.18.225.56 178.18.225.57
    IPv6 address missing from PeeringDB2a03:5f80:4::224:196 2a03:5f80:4::225:562a03:5f80:4::224:196 2a03:5f80:4::225:56 2a03:5f80:4::225:57
    Port speed differs2 × 20G20G
    • Add an entry: IPv4 178.18.225.57, IPv6 2a03:5f80:4::225:57, speed 20000 (20G), 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

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 IP-Home'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 220G across 4 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.49
185.232.61.5
2a0d:e180::60:49
2a0d:e180::61:5
2 × 40G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.112
109.239.136.217
2001:b28:3ff::136:112 2 × 20G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.196
178.18.225.56
2a03:5f80:4::224:196
2a03:5f80:4::225:56
2 × 20G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia PITER-IX Moscow Moscow, Russia 185.0.12.54
185.0.14.28
2001:7f8:eb::bb2a:1 2 × 30G Yes PeeringDB

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

These exchanges have a switch in a facility where IP-Home lists itself in PeeringDB, but don't have IP-Home 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
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 IP-Home lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 4 of 9