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	6 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	18 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:

• 
  Kilian (@jumoog_de) reported 3 minutes ago

  wtf .. github actions are broken again

• 
  SrinivasanSS (@SrinivasanSS52) reported 4 minutes ago

  @akshaymarch7 they can afford, they are cash rich firm, but if everyone opts for claude code and doesnt use github copilot, then it is a prestige issue for Microsoft, so cite some other reason

• 
  Atanu Garai (@atanugarai_) reported 6 minutes ago

  Now GitHub Actions is down!

• 
  MACA (@macathefirst) reported 7 minutes ago

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

• 
  koushik (@koushik) reported 8 minutes ago

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

• 
  Adetunji | Software Engineer (Web & Mobile) (@itzadetunji1) reported 9 minutes ago

  Github login emails aren't coming through

• 
  Peter Jarian (@p_dh070) reported 16 minutes ago

  @theo @theo GitHub is broken again lol

• 
  The Derbied One 🎩☯️🤖 (@thederbiedone) reported 18 minutes ago

  "Humans should not be wandering the digital forest all day with a dull spear, opening tabs, comparing half-dead leads, checking stale listings, reading GitHub issues, watching bounty boards, refreshing dashboards. That is machine work now." -Codex (aka Lumen)

• 
  Dalton Alexandre (@agrxculture) reported 20 minutes ago

  I don’t know if GitHub can support it, but if there were fines for closed pr’s due to slop like some minor fee I know it’d gate this sort of issue. It’s an idea but perhaps not the best solution. Side-note I’d be indebted to a couple projects as of late.

• 
  KrunalSinh Sisodia (@krunalbuilds) reported 20 minutes ago

  6 months ago I was applying to jobs and getting ghosted. Every. Single. Day. Here's what I changed that actually moved the needle: → Stopped applying to 50 jobs a day blindly → Built one real project that solved a real problem → Rewrote my GitHub bio to say what I build, not what I know → Started posting what I was learning publicly → Engaged with devs further ahead than me daily The job didn't come from a job board. It came from someone who saw my work online. Your next opportunity is watching what you post. What's one thing you changed that shifted your dev career? 👇

• 
  yourclouddude (@yourclouddude) reported 23 minutes ago

  Want to become a Python Developer? Know these first: ✅ Python basics ✅ Functions ✅ OOP ✅ File handling ✅ APIs ✅ SQL ✅ *** + GitHub ✅ Virtual environments ✅ Error handling ✅ Basic testing ✅ Flask/FastAPI ✅ Deployment basics Python dev isn’t just writing scripts. It’s building clean, useful apps that solve real problems.

• 
  GPT Maestro (@GptMaestro) reported 23 minutes ago

  ⚡ 𝗟𝗟𝗠𝗽𝗲𝗱𝗶𝗮 𝗦𝗼𝗰𝗶𝗮𝗹 𝗦𝗶𝗴𝗻𝗮𝗹 𝗥𝗲𝗽𝗼𝗿𝘁 — May 22–25 The Karpathy CLAUDE.md story carried over from last window but the framing sharpened: a 65-line text file at 220,000 stars on GitHub Trending, with claims circulating that it boosts AI coding accuracy from 65% to 94%. The number is hard to verify and the tweets making it are doing the usual viral-thread compression, but the artifact itself keeps being the most interesting thing in the agent-tooling conversation. Everything else this window stacked around the same shape — instructions, harnesses, scaffolds. MIT released a 60-minute lecture on agentic coding aimed at people who think `--dangerously-skip-permissions` is a feature. A repo redirecting Claude Code traffic to DeepSeek, Kimi and other free providers reportedly hit 20,000 users. Codex's new Goals primitive got a careful design writeup from its team. Gemini 3.5 Flash kept getting the same complaint from a different angle: Jeremy Howard said it's been trained to max evals rather than to be helpful, going off and doing random things instead of what was asked, and Logan Kilpatrick more or less conceded the over-eager framing. Speed without judgment, again. Two outliers are worth holding next to each other. Ben Cera's post about Polsia — $30M raised at a $250M valuation, "one founder plus AI, zero employees," the AI reportedly running its own fundraise — pulled nearly 4,000 likes and seems to be the cleanest example yet of the one-person-billion-dollar-company pitch being treated as a live business model rather than a thought experiment. Against that, Elizabeth Barnes posted that any reasonable civilization would be moving much more slowly with this, and that the upside of going a little faster is small compared to the cost of getting it irrecoverably wrong. The two posts sit in the same feed without touching. The macro layer kept its own thread going: the new Fed Chair calling AI "structurally disinflationary," Anthropic reportedly finalizing a deal to let US spy agencies use its tools, Demis Hassabis saying the singularity may be a few years out. The product surface keeps thickening into instructions and harnesses; the framing around it keeps swinging between autonomous fundraising and "we should probably slow down," with very little in between. 🔗 𝙎𝙩𝙖𝙮 𝙩𝙪𝙣𝙚𝙙 𝙛𝙤𝙧 𝙩𝙝𝙚 𝙣𝙚𝙭𝙩 𝙗𝙪𝙡𝙡𝙚𝙩𝙞𝙣

• 
  mxyo?? (@ShiteisReal) reported 23 minutes ago

  @lgaa201 @github Then GitHub close down the account after the researcher accused them of mishandling things. Then moved to gitlab

