Linode AS63949: PeeringDB fix list

Correct these entries (6)

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. DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214

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

   • In the entry with IPv4 185.1.171.248: set Speed to 300000 (300G) (now 10000).
2. DE-CIX Hamburg Hamburg, Germany · PeeringDB 74

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

   • In the entry with IPv4 185.1.210.222: set Speed to 300000 (300G) (now 10000).
3. DE-CIX Munich Munich, Germany · PeeringDB 248

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

   • In the entry with IPv4 185.1.208.228: set Speed to 300000 (300G) (now 10000).
4. DE-CIX New York New York, United States · PeeringDB 804

   Problem	PeeringDB has	The export has
   Port speed differs	50G	100G

   • In the entry with IPv4 206.82.104.96: set Speed to 100000 (100G) (now 50000).
5. LINX LON1 London, United Kingdom · PeeringDB 18

   Problem	PeeringDB has	The export has
   Port speed differs	100G	200G

   • In the entry with IPv4 195.66.225.73: set Speed to 200000 (200G) (now 100000).
6. SGIX Singapore, Singapore · PeeringDB 429

   Problem	PeeringDB has	The export has
   Port speed differs	100G	200G

   • In the entry with IPv4 103.16.102.249: set Speed to 200000 (200G) (now 100000).