EWE TEL: PeeringDB fix list

AS9145 · peeringdb.com/net/327

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

Make the changes on EWE TEL'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 (3)

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 Copenhagen Copenhagen, Denmark · PeeringDB 4043

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.0.4.5: set Speed to 100000 (100G) (now 1000).
DE-CIX Helsinki Helsinki, Finland · PeeringDB 4044

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.0.5.7: set Speed to 100000 (100G) (now 1000).
DE-CIX Oslo Oslo, Norway · PeeringDB 4041

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.0.7.5: set Speed to 100000 (100G) (now 1000).

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

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

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

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