ixreport

Prostor_telecom

AS12418

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
3Using the route servers
3To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

AS12418 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.224.43
    IPv62a03:5f80:4::224:43
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.225.175
    IPv62a03:5f80:4::225:175
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4195.208.209.148
    IPv62001:7f8:20:101::209:148
    SpeedNot published
    RS peerYes
    IPv4195.208.210.78
    IPv62001:7f8:20:101::210:78
    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.

  3. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    4 connections, so 4 entries:

    IPv4194.226.102.50
    IPv62001:7f8:20:202::102:50
    SpeedNot published
    RS peerYes
    IPv4194.226.101.78
    IPv62001:7f8:20:201::101:78
    SpeedNot published
    RS peerYes
    IPv4194.226.103.78
    IPv62001:7f8:20:202::103:78
    SpeedNot published
    RS peerYes
    IPv4194.226.100.50
    IPv62001:7f8:20:201::100:50
    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.

Exchanges over time

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

Map

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

Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.43
178.18.225.175
2a03:5f80:4::224:43
2a03:5f80:4::225:175
2 × 10G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 193.232.87.178
193.232.140.78
194.85.107.178
195.208.209.148
195.208.210.78
2001:7f8:20:101::209:148
2001:7f8:20:101::210:78
Yes Not in PeeringDB
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.50
194.226.101.78
194.226.102.50
194.226.103.78
2001:7f8:20:201::100:50
2001:7f8:20:201::101:78
2001:7f8:20:202::102:50
2001:7f8:20:202::103:78
Yes Not in PeeringDB