ALARMADI Adrian Dobrogowski: PeeringDB fix list

AS201695 · peeringdb.com/net/19752

One thing to fix in ALARMADI Adrian Dobrogowski's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on ALARMADI Adrian Dobrogowski'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 (1)

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.

EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:7f8:5b::607
Port speed differs 10G 20G
- In the entry with IPv4 178.216.42.60: set IPv6 to 2001:7f8:5b::607 (now empty); set Speed to 20000 (20G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:7f8:5b::607
Port speed differs	10G	20G

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