Domeneshop AS: PeeringDB fix list

Correct these entries (7)

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. Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 212.237.192.37: set Speed to 1000000 (1T) (now 10000).
2. Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 212.237.193.37: set Speed to 1000000 (1T) (now 10000).
3. Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 194.68.128.37: set Speed to 1000000 (1T) (now 10000).
4. Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 195.69.119.37: set Speed to 1000000 (1T) (now 10000).
5. Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 194.68.123.37: set Speed to 1000000 (1T) (now 10000).
6. Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1T

   • In the entry with IPv4 195.245.240.37: set Speed to 1000000 (1T) (now 10000).
7. STHIX - Stockholm Stockholm, Sweden · PeeringDB 172

   Problem	PeeringDB has	The export has
   Port speed differs	10G	1G

   • In the entry with IPv4 192.121.80.119: 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.