AI service network diagnostics

ChatGLM Entry Check: Chat, API & IP Risk

Check ChatGLM chat and open-platform entry paths separately, review region, ASN, proxy risk, and IPv4/IPv6 exits, and keep network evidence separate from API, account, and quota eligibility.

Locate region
  1. Parse IP
  2. Locate region
  3. Match ASN
  4. Check proxy / VPN / Tor
  5. Check risk lists
  6. Summarize AI access

ChatGLM access diagnosis

Live check
Checking

Checking

Public endpoint reachability
Checking
Measured from this browser
Access conditions reference
Checking
Reference based on public information
Exit network type
Checking
Current exit profile
Risk note
Checking
Based on exit network signals
Current exit IPCheckingCollecting network profile…

AI Availability

Live check on this network
Checking
Checking
Checking
Checking
Checking
How to read this check

ChatGLM: Chat Product and Open Platform Use Different Domains

Zhipu's consumer chat product and its developer open platform run on different primary domains. On networks that allow traffic by domain, only one side may be reachable.

Identify which side you are using

Corporate networks, campus networks, and some security software allow traffic by domain. When only one primary domain is allowed, the chat product may work while the open platform fails, or the other way around. Test each one.

Direct access is the expected path

Zhipu serves users in mainland China, where direct access is normal. An overseas data-center or proxy exit does not improve access and tends to add failures, so rule out proxy rules first.

Connectivity is not the same as API access

Connectivity only shows that a public resource can load. API calls can still fail because of keys, quota, or model permissions. Those are account-level conditions and fall outside IP and network checks.

ChatGLM Guides