Samsung SDS: PeeringDB fix list

AS6619 · peeringdb.com/net/401

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

Make the changes on Samsung SDS'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.

LINX LON1 London, United Kingdom · PeeringDB 18

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:7f8:4::19db:1
Port speed differs 1G 10G
- In the entry with IPv4 195.66.225.191: set IPv6 to 2001:7f8:4::19db:1 (now empty); set Speed to 10000 (10G) (now 1000).
SGIX Singapore, Singapore · PeeringDB 429

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:de8:12:100::103:37
- In the entry with IPv4 103.16.103.37: set IPv6 to 2001:de8:12:100::103:37 (now empty).

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:7f8:4::19db:1
Port speed differs	1G	10G

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:de8:12:100::103:37

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