CodeSandbox service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Is CodeSandbox Down? Check codesandbox.io Status and Outages
Run a live reachability check for codesandbox.io. Compare the regional responses with the problem you see in CodeSandbox.
Find CodeSandbox help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Understanding CodeSandbox connection and service problems
The CodeSandbox dashboard, development environment and application running inside it are separate layers.
The checker above requests codesandbox.io from eight configured locations and shows the responses and measurement times. Compare those observations with the actual CodeSandbox action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
CodeSandbox status information and official help
CodeSandbox help and reporting
Distinguish workspace startup from the application running inside it.
Open codesandbox.io
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Where to report a CodeSandbox problem
Distinguish workspace startup from the application running inside it.
Open CodeSandbox help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Include these details in a CodeSandbox report
Sandbox/project, environment type, failed command, log excerpt and timestamp with secrets removed.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to CodeSandbox.
What to check when CodeSandbox is not working
These are troubleshooting comparisons, not claims that CodeSandbox is currently experiencing a particular incident.
Start with the action that failed
Identify whether the workspace cannot start or the app starts and fails on one command.
Narrow down the affected service
Compare the environment/build log with a minimal project before restarting repeatedly.
Read the actual checker response
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if CodeSandbox is down: a step-by-step workflow
- Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
- Run the codesandbox.io check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
- Compare the relevant provider information. Open CodeSandbox status and check whether the named service and incident time fit your error.
- Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.
If CodeSandbox Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when CodeSandbox seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open codesandbox.io in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader CodeSandbox issue.
3. Compare permitted network paths
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting CodeSandbox support.
Frequently asked questions about CodeSandbox problems
Is CodeSandbox down, or is the problem limited to one feature?
Run the codesandbox.io check and compare its original timestamps and responses with your actual error. The CodeSandbox dashboard, development environment and application running inside it are separate layers.
Where can I report a problem with CodeSandbox?
Use the official help/reporting resource linked above. Distinguish workspace startup from the application running inside it.
What should I check first when CodeSandbox is not working?
Identify whether the workspace cannot start or the app starts and fails on one command. Compare the environment/build log with a minimal project before restarting repeatedly.
What information helps CodeSandbox support investigate?
Sandbox/project, environment type, failed command, log excerpt and timestamp with secrets removed.