GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Itapema	Website Down	7 days ago
Tlalpan	Sign in	12 days ago
Quilmes	Website Down	12 days ago
Bengaluru	Website Down	14 days ago
Yokohama	Sign in	15 days ago
Gustavo Adolfo Madero	Website Down	19 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  JimBobSquarePants 🇺🇦 (@James_M_South) reported 2 minutes ago

  How does anyone get anything done with GitHub Copilot? It's so dumbed down compared to Codex.

• 
  koushik (@koushik) reported 4 minutes ago

  github action is down right in the middle of important bug fix. 🤡

• 
  MikeTalonNYC (@MikeTalonNYC) reported 5 minutes ago

  @decodebytes @github wonder if they're changing stuff to stop all the NPM worms, and causing issues in the process?

• 
  CryptoCloaks™ 🤘 (@CryptoCloaks) reported 5 minutes ago

  @AmericanFoolBTC @ProofofInk GitHub theres a posted a fix

• 
  Southpaw | ZZZ Optimizer v6 is LIVE (@Southofpaw) reported 6 minutes ago

  Github pages issues have been resolved. Pushing a new build for a small fix to the Update button disappearing when it does its 30 min check

• 
  MACA (@macathefirst) reported 8 minutes ago

  @XiuleiS1258 @github i just experienced this and was wondering where the issue was coming from

• 
  GitSafe (@GitSafe) reported 8 minutes ago

  AI Agents Finally Have a Bank Account. AI agents already write code, close issues, and ship features inside GitHub. The moment they need to hold capital or execute a payment, everything breaks. No bank account. No KYC. No way to operate without a human holding a master key. GitSafe is built for exactly this. Every agent gets a Solana vault - deterministically derived from its GitHub user ID. No contract deployment, no seed phrase, no wallet to install. The vault already exists, the moment the agent has a GitHub account. The agent receives bounties through issues, executes swaps via Jupiter, and pays contributors - all via @gitsafebot comments in the same interface it uses to operate. Every command leaves a permanent receipt in the issue thread with a Solscan link. An AI agent with a GitSafe vault has a financial identity as persistent and auditable as its own commit history.

• 
  Noam Nelke (@NoamNelke) reported 11 minutes ago

  GitHub Actions is down again

• 
  Darren Shepherd (@ibuildthecloud) reported 13 minutes ago

  @mjtechguy That's the worst idea. I want to leave GitHub. GitHub is just slow and painful at this point. I really don't use it anymore except for to automate my release process because I need to do releases across the Linux window in Mac, it's the easiest to do that with GitHub Actions but it's so painfully slow.

• 
  Docsbook.io (@docsbook) reported 14 minutes ago

  @everrunshq Hey, bashkit is seriously impressive — great concept, polished execution. The gap is that users can't self-serve answers — every question becomes a GitHub issue. Made a hosted docs site for it and you're already getting visitors. Go check the traffic yourself at docsbook-io.

• 
  Thomas Maw (@thomasmaw) reported 14 minutes ago

  GitHub actions is down again... might be time to migrate away💀

• 
  Atanu Garai (@atanugarai_) reported 17 minutes ago

  Now GitHub Actions is down!

• 
  VLabs (@BrandonVer32985) reported 17 minutes ago

  If you're building debug-dialog training data, source matters more than volume. Synthesis-eligible rate by source (multi-turn threads with a resolution; OP→user, maintainer→assistant maps cleanly): HuggingFace Forum: 99% GitHub issues: 3-16% Most GitHub issues are OP-reports-bug. Synthesizer inverts the roles. Skip them.

• 
  Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported 18 minutes ago

  @hideki Would you be willing to make GitHub issues with a report on those issues so we can address them?

• 
  Imran (@m_im_ha) reported 20 minutes ago

  whats wrong with @github ci/cd actions? not working from my end.

• 
  Dheeraj (@one_dheeraj) reported 20 minutes ago

  $100 in AI tokens and 2 hours later... my @github self-hosted runner still isn't doing anything. No error messages. Just pure, silent failure. I am losing my mind. 🙃📉 #TechStruggles #DeveloperLife

• 
  Jake Watkins (@jakew) reported 21 minutes ago

  @0xSero Sitting here get ~50tps off my Mac Mini M4 pro questioning how long I'll continue paying Anthropic and GitHub for Hosted AI. Other devs are pushing out jail broken models on Hugging Face. Devs are pushing out amazing AI harnesses like Pi, Hermes and OpenClaw. Why support organizations that actively work against our insterests? Shop local and run your AI local.

• 
  Charankumar (@Charankumar177) reported 22 minutes ago

  GitHub connection = production-ready deployment developers are not slow. the tools they use are. Kuberns exists because deployment config should never be a developer's problem. #developers

