ixreport

TWOWIN NETWORK

AS133929 · TWOWIN

TWOWIN CO., LIMITED

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

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

Make the changes on TWOWIN NETWORK's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in TWOWIN NETWORK's PeeringDB record. Add one entry per connection with these values.

  1. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list
    IPv4103.16.103.42
    IPv62001:de8:12:100::103:42
    Speed10000 Mbps (10G)
    RS peerNo

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. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.16.103.42 is AS150436 Byteplus Pte. Ltd.103.16.103.42
    Address belongs to another network in PeeringDB2001:de8:12:100::103:42 is AS150436 Byteplus Pte. Ltd.2001:de8:12:100::103:42

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

Exchanges over time

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

Map

Where TWOWIN 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 30G across 3 exchanges.

Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.57.206 2001:de8:7::13:3929:1 10G Yes PeeringDB
Hong Kong HKIX Hong Kong, Hong Kong 123.255.91.109 2001:7fa:0:1::ca28:a16d 10G Yes Both
Singapore SGIX Singapore, Singapore 103.16.103.42 2001:de8:12:100::103:42 10G Not in PeeringDB Address taken

TWOWIN NETWORK lists no facilities in PeeringDB.