ixreport

Docker

AS21030 · cdnnow!

Docker LTD

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

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

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

PeeringDB fix list Printable page · CSV

4 things to fix in Docker's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct, 1 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.

Make the changes on Docker'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 (2)

On the exchange's own member list, but not in Docker's PeeringDB record. Add one entry per connection with these values.

  1. Uzbekistan SNS-IX Tashkent, Uzbekistan · PeeringDB 2836From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Sweden SOLIX MTU1500 Stockholm, Sweden · PeeringDB 128From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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.134 178.18.227.10 178.18.233.25178.18.224.118 178.18.224.174 178.18.225.134 178.18.225.205 178.18.227.10 178.18.233.25
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:118 2a03:5f80:4::224:174 2a03:5f80:4::225:134 2a03:5f80:4::225:205 2a03:5f80:4::227:10 2a03:5f80:4:1::233:25
    • In the entry with IPv4 178.18.225.134: set IPv6 to 2a03:5f80:4::225:134 (now empty).
    • In the entry with IPv4 178.18.227.10: set IPv6 to 2a03:5f80:4::227:10 (now empty).
    • In the entry with IPv4 178.18.233.25: set IPv6 to 2a03:5f80:4:1::233:25 (now empty).
    • Add an entry: IPv4 178.18.225.205, IPv6 2a03:5f80:4::225:205, speed 10000 (10G), RS peer yes.
    • Add an entry: IPv4 178.18.224.118, IPv6 2a03:5f80:4::224:118, speed 80000 (80G), RS peer yes.
    • Add an entry: IPv4 178.18.224.174, IPv6 2a03:5f80:4::224:174, speed 80000 (80G), 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 that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Russia DV-IXghost Chita, Russia · PeeringDB 2207

    Only one outside network

    IPv4185.1.118.23
    IPv6–
    SpeedNot published

Exchanges over time

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

Map

Where Docker'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

Russia BAIKAL-IX Irkutsk, Russia 185.1.76.44 Yes PeeringDB
Russia CLOUD-IX MSK Moscow, Russia 31.28.19.252 Yes PeeringDB
Russia CLOUD-IX SPB St. Petersburg, Russia 31.28.18.121 Yes PeeringDB
Russia Crimea-IX Simferopol, Russia 91.194.162.16 Yes PeeringDB
Russia DV-IXghost Chita, Russia 185.1.118.23 Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.72 Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.134
178.18.227.10
178.18.233.25
Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Kyrgyzstan KG-IX Bishkek Bishkek, Kyrgyzstan 185.1.110.97 Yes Both
Russia M-IX Simferopol, Russia 193.34.200.248 Yes PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.81 Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.25 Yes Both
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.80 Yes Both
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.113
194.226.102.113
Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.98 Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.175 Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.240 Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.47 Yes PeeringDB
Russia SFO-IX Barnaul, Novosibirsk, Russia 91.221.180.26 Yes PeeringDB
Uzbekistan SNS-IX Tashkent, Uzbekistan Not in PeeringDB
Sweden SOLIX MTU1500 Stockholm, Sweden Not in PeeringDB
Russia ULN-IX Ulyanovsk, Russia 185.1.19.32 Yes Both
Russia W-IX Moscow, Russia 193.106.112.175 Yes PeeringDB

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

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

Germany DE-CIX FrankfurtFrankfurt, Germany 1,075 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Germany KleyReXFrankfurt, Germany 471 Equinix FR7 - Frankfurt, Gutleutstrasse
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Bulgaria NetIXSofia, Bulgaria 204 Equinix FR7 - Frankfurt, Gutleutstrasse
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Germany MegaIX FrankfurtFrankfurt, Germany 114 Equinix FR7 - Frankfurt, Gutleutstrasse
Germany ERA-IX FrankfurtFrankfurt, Germany 85 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Germany Equinix FrankfurtFrankfurt, Germany 78 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Germany FogIXP FrankfurtFrankfurt, Germany 67 Equinix FR7 - Frankfurt, Gutleutstrasse
Germany 91-IXFrankfurt, Germany 53 Equinix FR7 - Frankfurt, Gutleutstrasse
Germany 1-DE FREEFrankfurt, Germany 27 Equinix FR7 - Frankfurt, Gutleutstrasse; Equinix FR8 - Frankfurt, West
Germany MAINPORT Peer-ExchangeFrankfurt am Main, Germany 14 Equinix FR7 - Frankfurt, Gutleutstrasse
Russia PIRIXSt.Petersburg, Russia 6 Miran-1
Facilities (6)

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

Germany Equinix FR7 - Frankfurt, GutleutstrasseFrankfurt 0 of 12
Russia Moscow M9Moscow 8 of 9
Germany Equinix FR8 - Frankfurt, WestFrankfurt 0 of 6
Russia Miran-1Санкт-Петербург 4 of 5
Russia Data-Center IMAQLIQSt. Petersburg 4 of 4
Russia Moscow TehnoGorodMoscow 3 of 3