DIGI RO
AS8708 · DIGI-RO
DIGI BORDER
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.
-
IPv4 194.53.172.114 194.53.172.119 IPv6 2001:7f8:26::a500:8708:1 2001:7f8:26::a500:8708:2 Speed Not published RS peer Not published The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.
-
2 connections, so 2 entries:
IPv4 80.81.192.87 IPv6 2001:7f8::2204:0:1 Speed 200000 Mbps (200G) RS peer Yes IPv4 80.81.197.4 IPv6 2001:7f8::2204:0:2 Speed 200000 Mbps (200G) RS peer Yes
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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 80.81.192.87 is AS6910 DIGI BORDER 80.81.192.87 Address belongs to another network in PeeringDB 80.81.197.4 is AS6910 DIGI BORDER 80.81.197.4 Address belongs to another network in PeeringDB 2001:7f8::2204:0:1 is AS6910 DIGI BORDER 2001:7f8::2204:0:1 Address belongs to another network in PeeringDB 2001:7f8::2204:0:2 is AS6910 DIGI BORDER 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 1 |
| Oct 27, 2026 | 1 |
| Oct 26, 2026 | 1 |
| Oct 25, 2026 | 1 |
| Oct 24, 2026 | 1 |
| Oct 23, 2026 | 1 |
| Oct 22, 2026 | 1 |
| Oct 21, 2026 | 1 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
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.
| BNIX Brussels, Belgium | Website list only | ||
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 200G | Not in PeeringDB Address taken |
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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| NetIXSofia, Bulgaria | 204 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| B-IXSofia, Bulgaria | 77 | |
| RoNIXBucharest, Romania | 43 | |
| Balcan-IXBucharest, Romania | 29 | |
| DSIXBucharest, Romania | 18 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (2)
The buildings DIGI RO lists in PeeringDB, and how many of the exchanges in each it's on.
| NXDATA-1 Bucharest (BUH1)Bucharest | 0 of 8 | |
| NXDATA-2 Bucharest (BUH2)Bucharest | 0 of 6 |