ixreport

GreywindNet

AS218796 · GreywindNet

Yunsheng Deng

4Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
3To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with GreywindNet? · Where should GreywindNet peer next? · Compare GreywindNet with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in GreywindNet's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on GreywindNet'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.242
    • In the entry with IPv6 2001:7f8:aa::242: set IPv4 to 185.0.24.242 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Japan TYIX Tokyo, Japan · PeeringDB 4866
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone23.154.164.170
    • In the entry with IPv6 2602:f429:31::2b: set IPv4 to 23.154.164.170 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

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

  1. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352Not on its IX-F export
    IPv4103.158.187.203
    IPv62a0f:5707:ffe3::203
    Speed1000 Mbps (1G)

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, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20262
Oct 6, 20263
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where GreywindNet'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 13G across 4 exchanges.

United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::242 10G Yes Both IPv4 not in PeeringDB
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::bd 1G Yes PeeringDB
Taiwan STUIX Taipei City, Taiwan 103.158.187.203 2a0f:5707:ffe3::203 1G Yes PeeringDB only
Japan TYIX Tokyo, Japan 2602:f429:31::2b 1G Yes Both IPv4 not in PeeringDB
Facilities (1)

The buildings GreywindNet 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

  • Oct 13, 2026 [PDB] AS218796 GREYWIND-AS added to STUIX
  • Oct 9, 2026 [PDB] AS218796 GREYWIND-AS now in PeeringDB at TYIX
  • Oct 8, 2026 [IXF] AS218796 GREYWIND-AS added to TYIX
  • Oct 7, 2026 [PDB] AS218796 GREYWIND-AS left STUIX
  • Oct 6, 2026 [PDB] AS218796 GREYWIND-AS added to STUIX