ER-Telecom: PeeringDB fix list
AS9049 · peeringdb.com/net/17746
2 things to fix in ER-Telecom's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on ER-Telecom'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 (1)
On the exchange's own member list, but not in ER-Telecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.19.23 IPv6 2001:7f8:7d::2359:1 Speed Not published RS peer Not published
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.224.152 178.18.226.90 178.18.226.160 178.18.224.152 178.18.225.7 178.18.226.90 178.18.226.160 IPv6 address missing from PeeringDB 2a03:5f80:4::224:152 2a03:5f80:4::226:90 2a03:5f80:4::226:160 2a03:5f80:4::224:152 2a03:5f80:4::225:7 2a03:5f80:4::226:90 2a03:5f80:4::226:160 Port speed differs 3 × 100G 200G + 3 × 100G - Add an entry: IPv4 178.18.225.7, IPv6 2a03:5f80:4::225:7, speed 200000 (200G), 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/9049/: 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.