What is GitHub Codespaces current status?

GitHub Codespaces is currently operational. You can check GitHub Codespaces status and current incidents and outages on the top of the page. The status is updated in almost real-time, and you can see the issues affecting customers.

Is GitHub Codespaces down today?

GitHub Codespaces was not down today according to the official status page. In the last 24 hours, there were 0 outages reported. IsDown continuously monitors the GitHub status page, looking for the latest outages and issues affecting customers. Check all recent outages in the section 'Latest GitHub Codespaces outages, issues and problems' at the top of the page.

When was the last GitHub Codespaces outage?

GitHub Codespaces last outage was on April 23, 2025 with the title "Incident with Issues, API Requests and Pages"

How to monitor or check GitHub Codespaces status?

You can use IsDown service or go to GitHub official status page. Some accounts also use Twitter to communicate the status.

How can I be notified when GitHub Codespaces is having issues?

You can create an account in IsDown and monitor multiple services or subscribe for updates on the official status page. IsDown will send you a notification in real-time when GitHub Codespaces has issues. GitHub official status page might also offer notification options such as email, SMS, or Slack.

GitHub Codespaces status - Is GitHub Codespaces Down? Current Outages & Updates

GitHub Codespaces user-reported issues in the last 24 hours

This chart displays the number of user-reported GitHub Codespaces problems over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.

Third-party monitoring

Stop Juggling Dozens of Status Pages – Monitor Them All in One Place

Monitoring 4000+ third-party services in real-time

Get custom alerts via Slack, Teams, Datadog, etc.

Create public or private status pages

Start Free Trial

14-day free trial · No credit card required

Trusted by thousands of teams

GitHub Codespaces outage history

IsDown has tracked 99 incidents for GitHub Codespaces since started monitoring GitHub downtimes in April 2020. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

Apr 23 2025

Incident with Issues, API Requests and Pages

16 days ago · lasted 44 minutes

We are investigating reports of degraded performance for API Requests, Issues and Pages
Apr 11 2025

Incident with Codespaces

29 days ago · lasted 25 minutes

We are investigating reports of degraded availability for Codespaces
Mar 21 2025

Incident with Codespaces

about 2 months ago · lasted about 1 hour

We are investigating reports of degraded performance for Codespaces
Feb 16 2025

Disruption with some GitHub services

3 months ago · lasted 37 minutes

We are investigating reports of degraded performance for Actions, Codespaces, Git Operations, Issues and Webhooks
Feb 14 2025

Disruption with some GitHub services

3 months ago · lasted about 8 hours

We are currently investigating this issue.
Apr 2020 ...

IsDown started monitoring GitHub status

We've tracked and collected 99 incidents for GitHub Codespaces since started monitoring GitHub status

Latest user comments about GitHub Codespaces issues

M

Max

10 days ago

The main page is broken and the actual code space won't even load. I tried restarting my device, tweaked the internet settings, and a lot of other things but it still wouldn't load.
G

Gary

15 days ago

Unable to connect to codespaces
M

Michael

22 days ago

The codespaces are not loading
C

cindy

22 days ago

Codespaces is not connecting
M

Matei

22 days ago

Page not loading Console: Uncaught SyntaxError: expected expression, got '<'
H

Henry

23 days ago

I'm locked in a "Setting up your codespace" screen
D

David

about 1 month ago

I can't connect to some of my codespaces.
S

sila

about 1 month ago

codespace is not connecting
M

Mike

about 1 month ago

Codespaces give an error when trying to load
A

Amanda

about 2 months ago

I can't get my codespace to load, it's stuck on the setting up remote connection loading bar (internet is working for all other sites)
C

CurrentUser

about 2 months ago

Connection errors, multiple times, many days a week. Almost always at around this hours. They should fix this
A

Andrew

2 months ago

My GitHub codespace gets stuck while building on both my local Visual Studio Code and when I open it in the browser. On VS Code, the bottom right corner toast message says "Setting up remote connections: Building codespace...". The bar is half finished, but it has stopped and hasn't gone any furt...
Z

Zack

3 months ago

Spontaneous prompts codespace restart, remote connection stalls on set up.
M

Mathew

3 months ago

Codespaces is stopping after a few minutes running and needs to be restarted to work. Multiple users at company experiencing issue.
T

tristan

3 months ago

502 Bad Gateway on my codespace link
I

Ilia

4 months ago

It displays "Stopping codespace..." and does nothing. Tried from diffrenet machines.
P

Padmanathan

5 months ago

I am unable to connect to GitHub codespaces
J

Jose

6 months ago

I'm trying to open a codespaces but it's freezing in the "Setting up your codespaces" view
L

L

6 months ago

Codespaces are down for a large number of users currently despite apparent "operational" greenlight on the github status page. The issue has been reported to them.
A

arvin

7 months ago

it says the code space is not available
A

abhinav

7 months ago

codespace is continuously loading
O

Omar

7 months ago

It’s says setting up remote connection but is slow and doesn’t connect
S

Stevo

7 months ago

