Network & access
The website being unreachable doesn't mean the API is down — they use different entry points; debug them separately.
Debug order
- 1Test the API first: curl verification across the route hosts in turn (api → main site → jp). If any works, carry on.
- 2Then test the web page: another browser / private window / network. If only the page is slow, API calls are unaffected.
- 3Check local proxy and DNS: proxy rules may only allow some domains — allow every route host.
- 4Nothing works: contact support with the time, region, network type and error screenshots.
Symptom table
| Symptom | Diagnosis |
|---|---|
| Page unreachable, curl works | The web entry is affected by your network; the API is fine — keep calling |
| One route times out, others work | Just swap the Base URL host (one config change in your client) |
| No route connects at all | Check local network / proxy first, then ask support about service status |
Service region restrictions: account & compliance.