GKIM-AS
AS218681 · Xr3azn
Geonwoo Kim
Tools: Where can I peer with GKIM-AS? · Where should GKIM-AS peer next?
PeeringDB fix list Printable page
One thing to fix in GKIM-AS's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-13 12:38 UTC.
Make the changes on GKIM-AS'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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 172.27.184.10 - In the entry with IPv6 2a0b:4e07:fb::10: set IPv4 to 172.27.184.10 (now empty).
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.
Exchanges over time
This chart fills in as daily counts build up; the first was Oct 13, 2026.
 |
KCIXP - Korea Community Internet Exchange Point Seoul, South Korea | 1G | Both IPv4 not in PeeringDB |
GKIM-AS lists no facilities in PeeringDB.