ixreport

DIGI RO

AS8708 · DIGI-RO

DIGI BORDER

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on DIGI RO'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 RO's PeeringDB record. Add one entry per connection with these values.

  1. Belgium BNIX Brussels, Belgium · PeeringDB 59From its website members list
    IPv4194.53.172.114 194.53.172.119
    IPv62001:7f8:26::a500:8708:1 2001:7f8:26::a500:8708:2
    SpeedNot published
    RS peerNot published

    The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv480.81.192.87
    IPv62001:7f8::2204:0:1
    Speed200000 Mbps (200G)
    RS peerYes
    IPv480.81.197.4
    IPv62001:7f8::2204:0:2
    Speed200000 Mbps (200G)
    RS peerYes

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB80.81.192.87 is AS6910 DIGI BORDER80.81.192.87
    Address belongs to another network in PeeringDB80.81.197.4 is AS6910 DIGI BORDER80.81.197.4
    Address belongs to another network in PeeringDB2001:7f8::2204:0:1 is AS6910 DIGI BORDER2001:7f8::2204:0:1
    Address belongs to another network in PeeringDB2001:7f8::2204:0:2 is AS6910 DIGI BORDER2001:7f8::2204: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, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
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 RO'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 400G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Belgium BNIX Brussels, Belgium 194.53.172.114
194.53.172.119
2001:7f8:26::a500:8708:1
2001:7f8:26::a500:8708:2
Website list only
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.87
80.81.197.4
2001:7f8::2204:0:1
2001:7f8::2204:0:2
2 × 200G Down Not in PeeringDB Address taken

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

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

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

Romania NXDATA-1 Bucharest (BUH1)Bucharest 0 of 8
Romania NXDATA-2 Bucharest (BUH2)Bucharest 0 of 6