e-Style ISP: PeeringDB fix list

AS20655 · peeringdb.com/net/15830

PeeringDB

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

Make the changes on e-Style ISP'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. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.215195.208.208.215 195.208.209.185
    IPv6 address missing from PeeringDB2001:7f8:20:101::208:2152001:7f8:20:101::208:215 2001:7f8:20:101::209:185
    • Add an entry: IPv4 195.208.209.185, IPv6 2001:7f8:20:101::209:185, 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/20655/: 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.