Identify which layer is failing

Failure to load covers at least four different symptoms. Discussing them together leads to the wrong conclusion, so pin down which one you have before going further.

  1. The entry page will not open

    The domain returns nothing, or returns an error page such as 403 or 502. This layer is about service status and basic connectivity.

  2. The sign-in redirect stalls

    The entry page loads but you stop or loop at the sign-in step. This layer is about browser session, cookies, and redirects; the network is usually secondary.

  3. The signed-in session misbehaves

    You can sign in, but the chat page is blank, keeps loading, or will not send. This layer is about browser state and the service, not the exit IP.

  4. Only one kind of request fails

    Pages work but uploads, image generation, or one task type fails. That is a feature-path problem, unrelated to the network exit.

Three checks that cover most cases

  1. Read the official status page first

    Platform-side degradation is the most common cause and the cheapest to rule out. OpenAI, Anthropic, and Google all publish public status pages.

  2. Compare in a clean browser

    Open the same page in a private window without extensions, or in another browser. If the clean environment works, the problem is extensions, cookies, or local cache, not the network.

  3. Change only the network

    Change one variable and nothing else. If the result changes with it, the exit is a real suspect. If it does not change, stop spending time on the IP.

Per-service differences worth knowing

Entry points and known differences (compiled from public material)
ServiceMain entryClient and web share a path?Known difference
ChatGPTchatgpt.comNoWebsite and app may use different domains and resolution paths
Claudeclaude.aiNoA published country list exists; check region messages against it
Geminigemini.google.comNoRegion limits may come from the account region or Workspace policy
DeepSeekchat.deepseek.comNoA page that will not open and a request that does not respond are different failures
Grokgrok.com and x.comYes (two paths)Both domain paths must work at the same time
Kimikimi.moonshot.cnNoRead the chat path and the file-upload path separately
Doubaodoubao.comNoThe app and the website are not the same path
Qwentongyi.aliyun.comNoThe usable entry depends on your exit region
ChatGLMchatglm.cnNoThe chat product and the open platform use different domains
MiniMaxminimax.io / hailuoai.comNoJudge the product entry and the generation job separately
MiMoDepends on your deployment-Open model: confirm whether you use a hosted or self-run entry

When the exit is actually the suspect

Only when the same page on the same device changes result purely because the network changed is the exit the main suspect. At that point, review its region, ASN, type, and whether IPv4 and IPv6 agree.

If changing the network changes nothing, the cause is on the service, account, browser, or client side. Switching nodes again only costs time and traffic.

What not to do

  • Do not cycle through nodes or proxy rules without a controlled comparison.
  • Do not conclude the whole network is broken because one service fails; check another service first.
  • Do not treat a failure to load as proof of an account restriction; they are different decision chains.
  • Do not skip the status page: platform-side incidents are more common than most people expect.

Sources and evidence limits

Sources below support the stated technical or policy boundary. Diagnostic comparisons in this guide remain observations, not account verdicts.