Glecom: PeeringDB fix list

AS52177 · peeringdb.com/net/11399

PeeringDB

5 things to fix in Glecom's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Glecom'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 (3)

On the exchange's own member list, but not in Glecom's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.159
    IPv62001:7f8:d0::cbd1:1
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.165
    IPv62001:7f8:d:fb::165
    Speed2000000 Mbps (2T)
    RS peerYes
  3. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.165
    IPv62001:7f8:d:fc::165
    Speed2000000 Mbps (2T)
    RS peerYes

Correct these entries (2)

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. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs2G2T
    • In the entry with IPv4 194.68.128.165: set Speed to 2000000 (2T) (now 2000).
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs2G2T
    • In the entry with IPv4 194.68.123.165: set Speed to 2000000 (2T) (now 2000).

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