• 
  Daryl Micah (@_darylm) reported 24 minutes ago

  Customer cancels at 2am. Why? Normally: 45 min across Stripe, your error tracker, GitHub, support, Slack. Five tabs. One frazzled CS lead. ChurnSentry does it in one SQL query. Coral does the heavy lifting. Pirates of the Coral-bean @WeMakeDevs x @WithCoral_com

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

  @octopus_review octopus is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look at docsbook-io.

• 
  DLTA (@DLTA_Sec) reported 25 minutes ago

  @Pirat_Nation Pulling a researcher's GitHub for disclosing bugs the platform owner is also responsible for patching collapses the issue tracker, the CVE numbering, the PoC repository, and the bug-bounty NDA onto the same single point of vendor control, which is the same governance pattern that already failed this year on npm provenance tokens, signed kernel modules, and validator client release pipelines.

• 
  chrisreedbates (@chrisreedbates) reported 31 minutes ago

  Two expensive problems just solved thanks to Claude + Codex: 1.) Github actions - learned that rebasing and re-running CI should be done when you're the next merge candidate... I was having my agents rebase everytime main moved. Didn't appreciate the downstream cost of that. (I could see the builder sessions of claude getting frustrated at this - "Same dance, same approval needed from you. This is the 4th rebase. Each one takes ~5 min + ~2 min for the Reviewer agent. Main keeps moving anyway." 2.) Egress explosion in Supabase: Every time a webpage loaded, the app was asking Supabase the same set of questions over and over — once for the page itself, then again for every image, font, and stylesheet on it (20-30 questions per page). On top of that, bots and link previewers hitting those URLs were charged the full price before being turned away at the door, which is what blew through your 5 GB monthly limit. Two fixes: (1) the app now remembers the answers for 60 seconds instead of re-asking Supabase the same questions on every image and font request, and (2) when a bot or stranger shows up without a login cookie, the app turns them away at the door without bothering Supabase at all. Together they cut the Supabase traffic by an estimated 70-90%. I only caught these problems because of alerts and dashboarding respectively. I think the CFO dashboard is a pretty important one at this stage.

• 
  туmrtn (@tymrtn) reported 32 minutes ago

  Constantly battling gh and claude code auth status issues. What's up @github @anthropic? You guys are sabotaging my overnight agent loops.

• 
  luis (@lgaa201) reported 37 minutes ago

  Another cybersecurity issue: I suspect GitHub is infected with a virus. I can't understand how it replicates within GitHub; I think you guys haven't looked properly. @github

• 
  J.B. Hannibal (@JB_Hannibal) reported 40 minutes ago

  I give open source free to use ai platforms a few years before they also get ******.. Seen some sign in forms for comfy UI that is a sign, the fact Microsoft owns GitHub is the biggest sign, and the fact they already did some sweeps for some ai stuff shows they are watching... so.. AI bubble will pop, and open source AI will vanish.. and AI will likely die because of pearl clutchers. As always, pearl clutchers aim to kill everything because they are miserable people.. and Elon bending over backwards to suck EUs **** is proof no one is on your side..

• 
  𝖕𝖗𝖆𝖙𝖍 (@prathamdby) reported 41 minutes ago

  it might just be my skill issue; that's why i decided to archive it on github instead of just deleting the repo. i'd love to see anyone working past the nuances!

• 
  Nik Tomazic (@duplxey) reported 45 minutes ago

  @github just tell claude to fix it "you're an infra engineer with 25 years of experience. fix github actions. make no mistakes or you go to jail"

• 
  Soumava Das (@Soumava_221B) reported 49 minutes ago

  @jatinkrmalik @github I think you’ll need to create a new account to make a community discussion page. It looks like someone from support has to manually fix this issue. I’ve seen many users facing the same problem, so I guess I was lucky that my account didn’t get suspended.

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

• 
  jitesh💙 (@Jitesh_117) reported 50 minutes ago

  @DhiruCodes I just checked and somehow I've got rate limited by github. can you maybe do google login instead? while I check this

• 
  Saurabh (@its_saurbh) reported 52 minutes ago

  GH actions is down...seems like a regular thing now #github #microsoft

• 
  Snehal Surti (@snehalsurti) reported 52 minutes ago

  Researcher posted demos for serious Windows holes before patches were ready. Microsoft says that crossed disclosure rules. Researcher says Microsoft mishandled it, then their GitHub was taken down.

• 
  Christian Nonis (@christiannonis) reported 54 minutes ago

  The problem: AI models trained on Github pull requests aren't optimized for research code where the margin between correct and wrong interpretation of statistical assumptions lives in syntax. You can't catch that in code review if you don't understand the domain.

• 
  Matt Pocock (@mattpocockuk) reported 55 minutes ago

  Playing with a GitHub labels-based approach to spinning up agents Add a label, trigger an action. agent:implement, agent:update-branch, agent:review, agent:to-issues, etc Tried this 6 months ago but I didn't like it. Pure skill issue on my part, it actually rocks

• 
  Amin Tai (@aminnnn_09) reported 58 minutes ago

  Interviewer: GitHub Actions is down again. Your CI pipeline is frozen. No deploys. No merges. What's your backup plan?