ixreport

Neuronnexion: PeeringDB fix list

AS9036 · peeringdb.com/net/733

PeeringDB

5 things to fix in Neuronnexion's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Neuronnexion'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 Neuronnexion's PeeringDB record. Add one entry per connection with these values.

  1. France Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From 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 (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.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a500:9036:1
    • In the entry with IPv4 80.249.210.36: set IPv6 to 2001:7f8:1::a500:9036: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.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::234c:0:1
    Port speed differs100M100G
    • In the entry with IPv4 80.81.193.152: set IPv6 to 2001:7f8::234c:0:1 (now empty); set Speed to 100000 (100G) (now 100).
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::234c:1
    • In the entry with IPv4 195.66.226.87: set IPv6 to 2001:7f8:4::234c:1 (now empty).
  4. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4c::234c:1
    • In the entry with IPv4 188.93.170.68: set IPv6 to 2001:7f8:4c::234c: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.

From ixreport.com/net/9036/: 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.