Is GitHub Down? Check the current GitHub status

GitHub is operational

Updated

GitHub not working for you?

Monitoring GitHub since April 2020. Learn more

Monitoring 11 GitHub services and regions

38 incidents in 2025

Current GitHub official ongoing incidents

No incidents reported in GitHub's status page

IsDown pulls data from GitHub's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.

GitHub issues reported by users in the last 24 hours

This chart displays the number of user-reported issues 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. We only consider an issue widespread if there are multiple reports within a short timeframe.

Latest user comments about GitHub problems

  • K

    Kresimir

    about 20 hours ago

    Copilot Getting the following error message: Conversation failed to load Reload the page to try again.

  • U

    Ujjwal

    1 day ago

    Copilot it is not processing any content via codespace access or via github

  • C

    CurrentUser

    2 days ago

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

  • C

    Chandrasekaran

    3 days ago

    Copilot GitHub Copilot not working within Visual Studio Code. Get this error in the output: 2025-03-18 11:56:37.755 [info] Logged in as jjchandru 2025-03-18 11:56:58.848 [error] GitHub Copilot could not connect to server. Extension activation failed: "net::ERR_CONNECTION_TIMED_OUT" 2025-03-18 11:56:58...

  • A

    A

    8 days ago

    Copilot 502, 400, request failed errors on copilot in vscode insiders

  • O

    omid

    9 days ago

    Copilot vscode copilot Err: Failed to sign in to GHE.com. Would you like to try again? You must be signed in to use Copilot.

  • P

    phil

    10 days ago

    Copilot [Conversations Warning] [CopilotClient] Issue with setting up the connection to 'https://api.githubcopilot.com/chat/completions', if you are using a proxy, check if HTTPS_PROXY is set correctly. https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient#http-proxy [Conversa...

  • A

    Alejandro

    11 days ago

    Actions self-hosted runner not taking jobs even when restarted

  • M

    Mohamad

    15 days ago

    Actions The Workflow keeps running and unable to be cancelled

  • J

    Jessica

    15 days ago

    Copilot It is not responding to any requests for instance definitions and meanings

  • A

    Andrew

    16 days ago

    Codespaces 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...

  • I

    Isak

    16 days ago

    Actions Blank screen, does not start, says started 4m ago but I cannot see anything?

  • C

    Csaba

    20 days ago

    Copilot same here. keeps generating and nothing happened.

  • L

    Lukasz

    21 days ago

    Copilot I cannot ask questions in the Web chat.

  • B

    Bob

    29 days ago

    Copilot This gives: RPC server exception: System.Exception: Error occurred while invoking intent 'None'. Bad Request

  • E

    Ender

    29 days ago

    Copilot Every chat I send into GitHub Copilot returns a "Sorry, your request failed. Please try again. Request id: Reason: Server error: 500 Internal Server Error"

  • L

    Loret

    about 1 month ago

    Copilot I enter my questions with no response.

  • Z

    Zack

    about 1 month ago

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

  • I

    Ivar

    about 1 month ago

    Copilot Not loading or suggesting

  • M

    Mathew

    about 1 month ago

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

  • K

    kelvin

    about 1 month ago

    Copilot not responding to auto complete

  • L

    Lorran

    about 1 month ago

    Copilot It keeps generating, generating, and never ends, never delivers any answers.

  • D

    David

    about 1 month ago

    Copilot Sorry, your request failed. Please try again. Request id: 5c93e76d-3b43-495d-8942-a32ef1b5c66a Reason: Request Failed: 400 Bad Request

  • J

    jason

    about 1 month ago

    when i click download zip file it gives me error 404 and i can not download any file

  • T

    tobias

    about 1 month ago

    Copilot not getting access, either on vscode or in github

  • J

    Joshua

    about 2 months ago

    Actions Large runners not being assigned

  • T

    tristan

    about 2 months ago

    Codespaces 502 Bad Gateway on my codespace link

  • J

    jason

    about 2 months ago

    Copilot when i use github copilot locally, it works well. But when i start the vpn to access remote company environment, the github copilot reports "sorry, please tray again latter"

  • J

    jason

    about 2 months ago

    Copilot github copilot always reports "Sorry, your request failed. Please try again."

  • L

    Leslie

    about 2 months ago

    Copilot Copilot is down. All functionalities including Chat, auto-complete and Git changes summary aren't working. They simple don't process

  • S

    Simon

    about 2 months ago

    504 The server didn't respond in time.

  • A

    Anubhav

    about 2 months ago

    cant open any repo on github

  • A

    alex

    about 2 months ago

    We couldn't respond to your request in time. Sorry about that. Please try refreshing and contact us if the problem persists.

  • M

    mich

    about 2 months ago

    Copilot "Sorry, your request failed. Please try again. "

  • A

    Abdulla

    about 2 months ago

    Github pages not loading properly

  • N

    Neil

    about 2 months ago

    Copilot Copilot not returning responses

  • J

    Jaden

    about 2 months ago

    Copilot Both copilot embedded in Github browser and embedded in VScode are saying unavailable whenever a prompt is entered

  • D

    Dang

    about 2 months ago

    Copilot Claude 3.5 Sonnet The return was not

  • W

    Wuffel

    about 2 months ago

    Copilot Copilot is not answering at all in PyCharm. So response. Nothing.

  • S

    Samuel

    about 2 months ago

    Copilot no completions are proposed, and "open completions pane" shows zero completions. github copilot chat works fine.

  • S

    Slav

    2 months ago

    Copilot GitHub Copilot VSCode Extension can't connect to authentication provider and gives the following message in output logs: "Error getting a session: Timed out waiting for authentication provider to register"

  • U

    Umair

    2 months ago

    Copilot I am unable to access github copilot on web

  • J

    Julian

    2 months ago

    git clone via https returns a 500 Internal Server Error

  • N

    Not

    2 months ago

    Copilot Can't make any code change request

  • I

    Ilia

    2 months ago

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

  • G

    Germi

    2 months ago

    Copilot status says ready, but can't chat, autocomplete, or generate commit messages

  • I

    Ivan

    2 months ago

    Actions Jobs are not getting picked up on GitHub hosted runners

  • M

    Morgan

    2 months ago

    Can't log in, create repos or orgs

  • W

    Wim

    2 months ago

    Copilot Autocomplete not working. Error in VS Code logs: [error] [fetchCompletions] Unhandled status from server: 504 request timeout . Also: [warning] [fetchCompletions] Response status was 429: {"error":{"code":"NoCapacity","message":"The service is temporarily unable to process your request. Please tr...

  • A

    Angelo

    2 months ago

    Copilot It always says Oops, there was a problem with your request, Please try again. Even though i am only saying hello. I restarted my ide, my internet, and all

  • I

    ivan

    2 months ago

    Copilot stuck in generating an answer

  • A

    Amber

    3 months ago

    Actions All actions are stuck in queue. "Waiting for a runner to pick up this job..."

  • J

    joe

    3 months ago

    Copilot when i prompt it to do something its stuck in generating. prompt done in vscode

  • N

    no

    3 months ago

    no PR can be made unicorn, 404 all around.

  • M

    Martin

    3 months ago

    Copilot GitHub Copilot Chat window in Visual Studio is not loading. There is a never ending hour-glass.

  • P

    Padmanathan

    3 months ago

    Codespaces I am unable to connect to GitHub codespaces

  • S

    Seb

    3 months ago

    Actions Not getting an action runner assigned

  • R

    Rachel

    4 months ago

    Copilot Getting token expired or invalid: 403 error

  • C

    Can

    4 months ago

    Actions Queued forever. Facing in last 3 days. Sometimes it runs first jobs but after that queues the others.. Stuck.

  • D

    DimaO

    4 months ago

    Actions Github actions are now getting bigger runners and getting queued forever

GitHub outage history

IsDown has tracked 626 incidents since started monitoring GitHub status in April 2020.

  • Mar 21 2025

    about 2 hours ago · lasted about 1 hour

    We are investigating reports of degraded performance for Codespaces More details

  • Mar 20 2025

    about 8 hours ago · lasted about 1 hour

    We are investigating reports of degraded performance for Pages More details

  • Mar 18 2025

    2 days ago · lasted about 1 hour

    We are investigating reports of degraded performance for Actions More details

  • Apr 2020 ...
    IsDown started monitoring GitHub status

    We've tracked and collected 626 incidents since started monitoring GitHub status

Sign up and check all outage history

GitHub outages in the last 30 days

Number of Incidents

19 issues

Last incident

0 days ago

Having problems with GitHub? What can you do?

  1. First, stay calm.

    • We know it's stressful when GitHub 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.
  2. Make a quick evaluation of the impact

    • 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 already acknowledge the issue? And published a status update? (You can find it in the top of the page or in GitHub status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If GitHub 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.
  4. 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.
  5. 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.
  6. Service has recovered?

    • 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.
  7. 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.
  8. 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 monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.
Official Status Pages + User Reports

Be the first to know when GitHub and other third-party services go down

Get instant alerts when your critical services go down. One dashboard to monitor all your vendors' status pages.

Start Your Free Trial
14-day free trial No credit card required Cancel anytime
Be the first to know when GitHub and other third-party services go down

Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.

Start Free Trial 14-day free trial · No credit card required · 3200+ cloud vendors available

Check the status of GitHub alternatives & related services

4 incidents in the last 30 days
Compare GitHub vs. Bitbucket
GitLab OK
13 incidents in the last 30 days
Compare GitHub vs. GitLab

Stay informed about GitHub status changes

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

IsDown monitors GitHub for major outages. A major outage is when GitHub 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 GitHub 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.

Frequently Asked Questions

How can I resolve issues when GitHub is down?

When GitHub is down, start by checking the official status page and IsDown's monitoring. If PRs, repository access, or deployment processes are affected, try using alternative workflows. If it's a network or connectivity issue, verify whether it's on GitHub's end or a local problem by testing a different network or clearing the DNS cache.

Keeping track of GitHub status updates helps in understanding the outage. In cases of widespread disruptions, teams can mitigate the impact by delaying non-critical tasks or working offline until service is restored.

How does IsDown notify users about GitHub outages?

IsDown provides real-time alerts when GitHub experiences disruptions. Users can set up notifications via Slack, PagerDuty, or email to stay informed. Whether it's a network problem, database failure, or deployment delay, IsDown keeps users updated. Tracking GitHub status checks ensures teams are aware of potential service interruptions before they escalate.

Can GitHub outages impact development workflows?

Yes, when GitHub experiences an outage, it can significantly disrupt software development workflows. Developers may be unable to push code, merge pull requests (PRs), or access repositories. This can delay releases, hinder collaboration, and affect automation pipelines, particularly in DevOps and CI/CD environments where GitHub is integrated with build and deployment processes.

What are common causes of GitHub outages?

GitHub outages can be caused by infrastructure failures, database issues, network congestion, or planned/unplanned system maintenance. Problems with query performance, API rate limits, or repository indexing may slow down searches and repository access. To determine whether an issue is widespread or isolated, developers should check GitHub's official status page and third-party monitoring platforms like IsDown for real-time outage reports.

How can teams mitigate the impact of GitHub downtime?

To reduce the impact of GitHub downtime, teams should implement contingency workflows. This may include maintaining local repositories for offline work, setting up alternative version control systems (e.g., GitLab, Bitbucket), or using mirrored repositories. For CI/CD pipelines, integrating multiple service providers can ensure redundancy. Regularly monitoring GitHub status updates allows teams to react proactively and adjust workflows as needed.

Is GitHub slow today?

Currently there's no report of GitHub being slow. Check on the top of the page if there are any reported problems by other users.

How are GitHub outages detected?

IsDown monitors the GitHub official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last GitHub outage?

GitHub last outage was on March 21, 2025 with the title "Incident with Codespaces"

GitHub not working for you? How do I know if GitHub is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How can I check GitHub status and outages?

Why use IsDown to monitor GitHub instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor GitHub and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

“Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.

We play well with others

Get GitHub outage notifications where you need them the most

The data and notifications you need, in the tools you already use.

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required