ixreport

ASPA CLOUD

AS202207

ASPA CLOUD SL

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with ASPA CLOUD? · Where should ASPA CLOUD peer next? · Compare ASPA CLOUD with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in ASPA CLOUD's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on ASPA 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 (1)

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. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.193.2185.1.192.190 185.1.193.2
    IPv6 address missing from PeeringDB2001:7f8:a0:0:3:15df:0:22001:7f8:a0:0:3:15df:0:1 2001:7f8:a0:0:3:15df:0:2
    Port speed differs10G10G + 1G
    • Add an entry: IPv4 185.1.192.190, IPv6 2001:7f8:a0:0:3:15df:0:1, speed 1000 (1G), RS peer yes.

Exchanges over time

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

Map

Where ASPA 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 10G across 1 exchange.

Spain DE-CIX Madrid Madrid, Spain 185.1.193.2 2001:7f8:a0:0:3:15df:0:2 10G 9 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs

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

These exchanges have a switch in a facility where ASPA CLOUD lists itself in PeeringDB, but don't have ASPA 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.

Spain IXPlay Global PeersMadrid, Spain 63 IPCore Datacenter Madrid
United States Global Peer ExchangeWashington, United States 6 Global Switch Madrid
Facilities (2)

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

Spain Global Switch MadridMadrid 1 of 2
Spain IPCore Datacenter MadridMadrid 0 of 1