it's loading forever in any browser. I see it in my Codespaces but all I get is Setting up remote connection: Connecting to codespacem
A

Anna

7 months ago

It keeps stopping randomly and wont start.
T

Travis

8 months ago

my codespace started saying that i need to reload the repository then after i reloaded it, it does the usual booting up "setting up" and it just get stuck there.
S

Samella

8 months ago

Logging on. Tells me my computer is offline, but it isn't. I have disabled my Firewall and allowed cookies. It has been 3 days.
C

Cameron

8 months ago

I have a coding assignment due tomorrow, and its not letting me code and always sending me to an error page. Please help.
C

Christian

8 months ago

Github Classroom gives an error 500 when accepting an assignment, and github codespaces wont open up for that Classroom
D

David

8 months ago

I can't access any of my codespaces
N

nic

9 months ago

The workbench failed to connect to the server (Error: exception was thrown by handler. exception: failed to start vs code remote server.)
L

Leonid

9 months ago

Can't start new codespaces
D

Dani

9 months ago

Cannot connect to codespaces service.
N

nic

9 months ago

cant log in. says "setting up codespace" but never comes past
R

rodrigo

10 months ago

i have a message that says unable to start codespace
T

Trang

10 months ago

cannot create or access to codespaces
D

Darnel

10 months ago

I keep getting a loading error tied to the vs code it doesnt open up to my files.
N

Nathan

10 months ago

I cannot seem to connect properly as usual
V

Vadim

10 months ago

https://turbo-space-goggles-r4rwr6x4gwrrcpw97.github.dev/?autoStart=true&folder=%2Fworkspaces%2F174781382&vscodeChannel=stable Building code space takes forever
M

M

11 months ago

I get these errors all of a sudden: (Error: exception was thrown by handler. exception: failed to start vs code remote server.) Failed to save 'quoted.html': ENOPRO: No file system provider found for resource 'vscode-remote://blabla' And a read-only filesystem error.
A

Ahmad

11 months ago

Slow opening Codespaces, always disconnect, terminal not responding then disconnect again
J

Jin

11 months ago

codespace is loading forever, even rebuild container is resulted in error
C

Carles

12 months ago

Unable to start codespace. Please try again later...
R

ram

12 months ago

Not able to open an existing codespace, failing with the error - ""Unable to start codespace. Please try again later."
V

valerii

12 months ago

Unable to start codespace. Please try again later.
J

John

12 months ago

Codespaces says it's down and investigating this issue. I have access to all my files but can't launch codespaces
A

Anonymous

12 months ago

Unable to start codespace. Please try again later.
A

Andriawan

12 months ago

it won't started normally. there was error notification said "Unable to start codespace. Please try again later."
E

Evan

12 months ago

unable to access my cs50 server for codework
T

Terence

12 months ago

Signing intoVisual Studio Code for CS50: Produces: Unable to start codespace. Please try again later.
D

Daphne

about 1 year ago

Unable to compile C++ files.
M

Mary

about 1 year ago

Codespace fail to be created. After several minutes says it has been deleted.
E

enzo

over 1 year ago

keeps reloading all the time
V

Vishal

over 1 year ago

unable to open the codespace. it only says connecting and then nothing happens
M

Mansehej

over 1 year ago

Not working, reloading

GitHub Codespaces outages in the last 30 days

Number of Incidents

2 issues

Last incident

16 days ago

Seamless Integrations

Get GitHub outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.

Never miss an outage

Easy setup · No coding required

Works with your existing stack

Having problems with GitHub Codespaces? What can you do?

First, stay calm.
- We know it's stressful when GitHub Codespaces is down, but running around is not going to fix it.
- Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
Make a quick evaluation of the impact of the GitHub Codespaces outage
- Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
- Did GitHub Codespaces already acknowledge the issue? And published a status update? (You can find it in the top of the page or in GitHub Codespaces status page)
- If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
Communicate with your team and users quickly
- If GitHub Codespaces is having problems and impacting your business, it's important to keep your team and users informed.
- Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
- If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
Understand the root cause
- After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
- Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
Is there any mitigation for the issue?
- Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
- Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
Did GitHub Codespaces recover?
- Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
Post-incident analysis
- Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
- Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
- Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
Prepare for the next incident, because it will happen again
- Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
- Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.
- For a complete overview of GitHub’s status across all services, including repositories, API requests, and workflows, visit the GitHub Status Page on IsDown

Related Services Dashboard

Services commonly monitored together with GitHub

Create your own dashboard

AWS

Google Cloud

Google Workspace

Cloudflare

MINOR

Azure

Slack

Datadog US1

Zoom

Figma

Microsoft 365

Adobe

HubSpot

Aircall

Stripe

Airtable

Want to be informed about GitHub status changes?

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

IsDown monitors Codespaces for major outages. A major outage is when Codespaces experiences a critical issue that severely affects one or more services/regions. When GitHub marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors GitHub status page for minor outages. A minor outage is when Codespaces experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Maintenance Feed

GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.

Component Filtering

IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

GitHub and other vendors don't always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.