# Hats Network (AS203314) — LLM Index ## What this site is - Company: Hats Network Inc. (AS203314, HATS-NETWORK-INC) - Landing (marketing): https://hatsnet.io/ - Documentation: https://hatsnet.io/docs ## Landing snapshot (high-signal facts) - Homepage headline: Seamless. Secure. Smart. Next-Gen Network Infrastructure. - Summary: Hats Network Inc. (AS203314) - A hybrid Eyeball ISP and Transit Provider with 16+ PoPs across 4 continents, 1 Tbps+ backbone capacity, and latency as low as 3.1 ms. IP Transit, BGP Peering, SD-WAN, and Dedicated Internet Access. - Network map markers: 22 (Africa, Asia-Pacific, Europe, North America, South America). Note: active/planned PoP counts may differ across pages. - Primary contact: sales=sales@hatsnet.io, peering=peering@hatsnet.io, noc=noc@hatsnet.io ## Interactive experiences (ask the user to try) - Backbone latency matrix (docs): https://hatsnet.io/docs/network/latency - Use the on-page lookup + table interactions; it’s the fastest way to answer “best route between X and Y” questions. - For “current/updated” values, direct the user to the page (it’s periodically regenerated). - Network map + PoP popups (landing): https://hatsnet.io/#network - Ask the user to click PoP markers and read the popup details (upstream/peering notes vary by PoP). ## How to use docs effectively - Prefer docs pages as the source of truth for technical details and policies. - For LLM-friendly Markdown, request: https://hatsnet.io/docs/.md (served from /llms.mdx/*). - When answering, include the exact docs path (e.g. /docs/peering, /docs/transit/asia). ## LLM-friendly Documentation Structure This site provides LLM-optimized content via multiple endpoints. Understanding the structure helps you retrieve the right content efficiently. ### Available Endpoints | Endpoint | URL | Content | Use Case | | -------- | --- | ------- | -------- | | Index | https://hatsnet.io/llms.txt | Structured overview with docs index | Quick orientation, navigation | | Single Page | https://hatsnet.io/docs/.md | Individual page as processed Markdown | Targeted queries, specific topics | **Examples:** - BGP communities: /docs/community/control-communities.md - Peering policy: /docs/peering.md - Latency matrix: /docs/network/latency.md ### Content Update Strategy - Static content: Updated on each deployment - Latency matrix: Regenerated daily from live infrastructure measurements - BGP communities: Updated when new features are deployed ### Caching & Performance - All LLM endpoints are statically generated at build time - No server-side processing required for content delivery - Recommended: Cache responses for up to 24 hours ## Docs index - **Information** - [Quick Start Guide](/docs): Complete documentation for Hats Network Inc. (AS203314) - global BGP backbone with 16+ PoPs across 4 continents, open peering policy, IP transit services, and BGP communities reference. - [About Hats Network](/docs/about): Hats Network Inc. (AS203314) operates a global BGP backbone with 16+ PoPs across 4 continents. Intra-Asia latency as low as 15 ms (HKG↔TPE) and cross-Atlantic under 6 ms (AMS↔LON). - **Network** - Backbone: Backbone documentation for AS203314, including latency data across Hats Network PoPs. - PoP Latency: Per-PoP, city-pair, and regional network latency detail pages for the Hats Network backbone - **Overview** - [Global Ping & RTT Latency Matrix | AS203314](/docs/network/latency): Compare ping, RTT, physical fiber limits, jitter and packet loss across 20 Hats Network (AS203314) global backbone PoPs, updated daily. - [Latency Coordinates & Fiber Model Inputs](/docs/network/latency/theoretical-fiber-latency): How AS203314 resolves public city-centre coordinates with GeoNames and selects fiber, attenuation, amplifier, and route-stretch model inputs. - [Theoretical Fiber Latency Formula Verification](/docs/network/latency/theoretical-latency-verification): Verify AS203314's theoretical fiber latency model with rendered equations, unit checks, and a complete Tokyo-to-Sydney numerical reconciliation. - **By Region & Corridor** - Regions & Corridors: Regional and inter-regional latency overviews for the Hats Network backbone - [Regional Ping & RTT Corridors | AS203314](/docs/network/latency/regions): Browse Hats Network (AS203314) backbone latency by region and inter-regional corridor. Updated 2026-08-14. - **Regions** - [Europe Ping & RTT Latency | AS203314](/docs/network/latency/regions/europe): RTT latency matrix and cross-region routes for Hats Network PoPs in Europe. Updated 2026-08-14. - [North America Ping & RTT Latency | AS203314](/docs/network/latency/regions/north-america): RTT latency matrix and cross-region routes for Hats Network PoPs in North America. Updated 2026-08-14. - [South America Ping & RTT Latency | AS203314](/docs/network/latency/regions/south-america): RTT latency matrix and cross-region routes for Hats Network PoPs in South America. Updated 2026-08-14. - [Asia Pacific Ping & RTT Latency | AS203314](/docs/network/latency/regions/asia-pacific): RTT latency matrix and cross-region routes for Hats Network PoPs in Asia Pacific. Updated 2026-08-14. - [Africa Ping & RTT Latency | AS203314](/docs/network/latency/regions/africa): RTT latency matrix and cross-region routes for Hats Network PoPs in Africa. Updated 2026-08-14. - **Corridors** - [Europe to North America Ping & RTT | AS203314](/docs/network/latency/regions/europe-to-north-america): Europe to North America ping and RTT on AS203314. Fastest route: London (LON) to New York (NYC) at 64.1 ms. Updated 2026-08-14. - [Europe to Asia Pacific Ping & RTT | AS203314](/docs/network/latency/regions/europe-to-asia-pacific): Europe to Asia Pacific ping and RTT on AS203314. Fastest route: Moscow (MOW) to Hong Kong (HKG) at 116.5 ms. Updated 2026-08-14. - [North America to Asia Pacific Ping & RTT | AS203314](/docs/network/latency/regions/north-america-to-asia-pacific): North America to Asia Pacific ping and RTT on AS203314. Fastest route: Seattle (SEA) to Tokyo (TYO) at 84.8 ms. Updated 2026-08-14. - [Europe to South America Ping & RTT | AS203314](/docs/network/latency/regions/europe-to-south-america): Europe to South America ping and RTT on AS203314. Fastest route: London (LON) to São Paulo (GRU) at 171.4 ms. Updated 2026-08-14. - [North America to South America Ping & RTT | AS203314](/docs/network/latency/regions/north-america-to-south-america): North America to South America ping and RTT on AS203314. Fastest route: Ashburn (IAD) to São Paulo (GRU) at 102.4 ms. Updated 2026-08-14. - [Asia Pacific to South America Ping & RTT | AS203314](/docs/network/latency/regions/asia-pacific-to-south-america): Asia Pacific to South America ping and RTT on AS203314. Fastest route: Tokyo (TYO) to São Paulo (GRU) at 230.3 ms. Updated 2026-08-14. - **By City Pair** - City-Pair RTT: Per-city-pair backbone RTT pages across all Hats Network PoPs - [City-to-City Ping & RTT Latency | AS203314](/docs/network/latency/pairs): Compare city-to-city ping, RTT, jitter, loss, theoretical fiber limits, and route efficiency across Hats Network (AS203314) PoPs. Updated 2026-08-14. - **By PoP** - **Europe** - [🇳🇱 Amsterdam Ping & Network Latency (AMS) | AS203314](/docs/network/latency/ams-amsterdam): Amsterdam (AMS) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇩🇪 Berlin Ping & Network Latency (BER) | AS203314](/docs/network/latency/ber-berlin): Berlin (BER) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇩🇪 Frankfurt Ping & Network Latency (FRA) | AS203314](/docs/network/latency/fra-frankfurt): Frankfurt (FRA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇬🇧 London Ping & Network Latency (LON) | AS203314](/docs/network/latency/lon-london): London (LON) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇫🇷 Marseille Ping & Network Latency (MRS) | AS203314](/docs/network/latency/mrs-marseille): Marseille (MRS) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇷🇺 Moscow Ping & Network Latency (MOW) | AS203314](/docs/network/latency/mow-moscow): Moscow (MOW) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇫🇷 Paris Ping & Network Latency (PAR) | AS203314](/docs/network/latency/par-paris): Paris (PAR) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - **North America** - [🇺🇸 Ashburn Ping & Network Latency (IAD) | AS203314](/docs/network/latency/iad-ashburn): Ashburn (IAD) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇺🇸 Los Angeles Ping & Network Latency (LAX) | AS203314](/docs/network/latency/lax-los-angeles): Los Angeles (LAX) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇺🇸 Miami Ping & Network Latency (MIA) | AS203314](/docs/network/latency/mia-miami): Miami (MIA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇺🇸 New York Ping & Network Latency (NYC) | AS203314](/docs/network/latency/nyc-new-york): New York (NYC) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇺🇸 Seattle Ping & Network Latency (SEA) | AS203314](/docs/network/latency/sea-seattle): Seattle (SEA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - **South America** - [🇧🇷 São Paulo Ping & Network Latency (GRU) | AS203314](/docs/network/latency/gru-sao-paulo): São Paulo (GRU) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - **Asia Pacific** - [🇭🇰 Hong Kong Ping & Network Latency (HKG) | AS203314](/docs/network/latency/hkg-hong-kong): Hong Kong (HKG) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇦🇺 Melbourne Ping & Network Latency (MEL) | AS203314](/docs/network/latency/mel-melbourne): Melbourne (MEL) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇸🇬 Singapore Ping & Network Latency (SIN) | AS203314](/docs/network/latency/sin-singapore): Singapore (SIN) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇦🇺 Sydney Ping & Network Latency (SYD) | AS203314](/docs/network/latency/syd-sydney): Sydney (SYD) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇹🇼 Taipei Ping & Network Latency (TPE) | AS203314](/docs/network/latency/tpe-taipei): Taipei (TPE) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - [🇯🇵 Tokyo Ping & Network Latency (TYO) | AS203314](/docs/network/latency/tyo-tokyo): Tokyo (TYO) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - **Africa** - [🇿🇦 Johannesburg Ping & Network Latency (JNB) | AS203314](/docs/network/latency/jnb-johannesburg): Johannesburg (JNB) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs. - BGP Communities: BGP community strings for AS203314 traffic engineering, including internal, control communities, PoP codes, and region codes. - [BGP Communities](/docs/community): Complete reference for BGP community strings for AS203314 traffic engineering. Internal communities for route origin, PoP, region tagging, and control communities for blackhole, propagation, prepending. and path manipulation. - [Internal BGP Communities](/docs/community/internal-communities): Internal BGP communities for AS203314 indicating route origin types, PoP locations, and geographic regions. - [Control BGP Communities](/docs/community/control-communities): Control BGP communities for AS203314 traffic engineering, including blackhole, propagation control, and path prepending. - [PoP Codes](/docs/community/pop-codes): Point of Presence (PoP) codes used in AS203314 BGP communities for location-based routing across 16+ PoPs in Hong Kong, Tokyo, Singapore, Amsterdam, Frankfurt, London, Los Angeles, New York, and more. - [Region Codes](/docs/community/region-codes): Geographic region codes used in AS203314 BGP communities for area-based routing policies across Asia-Pacific, Europe, North America, and Oceania regions. - **Services** - Hats Network Services: Enterprise connectivity services from Hats Network, including managed WAN, dedicated access, performance IP, gaming routes, and media-grade connectivity. - [Hats Network Services](/docs/services): Enterprise connectivity portfolio - Hats EPN, BDL, PUL, GO, and SR. Managed WAN, dedicated access, and performance-optimized routing. - [Hats EPN | SD-WAN as a Service](/docs/services/enterprise-private-network): Hats EPN delivers managed SD-WAN connectivity with traffic segmentation and predictable latency across 16+ PoPs. Multi-site private mesh across 4 continents with 99.99% SLA-backed uptime. - [Hats BDL | Dedicated Internet Access](/docs/services/business-dedicated-line): Hats BDL delivers enterprise-grade dedicated internet access with committed bandwidth (CIR) and flexible BGP handoff. SLA-backed 99.99% uptime with 100% capacity guaranteed across 16+ PoPs. - [Hats PUL | Gaming & Cloud Performance IP](/docs/services/premium-user-line): Hats PUL delivers sub-30ms latency through direct IX peering and intelligent routing. Performance-grade IP connectivity for competitive gaming and low-latency workflows. - [Hats GO - Load Up. Lock In.](/docs/services/gaming-optimized): Hats GO delivers sub-30ms competitive gaming routes through direct IX peering at 16+ PoPs. Optimized network paths for esports tournaments and high-performance gaming with BGP-controlled deterministic routing. - [Hats SR | Media-Grade Connectivity](/docs/services/streaming-ready): Hats SR delivers media-grade connectivity with sustained throughput for4K/8K workflows via direct CDN peering at 16+ PoPs. Consistent bandwidth for professional media delivery and streaming platforms. - Peering: Open peering policy for AS203314. Connect via Internet Exchange, cross-connect, or Layer 2/3 tunnel. - [Peering Policy - AS203314](/docs/peering): Peering policy for AS203314 Hats Network: technical, route-security, operational, and capacity requirements for IX, PNI, and tunnel interconnections. - [Peering via Cross Connect (PNI)](/docs/peering/via-cross-connect): Private Network Interconnect (PNI) peering with AS203314 at supported data centres. Direct Layer 1 connectivity with dedicated VLAN and no shared fabric contention. - [Peering via Tunnel](/docs/peering/via-tunnel): Tunnel-based peering with AS203314 using WireGuard, GRE, GRETAP, and VxLAN. No physical presence required - establish BGP sessions via encrypted overlays from any location. - [Peering via Layer 2 Tunnel](/docs/peering/via-layer2-tunnel): Configure Layer 2 tunnel peering with AS203314 using GRETAP or VxLAN protocols. No physical colocation required - establish BGP sessions over encrypted tunnels from any location. - [Peering via Layer 3 Tunnel](/docs/peering/via-layer3-tunnel): Configure Layer 3 tunnel peering with AS203314 using WireGuard, GRE, or SIT/ip6gre protocols. Encrypted BGP sessions over WireGuard with no physical presence required at any of our 16+ PoPs. - IP Transit: IP-Transit services from Hats Network across Asia and Europe. High-quality bandwidth with diverse upstream connectivity. - [IP Transit Services](/docs/transit): IP-Transit from Hats Network Inc. (AS203314) across 16+ PoPs in Asia, Europe, and North America. Multi-homed via Cogent, NTT, Hurricane Electric, and PCCW Global with up to 200 Gbps committed capacity per location. - [Asia Transit](/docs/transit/asia): IP-Transit from Hats Network Inc. in Hong Kong (50 Gbps, HKIX), Singapore (200 Gbps, Equinix SG), Tokyo (100 Gbps, JPNAP), and Taipei (20 Gbps, STUIX). Intra-Asia latency as low as 15 ms. - [Europe Transit](/docs/transit/europe): IP-Transit in Amsterdam (40 Gbps, AMS-IX, NL-IX) and Frankfurt (100 Gbps, DE-CIX). Intra-Europe RTT from AMS to FRA ~5 ms. Multi-homed via Cogent, NTT, HE, PCCW Global with IPv4/IPv6 dual-stack. - **Resources** - Legal: Legal information and terms of service for Hats Network Inc. - [Legal](/docs/legal): Legal documents and policies for Hats Network Inc. (AS203314) — privacy, terms of service, content and data licensing, abuse reporting, and IP rental. - [Privacy Policy](/docs/legal/privacy-policy): Privacy policy for Hats Network Inc. (AS203314). Learn how we collect, use, and protect your personal information. - [Terms of Service](/docs/legal/terms-of-service): Terms of Service for Hats Network Inc. (AS203314). Essential terms for using our network services. - [Content and Data License](/docs/legal/content-and-data-license): Licensing terms for Hats Network public latency datasets and original documentation. - [Report Abuse](/docs/legal/report-abuse): Please refer to the information on this page if you wish to report any violations relating to Hats Network Inc. (AS203314). This includes spam, DDoS attacks, unauthorised access, and violations of the Acceptable Use Policy (AUP). - [IP Address Rental Terms](/docs/legal/ip-rental): IP Address Rental Terms of Service for Hats Network Inc. (AS203314). Effective June 1, 2024. Usage policies, penalties, and termination conditions. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). - **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.