Docker
AS21030 · cdnnow!
Docker LTD
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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.225.134 178.18.227.10 178.18.233.25 178.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 PeeringDB none 2a03: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.
-
Only one outside network
IPv4 185.1.118.23 IPv6 – Speed Not published
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 22 |
| Nov 18, 2026 | 22 |
| Nov 17, 2026 | 22 |
| Nov 16, 2026 | 22 |
| Nov 15, 2026 | 22 |
| Nov 14, 2026 | 22 |
| Nov 13, 2026 | 22 |
| Nov 12, 2026 | 22 |
| Nov 11, 2026 | 22 |
| Nov 10, 2026 | 22 |
| Nov 9, 2026 | 22 |
| Nov 8, 2026 | 21 |
| Nov 7, 2026 | 21 |
| Nov 6, 2026 | 22 |
| Nov 5, 2026 | 22 |
| Nov 4, 2026 | 22 |
| Nov 3, 2026 | 22 |
| Nov 2, 2026 | 22 |
| Nov 1, 2026 | 22 |
| Oct 31, 2026 | 22 |
| Oct 30, 2026 | 22 |
| Oct 29, 2026 | 22 |
| Oct 28, 2026 | 22 |
| Oct 27, 2026 | 22 |
| Oct 26, 2026 | 22 |
| Oct 25, 2026 | 22 |
| Oct 24, 2026 | 22 |
| Oct 23, 2026 | 22 |
| Oct 22, 2026 | 22 |
| Oct 21, 2026 | 22 |
| Oct 20, 2026 | 22 |
| Oct 19, 2026 | 22 |
| Oct 18, 2026 | 22 |
| Oct 17, 2026 | 22 |
| Oct 16, 2026 | 22 |
| Oct 15, 2026 | 22 |
| Oct 14, 2026 | 22 |
| Oct 13, 2026 | 22 |
| Oct 12, 2026 | 22 |
| Oct 11, 2026 | 22 |
| Oct 10, 2026 | 22 |
| Oct 9, 2026 | 22 |
| Oct 8, 2026 | 22 |
| Oct 7, 2026 | 22 |
| Oct 6, 2026 | 22 |
| Oct 5, 2026 | 22 |
| Oct 4, 2026 | 22 |
| Oct 3, 2026 | 22 |
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.
| BAIKAL-IX Irkutsk, Russia | PeeringDB | ||
| CLOUD-IX MSK Moscow, Russia | PeeringDB | ||
| CLOUD-IX SPB St. Petersburg, Russia | PeeringDB | ||
| Crimea-IX Simferopol, Russia | PeeringDB | ||
| DV-IXghost Chita, Russia | PeeringDB | ||
| Global-IX Amsterdam, Netherlands | PeeringDB | ||
| GNM-IX Amsterdam, Netherlands | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | ||
| KG-IX Bishkek Bishkek, Kyrgyzstan | Both | ||
| M-IX Simferopol, Russia | PeeringDB | ||
| MSK-IX Ekaterinburg Ekaterinburg, Russia | Both | ||
| MSK-IX Moscow Moscow, Russia | Both | ||
| MSK-IX Novosibirsk Novosibirsk, Russia | Both | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | Both | ||
| PITER-IX Frankfurt Frankfurt, Germany | PeeringDB | ||
| PITER-IX Helsinki Helsinki, Finland | PeeringDB | ||
| PITER-IX Moscow Moscow, Russia | PeeringDB | ||
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | PeeringDB | ||
| SFO-IX Barnaul, Novosibirsk, Russia | PeeringDB | ||
| SNS-IX Tashkent, Uzbekistan | Not in PeeringDB | ||
| SOLIX MTU1500 Stockholm, Sweden | Not in PeeringDB | ||
| ULN-IX Ulyanovsk, Russia | Both | ||
| W-IX Moscow, Russia | PeeringDB |
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.
| DE-CIX FrankfurtFrankfurt, Germany | 1,075 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| NetIXSofia, Bulgaria | 204 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Eurasia Peering IXMoscow, Russia | 136 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| 91-IXFrankfurt, Germany | 53 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (6)
The buildings Docker lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR7 - Frankfurt, GutleutstrasseFrankfurt | 0 of 12 | |
| Moscow M9Moscow | 8 of 9 | |
| Equinix FR8 - Frankfurt, WestFrankfurt | 0 of 6 | |
| Miran-1Санкт-Петербург | 4 of 5 | |
| Data-Center IMAQLIQSt. Petersburg | 4 of 4 | |
| Moscow TehnoGorodMoscow | 3 of 3 |