ixreport

JK-Network

AS207705

Jyun-Kai Hu

5Exchanges, of which 1 VIX
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
4Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

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

Make the changes on JK-Network'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. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.35none
    • In the entry with IPv4 185.1.125.35: set IPv4 to (empty) (now 185.1.125.35).
  2. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.158.187.73none
    • In the entry with IPv4 103.158.187.73: set IPv4 to (empty) (now 103.158.187.73).

    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

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where JK-Network'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 3.6G across 5 exchanges.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.35 2001:7f8:d0::3:2b59:1 100M Yes Both IPv4 not in export
United States Lambda-IX Fremont, United States 149.112.26.20 2a0f:607:1070::20 1G Yes PeeringDB
Taiwan Poema IXVIX Taipei City, Taiwan 2404:f4c0:f70e:1980::207:705 500M PeeringDB only
Taiwan STUIX Taipei City, Taiwan 103.158.187.73 2a0f:5707:ffe3::73 1G 11 routes Both IPv4 not in export
United States Zero Internet eXchange San Jose San Jose, United States 23.145.168.228 2a13:b487:3200::20:7705:1 1G Yes PeeringDB

JK-Network lists no facilities in PeeringDB.