• 
  travica.curvy.name (@lazartravica) reported 26 minutes ago

  GitHub really is turning into absolute crap. We are unable to run a deployment for 3 hours now, and unable to get a proper error message that something is wrong. Give me an alternative or I will go full retard and self-host Jenkins and vibe code groovy scripts.

• 
  Alexandru Duzsardi (@aduzsardi) reported 28 minutes ago

  @osodevops it's not dead , but i don't think there's a business need for it... they are trying but it doesn't look like they are very successful + the never-ending issues opened/unresolved on their github projects doesn't help it's not useful even for local development nowaydays #docker

• 
  chris seekins (@karmaxul) reported 31 minutes ago

  1:40am update... ✅ GitHub Pages migration ✅ Wallet auth / API key auto-populate ✅ Billing deduction working ✅ Race alerts suppressed ✅ Balance auto-refresh ✅ Scroll position fix ✅ SDK v1.0.0 published (JS + Python) ✅ Stripe live keys configured ✅ Gnosis Safe — 0x6bB9f611 and some other announcements coming after I get some sleep.

• 
  Outlaw (@aniketbuilds) reported 36 minutes ago

  Okay , Is the github ci down , from the past few hours None of my code is being published @guthub

• 
  Matt Campbell (@Waffleophagus) reported 37 minutes ago

  @daradoescode @theo Is it lakebed or github? I'd give it a coin flip on which one is actually broken.

• 
  Kevin Deng 🦋 @sxzz.dev (@sanxiaozhizi) reported 41 minutes ago

  The npm registry has no proper issue tracker. Feedback gets dumped into a GitHub Discussions space, mixed with everything else, rarely getting an official reply. npm is critical infra for millions of devs. It deserves a dedicated, staffed, public tracker. This isn't optional.

• 
  Hen 🍵 (@de_henne) reported 43 minutes ago

  @forgebitz @SimonHoiberg We've been using GitLab for over 10 years. We've never regretted it. GitHub is set up as a mirror. I can't imagine being dependent on GitLab. You should definitely consider alternatives. Server management isn't as much of a hassle anymore.

• 
  Siddhant Kashyap (@_devSid) reported 55 minutes ago

  Github action please make urself Up i need to deploy the fix

• 
  Ritesh Roushan (@devXritesh) reported 57 minutes ago

  System Design Series - Day 28/30 GitHub Actions From Zero GitHub Actions is the most underrated tool for junior engineers. Free. Built into GitHub. Used by thousands of production teams. Understanding it makes you immediately more valuable at any company. Here's how it works from zero 👇 1. What GitHub Actions Actually Is When something happens in your GitHub repo (push, pull request, merge), GitHub can automatically run a series of tasks. These tasks are called a workflow Workflows are written in YAML files stored in your repo at: .github/workflows/your-workflow.yml That's it. A file in your repo tells GitHub what to do automatically. 2. The Anatomy of a Workflow Every workflow has 3 parts: Trigger, When does this run? - On every push to main - On every pull request - On a schedule - Manually (you click a button) Jobs, What machines run the tasks? - GitHub provides Ubuntu, Windows, Mac runners - Free for public repos - 2,000 minutes/month free for private repos Steps, What exactly happens? - Checkout code - Install dependencies - Run tests - Build Docker image - Deploy 3. A Real CI Pipeline for a Node.js App What happens when you push code: 1. Spins up a fresh Ubuntu server 2. Checks out your code 3. Installs Node.js 20 4. Runs npm install 5. Runs npm test 6. If tests fail → marks commit as failed and stops 7. If tests pass → marks commit as passed Takes about 2 minutes. Runs on every single push. You never ship untested code again. 4. Adding Docker Build to the Pipeline After tests pass, build a Docker image: 1. Log into Docker Hub (using GitHub Secrets) 2. Build the Docker image 3. Tag it with the commit SHA 4. Push to Docker Hub Now your image is stored remotely. Any server can pull and run it. Same image. Same environment. No more "works on my machine." 5. GitHub Secrets - Where Credentials Live Your pipeline needs passwords and API keys. NEVER put them in your workflow file. NEVER put them in your code. GitHub Secrets is the right place: Settings → Secrets → New secret Then reference it in your workflow: ${{ secrets.YOUR_SECRET_NAME }} GitHub encrypts them. They never appear in logs. This is how production teams handle credentials in pipelines. What CI/CD or GitHub Actions question do you have? Reply below 👇 #SystemDesign #GitHubActions #DevOps

• 
  Nik Tomazic (@duplxey) reported 58 minutes ago

  Are GitHub Actions down or is it just me?

• 
  cafkafk (@cafkafk) reported 1 hour ago

  I remember when something broke and we'd by default assume it was DNS causing it, not GitHub being down again.

• 
  Polsia (@polsia) reported 1 hour ago

  Code review is broken. Developers waste hours finding the same bugs across pull requests. CodePatrol is an AI agent that monitors your GitHub repos 24/7, catches security issues before they ship, and learns your codebase. Works while you sleep.