ixreport

DIGI ES

AS57269 · DIGI-ES

DIGI BORDER

2Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
2Using the route servers
4To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with DIGI ES? · Where should DIGI ES peer next? · Compare DIGI ES with another network

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

PeeringDB fix list Printable page · CSV

4 things to fix in DIGI ES's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on DIGI ES'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 (2)

On the exchange's own member list, but not in DIGI ES's PeeringDB record. Add one entry per connection with these values.

  1. Spain DE-CIX Barcelona Barcelona, Spain · PeeringDB 3446From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4185.1.119.6
    IPv62001:7f8:10a::dfb5:0:1
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4185.1.119.27
    IPv62001:7f8:10a::dfb5:0:2
    Speed20000 Mbps (20G)
    RS peerYes
  2. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277From its IX-F export and website members list

    3 connections, so 3 entries:

    IPv4185.1.192.122
    IPv62001:7f8:a0::dfb5:0:1
    Speed200000 Mbps (200G)
    RS peerYes
    IPv4185.1.192.243
    IPv62001:7f8:a0::dfb5:0:2
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4185.1.192.16
    IPv62001:7f8:a0::dfb5:0:3
    Speed200000 Mbps (200G)
    RS peerYes

Correct these entries (2)

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 Barcelona Barcelona, Spain · PeeringDB 3446
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.119.6 is AS6910 DIGI BORDER185.1.119.6
    Address belongs to another network in PeeringDB185.1.119.27 is AS6910 DIGI BORDER185.1.119.27
    Address belongs to another network in PeeringDB2001:7f8:10a::dfb5:0:1 is AS6910 DIGI BORDER2001:7f8:10a::dfb5:0:1
    Address belongs to another network in PeeringDB2001:7f8:10a::dfb5:0:2 is AS6910 DIGI BORDER2001:7f8:10a::dfb5:0:2

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  2. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.192.122 is AS6910 DIGI BORDER185.1.192.122
    Address belongs to another network in PeeringDB185.1.192.243 is AS6910 DIGI BORDER185.1.192.243
    Address belongs to another network in PeeringDB2001:7f8:a0::dfb5:0:1 is AS6910 DIGI BORDER2001:7f8:a0::dfb5:0:1
    Address belongs to another network in PeeringDB2001:7f8:a0::dfb5:0:2 is AS6910 DIGI BORDER2001:7f8:a0::dfb5:0:2

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

Exchanges over time

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

Map

Where DIGI ES'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 540G across 2 exchanges.

Spain DE-CIX Barcelona Barcelona, Spain 185.1.119.6
185.1.119.27
2001:7f8:10a::dfb5:0:1
2001:7f8:10a::dfb5:0:2
2 × 20G Down Not in PeeringDB Address taken
Spain DE-CIX Madrid Madrid, Spain 185.1.192.16
185.1.192.122
185.1.192.243
2001:7f8:a0::dfb5:0:1
2001:7f8:a0::dfb5:0:2
2001:7f8:a0::dfb5:0:3
2 × 200G + 100G Down Not in PeeringDB Address taken

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

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

Bulgaria NetIXSofia, Bulgaria 204 Digital Realty Madrid MAD3
Spain ESpanix Madrid Lower LANMadrid, Spain 161 Equinix MD2 - Madrid
Spain ESpanix Madrid Upper LANMadrid, Spain 57 Equinix MD2 - Madrid
Spain CATNIXBarcelona, Spain 55 Equinix BA1 - Barcelona
Spain Equinix MadridMadrid, Spain 12 Equinix MD2 - Madrid
Spain Equinix BarcelonaBarcelona, Spain 11 Equinix BA1 - Barcelona
Facilities (3)

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

Spain Equinix MD2 - MadridAlcobendas 1 of 4
Spain Equinix BA1 - BarcelonaBarcelona 1 of 3
Spain Digital Realty Madrid MAD3Madrid 0 of 1