Eastlink: PeeringDB fix list

AS11260 · peeringdb.com/net/2081

PeeringDB

One thing to fix in Eastlink's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Eastlink'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.

  1. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export206.82.104.184 206.82.104.187206.82.104.184
    IPv6 address in PeeringDB, not in the export2001:504:36::2bfc:0:1 2001:504:36::5a90:0:12001:504:36::2bfc:0:1
    Port speed differs2 × 100G100G
    • The entry with IPv4 206.82.104.187, IPv6 2001:504:36::5a90:0:1 isn't in the export: delete it if that connection is gone.

From ixreport.com/net/11260/: 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.