Hats Network | LogoHats Network

About Hats Network

Company background, network locations and operator contacts for Hats Network Inc. (AS203314).

AS203314 - Global BGP Backbone

Hats Network Inc. operates AS203314, an eyeball ISP and IP transit network. We provide peering and transit services across the locations listed in our operational references.

  • Founded: 16 Aug 2022
  • ASN: AS203314
  • Peering policy: Open, subject to the published requirements
  • Network type: Eyeball ISP and transit provider

What We Operate

Our work covers backbone routing, interconnection and customer handoffs. The service pages describe delivery options; the peering policy sets the requirements for exchanging routes with us.

Use the network map for location context, PeeringDB for current peering coordinates, and the dated latency dataset for published measurements. These sources describe different aspects of the network and should not be treated as interchangeable.

Network Resources

Global Presence

Loading map...

The map shows the network's published locations. Availability, port capacity and handoff details must be confirmed for an order. PeeringDB is the operational reference for peering.

Core Locations

RegionCityIATACapacityIX ExchangesStatus
Hong KongHong KongHKG1/HKG2/HKG350 GbpsEquinix HK, HKIXActive
JapanTokyoTYO2100 GbpsEquinix Tokyo, JPIX, BBIX, JPNAPActive
SingaporeSingaporeSIN1200 GbpsEquinix SG, SGIXActive
NetherlandsAmsterdamAMS40 GbpsAMS-IX, NL-IXActive
GermanyFrankfurtFRA100 GbpsDE-CIX FrankfurtActive
UKLondonLON100 GbpsLINXActive

Edge Locations

RegionCityIATACapacityIX ExchangesStatus
TaiwanTaipeiTPE1/TPE220 GbpsSTUIX, TPIX-TW, TWIXActive
GermanyBerlinBERNot listedDE-CIX, BCIXActive
FranceCalaisCQF11 GbpsNot listedActive
FranceMarseilleMRS80 GbpsFrance-IXActive
USALos AngelesLAX100 GbpsSFMIXActive
USAAshburnIADNot listedNot listedActive
USANew YorkNYC150 GbpsNYIIX, DE-CIX New YorkActive
USASeattleSEA100 GbpsSIX SeattleActive
CanadaTorontoYYZ1Not listedNot listedActive
AustraliaMelbourneMELNot listedHE / SuperloopActive
South AfricaJohannesburgJNBNot listedHE OnlyPlanned
BrazilSão PauloGRUNot listedNTT / AscentyPlanned

Backbone Latency Matrix

Key routes (representative sample, updated periodically):

RouteRTT (ms)Region Pair
Hong Kong → Taipei~15Intra-Asia
Hong Kong → Singapore~32Intra-Asia
Amsterdam → Frankfurt~5Intra-Europe
Amsterdam → London~6Intra-Europe
Ashburn → New York~6Intra-NorthAm
New York → London~92Trans-Atlantic
Hong Kong → Los Angeles~145Trans-Pacific
Singapore → Melbourne~89Asia-Oceania

For dated measurements and the full set of origins, see the Backbone Latency Matrix. The approximate values above are reference examples.

Los Angeles (LAX)

Los Angeles is a US West Coast handoff market. The published site information lists SFMIX and 100 Gbps committed capacity. Check the Los Angeles latency page for the current dataset rather than using a fixed RTT estimate.

New York (NYC)

New York is an East Coast handoff market with 150 Gbps committed capacity and NYIIX and DE-CIX New York peering listed here. The New York route measurements include both transatlantic and domestic comparisons.

Seattle (SEA)

Seattle provides a Pacific Northwest location with SIX Seattle peering and HE and Cogent upstreams. The listed committed capacity is 100 Gbps. Seattle's measured routes separate regional and trans-Pacific RTTs.

Marseille (MRS)

Marseille is a Mediterranean location with France-IX peering and 80 Gbps committed capacity listed here. See the Marseille route measurements for dated RTT values.

Calais (CQF1)

Calais announces 2a0c:9a40:95ea::/48 through MoeDove (AS44324). Its location code is 253; it supplies an additional European path for the North American backbone.

Toronto (YYZ1)

Toronto is the Canadian edge location, with a North American path toward Europe. It announces 2a0c:9a40:95eb::/48 and 2a13:a5c7:2526::/48 through ParadoxNetworks (AS52025). The primary node address is 2a13:a5c7:2526:1001::1, and the location code is 304.

Melbourne (MEL)

Melbourne is an Australian location with HE and Superloop upstream connectivity. Use the Melbourne latency page to compare the published routes to Singapore and other destinations.

Contact Us

Need Help?

Send orders to Sales, peering requests to the Peering team, and network incidents to the NOC. Support handles general enquiries and abuse reports.

Contact Information

TeamEmail AddressPurpose
Sales[email protected]IP-Transit orders, pricing inquiries
Peering[email protected]Peering requests, PNI arrangements
NOC[email protected]Network issues, outages
Support[email protected]Abuse reports, general support

On this page