FASTNET SOLUTIONS: PeeringDB fix list
AS273861 · peeringdb.com/net/42869
One thing to fix in FASTNET SOLUTIONS's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on FASTNET SOLUTIONS'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 (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 IPv4 address missing from PeeringDB 45.68.60.105 45.68.60.105 45.68.60.106 IPv6 address missing from PeeringDB 2801:19:7800:2::105 2801:19:7800:2::105 2801:19:7800:2::106 Port speed differs 10G 1G - In the entry with IPv4 45.68.60.105: set Speed to 1000 (1G) (now 10000).
- Add an entry: IPv4 45.68.60.106, IPv6 2801:19:7800:2::106, speed 1000 (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.
From ixreport.com/net/273861/: 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.