BelCloud Ltd.
AS44901
Tools: Where can I peer with BelCloud Ltd.? · Where should BelCloud Ltd. peer next? · Compare BelCloud Ltd. with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in BelCloud Ltd.'s PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct. As of 2026-11-19 12:40 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 (4)
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.
-
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 10G 100G - In the entry with IPv4 95.133.136.23: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 17 |
| Nov 18, 2026 | 17 |
| Nov 17, 2026 | 17 |
| Nov 16, 2026 | 17 |
| Nov 15, 2026 | 17 |
| Nov 14, 2026 | 17 |
| Nov 13, 2026 | 17 |
| Nov 12, 2026 | 17 |
| Nov 11, 2026 | 17 |
| Nov 10, 2026 | 17 |
| Nov 9, 2026 | 17 |
| Nov 8, 2026 | 18 |
| Nov 7, 2026 | 18 |
| Nov 6, 2026 | 18 |
| Nov 5, 2026 | 18 |
| Nov 4, 2026 | 18 |
| Nov 3, 2026 | 18 |
| Nov 2, 2026 | 18 |
| Nov 1, 2026 | 18 |
| Oct 31, 2026 | 18 |
| Oct 30, 2026 | 18 |
| Oct 29, 2026 | 18 |
| Oct 28, 2026 | 18 |
| Oct 27, 2026 | 18 |
| Oct 26, 2026 | 18 |
| Oct 25, 2026 | 17 |
| Oct 24, 2026 | 17 |
| Oct 23, 2026 | 17 |
| Oct 22, 2026 | 17 |
| Oct 21, 2026 | 17 |
| Oct 20, 2026 | 17 |
| Oct 19, 2026 | 17 |
| Oct 18, 2026 | 17 |
| Oct 17, 2026 | 17 |
| Oct 16, 2026 | 17 |
| Oct 15, 2026 | 17 |
| Oct 14, 2026 | 17 |
| Oct 13, 2026 | 17 |
| Oct 12, 2026 | 17 |
| Oct 11, 2026 | 17 |
| Oct 10, 2026 | 17 |
| Oct 9, 2026 | 17 |
| Oct 8, 2026 | 17 |
| Oct 7, 2026 | 17 |
| Oct 6, 2026 | 17 |
| Oct 5, 2026 | 17 |
| Oct 4, 2026 | 17 |
| Oct 3, 2026 | 17 |
In the last 30 days BelCloud Ltd. joined 0 exchanges and left 1. Growing networks
Left
- InterLAN-IX Bucharest Nov 9, 2026
Map
Where BelCloud Ltd.'s exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | Not in PeeringDB | ||
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| BIX Budapest, Hungary | Website list only | ||
| BIX.BG Sofia, Bulgaria | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 20G | Both Speed differs | |
| FogIXP Avers, Switzerland | 10G | Both | |
| Global-IX Amsterdam, Netherlands | 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 100G + 2 × 10G | Both Speed differs | |
| GNM-IX UA Kiev, Ukraine | 100G + 10G | PeeringDB | |
| GR-IX::Athens Athens, Greece | Website list only | ||
| GR-IX::Thessaloniki Thessaloniki, Greece | 1G | Both | |
| KleyReX Frankfurt, Germany | 10G | Both | |
| NetIX Sofia, Bulgaria | 40G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 1.25G | Not in PeeringDB | |
| RegPEX Ankara, Türkiye | 10G | Both Speed differs | |
| TurkIX Sofia Sofia, Bulgaria | 100G | Both | |
| VarnaIX Varna, Bulgaria | 1G | PeeringDB |
Facilities (1)
The buildings BelCloud Ltd. lists in PeeringDB, and how many of the exchanges in each it's on.
| S3 Company Ltd.Sofia | 3 of 3 |
Recent changes Search them
- Nov 9, 2026 [IXF] AS44901 BelCloud Ltd. left InterLAN-IX
- Nov 9, 2026 [PDB] AS44901 BelCloud Ltd. no longer in PeeringDB at InterLAN-IX (still on its IX-F list)