ixreport

ZCOM.cz s.r.o.

AS206548 · ZCOM, Tlap

ZCOM.cz

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

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

Make the changes on ZCOM.cz s.r.o.'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. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.20.69: set Speed to 12500 (12.5G) (now 100000).

Exchanges over time

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

Map

Where ZCOM.cz s.r.o.'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 200G across 2 exchanges.

Czechia NIX.CZ Prague, Czechia 91.210.16.225 2001:7f8:14::19:1 100G Yes Both
Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia 185.0.20.69 2001:7f8:7f::69 100G Yes Both Speed differs

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

These exchanges have a switch in a facility where ZCOM.cz s.r.o. lists itself in PeeringDB, but don't have ZCOM.cz s.r.o. 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.

Czechia NIX.CZ FENIXPrague, Czechia 8 TTC TELEPORT DC1; TTC TELEPORT DC2
Facilities (2)

The buildings ZCOM.cz s.r.o. lists in PeeringDB, and how many of the exchanges in each it's on.

Czechia TTC TELEPORT DC1Prague 2 of 3
Czechia TTC TELEPORT DC2Prague 2 of 3