ixreport

Setsuna Network

AS205592 · CHILIN.H

4Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Network ServicesType
OpenPeering policy
4Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

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

Make the changes on Setsuna 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 (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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.254
    • In the entry with IPv6 2001:7f8:aa::254: set IPv4 to 185.0.24.254 (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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Setsuna Network has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Taiwan NRIX Taipei City, Taiwan · PeeringDB 4299Not on its website members list
    IPv4–
    IPv62001:ded:c000::49
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

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

Map

Where Setsuna 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 31G across 4 exchanges.

United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::254 10G Yes Both IPv4 not in PeeringDB
Taiwan NRIX Taipei City, Taiwan 2001:ded:c000::49 10G Yes PeeringDB only
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::c4 10G Yes PeeringDB
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:20:5592:1 1G Yes PeeringDB

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where Setsuna Network lists itself in PeeringDB, but don't have Setsuna Network as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Taiwan TPIX-TWTaipei/Taiwan, Taiwan 168 Chief HD Building Taipei
Taiwan STUIXTaipei City, Taiwan 131 Chief HD Building Taipei
United States Global Peer ExchangeWashington, United States 6 Chief HD Building Taipei
Facilities (1)

The buildings Setsuna Network lists in PeeringDB, and how many of the exchanges in each it's on.

Taiwan Chief HD Building TaipeiTaipei 1 of 4