GlobalXtreme: PeeringDB fix list
AS45701 · peeringdb.com/net/21944
6 things to fix in GlobalXtreme's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on GlobalXtreme'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 GlobalXtreme's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (5)
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 10G 2.5G - In the entry with IPv4 80.249.213.124: set Speed to 2500 (2.5G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 80.81.194.208: set Speed to 200000 (200G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 123.108.9.59: set Speed to 10000 (10G) (now 20000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 40G - In the entry with IPv4 119.11.184.109: set Speed to 40000 (40G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 195.66.231.26: set Speed to 1000 (1G) (now 10000).
From ixreport.com/net/45701/: 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.