VAGUE: PeeringDB fix list
AS212121 · peeringdb.com/net/26781
2 things to fix in VAGUE's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on VAGUE'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 185.1.125.239 185.1.125.236 185.1.125.239 - In the entry with IPv6 2001:7f8:d0::3:3c99:1: set IPv4 to 185.1.125.236 (now empty).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If VAGUE has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2001:7f8:11f:be00:212:121:0:1 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/212121/: 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.