FogNet - iFog GmbH: PeeringDB fix list
AS34927 · peeringdb.com/net/20164
13 things to fix in FogNet - iFog GmbH's PeeringDB record, from what its exchanges publish: 2 to add, 10 to correct, 1 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.
Make the changes on FogNet - iFog 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 (2)
On the exchange's own member list, but not in FogNet - iFog GmbH'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.
-
UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list2 connections, so 2 entries:
IPv4 192.34.27.8 IPv6 – Speed Not published RS peer Not published IPv4 – IPv6 2602:ffb1:200:0:192:34:27:8 Speed Not published RS peer Not published 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 (10)
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 1G 10G - In the entry with IPv4 185.1.170.232: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 500M 10G - In the entry with IPv4 80.81.196.156: set Speed to 10000 (10G) (now 500).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.210.200: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.131.46: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 2 × 100M 10G + 1G - In the entry with IPv4 185.1.192.103: set Speed to 1000 (1G) (now 100).
- In the entry with IPv4 185.1.192.235: set Speed to 10000 (10G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.208.208: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 10G 40G - In the entry with IPv4 149.112.75.22: set Speed to 40000 (40G) (now 10000).
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 Port speed differs 6 × 10G 4 × 10G + 2 × 1G - In the entry with IPv4 185.1.147.14: set Speed to 1000 (1G) (now 10000).
- In the entry with IPv4 185.1.147.162: set Speed to 1000 (1G) (now 10000).
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 Port speed differs 2G 4G - In the entry with IPv4 206.55.196.68: set Speed to 4000 (4G) (now 2000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 206.197.187.106: set Speed to 10000 (10G) (now 1000).
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.255.13 IPv6 2001:7f8:12f::13 Speed 10000 Mbps (10G)
From ixreport.com/net/34927/: 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.