Azertelecom: PeeringDB fix list
AS196925 · peeringdb.com/net/6995
3 things to fix in Azertelecom's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Azertelecom'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 Azertelecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.18.225.190 IPv6 2a03:5f80:4::225:190 Speed 200000 Mbps (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.
Correct these entries (2)
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 200G 400G - In the entry with IPv4 80.81.194.196: set Speed to 400000 (400G) (now 200000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.208.208.11 195.208.208.11 195.208.210.11 IPv6 address missing from PeeringDB 2001:7f8:20:101::208:11 2001:7f8:20:101::208:11 2001:7f8:20:101::210:11 - Add an entry: IPv4 195.208.210.11, IPv6 2001:7f8:20:101::210:11, 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/196925/: 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.