ixreport

Tcloudnet

AS399077

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

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in Tcloudnet's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 18:41 UTC.

Make the changes on Tcloudnet'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 Tcloudnet's PeeringDB record. Add one entry per connection with these values.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
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, 20268
Oct 19, 20268
Oct 18, 20268
Oct 17, 20268
Oct 16, 20268
Oct 15, 20268
Oct 14, 20268
Oct 13, 20268
Oct 12, 20268
Oct 11, 20268
Oct 10, 20268
Oct 9, 20268
Oct 8, 20268
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where Tcloudnet'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 430G, at the 7 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Hong Kong BBIX Hong Kong Hong Kong, Hong Kong 103.203.158.171 2403:c780:b800:bb00:0:39:9077:1 10G Yes PeeringDB
Singapore BBIX Singapore Singapore, Singapore 103.231.152.169 2001:df5:b800:bb00:0:39:9077:1 10G Yes PeeringDB
Japan BBIX Tokyo Tokyo, Japan Not in PeeringDB
United States BBIX US-West West Coast, United States 101.203.74.37 2403:c780:7200:b074:0:39:9077:1 10G Yes PeeringDB
Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.56.212 2001:de8:7::39:9077:1 100G Yes PeeringDB
United States Equinix San Jose San Jose, United States 206.223.117.163 2001:504:0:1:0:39:9077:1 100G Yes PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.230.66 2001:de8:4::39:9077:1 100G Yes PeeringDB
Singapore SGIX Singapore, Singapore 103.16.102.201 2001:de8:12:100::201 100G Yes Both

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

These exchanges have a switch in a facility where Tcloudnet lists itself in PeeringDB, but don't have Tcloudnet 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.

Facilities (4)

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

Singapore Equinix SG1 - SingaporeSingapore 3 of 11
United States Equinix SV1/SV5/SV10 - Silicon Valley, San JoseSan Jose 2 of 8
Hong Kong Equinix HK1 - Hong KongTsuen Wan 2 of 6
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4