Skip to main content
replit.health
GitHub Codespaces

Is GitHub Codespaces down? Live status

Container-based dev environments from GitHub

Live GitHub Codespaces reachability — the container-based dev environment tied to GitHub, checked from your browser against public GitHub surfaces.

GitHub Codespaces uptime can be verified by checking GitHub's status page and testing web connectivity to active dev container sessions. If Codespaces fails to load, common causes include browser cookie misconfigurations, regional datacenter outages, organizational policy restrictions, or active GitHub service disruptions.

GitHubCodespaces API Status

Live, in-browser checks against GitHubCodespaces's public APIs. Refreshes every 15s.

Checking…

Reachability

DNS / TCP / TLS for GitHub Codespaces surfaces

3 endpoints
  • GitHub
    github.com root
    —ms
    warming up
  • Codespaces host
    github.com/codespaces
    —ms
    warming up
  • GitHub API
    api.github.com base
    —ms
    warming up
Polling every 15s · Last updated — · Next in 15sOpen GitHubCodespaces ↗

Codespaces runs inside github.com; there is no dedicated public API for browser-based reachability. These checks confirm GitHub's surfaces are up. Container start failures and region incidents show on GitHub's official status page.

Sponsored · GitHub Codespaces
Ask Cody
Cloud dev · GitHub

I'm Cody — your GitHub Codespaces helper. Ask about dev containers, machine sizes, prebuilds, or free tier.

Open Codespaces

Sponsored content. replit.health may earn a referral reward when you sign up via this widget. Answers are informational only — not financial or engineering advice.

About GitHubCodespaces

GitHub Codespaces spins up a full VS Code dev environment inside a container tied to a GitHub repo. Because the surface lives at github.com, its availability tracks GitHub itself — but container start times and region routing add extra failure modes on top.

GitHubCodespaces at a glance

Launched
2020 (GA 2021)
Parent
GitHub (Microsoft)
Runtime
Dev container (OCI image)
Free tier
60 core-hours/month (personal)
Regions
Multi-region (auto-selected)

Common GitHubCodespaces issues

  • Container start timeout

    Custom dev containers can time out at build. Push a simpler devcontainer.json or use a prebuild to cache heavy setup.

  • Port forwarding not working

    Private forwarded ports require signed-in access. Mark the port Public in the Ports tab or share the URL from an authenticated session.

Background

GitHub launched Codespaces in 2020 as a browser-based VS Code environment powered by cloud containers. It went generally available in 2021 and became a core piece of GitHub's developer experience story after the Microsoft acquisition.

Frequently asked

How do I know if GitHub Codespaces is down?
Check the official GitHub Status dashboard at githubstatus.com or use replit.health to test live reachability. If public GitHub API services or Codespaces containers fail to respond, an outage is likely occurring.
Why is my GitHub Codespaces stuck on loading?
A stuck Codespace usually indicates container build failures, network timeout issues, or corrupted devcontainer configurations. Rebuilding the container or launching from a different region often resolves transient loading stalls.
Is Codespaces down or is it my network?
If githubstatus.com reports green but your Codespace fails, check your local firewall, VPN, and corporate proxy settings. WebSocket connections on standard ports are required for Codespaces terminal communication.
Is GitHub Codespaces down right now?
Green dots on github.com and api.github.com mean the front doors are reachable. Codespaces-specific incidents (container start failures, region outages) are reported on GitHub's status page.
Why is my Codespace stuck on 'Starting'?
Most stuck starts are region-level capacity issues or a prebuild that hasn't finished. Try a smaller machine type or a different region.

Learn more

About this check

All data is provided on a best-effort basis with no guarantees about accuracy or availability. This is an unofficial status page and is not affiliated with, endorsed by, or sponsored by GitHubCodespaces.

Checks run client-side from your browser against GitHubCodespaces's public endpoints. Latency reflects your network path, not the server's health alone. See our resources for more on how to read these checks.