Global Secure Layer: PeeringDB fix list

AS137409 · peeringdb.com/net/16620

PeeringDB

6 things to fix in Global Secure Layer's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-10-08 20:58 UTC.

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

  1. United States SIX Seattle (Jumbo) Seattle, United States · PeeringDB 1285From its IX-F export and website members list
    IPv4149.112.97.146
    IPv62001:504:16:1::2:18c1
    Speed100000 Mbps (100G)
    RS peerNot 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 (5)

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs100G400G
    • In the entry with IPv4 185.1.171.28: set Speed to 400000 (400G) (now 100000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs100G400G
    • In the entry with IPv4 185.1.210.227: set Speed to 400000 (400G) (now 100000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs100G400G
    • In the entry with IPv4 185.1.208.232: set Speed to 400000 (400G) (now 100000).
  4. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs100G40G
    • In the entry with IPv4 5.57.81.11: set Speed to 40000 (40G) (now 100000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  5. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    Port speed differs10G25G
    • In the entry with IPv4 206.41.105.90: set Speed to 25000 (25G) (now 10000).

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