SYSTEMTELECOM: PeeringDB fix list
AS50776 · peeringdb.com/net/20841
One thing to fix in SYSTEMTELECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on SYSTEMTELECOM'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a03:5f80:4::226:244 Port speed differs 5G 20G - In the entry with IPv4 178.18.226.244: set IPv6 to 2a03:5f80:4::226:244 (now empty); set Speed to 20000 (20G) (now 5000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/50776/: 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.