Elbracht-Computer NGS: PeeringDB fix list
AS29404 · peeringdb.com/net/3155
6 things to fix in Elbracht-Computer NGS's PeeringDB record, from what its exchanges publish: 5 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Elbracht-Computer NGS'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 (5)
On the exchange's own member list, but not in Elbracht-Computer NGS's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.170.67 IPv6 2001:7f8:9e::72dc:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 185.1.210.83 IPv6 2001:7f8:3d::72dc:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 185.1.208.74 IPv6 2001:7f8:44::72dc:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 193.189.82.76 IPv6 2001:7f8:33::a102:9404:1 Speed 100 Mbps (100M) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 Port speed differs 10G 20G - In the entry with IPv4 80.81.192.134: set Speed to 20000 (20G) (now 10000).
From ixreport.com/net/29404/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.