ixreport

MTM-INFO S.J.

AS51390

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

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

Make the changes on MTM-INFO S.J.'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. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::102
    • In the entry with IPv4 89.46.144.102: set IPv6 to 2001:678:3ac::102 (now empty).

    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

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 MTM-INFO S.J.'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 130G across 4 exchanges.

Poland EPIX.Warszawa Warsaw, Poland 89.46.144.102 100G Yes Both IPv6 not in PeeringDB
Poland Equinix Warsaw Warsaw, Poland 195.182.218.3 10G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.0.87 10G Yes Both
Poland TPIX PL Warsaw, Poland 195.149.232.37 10G Yes Both
Facilities (2)

The buildings MTM-INFO S.J. lists in PeeringDB, and how many of the exchanges in each it's on.

Poland DCENTER.PL - FT21Warsaw No exchange
Poland Quicktel Sp. z o.o.Katowice No exchange