Grok egress and connectivity
Compare public connectivity and egress for Grok. Distinguish grok.com from api.x.ai and consult the relevant official information.
Grok: identify the entry point
Grok on the web, Grok on X and the developer API are different entry points. The official status site links product and API destinations. Identify the entry point involved instead of extending one domain’s response to every product.
Choose the next check for your symptom
If the Grok website and API behave differently, record each target and time, then inspect official incidents and DNS/certificate observations separately. API authentication errors require the developer console.
Record the current exit, measurement time and readable sources. Start with light connectivity checks, then use domain or persistent-connection checks when needed. Retest after changing one setting.
What these observations do not validate
This site does not log into your account or run paid model requests. Official status information describes service scope. No matching incident, or a successful public probe, does not guarantee account access or a particular application request.
Related tools and guides
Live measurements run in your browser after JavaScript loads. This introduction contains no visitor detection results.