NFOrce Internet Services :: 43350: PeeringDB fix list
AS43350 · peeringdb.com/net/2435
4 things to fix in NFOrce Internet Services :: 43350's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on NFOrce Internet Services :: 43350'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 2 × 100G 100G + 90G - In the entry with IPv4 80.249.208.228: set Speed to 90000 (90G) (now 100000).
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 100G 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 100G 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 IPv4 address in PeeringDB, not in the export 195.66.226.121 195.66.226.154 195.66.226.121 IPv6 address in PeeringDB, not in the export 2001:7f8:4::a956:1 2001:7f8:4::a956:2 2001:7f8:4::a956:1 - The entry with IPv4 195.66.226.154, IPv6 2001:7f8:4::a956:2 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/43350/: 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.