ixreport

Heptasky

AS153771 · Heptasky

Heptasky Hong Kong Limited

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

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

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

  1. Hong Kong Hong Kong Global Internet Exchange Hong Kong, Hong Kong · PeeringDB 4625From its IX-F export and website members list
    IPv4–
    IPv62404:c140:101e::15:3771
    Speed100000 Mbps (100G)
    RS peerYes

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

Exchanges over time

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

Map

Where Heptasky'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 200G across 2 exchanges.

Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.57.85 2001:de8:7::15:3771:1 100G Yes PeeringDB
Hong Kong Hong Kong Global Internet Exchange Hong Kong, Hong Kong 138.252.211.27 2404:c140:101e::15:3771 100G 1 routes Not in PeeringDB

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

These exchanges have a switch in a facility where Heptasky lists itself in PeeringDB, but don't have Heptasky 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 Equinix HK2 - Hong Kong
Bulgaria NetIXSofia, Bulgaria 204 Equinix HK2 - Hong Kong; Equinix TY7 - Tokyo
Japan Equinix TokyoTokyo, Japan 127 Equinix TY7 - Tokyo
Hong Kong ixFabric - Hong KongHong Kong, Hong Kong 50 iTech Towers 2
Hong Kong DataSphere Internet Exchange (Hong Kong)Hong Kong, Hong Kong 29 iTech Towers 2
Switzerland AKIXZurich, Switzerland 11 Equinix HK2 - Hong Kong
United States Global Peer ExchangeWashington, United States 6 Equinix HK2 - Hong Kong
Hong Kong Ciallo~(∠·ω< )⌒ IX - HKHong Kong, Hong Kong 4 Equinix HK2 - Hong Kong
Australia ixFabricGlobal, Australia 2 Equinix HK2 - Hong Kong
Facilities (3)

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

Hong Kong Equinix HK2 - Hong KongKwai Chung 2 of 8
Hong Kong iTech Towers 2New Territories 1 of 3
Japan Equinix TY7 - TokyoTokyo 0 of 2

Recent changes Search them

  • Oct 13, 2026 [PDB] AS153771 Heptasky added to Equinix Hong Kong