BelCloud Ltd.: PeeringDB fix list
AS44901 · peeringdb.com/net/11319
7 things to fix in BelCloud Ltd.'s PeeringDB record, from what its exchanges publish: 3 to add, 4 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on BelCloud Ltd.'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 (3)
On the exchange's own member list, but not in BelCloud Ltd.'s PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members list
IPv4 185.0.20.208 IPv6 2001:7f8:7f::208 Speed 1250 Mbps (1.25G) RS peer Yes
Correct these entries (4)
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 193.169.198.192 193.169.198.192 193.169.199.102 IPv6 address missing from PeeringDB 2001:7f8:58::af65:0:1 2001:7f8:58::af65:0:1 2001:7f8:58::af65:0:2 - Add an entry: IPv4 193.169.199.102, IPv6 2001:7f8:58::af65:0:2.
-
Problem PeeringDB has The export has Port speed differs 20G 100G - In the entry with IPv4 80.81.196.128: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G + 2 × 10G 10G - In the entry with IPv4 178.18.224.10: set Speed to 10000 (10G) (now 100000).
- In the entry with IPv4 178.18.236.62: set Speed to 10000 (10G) (now 100000).
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 2 × 10G 10G 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/44901/: 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.