TELECOM ARMENIA: PeeringDB fix list
AS12297 · peeringdb.com/net/25374
4 things to fix in TELECOM ARMENIA's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 21:35 UTC.
Make the changes on TELECOM ARMENIA'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 TELECOM ARMENIA's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.226.166 IPv6 2001:67c:29f0::1:2297:1 Speed Not published 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.
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.
-
Problem PeeringDB has The export has Port speed differs 20G 40G - In the entry with IPv4 185.1.30.50: set Speed to 40000 (40G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 30G 100G - In the entry with IPv4 80.81.196.122: set Speed to 100000 (100G) (now 30000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.224.20 178.18.224.20 178.18.236.73 IPv6 address missing from PeeringDB 2a03:5f80:4::224:20 2a03:5f80:4::224:20 2a03:5f80:4:2::236:73 Port speed differs 50G 2 × 100G - In the entry with IPv4 178.18.224.20: set Speed to 100000 (100G) (now 50000).
- Add an entry: IPv4 178.18.236.73, IPv6 2a03:5f80:4:2::236:73, 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/12297/: 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.