Openfactory GmbH: PeeringDB fix list
AS58299 · peeringdb.com/net/7194
14 things to fix in Openfactory GmbH's PeeringDB record, from what its exchanges publish: 10 to add, 4 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Openfactory GmbH'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 (10)
On the exchange's own member list, but not in Openfactory GmbH's PeeringDB record. Add one entry per connection with these values.
-
IPv4 151.158.193.1 IPv6 – Speed 1000 Mbps (1G) RS peer No -
2 connections, so 2 entries:
IPv4 185.1.147.130 IPv6 2001:7f8:ca:1::130 Speed 1000 Mbps (1G) RS peer Yes IPv4 185.1.147.18 IPv6 2001:7f8:ca:1::18 Speed 10000 Mbps (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.
-
IPv4 185.0.30.32 IPv6 2001:7f8:11c:1:0:5:8299:1 Speed 10000 Mbps (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.
-
IPv4 185.1.160.137 IPv6 2001:7f8:10f::e3bb:137 Speed 10000 Mbps (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.
-
IPv4 193.189.82.50 IPv6 2001:7f8:33::a105:8299:1 Speed 100 Mbps (100M) 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.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its IX-F export and website members list
IPv4 185.1.32.65 IPv6 2001:7f8:8f::a505:8299:1 Speed 10000 Mbps (10G) RS peer Yes -
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
IPv4 193.239.118.73 IPv6 2001:7f8:13::a505:8299:1 Speed Not published 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.
-
IPv4 193.201.148.145 IPv6 2001:7f8:117:2:0:5:8299:1 Speed 10000 Mbps (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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 91.206.52.130 IPv6 2001:7f8:24::82 Speed 10000 Mbps (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.
Correct these entries (4)
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 Port speed differs 2 × 1G 200G + 10G - In the entry with IPv4 185.1.170.236: set Speed to 10000 (10G) (now 1000).
- In the entry with IPv4 185.1.171.105: set Speed to 200000 (200G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 2G 10G - In the entry with IPv4 80.81.196.197: set Speed to 10000 (10G) (now 2000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.210.67: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.208.55: set Speed to 10000 (10G) (now 1000).
From ixreport.com/net/58299/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.