ixreport

ZYC Network

AS23347

ZYC Network LLC

6Exchanges, of which 1 VIX
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

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

Make the changes on ZYC 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 missing from PeeringDBnone185.0.24.180
    • In the entry with IPv6 2001:7f8:aa::180: set IPv4 to 185.0.24.180 (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.

  2. Japan TYIX Tokyo, Japan · PeeringDB 4866
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone23.154.164.175
    • In the entry with IPv6 2602:f429:31::30: set IPv4 to 23.154.164.175 (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

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
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

In the last 30 days ZYC Network joined 1 exchange and left 0. Growing networks

Joined

  • TYIX Tokyo Oct 31, 2026

Map

Where ZYC 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 23.524G across 6 exchanges.

Germany 91-IX Frankfurt, Germany 2001:7f8:1a:91::124 10G Yes PeeringDB
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::180 10G Yes Both IPv4 not in PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 185.1.166.23 2001:7f8:f2:e1:0:2:3347:1 1G Yes PeeringDB
Taiwan Poema IXVIX Taipei City, Taiwan 2404:f4c0:f70e:1980::23:347 500M PeeringDB only
Japan TYIX Tokyo, Japan 2602:f429:31::30 1G Yes Both IPv4 not in PeeringDB
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:2:3347:1 1.024G Yes PeeringDB
Facilities (1)

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

United Kingdom Vinters ConnectMaidstone 1 of 1

Recent changes Search them

  • Nov 1, 2026 [PDB] AS23347 ZYC Network now in PeeringDB at TYIX
  • Oct 31, 2026 [IXF] AS23347 ZYC Network added to TYIX