ONECOM: PeeringDB fix list
AS39513 · peeringdb.com/net/28113
2 things to fix in ONECOM's PeeringDB record, from what its exchanges publish: 1 to add, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on ONECOM'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 ONECOM's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 91.213.73.15 IPv6 2001:7f8:174::15 Speed 100000 Mbps (100G)
From ixreport.com/net/39513/: 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.