Feral Hosting
AS200052 · feral
Feral.io Ltd
Tools: Where can I peer with Feral Hosting? · Where should Feral Hosting peer next? · Compare Feral Hosting with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
9 things to fix in Feral Hosting's PeeringDB record, from what its exchanges publish: 1 to add, 8 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Feral Hosting'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 Feral Hosting'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.
Correct these entries (8)
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 IPv6 address missing from PeeringDB none 2001:7f8:1:0:a500:20:52:1 - In the entry with IPv4 80.249.211.10: set IPv6 to 2001:7f8:1:0:a500:20:52:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:12a::5 - In the entry with IPv4 185.1.240.5: set IPv6 to 2001:7f8:12a::5 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a03:5f80:4::224:69 2a03:5f80:4:2::236:84 Port speed differs 2 × 10G 10G - In the entry with IPv4 178.18.224.69: set IPv6 to 2a03:5f80:4::224:69 (now empty).
- In the entry with IPv4 178.18.236.84: set IPv6 to 2a03:5f80:4:2::236:84 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4::3:d74:1 Port speed differs 10G 100G - In the entry with IPv4 195.66.226.194: set IPv6 to 2001:7f8:4::3:d74:1 (now empty); set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:1:0:3:d74:1 - In the entry with IPv4 195.66.238.194: set IPv6 to 2001:7f8:4:1:0:3:d74:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:17::3:d74:1 - In the entry with IPv4 5.57.81.90: set IPv6 to 2001:7f8:17::3:d74:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:13::a520:52:1 - In the entry with IPv4 193.239.117.86: set IPv6 to 2001:7f8:13::a520:52:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:b7::a520:52:1 - In the entry with IPv4 185.1.222.43: set IPv6 to 2001:7f8:b7::a520:52:1 (now empty).
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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 12 |
| Nov 18, 2026 | 12 |
| Nov 17, 2026 | 12 |
| Nov 16, 2026 | 12 |
| Nov 15, 2026 | 12 |
| Nov 14, 2026 | 12 |
| Nov 13, 2026 | 12 |
| Nov 12, 2026 | 12 |
| Nov 11, 2026 | 12 |
| Nov 10, 2026 | 12 |
| Nov 9, 2026 | 12 |
| Nov 8, 2026 | 11 |
| Nov 7, 2026 | 11 |
| Nov 6, 2026 | 11 |
| Nov 5, 2026 | 11 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 11 |
| Oct 24, 2026 | 11 |
| Oct 23, 2026 | 11 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 12 |
| Oct 19, 2026 | 12 |
| Oct 18, 2026 | 12 |
| Oct 17, 2026 | 12 |
| Oct 16, 2026 | 12 |
| Oct 15, 2026 | 12 |
| Oct 14, 2026 | 12 |
| Oct 13, 2026 | 12 |
| Oct 12, 2026 | 12 |
| Oct 11, 2026 | 12 |
| Oct 10, 2026 | 12 |
| Oct 9, 2026 | 12 |
| Oct 8, 2026 | 12 |
| Oct 7, 2026 | 12 |
| Oct 6, 2026 | 12 |
| Oct 5, 2026 | 12 |
| Oct 4, 2026 | 12 |
| Oct 3, 2026 | 12 |
Map
Where Feral Hosting'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.
| AMS-IX Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| BBIX Amsterdam Amsterdam, Netherlands | 10G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | Not in PeeringDB | ||
| ERA-IX Amsterdam Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| Global-IX Amsterdam, Netherlands | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 10G | Both IPv6 not in PeeringDBSpeed differs | |
| GNM-IX UA Kiev, Ukraine | 10G | PeeringDB | |
| LINX LON1 London, United Kingdom | 10G | Both IPv6 not in PeeringDBSpeed differs | |
| LINX LON2 London, United Kingdom | 10G | Both IPv6 not in PeeringDB | |
| LONAP London, United Kingdom | 40G | Both IPv6 not in PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| Speed-IX Dronten, Netherlands | 10G | Both IPv6 not in PeeringDB |
These exchanges have a switch in a facility where Feral Hosting lists itself in PeeringDB, but don't have Feral Hosting 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.
| FogIXPAvers, Switzerland | 532 | |
| Frys-IXFryslân, Netherlands | 338 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| NetIXSofia, Bulgaria | 204 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| Kent Internet Exchange PointKent, United Kingdom | 102 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Balcan-IXBucharest, Romania | 29 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| NL-ix 2Amsterdam, Netherlands | 19 | |
| RegPEXAnkara, Türkiye | 19 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 |
Facilities (3)
The buildings Feral Hosting lists in PeeringDB, and how many of the exchanges in each it's on.
| NIKHEF AmsterdamAmsterdam | 6 of 28 | |
| Telehouse - London (Docklands North)London | 5 of 11 | |
| Digital Realty AMS3/5/7/8/10 - AmsterdamAmsterdam | 3 of 4 |