CodePen help and reporting
Use CodePen support for platform/editor issues; isolate third-party resources in a minimal Pen.
Live Domain Check
Is CodePen Down? Check codepen.io Status and Outages
Run a live reachability check for codepen.io. Compare the regional responses with the problem you see in CodePen.
Find CodePen 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
Is CodePen working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding CodePen connection and service problems
A CodePen editor, preview frame and third-party resource can fail independently.
The checker above requests codepen.io from eight configured locations and shows the responses and measurement times. Compare those observations with the actual CodePen action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
CodePen official website and help
Open codepen.io
Open the website in your browser and compare it with the result above.
Where to report problems with CodePen
Open CodePen help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Pen link, editor/preview action, browser and first error, keeping private code private.
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 CodePen.
What to check when CodePen is not working
These are troubleshooting comparisons, not claims that CodePen is currently experiencing a particular incident.
Start with the action that failed
Keep the source and compare a minimal Pen without external dependencies with the affected Pen.
Narrow down the affected service
Inspect the preview's first error and failed external URL; use CodePen support for editor/account issues.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests 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 CodePen is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the codepen.io check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open CodePen help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If CodePen Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when CodePen seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open codepen.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 CodePen issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting CodePen support.
Frequently asked questions about CodePen problems
Is CodePen down, or is the problem limited to one feature?
Run the codepen.io check and compare its original timestamps and responses with your actual error. A CodePen editor, preview frame and third-party resource can fail independently.
Where can I report a problem with CodePen?
Use the community buttons on this page to share whether the service works for you. For help from CodePen, use the official help/reporting resource linked above. Use CodePen support for platform/editor issues; isolate third-party resources in a minimal Pen.
What should I check first when CodePen is not working?
Keep the source and compare a minimal Pen without external dependencies with the affected Pen. Inspect the preview's first error and failed external URL; use CodePen support for editor/account issues.
What information helps CodePen support investigate?
Pen link, editor/preview action, browser and first error, keeping private code private.