SIA Tet: PeeringDB fix list

AS12578 · peeringdb.com/net/4294

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

Make the changes on SIA Tet'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 (2)

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

DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list

IPv4 185.1.210.68

IPv6 2001:7f8:3d::3122:0:1

Speed 100000 Mbps (100G)

RS peer Yes
DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list

IPv4 185.1.208.56

IPv6 2001:7f8:44::3122:0:1

Speed 100000 Mbps (100G)

RS peer Yes

IPv4	185.1.210.68
IPv6	2001:7f8:3d::3122:0:1
Speed	100000 Mbps (100G)
RS peer	Yes

IPv4	185.1.208.56
IPv6	2001:7f8:44::3122:0:1
Speed	100000 Mbps (100G)
RS peer	Yes

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.

DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214

Problem PeeringDB has The export has

Port speed differs 10G 100G
- In the entry with IPv4 185.1.171.23: set Speed to 100000 (100G) (now 10000).
DE-CIX Hamburg Hamburg, Germany · PeeringDB 74

Problem PeeringDB has The export has

Address belongs to another network in PeeringDB 185.1.210.68 is AS133731 Royal Network Technology 185.1.210.68

An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
DE-CIX Munich Munich, Germany · PeeringDB 248

Problem PeeringDB has The export has

Address belongs to another network in PeeringDB 185.1.208.56 is AS133731 Royal Network Technology 185.1.208.56

An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846

Problem PeeringDB has The export has

Port speed differs 20G 40T
- In the entry with IPv4 194.68.128.177: set Speed to 40000000 (40T) (now 20000).
Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847

Problem PeeringDB has The export has

Port speed differs 20G 40T
- In the entry with IPv4 195.69.119.177: set Speed to 40000000 (40T) (now 20000).
Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70

Problem PeeringDB has The export has

Port speed differs 20G 40T
- In the entry with IPv4 194.68.123.177: set Speed to 40000000 (40T) (now 20000).
Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845

Problem PeeringDB has The export has

Port speed differs 20G 40T
- In the entry with IPv4 195.245.240.177: set Speed to 40000000 (40T) (now 20000).

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

Problem	PeeringDB has	The export has
Address belongs to another network in PeeringDB	185.1.210.68 is AS133731 Royal Network Technology	185.1.210.68

Problem	PeeringDB has	The export has
Address belongs to another network in PeeringDB	185.1.208.56 is AS133731 Royal Network Technology	185.1.208.56

Problem	PeeringDB has	The export has
Port speed differs	20G	40T

Problem	PeeringDB has	The export has
Port speed differs	20G	40T

Problem	PeeringDB has	The export has
Port speed differs	20G	40T

Problem	PeeringDB has	The export has
Port speed differs	20G	40T

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