ixreport

HITC

AS24088 · HITC (HTC INTERNATIONAL TELECOMMUNICATION JOINT STOCK COMPANY)

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in HITC's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on HITC'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 (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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.81.196.96: set Speed to 10000 (10G) (now 1000).

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, 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

Map

Where HITC'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 31G across 4 exchanges.

Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.116 2001:df6:480::5e18:0:1 10G 96 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.96 2001:7f8::5e18:0:2 1G 69 routes Both Speed differs
Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.56.226 2001:de8:7::2:4088:1 10G Yes PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.229.159 2001:de8:4::2:4088:1 10G Yes PeeringDB

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

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

Hong Kong HKIXHong Kong, Hong Kong 300 MEGA-i (iAdvantage Hong Kong)
Singapore SGIXSingapore, Singapore 277 Equinix SG1 - Singapore
Bulgaria NetIXSofia, Bulgaria 204 MEGA-i (iAdvantage Hong Kong); Equinix SG1 - Singapore
Singapore BBIX SingaporeSingapore, Singapore 169 Equinix SG1 - Singapore
Hong Kong BBIX Hong KongHong Kong, Hong Kong 104 MEGA-i (iAdvantage Hong Kong)
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 Equinix SG1 - Singapore
Singapore MegaIX SingaporeSingapore, Singapore 46 Equinix SG1 - Singapore
Hong Kong IAIXHong Kong, Hong Kong 20 MEGA-i (iAdvantage Hong Kong)
Singapore GNM-IX SGSingapore, Singapore 15 Equinix SG1 - Singapore
Singapore AMS-IX SingaporeSingapore, Singapore 14 Equinix SG1 - Singapore
Singapore Impart IXSingapore, Singapore 7 Equinix SG1 - Singapore
United States Global Peer ExchangeWashington, United States 6 Equinix SG1 - Singapore
Facilities (2)

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

Singapore Equinix SG1 - SingaporeSingapore 2 of 11
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 0 of 4