Claude Troubleshooting Checklist: What to do when the page keeps spinning, messages fail to send, or verification gets stuck

The most annoying thing about using Claude isn’t that it answers slowly—it’s when the page keeps spinning, messages won’t send, or verification keeps getting stuck. Below is a Claude troubleshooting flow in the order of “first confirm external causes—then handle the browser—finally check the account,” which should help you pinpoint most common issues. Each step is short, but it’s best to follow them in order—don’t start by repeatedly refreshing.

First rule out server-side fluctuations: don’t brute-force it during an outage

The first step in Claude troubleshooting is to check whether Anthropic’s status page (status.anthropic.com) is showing an active incident, especially for login, chat, and file-related components. If the status is abnormal, clearing your local cache likely won’t restore things immediately—you’ll need to wait for the official fix. In the meantime, try to reduce frequent retries to avoid triggering stricter risk controls or rate limiting.

Blank page / endless loading: usually cache, extensions, or network blocking

If Claude opens to a blank screen or loads endlessly, test in an incognito window first; if it works in incognito, it’s almost certainly caused by extensions or site data. Next, clear cookies and cache for that site (only Claude-related data is enough), and temporarily disable ad blockers, script managers, and privacy/anti-tracking extensions. On the network side, if you’re using a proxy or an enterprise gateway, requests may be blocked—switching to a mobile hotspot or home network is often a quick way to verify the source.

Message send failure / error and retry: check rate limits and blocked requests

When Claude shows “Send failed” or “Something went wrong,” first try sending a shorter input once—failures are more common with long text, pasting large amounts of content, or high-frequency multi-turn chats. Then consider whether repeated rapid clicks on retry have triggered rate limiting; waiting a minute or two before sending again is usually more stable. If you’re on a corporate network, some security software may block WebSocket or cross-origin requests; this is very common in Claude troubleshooting, and switching networks is the fastest way to confirm.

Verification stuck / repeated login: often related to time, device, and risk controls

If the verification keeps spinning or repeatedly asks you to verify, first make sure your system time and time zone are set to sync automatically (time drift can cause verification to fail). Then, in “logged-in devices,” sign out of other infrequently used sessions, and operate using only one browser window to avoid triggering risk policies from multiple simultaneous sessions. If you still can’t pass after multiple attempts, stop tinkering and submit a support ticket via the official help center, clearly including error screenshots, browser version, and network environment details—this often resolves the Claude troubleshooting process faster than blind retries.