AS18186 - GeoIP Technical Specification

1. Core ASN & Global Physical PoP Information

Country/Region Code	City	Data Center	Technical Note
HK (Hong Kong, China)	Tseung Kwan O	MEGA-i (Netfrontier) Data Center	Verified via PeeringDB & on-site inspection
SG (Singapore)	Singapore	EQ-SG1 (Equinix) Data Center	Equinix Singapore IBX, PeeringDB Facility ID verified
JP (Japan)	Tokyo	EQTY8 (Equinix) Data Center	Equinix Tokyo TY8 IBX, global peering capability enabled
TW (Taiwan, China)	Taipei	(Specify Data Center Name if available)	Regional PoP for Chinese Taiwan market, verified via internal deployment records
US (United States)	Los Angeles	Coresite Data Center	North America core PoP, no detailed physical address disclosed

                ⚠️ GeoIP Positioning Principle: Only based on physical server/network equipment location of each PoP, irrelevant to upstream ISP, customer origin or service direction. Each IP prefix is mapped to its corresponding deployed PoP.
            

2. RFC 8805 Compliant GeoFeed (Multi-PoP Support)

Official GeoFeed URL (HTTPS, No Auth, No Redirect):
https://geo.nebulaglobal.com/geofeed.csv

2.1 File Specification

File Name: geofeed.csv
Encoding: UTF-8 (without BOM)
Line Ending: Unix LF (\n), not Windows CRLF (\r\n)
Cache Policy: max-age=86400 (24 hours)
HTTP Status Code: 200 OK (permanent, no redirects)
Coverage: All IP prefixes of AS18186 (Hong Kong/Singapore/Japan/Taiwan/Los Angeles PoPs)

2.2 Field Definition (RFC 8805 Standard, Multi-PoP Example)

prefix,country_code,region,city,postal_code
# Hong Kong, China (MEGA-i)
38.182.224.0/24,HK,Hong Kong,Tseung Kwan O,
38.182.227.0/24,HK,Hong Kong,Tseung Kwan O,
38.182.138.0/24,HK,Hong Kong,Tseung Kwan O,
# Singapore (EQ-SG1)
103.21.xx.0/24,SG,Singapore,Singapore,
103.22.xx.0/24,SG,Singapore,Singapore,
# Japan (EQTY8)
133.186.xx.0/24,JP,Tokyo,Tokyo,
157.78.xx.0/24,JP,Tokyo,Tokyo,
# Taiwan, China
140.xx.xx.0/24,TW,Taiwan,Taipei,
# United States (Coresite, Los Angeles)
198.xx.xx.0/24,US,California,Los Angeles,
... (full list available in official GeoFeed URL)
            

2.3 Technical Validation Commands

# Check HTTP status and response headers
curl -I https://geo.nebulaglobal.com/geofeed.csv

# Verify file encoding and content format
curl https://geo.nebulaglobal.com/geofeed.csv | file -

# Ensure no UTF-8 BOM (no leading 0xEF 0xBB 0xBF)
hexdump -C <(curl -s https://geo.nebulaglobal.com/geofeed.csv) | head -1

# Verify multi-PoP content coverage
curl -s https://geo.nebulaglobal.com/geofeed.csv | grep -E "HK|SG|JP|TW|US"
            

3. RIR Official Declaration

The GeoFeed URL (covering Hong Kong/Singapore/Japan/Taiwan/Los Angeles PoPs) has been added to the WHOIS/IRR record of AS18186 in the corresponding Regional Internet Registry (RIR):

RIR: APNIC (covers Hong Kong/Singapore/Japan/Taiwan IP allocations) & ARIN (covers United States IP allocations)
Added Field: geofeed: https://geo.nebulaglobal.com/geofeed.csv
Verification Method: Query AS18186 via APNIC Whois and ARIN Whois

4. Maintenance & Update Process (Multi-PoP Synchronization)

When adding/removing IP prefixes for any PoP (Hong Kong/Singapore/Japan/Taiwan/Los Angeles) of AS18186, update geofeed.csv first (no Nginx restart required, immediate effect)
Synchronize the updated multi-PoP prefix list to PeeringDB and corresponding RIR WHOIS records within 24 working hours
Monitor GeoFeed URL availability 24/7 (alert on HTTP 4xx/5xx status codes via Zabbix/Prometheus)
Announce critical multi-PoP changes to major GeoIP vendors via official correction channels if necessary
Quarterly review of GeoFeed data consistency (cross-verify Hong Kong/Singapore/Japan/Taiwan/Los Angeles PoP mappings) and compliance with RFC 8805 updates

5. Contact & Technical Support

NOC (24/7 Technical Support): noc@nebulaglobal.com
Peering & Interconnection: peering@nebulaglobal.com
GeoFeed Update Frequency: Real-time for IP prefix changes (any PoP), quarterly formal multi-PoP data review

AS18186 - Official GeoIP Technical Specification