Geographic availability
Where PredictAsiaX serves live traffic and where it does not. This page describes the technical serving posture — jurisdictional CDN routing, IP-based access controls, terms-of-service scope. It is not a regulatory declaration.
Serving posture
✅ Actively served
- Southeast Asia: Singapore, Malaysia, Thailand, Indonesia, Vietnam, Philippines
- East Asia: Japan, South Korea, Hong Kong, Taiwan
- South Asia: India
- Rest of world (default): Full API + docs access; check local requirements before trading real money
⛔ Blocked at edge
- United States: Blocked at edge. US traders should use a CFTC-registered venue in their jurisdiction.
- Mainland China (PRC): Blocked at CDN edge. Terms of service prohibit access from PRC IPs.
- OFAC / EU / UN sanctions lists: Blocked at edge (Iran, North Korea, Russia, Syria, Cuba, Belarus, etc.). Enforcement runs at every request via CF Workers WAF rules.
- Ontario, Canada: Blocked pending compliance review.
Per-jurisdiction detail
| Jurisdiction | Status | Notes |
|---|---|---|
| 🇸🇬 Singapore | Served | Full functionality. Native locale + priority latency (SIN CF colo). |
| 🇲🇾 Malaysia | Served | Full functionality. Bahasa Melayu locale. |
| 🇹🇭 Thailand | Served | Full functionality. Thai locale. |
| 🇮🇩 Indonesia | Served | Full functionality. Bahasa Indonesia locale. |
| 🇻🇳 Vietnam | Served | Full functionality. Tiếng Việt locale. |
| 🇵🇭 Philippines | Served | Full functionality. Filipino locale. |
| 🇯🇵 Japan | Served | Full functionality. 日本語 locale + JGB / BOJ / TOPIX markets prioritized. |
| 🇰🇷 South Korea | Served | Full functionality. 한국어 locale + K-pop / KOSPI markets prioritized. |
| 🇭🇰 Hong Kong | Served | Full functionality. 粵語 + 繁體中文 locales. Hang Seng markets prioritized. |
| 🇹🇼 Taiwan | Served | Full functionality. 繁體中文 locale. |
| 🇮🇳 India | Served | Full functionality. हिंदी + English locales. IPL / T20 markets prioritized. |
| 🇦🇺 Australia | Served | Full functionality. BBL cricket markets prioritized. Check local requirements before trading. |
| 🇺🇸 United States | Blocked | CF WAF rule blocks all US-origin traffic to trading endpoints (api.predictasiax.com/v1/orders, /v1/portfolio). Docs remain readable. Use a CFTC-registered venue for onshore access. |
| 🇨🇦 Canada (Ontario) | Blocked | ON-only block. Rest of Canada remains accessible. |
| 🇨🇳 China (mainland) | Blocked | All PRC IPs blocked at edge, including Hong Kong-registered residents accessing from mainland. |
| 🌐 EU / EEA | Docs only | Docs + read-only markets. Trading endpoints require KYC review pending EU compliance evaluation. |
| 🇬🇧 United Kingdom | Docs only | Docs + read-only. Trading pending FCA-permitted mode. |
| 🇮🇷 🇰🇵 🇷🇺 🇸🇾 🇨🇺 🇧🇾 | Blocked | OFAC / EU / UN sanctions. |
How enforcement works
Access is decided at the CDN edge (Cloudflare Worker + WAF rules) before your request reaches any application logic. Enforcement inputs:
- IP → Country: MaxMind GeoIP resolved by CF at connection time. Result available via
CF-IPCountryheader. - ASN check: Certain sanctioned or high-risk ASNs blocked regardless of country.
- Sanctions-list ETL: OFAC SDN, EU consolidated, UN 1267 lists imported daily. Blocked IPs marked at edge.
- User-declared jurisdiction: On builder application, declared jurisdiction is snapshotted in
builders.jurisdiction. Serving continues to check both IP and declared value on every request. - VPN detection: We do not aggressively block commercial VPN exits, but we do log VPN-flagged requests to
complianceevents for later review. Repeated jurisdiction spoofing triggersabuse_flags.
What a blocked user sees
A blocked user gets an HTTP 451 (Unavailable For Legal Reasons) with a short message + link back to this page. Docs (docs.predictasiax.com) remain readable from most blocked regions for research purposes — the block hits predictasiax.com trading UI and api.predictasiax.com trading endpoints only.
If you move to a served jurisdiction
Serving is per-request based on live IP. Moving to a served country restores access immediately — no application update. The builders.jurisdiction field on your builder profile is separate: if you move permanently, update it via PATCH /v1/builders/me so attribution + payouts align with the new address.
See also: API Terms · Asia-Native Markets · Tier Progression