EMIND: PeeringDB fix list

AS49535 · peeringdb.com/net/21216

2 things to fix in EMIND's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on EMIND's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

MIX Bologna Bologna, Italy · PeeringDB 3730

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:7f8:101:13::19
- In the entry with IPv4 185.1.231.19: set IPv6 to 2001:7f8:101:13::19 (now empty).
MIX-IT Milan, Italy · PeeringDB 35

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:7f8:b:100:1d1:a5d4:9535:229
Port speed differs 2G 100G
- In the entry with IPv4 217.29.66.229: set IPv6 to 2001:7f8:b:100:1d1:a5d4:9535:229 (now empty); set Speed to 100000 (100G) (now 2000).

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:7f8:101:13::19

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:7f8:b:100:1d1:a5d4:9535:229
Port speed differs	2G	100G

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