ixreport

Latitude.sh AS262287: PeeringDB fix list

AS262287 · peeringdb.com/net/17301

PeeringDB

2 things to fix in Latitude.sh AS262287's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-14 00:37 UTC.

Make the changes on Latitude.sh AS262287'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 (2)

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 MegaIX Ashburn Ashburn, United States · PeeringDB 1178
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.53.170.47 206.53.170.61 206.53.170.66 206.53.170.67206.53.170.47 206.53.170.51 206.53.170.61 206.53.170.66 206.53.170.67
    IPv6 address missing from PeeringDB2606:a980:0:3::2f 2606:a980:0:3::3d 2606:a980:0:3::42 2606:a980:0:3::432606:a980:0:3::2f 2606:a980:0:3::33 2606:a980:0:3::3d 2606:a980:0:3::42 2606:a980:0:3::43
    • Add an entry: IPv4 206.53.170.51, IPv6 2606:a980:0:3::33, RS peer no.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. United States MegaIX Chicago Chicago, United States · PeeringDB 4507
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.53.206.10 206.53.206.15 206.53.206.21206.53.206.10 206.53.206.15 206.53.206.21 206.53.206.22
    IPv6 address missing from PeeringDB2606:a980:0:d::a 2606:a980:0:d::f 2606:a980:0:d::152606:a980:0:d::a 2606:a980:0:d::f 2606:a980:0:d::15 2606:a980:0:d::16
    • Add an entry: IPv4 206.53.206.22, IPv6 2606:a980:0:d::16, RS peer yes.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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