Is Grok (xAI) down?

Understanding Grok (xAI) availability

Grok access can fail at several points: the web service at grok.com, the xAI API at api.x.ai, your sign-in or account session, or the connection between your device and the service. Similar symptoms can result, including blank pages, sign-in loops, timeouts, refused connections, DNS errors, and failed API requests.

The official xAI status page is the best first check for a provider-reported incident. A clear status page does not rule out an isolated account problem, stale browser data, DNS failure, VPN or proxy interference, regional connectivity trouble, or an invalid or unauthorized API request.

Use the scope of the failure to guide the diagnosis:

• The web service and API fail across separate networks: a broader xAI service problem becomes more likely.
• Only the web service fails: investigate the browser session, extensions, sign-in state, or web access.
• Only API requests fail: inspect the endpoint, credentials, permissions, request format, and account configuration.
• Only one device or network fails: prioritize local DNS, firewall, VPN, proxy, browser, or ISP troubleshooting.

A status page describes reported provider conditions; it does not validate a particular account, browser session, network path, or API request.

Troubleshooting Grok (xAI)

1. Check for a provider incident

Open the official xAI status page and look for an active incident or degradation affecting the relevant service. If an incident is reported, local browser changes are unlikely to restore access. Wait for the provider to report recovery, then retry periodically.

If no incident is listed, continue with the scope tests below. An unlisted problem may be isolated, newly developing, or limited to the web service, API, account, or network.

2. Separate web access from API access

• Grok web access fails but API requests work: Try a private window, another browser, or another device. Focus on cookies, extensions, login state, and web-specific access.
• API requests fail but Grok works in the browser: Review the API response, endpoint, credentials, permissions, request body, selected model or resource values, and account configuration. Browser availability does not validate an API request.
• Both paths fail: Test from a second network or device and check the status page. Failure across independent connections makes a provider-side problem more plausible.

3. Check browser and account-session problems

For a blank page, sign-in loop, stale content, or unexpected web error:

1. Refresh once, then try a private browsing window.
2. Temporarily disable extensions that modify scripts, privacy controls, or network requests.
3. Clear site data for the affected service if the session appears stuck.
4. Sign in again through the normal Grok web address.
5. Try another browser or device.

If another account or device works on the same network, the problem may be limited to the original account session or device rather than a general outage. Do not share passwords, session cookies, or account tokens while asking for help.

4. Investigate network and DNS errors

For a DNS failure, connection refusal, or timeout, test another network such as mobile data. Compare the result without changing several network settings at once. If the service works elsewhere, investigate the local DNS resolver, firewall, VPN, proxy, router, or ISP filtering.

Do not bypass an SSL or certificate warning. Confirm the address, system date and time, browser updates, VPN or proxy settings, and any network security inspection before continuing. For repeated connection failures, record the exact browser error instead of repeatedly refreshing.

5. Diagnose xAI API failures

Record the HTTP status, response body, request time, endpoint, and whether the same request fails from another environment. Then check authentication, permissions, request formatting, selected model or resource values, and account settings.

Treat common categories differently: authentication or permission responses point toward credentials or access configuration; malformed-request responses point toward the request; rate-limit responses point toward request volume or account limits; and gateway or server responses may indicate an upstream service problem. The exact response body should guide the next step.

Change one suspected variable at a time. Redact API keys, authorization headers, personal data, and unredacted request logs before sharing them. If a valid request fails consistently from separate networks and the status page reports an incident, a provider-side cause is more likely.