ixreport

Gigacom Systems

AS51341 · Gigacom

Gigacom Systems LLC.

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
6Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Gigacom Systems? · Where should Gigacom Systems peer next? · Compare Gigacom Systems 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 Gigacom Systems's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Gigacom Systems'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 differs2 × 20G20G

    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.

Exchanges over time

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

Map

Where Gigacom Systems'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 190G across 6 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.217
31.28.19.223
2 × 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.61.32 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.34
178.18.227.103
2a03:5f80:4::224:34
2a03:5f80:4::227:103
2 × 20G Yes Both Speed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.77
195.208.209.197
2001:7f8:20:101::209:77
2001:7f8:20:101::209:197
2 × 20G Yes Both
Russia PITER-IX Moscow Moscow, Russia 185.0.13.41 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.226 40G Yes PeeringDB

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where Gigacom Systems lists itself in PeeringDB, but don't have Gigacom Systems as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (2)

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

Russia Moscow M9Moscow 6 of 9
Russia IXcellerate MOS5Moscow No exchange