ixreport

Nyco Cloud Network

AS197817

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
8Using the route servers
4To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Nyco Cloud Network? · Where should Nyco Cloud Network peer next? · Compare Nyco Cloud Network with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Nyco Cloud Network's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Nyco Cloud 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 (4)

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. United States CXIX - Great Lakes NewYork, United States · PeeringDB 4721
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone33.0.0.84
    • In the entry with IPv6 2a0f:7803:fc60:aaaa::1978:17: set IPv4 to 33.0.0.84 (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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.230
    • In the entry with IPv6 2001:7f8:aa::230: set IPv4 to 185.0.24.230 (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.

  3. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone103.158.187.189
    • In the entry with IPv6 2a0f:5707:ffe3::189: set IPv4 to 103.158.187.189 (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.

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

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

Map

Where Nyco Cloud 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 36G across 8 exchanges.

Germany 91-IX Frankfurt, Germany 2001:7f8:1a:91::104 10G Yes PeeringDB
United States CXIX - Great Lakes NewYork, United States 2a0f:7803:fc60:aaaa::1978:17 10G Yes Both IPv4 not in PeeringDB
Hong Kong DataSphere Internet Exchange (Hong Kong) Hong Kong, Hong Kong 2602:f613::1978:17:1 1G Yes PeeringDB
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::230 10G Yes Both IPv4 not in PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 2001:7f8:f2:e1:0:19:7817:1 1G Yes PeeringDB
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::7f
2602:f92a:1315:2::80
2 × 1G Yes PeeringDB
Taiwan STUIX Taipei City, Taiwan 2a0f:5707:ffe3::189 1G 4 routes Both IPv4 not in PeeringDB
Japan TYIX Tokyo, Japan 2602:f429:31::16 1G Yes Both IPv4 not in PeeringDB

Nyco Cloud Network lists no facilities in PeeringDB.