The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A “Request timed out” message means ChatGPT did not finish the request before a browser, app, network, proxy, or OpenAI service timeout. It does not prove that ChatGPT is down.
First, check status.openai.com. If no ChatGPT incident is listed, wait 30–60 seconds, select Stop generating and then Regenerate, and try the prompt in a new chat. If it works on a phone hotspot but not Wi-Fi, your network, VPN, proxy, DNS filter, firewall, or WebSocket connection is the leading suspect.
What “Request timed out” means
ChatGPT started, or attempted to start, a request but no complete response arrived within the allowed time. The timeout can occur at several layers:
- OpenAI’s ChatGPT service or a particular model
- The web browser or native app
- Your home, school, or company network
- A VPN, proxy, secure web gateway, or firewall
- A blocked or interrupted streaming/WebSocket connection
OpenAI’s help documentation describes related symptoms such as slow responses, endless spinning, interrupted generation, network errors, and WebSocket errors rather than one universal timeout code. The exact wording and buttons can vary by platform and app version. See OpenAI’s error-message guidance.
#1 Best Overall
A timeout is different from an authentication failure, account restriction, rate-limit notice, or a generic “Something went wrong” message. Those errors require different remedies.
Check whether ChatGPT is down
Open status.openai.com and look specifically for a ChatGPT incident, not only an API incident. On August 18, 2026, the page reported that services were fully operational and that OpenAI was not aware of a system-wide issue.
A green status does not rule out a regional connectivity problem, an account- or model-specific failure, a corporate firewall, or a broken browser session. The status page reports aggregate availability, and individual availability can vary by subscription tier, model, and feature.
If an incident is listed
Retry later and monitor the incident. Local cache cleanup or DNS changes cannot repair a confirmed platform outage. If the service is partially available, a new chat or another model may still work.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
Fast fixes, in the right order
- Wait 30–60 seconds. A slow response may still complete.
- Stop and regenerate. Select Stop generating, then Regenerate. If it fails again, do not keep retrying the same stuck turn.
- Start a new chat. Send the same prompt in a blank conversation. Long conversations with many turns can become sluggish or fail.
- Refresh or restart. In a browser, hard-refresh with
Ctrl + Shift + Ron Windows/Linux orCmd + Shift + Ron macOS. Fully quit and reopen the desktop or mobile app. - Sign out and back in. This refreshes an expired or corrupted session after a normal refresh has failed.
These steps test different scopes: regeneration tests the current response, a new chat tests conversation state, and a refresh tests the browser or app session.
Use a private window to isolate browser problems
Open ChatGPT in an incognito or private window. If the timeout disappears, an extension, cookie, cached site data, or damaged browser profile is likely involved.
- Disable extensions that modify pages or traffic, including ad blockers, script blockers, privacy tools, and security extensions.
- Retry ChatGPT.
- If it works, re-enable extensions one at a time to identify the conflict.
- Clear ChatGPT site data or cookies, sign in again, and retest.
- Try another browser or a fresh browser profile.
Clearing ChatGPT site data does not delete your account conversations stored by the service, but it will sign you out and remove local session data. OpenAI recommends clearing site data or cookies when blank, frozen, or endlessly loading pages continue: error-message guidance.
Test another device or network
Use a phone hotspot or cellular connection, and compare the result with your usual Wi-Fi.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #3
| Test result | Most likely scope | Next action |
|---|---|---|
| Works on hotspot, fails on Wi-Fi | Router, DNS filtering, VPN, proxy, firewall, TLS inspection, or WebSocket blocking | Disable your own VPN temporarily; ask the network administrator to review filtering and allowlist rules. |
| Fails on Wi-Fi and cellular | Browser/app session, account, model, or OpenAI-side problem | Try a private window, another model, and another device; collect diagnostics if reproducible. |
| Works in browser, fails in app | App version, app cache, certificate, or device configuration | Update, force-close, relaunch, and use the browser as a temporary workaround. |
| Works for another person on the same network | Your device, browser, account, or session | Repeat the private-window and sign-out tests on your device. |
OpenAI recommends comparing company Wi-Fi with a cellular hotspot for this exact network-versus-client diagnosis: network recommendations.
Check whether one chat, model, or account is affected
Run four controlled tests: a brand-new chat, a shorter prompt, another available model, and the same account in a private window or on another device. OpenAI’s slow-response guidance recommends switching models and starting a new chat to determine the scope: slow-response guidance.
- Only one long conversation fails: conversation size or corrupted session state is plausible. Move the necessary context into a new chat.
- Only one model fails: that model may have temporary capacity or availability trouble. Use another model and check status later.
- Every model and chat fails: investigate the account, browser, network, or service.
- Only one device fails: local software, certificates, extensions, or app data are the leading suspects.
Fix VPN, proxy, DNS, firewall, and WebSocket interference
A normal web page can load while response streaming fails. ChatGPT conversation updates use the secure WebSocket destination wss://ws.chatgpt.com over TCP port 443, and the proxy or firewall must permit the WebSocket Upgrade handshake. A device that allows ordinary HTTPS pages but closes WebSocket connections early can produce stalls and timeouts.
On a personal network
- Temporarily turn off a VPN, proxy, secure-DNS filter, web-protection feature, or privacy extension, then test again.
- Restart the router if other devices show the same failure.
- Do not change DNS providers as a default fix; managed devices may prohibit it, and the cause may instead be filtering or WebSocket handling.
On a company or school network
Ask IT to review OpenAI’s current allowlist and permit the required WebSocket traffic. OpenAI lists domains including:
Rank #4
*.auth.openai.com*.chatgpt.com*.openai.com*.oaistatic.com*.oaiusercontent.comchat.openai.com
The complete, current list and WebSocket requirements are in OpenAI’s network recommendations. Cisco Umbrella, Zscaler Internet Access, Symantec Cloud Secure Web Gateway, McAfee Web Gateway, Sophos Firewall, Barracuda Web Security Gateway, and Fortinet FortiGuard URL Filtering are examples of infrastructure that may inspect or filter traffic; their presence does not by itself prove a vendor defect. Do not disable corporate security controls without authorization.
Mobile and desktop app checks
- Update the official ChatGPT app.
- Force-close it and relaunch.
- Sign out and sign in again.
- Disable a VPN and test on cellular data.
- Open ChatGPT in a browser on the same device.
- Reinstall only as a later step, after preserving any local information you need.
On macOS, TLS/SSL inspection by a managed network can cause certificate or network-configuration errors. If the app is blocked, the web version may work temporarily; see OpenAI’s network guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to contact OpenAI Support
Escalate when the timeout is reproducible across multiple browsers, a private window, more than one device, and both Wi-Fi and cellular; affects multiple chats or models; continues after the status page returns to normal; or affects a paid or workspace account.
Use the chat bubble at the bottom-right of help.openai.com. Include:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsBest Value
- Exact error text, date, time, and time zone
- Browser or app and version, operating system, device, and network type
- Whether a VPN or proxy was active
- Model used, conversation URL or ID, and reproduction steps
- Screenshots or a screen recording
- Relevant request or completion IDs, when available
Never send passwords or one-time codes, and remove unnecessary personal information.
Capture a sanitized HAR file (browser only)
- Open Developer Tools with
Ctrl + Shift + Ion Windows/Linux orCmd + Option + Ion macOS. - Select Network and enable Preserve log.
- Clear the existing log, reproduce the timeout, then use the export control and choose Export HAR (sanitized).
- Review the file for sensitive data before attaching it.
OpenAI’s Support article says HAR attachments are limited to 25 MB and that the desktop app currently does not provide Developer Tools for HAR capture: Support guidance.
ChatGPT website/app timeout versus OpenAI API timeout
This guide covers the ChatGPT website and apps. If your own program reports a request timeout while calling the OpenAI API, investigate client timeout settings, proxy or load-balancer behavior, request IDs, and API service health instead. OpenAI’s API troubleshooting guidance explains that a request missing from service-health data may not have reached OpenAI because it failed upstream: API timeout troubleshooting.
Quick Recap
What not to do
- Do not assume a timeout proves an OpenAI outage.
- Do not repeatedly retry a single stuck conversation.
- Do not upload an unsanitized HAR file publicly.
- Do not disable corporate security software without IT approval.
- Do not install third-party “ChatGPT repair” tools or pay for a VPN before testing a hotspot.
- Do not delete a conversation before checking whether only that conversation is affected.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




