ixreport

CETIN Ltd. Belgrade: PeeringDB fix list

AS15958 · peeringdb.com/net/5066

PeeringDB

4 things to fix in CETIN Ltd. Belgrade's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on CETIN Ltd. Belgrade'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 (2)

On the exchange's own member list, but not in CETIN Ltd. Belgrade's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.236.171
    IPv62a03:5f80:4:2::236:171
    Speed100000 Mbps (100G)
    RS peerYes

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

  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.228.141
    IPv62001:7f8:4::3e56:1
    Speed10000 Mbps (10G)
    RS peerYes

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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    IPv4 address differs193.188.137.160193.188.137.102
    • In the entry with IPv4 193.188.137.160: set IPv4 to 193.188.137.102 (now 193.188.137.160).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 80.81.195.87: set Speed to 100000 (100G) (now 50000).

From ixreport.com/net/15958/: 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.