ixreport

Acrion Cloud

AS213092 · Acrion International

Acrion International Limited

18Exchanges, of which 3 VIX
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
18Using the route servers
5To fix in PeeringDB
4Facilities in PeeringDB

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.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.170.243
    IPv6 address in PeeringDB, not in the export2001:7f8:9e:0:3:406:0:1 2001:7f8:9e:0:3:4064:0:12001:7f8:9e:0:3:406:0:1
    Port speed differs200G + 1G200G
    • 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).
  2. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.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.

  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.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.

  4. Canada ONIX Toronto, Canada · PeeringDB 4059
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone149.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.

  5. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone192.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

05101520Oct 3, 2026Nov 19, 202618
Show as a table
DateExchanges
Nov 19, 202618
Nov 18, 202618
Nov 17, 202618
Nov 16, 202618
Nov 15, 202618
Nov 14, 202617
Nov 13, 202618
Nov 12, 202618
Nov 11, 202618
Nov 10, 202618
Nov 9, 202618
Nov 8, 202618
Nov 7, 202618
Nov 6, 202618
Nov 5, 202618
Nov 4, 202618
Nov 3, 202618
Nov 2, 202618
Nov 1, 202618
Oct 31, 202618
Oct 30, 202618
Oct 29, 202618
Oct 28, 202618
Oct 27, 202618
Oct 26, 202618
Oct 25, 202618
Oct 24, 202618
Oct 23, 202618
Oct 22, 202618
Oct 21, 202618
Oct 20, 202618
Oct 19, 202618
Oct 18, 202618
Oct 17, 202618
Oct 16, 202618
Oct 15, 202618
Oct 14, 202618
Oct 13, 202618
Oct 12, 202618
Oct 11, 202618
Oct 10, 202618
Oct 9, 202618
Oct 8, 202618
Oct 7, 202618
Oct 6, 202618
Oct 5, 202618
Oct 4, 202618
Oct 3, 202618

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.

Exchanges

Total port capacity 212.4G, at the 16 of 18 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:4064:1 Yes Both
United Kingdom BFD-IX Bradford, United Kingdom 2001:7f8:da:0:ffff::11 100M Yes Both
Switzerland CHIX-CH Frauenfeld, Switzerland 2001:7f8:cc:333:0:21:3092:1 1G Yes PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 2001:7f8:9e:0:3:406:0:1
2001:7f8:9e:0:3:4064:0:1
200G + 1G Down Both IPv4 not in PeeringDBIPv6 not in exportSpeed differs
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:21:3092:1 1G Yes Both
United States FREMIX Fremont, United States 2001:504:125:e0::36 1G Yes Both
United States ixFabric - Kansas Kansas, United States 2a0e:8f01:1000:32::138 1G Yes PeeringDB
Ukraine ixFabric - KyivVIX Kyiv, Ukraine 2a0e:8f01:1000:54::108 1G Yes PeeringDB
United States ixFabric - MiamiVIX Miami, United States 2a0e:8f01:1000:40::112 1G Yes PeeringDB
Finland IXP FI HEL Helsinki, Finland 2001:7f8:d0:4649:0:3:4064:1 1G Yes PeeringDB
Netherlands IXP NL DRO Dronten, Netherlands 2001:7f8:d0:4e4c:0:3:4064:1 1G Yes PeeringDB
United States IXP US FRE Fremont, United States 2001:7f8:d0:5553:0:3:4064:1 1G Yes PeeringDB
Germany KleyReX Frankfurt, Germany 2001:7f8:33::a121:3092:1 100M Yes Both IPv4 not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 2001:7f8:13::a521:3092:1 Yes Both IPv4 not in PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::62 1G Yes Both IPv4 not in PeeringDB
Egypt PyramIXVIX Cairo, Egypt 2a0e:46c4:102::213:92:1 100M Yes Both
Germany SBIX Dusseldorf Dusseldorf, Germany 2001:7f8:d9:5a:b901::9a16 100M Yes PeeringDB
Canada UNM-Exch Canada-West Vancouver, Canada 2602:ffb1:200:0:192:34:27:32 1G Yes Both IPv4 not in PeeringDB

Exchanges in its buildings that it isn't on (7)

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.

Facilities (4)

The buildings Acrion Cloud lists in PeeringDB, and how many of the exchanges in each it's on.

Germany WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf 2 of 6
Germany Hetzner Online NBG1 (Nuremberg)Nuremberg 0 of 4
Germany Hetzner Online FSN1 (Falkenstein)Falkenstein No exchange
United Kingdom 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)