Wofbit Networks: PeeringDB fix list
AS207113 · peeringdb.com/net/39548
5 things to fix in Wofbit Networks's PeeringDB record, from what its exchanges publish: 4 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Wofbit Networks'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 (4)
On the exchange's own member list, but not in Wofbit Networks's PeeringDB record. Add one entry per connection with these values.
-
IPv4 – IPv6 2001:7f8:ca:1:0:20:7113:1 Speed 1000 Mbps (1G) 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.
-
IPv4 149.112.29.127 IPv6 2001:504:125:e0::127 Speed Not published RS peer Not published -
IPv4 149.112.60.44 IPv6 2001:504:125:e2::44 Speed Not published RS peer Not published -
IPv4 149.112.50.124 IPv6 2001:504:125:e1::124 Speed 1000 Mbps (1G) 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 Port speed differs 10G 1G - In the entry with IPv4 196.60.8.120: set Speed to 1000 (1G) (now 10000).
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/207113/: 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.