Sibirskie Seti AS34757: PeeringDB fix list
AS34757 · peeringdb.com/net/12187
2 things to fix in Sibirskie Seti AS34757's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Sibirskie Seti AS34757'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 (1)
On the exchange's own member list, but not in Sibirskie Seti AS34757's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 178.18.233.26 IPv6 2a03:5f80:4:1::233:26 Speed 20000 Mbps (20G) RS peer Yes IPv4 178.18.226.154 IPv6 2a03:5f80:4::226:154 Speed 10000 Mbps (10G) 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.
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 IPv6 address missing from PeeringDB none 2001:7f8:20:401::87:61 - In the entry with IPv4 193.232.87.61: set IPv6 to 2001:7f8:20:401::87:61 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/34757/: 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.