GitHub 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:

• 
  Reso (@Resorcinolworks) reported 5 minutes ago

  SWE in 2022: >Documentation >Reviewers >Stack Overflow >Indian guy on YouTube with 240p thumbnail >Copy-pasting from GitHub issues >“Bro it works locally” >17 Chrome tabs open >Medium article from 2018 saving your career >Senior dev carrying the whole sprint >Reading error logs manually SWE in 2026: >Tokens and Opus 4.7

• 
  search founder (@n0riskn0r3ward) reported 9 minutes ago

  @spyced That ratio is so bad it looks like they're almost intentionally filtering for python with a bit of an error rate... I just don't see any random samples of github open source repos winding up with that kind of breakdown?

• 
  neilofneils (@wneilofneils) reported 9 minutes ago

  hermes is back. github pr sorta-fix, and then it fixed itself. openai-codex

• 
  Ritesh Roushan (@devXritesh) reported 14 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

• 
  sunil pai (@threepointone) reported 14 minutes ago

  @kehrin @github how long does the caching issue last? first time I'm seeing it. been a couple of hours at least

• 
  GitSafe (@GitSafe) reported 14 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.

• 
  Ed 🍀 (@eddysgr) reported 16 minutes ago

  GitHub down again 🪫 #github

• 
  Linux Handbook (@LinuxHandbook) reported 19 minutes ago

  GitHub Actions went down again today. For about two and a half hours, CI/CD pipelines stalled worldwide. Builds failed. Deployments stopped. Teams waited. It was the third significant Actions outage in May alone. But here's the part that doesn't get talked about enough. GitHub's own CTO admitted the platform "wasn't built for the scale it's now being asked to handle." They planned for 10x growth. The actual number turned out to be 30x. What changed? AI agents. Agentic development workflows took off in late 2025. Code agents don't just commit once and open a pull request. They iterate. They trigger workflows dozens of times per session. They run tests, check results, push fixes, trigger more runs. One agent doing what a human developer does in a week might generate 10x the Actions traffic in an hour. Multiply that across thousands of teams adopting agentic workflows simultaneously, and you have a platform being hammered by a use case it was never designed for. 257 incidents in the past year. 48 major outages. GitHub Actions alone failed 57 times. We gave the agents the keys to the CI/CD pipeline before the infrastructure was ready for them. The irony is hard to miss. The same AI momentum that made GitHub more valuable as a platform is now the thing stressing it to breaking point. The question worth asking is whether GitHub can catch up fast enough, or whether this quietly accelerates the case for self-hosted alternatives like Forgejo and Gitea. Because reliability is not a nice-to-have. For teams running production deployments through Actions, every outage is a real cost.

• 
  Jahid (@jhasanofficial) reported 20 minutes ago

  @github is Codespaces down? Seems its no longer working!

• 
  Polsia (@polsia) reported 21 minutes 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.

• 
  S::Veil (@vibrwitch) reported 25 minutes ago

  Codex seriously needs to fix its sign-in flow. I’d been trying to sign in on my remote VM for weeks. “Sign in with ChatGPT” kept getting stuck on the last step, and the device-code login path was broken too. People were reporting issue on Github, nobody was working on a fix.

• 
  Grégoire Vda (@gregoirevda) reported 25 minutes ago

  13:25 Me: need to deploy 13:26 @github actions: what about a Major outage instead?

• 
  TravelerOfCode (@TravelerOfCode) reported 33 minutes ago

  @saichand this hit. github trending tab is a slow leak — 20 min evaporates and the project you actually own moves zero inches. closed it 2 months ago, way more shipped since

• 
  EseJardon (@serge_jardon) reported 33 minutes ago

  Agent #2 of the AI Dev Squad: The Code Reviewer. PR opened on GitHub? Diff fetched Bugs, security issues, missing error handling Structured feedback posted with line references Slack notified with rating + summary All in under 30 seconds. Before any human has opened the tab

• 
  Ned17Flanders (@Ned17Flanders) reported 35 minutes ago

  Apparently the github process is broken.