Acrion Cloud
AS213092 · Acrion International
Acrion International Limited
Tools: Where can I peer with Acrion Cloud? · Where should Acrion Cloud peer next? · Compare Acrion Cloud with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
5 things to fix in Acrion Cloud's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Acrion Cloud's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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 IPv4 address missing from PeeringDB none 185.1.170.243 IPv6 address in PeeringDB, not in the export 2001:7f8:9e:0:3:406:0:1 2001:7f8:9e:0:3:4064:0:1 2001:7f8:9e:0:3:406:0:1 Port speed differs 200G + 1G 200G - The entry with IPv4 –, IPv6 2001:7f8:9e:0:3:4064:0:1 isn't in the export: delete it if that connection is gone.
- In the entry with IPv6 2001:7f8:9e:0:3:406:0:1: set IPv4 to 185.1.170.243 (now empty).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.189.83.83 - In the entry with IPv6 2001:7f8:33::a121:3092:1: set IPv4 to 193.189.83.83 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.239.119.129 - In the entry with IPv6 2001:7f8:13::a521:3092:1: set IPv4 to 193.239.119.129 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 149.112.50.62 - In the entry with IPv6 2001:504:125:e1::62: set IPv4 to 149.112.50.62 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 192.34.27.32 - Add an entry: IPv4 192.34.27.32, IPv6 –.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 18 |
| Nov 18, 2026 | 18 |
| Nov 17, 2026 | 18 |
| Nov 16, 2026 | 18 |
| Nov 15, 2026 | 18 |
| Nov 14, 2026 | 17 |
| Nov 13, 2026 | 18 |
| Nov 12, 2026 | 18 |
| Nov 11, 2026 | 18 |
| Nov 10, 2026 | 18 |
| Nov 9, 2026 | 18 |
| 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 | 18 |
| Oct 24, 2026 | 18 |
| Oct 23, 2026 | 18 |
| Oct 22, 2026 | 18 |
| Oct 21, 2026 | 18 |
| Oct 20, 2026 | 18 |
| Oct 19, 2026 | 18 |
| Oct 18, 2026 | 18 |
| Oct 17, 2026 | 18 |
| Oct 16, 2026 | 18 |
| Oct 15, 2026 | 18 |
| Oct 14, 2026 | 18 |
| Oct 13, 2026 | 18 |
| Oct 12, 2026 | 18 |
| Oct 11, 2026 | 18 |
| Oct 10, 2026 | 18 |
| Oct 9, 2026 | 18 |
| Oct 8, 2026 | 18 |
| Oct 7, 2026 | 18 |
| Oct 6, 2026 | 18 |
| Oct 5, 2026 | 18 |
| Oct 4, 2026 | 18 |
| Oct 3, 2026 | 18 |
Map
Where Acrion Cloud'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.
| 4b42 Internet Exchange Point Zurich, Switzerland | Both | ||
| BFD-IX Bradford, United Kingdom | 100M | Both | |
| CHIX-CH Frauenfeld, Switzerland | 1G | PeeringDB | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 200G + 1G | Both IPv4 not in PeeringDBIPv6 not in exportSpeed differs | |
| FogIXP Avers, Switzerland | 1G | Both | |
| FREMIX Fremont, United States | 1G | Both | |
| ixFabric - Kansas Kansas, United States | 1G | PeeringDB | |
| ixFabric - KyivVIX Kyiv, Ukraine | 1G | PeeringDB | |
| ixFabric - MiamiVIX Miami, United States | 1G | PeeringDB | |
| IXP FI HEL Helsinki, Finland | 1G | PeeringDB | |
| IXP NL DRO Dronten, Netherlands | 1G | PeeringDB | |
| IXP US FRE Fremont, United States | 1G | PeeringDB | |
| KleyReX Frankfurt, Germany | 100M | Both IPv4 not in PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Both IPv4 not in PeeringDB | ||
| ONIX Toronto, Canada | 1G | Both IPv4 not in PeeringDB | |
| PyramIXVIX Cairo, Egypt | 100M | Both | |
| SBIX Dusseldorf Dusseldorf, Germany | 100M | PeeringDB | |
| UNM-Exch Canada-West Vancouver, Canada | 1G | Both IPv4 not in PeeringDB |
These exchanges have a switch in a facility where Acrion Cloud lists itself in PeeringDB, but don't have Acrion Cloud as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| LOCIX DUSSELDORFDusseldorf, Germany | 204 | |
| MegaIX DusseldorfDusseldorf, Germany | 97 | |
| N-IXNürnberg, Germany | 23 | |
| frankonIXNuremberg, Germany | 22 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 |
Facilities (4)
The buildings Acrion Cloud lists in PeeringDB, and how many of the exchanges in each it's on.
| WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf | 2 of 6 | |
| Hetzner Online NBG1 (Nuremberg)Nuremberg | 0 of 4 | |
| Hetzner Online FSN1 (Falkenstein)Falkenstein | No exchange | |
| VeloxServ DC2 - WolverhamptonWolverhampton | No exchange |
Recent changes Search them
- Nov 15, 2026 [PDB] AS213092 Acrion Cloud now in PeeringDB at DE-CIX Dusseldorf
- Nov 15, 2026 [PDB] AS213092 Acrion Cloud added to SBIX Dusseldorf
- Nov 15, 2026 [PDB] AS213092 Acrion Cloud now in PeeringDB at PyramIX
- Nov 14, 2026 [PDB] AS213092 Acrion Cloud no longer in PeeringDB at DE-CIX Dusseldorf (still on its IX-F list and on its website's members list)
- Nov 14, 2026 [PDB] AS213092 Acrion Cloud left SBIX Dusseldorf
- Nov 14, 2026 [PDB] AS213092 Acrion Cloud no longer in PeeringDB at PyramIX (still on its IX-F list and on its website's members list)