ixreport

DoubleGIS

AS197482 · 2GIS

4Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
SelectivePeering policy
2Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

2 things to fix in DoubleGIS's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on DoubleGIS's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in DoubleGIS's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export and website members list
    IPv4195.208.209.150
    IPv6–
    SpeedNot published
    RS peerYes

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

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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:8
    • In the entry with IPv4 178.18.225.8: set IPv6 to 2a03:5f80:4::225:8 (now empty).

    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

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

Map

Where DoubleGIS'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 40G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.8 10G Yes Both IPv6 not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.209.150 Yes Not in PeeringDB
Russia RED-IX Krasnoyarsk, Russia 185.1.13.88 10G PeeringDB
Russia W-IX Moscow, Russia 193.106.112.13
193.106.112.110
2 × 10G PeeringDB

DoubleGIS lists no facilities in PeeringDB.