BIG TELECOM: PeeringDB fix list
AS35810 · peeringdb.com/net/17506
One thing to fix in BIG TELECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on BIG TELECOM'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 IPv4 address missing from PeeringDB 178.18.225.123 178.18.225.123 178.18.226.181 IPv6 address missing from PeeringDB 2a03:5f80:4::225:123 2a03:5f80:4::225:123 2a03:5f80:4::226:181 Port speed differs 20G 100G - In the entry with IPv4 178.18.225.123: set Speed to 100000 (100G) (now 20000).
- Add an entry: IPv4 178.18.226.181, IPv6 2a03:5f80:4::226:181, speed 100000 (100G), RS peer yes.
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/35810/: 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.