ixreport

CELCOM

AS198418

CELCOM Sp. z o.o.

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

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in CELCOM's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on CELCOM'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 CELCOM's PeeringDB record. Add one entry per connection with these values.

  1. Poland TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list
    IPv4195.149.232.14
    IPv62001:7f8:27::19:8418:1
    SpeedNot published
    RS peerNot published

    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 (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 EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:5b::509
    • In the entry with IPv4 178.216.41.219: set IPv6 to 2001:7f8:5b::509 (now empty).

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

  2. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::99
    • In the entry with IPv4 89.46.144.99: set IPv6 to 2001:678:3ac::99 (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

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 CELCOM'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 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.41.219 10G Yes Both IPv6 not in PeeringDB
Poland EPIX.Warszawa Warsaw, Poland 89.46.144.99 10G Yes Both IPv6 not in PeeringDB
Poland TPIX PL Warsaw, Poland 195.149.232.14 2001:7f8:27::19:8418:1 Not in PeeringDB

CELCOM lists no facilities in PeeringDB.