Doha IX Route Servers: PeeringDB fix list
AS211942 · peeringdb.com/net/25790
2 things to fix in Doha IX Route Servers'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 Doha IX Route Servers'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 Doha IX Route Servers's PeeringDB record. Add one entry per connection with these values.
-
3 connections, so 3 entries:
IPv4 194.42.47.124 IPv6 2001:7f8:162:0:3:3be6:a:1 Speed 20000 Mbps (20G) RS peer No IPv4 194.42.47.125 IPv6 2001:7f8:162:0:3:3be6:a:2 Speed 20000 Mbps (20G) RS peer No IPv4 194.42.47.126 IPv6 2001:7f8:162:0:3:3be6:b:dead Speed 20000 Mbps (20G) RS peer No
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 Address belongs to another network in PeeringDB 194.42.47.124 is AS215791 Doha IX MAPS Route Servers 194.42.47.124 Address belongs to another network in PeeringDB 194.42.47.125 is AS215791 Doha IX MAPS Route Servers 194.42.47.125 Address belongs to another network in PeeringDB 2001:7f8:162:0:3:3be6:a:1 is AS215791 Doha IX MAPS Route Servers 2001:7f8:162:0:3:3be6:a:1 Address belongs to another network in PeeringDB 2001:7f8:162:0:3:3be6:a:2 is AS215791 Doha IX MAPS Route Servers 2001:7f8:162:0:3:3be6:a:2 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/211942/: 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.