Wnet Telecom USA: PeeringDB fix list
AS1820 · peeringdb.com/net/19501
9 things to fix in Wnet Telecom USA's PeeringDB record, from what its exchanges publish: 1 to add, 6 to correct, 2 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Wnet Telecom USA'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 Wnet Telecom USA's PeeringDB record. Add one entry per connection with these values.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members listIPv4 193.239.118.196 IPv6 2001:7f8:13::a500:1820:1 Speed Not published 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 (6)
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 1G 250M - In the entry with IPv4 103.247.139.71: set Speed to 250 (250M) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 89.46.145.178: set Speed to 20000 (20G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G + 20G 100G + 20G PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 5G - In the entry with IPv4 5.57.82.50: set Speed to 5000 (5G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 25G 3.125G - In the entry with IPv4 185.0.20.78: set Speed to 3125 (3.125G) (now 25000).
-
Problem PeeringDB has The export has Port speed differs 40G 20G - In the entry with IPv4 212.91.0.108: set Speed to 20000 (20G) (now 40000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Wnet Telecom USA has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.213.30 IPv6 2001:7f8:14d::30 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 185.1.51.39 IPv6 2001:7f8:5d::1e Speed 40000 Mbps (40G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/1820/: 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.