ixreport

Kinescope

AS212236 · Kinescope

Kinescope LLC

9Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
9Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Kinescope? · Where should Kinescope peer next? · Compare Kinescope with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Kinescope's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Kinescope'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs40G200G
    • In the entry with IPv4 178.18.227.11: set Speed to 200000 (200G) (now 40000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

0246810Oct 3, 2026Nov 19, 20269
Show as a table
DateExchanges
Nov 19, 20269
Nov 18, 20269
Nov 17, 20269
Nov 16, 20269
Nov 15, 20269
Nov 14, 20269
Nov 13, 20269
Nov 12, 20269
Nov 11, 20269
Nov 10, 20269
Nov 9, 20269
Nov 8, 20269
Nov 7, 20269
Nov 6, 20269
Nov 5, 20269
Nov 4, 20269
Nov 3, 20269
Nov 2, 20269
Nov 1, 20269
Oct 31, 20269
Oct 30, 20269
Oct 29, 20269
Oct 28, 20269
Oct 27, 20269
Oct 26, 20269
Oct 25, 20269
Oct 24, 20269
Oct 23, 20269
Oct 22, 20269
Oct 21, 20269
Oct 20, 20269
Oct 19, 20269
Oct 18, 20269
Oct 17, 20269
Oct 16, 20269
Oct 15, 20269
Oct 14, 20269
Oct 13, 20269
Oct 12, 20269
Oct 11, 20269
Oct 10, 20269
Oct 9, 20269
Oct 8, 20269
Oct 7, 20269
Oct 6, 20269
Oct 5, 20269
Oct 4, 20269
Oct 3, 20269

Map

Where Kinescope's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 300G across 9 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.30 2a00:13c0:3:1::1f1c:131e 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.184 2a0d:e180::60:184 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.81 2001:b28:3ff::32a3:0:1 40G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.11 2a03:5f80:4::227:11 40G Yes Both Speed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.23 2001:7f8:20:101::209:23 40G Yes Both
Russia PITER-IX Moscow Moscow, Russia 185.0.12.244 40G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.96 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.16 40G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.57 40G Yes PeeringDB
Facilities (1)

The buildings Kinescope lists in PeeringDB, and how many of the exchanges in each it's on.

Russia IXcellerate MOS1Moscow 6 of 6