ixreport

Microsystem Kecskemet: PeeringDB fix list

AS197889 · peeringdb.com/net/23905

PeeringDB

One thing to fix in Microsystem Kecskemet's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Microsystem Kecskemet'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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.188.137.92193.188.137.89 193.188.137.92
    IPv6 address missing from PeeringDBnone2001:7f8:35::19:7889:1 2001:7f8:35::19:7889:2
    Port speed differs10G2 × 10G
    • In the entry with IPv4 193.188.137.92: set IPv6 to 2001:7f8:35::19:7889:1 (now empty).
    • Add an entry: IPv4 193.188.137.89, IPv6 2001:7f8:35::19:7889:2, speed 10000 (10G), RS peer yes.

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