ixreport

MetroLine (AS50898)

AS50898

MetroLine Sp. z o.o.

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
3Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

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

Make the changes on MetroLine (AS50898)'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 (2)

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 THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:60::5:898:1none
    • In the entry with IPv4 212.91.1.76: set IPv6 to (empty) (now 2001:7f8:60::5:898:1).

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

  2. Poland TPIX PL Warsaw, Poland · PeeringDB 482
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.149.233.42195.149.233.41 195.149.233.42
    IPv6 address missing from PeeringDB2001:7f8:27::5:898:22001:7f8:27::5:898:1 2001:7f8:27::5:898:2
    • Add an entry: IPv4 195.149.233.41, IPv6 2001:7f8:27::5:898:1.

    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 MetroLine (AS50898)'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 30G across 3 exchanges.

Poland Equinix Warsaw Warsaw, Poland 195.182.219.145 2001:7f8:42::5:898:1 10G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.1.76 2001:7f8:60::5:898:1 10G Yes Both IPv6 not in export
Poland TPIX PL Warsaw, Poland 195.149.233.42 2001:7f8:27::5:898:2 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

MetroLine (AS50898) lists no facilities in PeeringDB.