Windstream Communication Limited: PeeringDB fix list
AS139009 · peeringdb.com/net/26978
5 things to fix in Windstream Communication Limited's PeeringDB record, from what its exchanges publish: 4 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Windstream Communication Limited's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (4)
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 10M - In the entry with IPv4 103.228.172.30: set Speed to 10 (10M) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 30G + 10G 100G + 19.994G + 10G - In the entry with IPv4 103.27.170.180: set Speed to 10000 (10G) (now 30000).
- In the entry with IPv4 103.27.170.249: set Speed to 19994 (19.994G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 30G 100G - In the entry with IPv4 45.120.251.110: set Speed to 100000 (100G) (now 30000).
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 200G - In the entry with IPv4 185.1.8.149: set Speed to 200000 (200G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Windstream Communication Limited 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.15.47 IPv6 2001:7f8:7a::13:9009:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/139009/: 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.