ixreport

Sprintel s.r.o.: PeeringDB fix list

AS197013 · peeringdb.com/net/6908

PeeringDB

2 things to fix in Sprintel s.r.o.'s PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Sprintel 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 (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
    IPv6 address missing from PeeringDBnone2001:7f8:14::44:1
    • In the entry with IPv4 91.210.16.142: set IPv6 to 2001:7f8:14::44:1 (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. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G25G
    • In the entry with IPv4 185.0.20.66: set Speed to 25000 (25G) (now 100000).
    • In the entry with IPv4 185.0.20.67: set Speed to 25000 (25G) (now 100000).

From ixreport.com/net/197013/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.