ixreport

TKR Jasek

AS207187 · xGbE

TKR Jasek, s.r.o.

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

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

Make the changes on TKR Jasek'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. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 50G50G

    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.

  2. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 25G + 10G7.5G
    • In the entry with IPv4 185.0.20.158: set Speed to 7500 (7.5G) (now 25000).
    • In the entry with IPv4 185.0.20.99: set Speed to 7500 (7.5G) (now 10000).
    • In the entry with IPv4 185.0.21.12: set Speed to 7500 (7.5G) (now 25000).

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 TKR Jasek'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 160G across 2 exchanges.

Czechia NIX.CZ Prague, Czechia 91.210.16.77
91.210.17.77
2001:7f8:14::38:1
2001:7f8:14::38:2
2 × 50G Yes Both Speed differs
Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia 185.0.20.99
185.0.20.158
185.0.21.12
2001:7f8:7f::99
2001:7f8:7f::158
2001:7f8:7f::c:12
2 × 25G + 10G Yes Both Speed differs

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

These exchanges have a switch in a facility where TKR Jasek lists itself in PeeringDB, but don't have TKR Jasek 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 GNM-IXAmsterdam, Netherlands 741 CE Colo Prague
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 CE Colo Prague
Bulgaria NetIXSofia, Bulgaria 204 CE Colo Prague
Netherlands Global-IXAmsterdam, Netherlands 138 CE Colo Prague
Czechia NIX.CZ FENIXPrague, Czechia 8 CE Colo Prague; TTC TELEPORT DC1
Czechia 1-CZ FREEPrague, Czechia 6 CE Colo Prague
Facilities (2)

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

Czechia CE Colo PraguePrague 2 of 8
Czechia TTC TELEPORT DC1Prague 2 of 3