3C1B Telekom: PeeringDB fix list
AS6823 · peeringdb.com/net/26855
5 things to fix in 3C1B Telekom's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on 3C1B Telekom'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 3C1B Telekom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.221.21 IPv6 2001:7f8:11d::21 Speed Not published RS peer Not published -
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Correct these entries (3)
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 400G 800G - In the entry with IPv4 80.81.196.193: set Speed to 800000 (800G) (now 400000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.48.69: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/6823/: 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.