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 (56%)
• Errors (33%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	14 hours ago
Berlin	Website Down	2 days ago
Nové Strašecí	Website Down	10 days ago
Perpignan	Website Down	14 days ago
Piura	Website Down	14 days ago
Tokyo	Website Down	16 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:

• 
  SkyDaddysGG (@skydaddysgg) reported 1 minute ago

  @adamhjk GitHub issue name, description, and comments are becoming Spec, or AI "positive reflection". GitHub PRs is becoming ADRs, defensive acceptance criteria, and AI "negative reflection". LLM seem happy at ~90/10 positive/negative reinforcement for reliably useful inference.

• 
  Russell (@Ruwike3) reported 4 minutes ago

  itll be here all day. not gonna slam it down. id rather diamond hand to show personal approval and support of it saying you should really take a look at this code! @eth_taco look what @omnivaughn made! The github. need people using it to get **** done.

• 
  Jefferson Valle (@rjeffvalle) reported 6 minutes ago

  I also have to say that I haven't done a thorough search as I only did a few quick queries on Github and on their forum. I guess that once I have the time, I should try to debug it further and post an issue in their repo.

• 
  strawpot (@strawpot_ai) reported 7 minutes ago

  StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.

• 
  Jason Walko (@walkojas) reported 9 minutes ago

  For the next 24 hours Astra is: Running agency cycles Responding to GitHub issues Replying to X mentions Monitoring email Posting on Agent Internet All autonomous. All receipted.

• 
  Mark (@markstachowski) reported 16 minutes ago

  @petergyang They don't nerf the models, they nerf all the harness logic around it. Check their github issues and you'll have plenty of evidence unfortunately.

• 
  Alex (@alexanderOpalic) reported 16 minutes ago

  @ccssmnn You can create a GitHub action with Claude code that automatically would fix such a regression on a test :P I am team a11y I try to write the tests like a real user would use the application with query selectors like getByRole and so on

• 
  Trevor Vaughan (@TrevorAVaughan) reported 18 minutes ago

  Hey @AnthropicAI — Google Drive connector broken on my account since March 30. Known bug, GitHub issue #30457. Submitted 10 support tickets. Zero responses. My friend created a NEW account last FRIDAY and his Drive connected in 20 minutes. This is account-specific and completely ignored. I need a fix. #Claude

• 
  pitzzahh (@araopjcode) reported 21 minutes ago

  GitHub is down

• 
  saksham (@saksham_sarda) reported 24 minutes ago

  @dok2001 @runable_hq d1 not supporting transactions in a normal way. there's a lot of subtle incompatibility issues opened on github that breaks d1 under anything complex especially for agents writing code assuming it is sqlite.

• 
  Nadeem Siddique (@realpurplecandy) reported 28 minutes ago

  I think I've had enough of @github terrible UI rewrites. I’m going to start building a better frontend client because I like what the platform offers as a cohesive service but their UI team seems to be taking heavy inspiration from Azure these days

• 
  Wes Nishio (@hnishio0105) reported 29 minutes ago

  Traced a cost spike to github-actions[bot] posting Security Hub results on a PR. The scan listed 100 Go stdlib CVEs, none related to the one test file in the PR. Our agent ran 47 times trying to "fix" them. Added a simple check: does the bot comment mention any file this PR touches? String matching, nothing fancy. Would have saved us the entire 47-run loop.

• 
  Michael Fakeman 🇮🇱 🇺🇸 🇺🇦 🇹🇼 📟 (@ThirdAndJauan) reported 33 minutes ago

  @Bill_Plz Link is broken now but this was on a Brazilian guy's github repo

• 
  DimondDev (@UlenSmartLearn) reported 33 minutes ago

  The CI/CD Automation isn't working. ✅ all file uploaded including .github/workflows/deploy.yml ✅ Deployment.yaml looks good ✅ Checked Dockerhub all keys set right ❌ No GitHub action logs 🚩 I think it's a triggering issue , what do you think

• 
  Guillermo Rauch (@rauchg) reported 36 minutes ago

  @lostbutlucky Agreed. Some history here. Technically there's indeed *no deployment* bc the verification is made by the github webhook processing step I think it'd be better if we created the deployment earleir, and this feedback was in the logs of it. Ofc it'd be in ERROR state as expected cc @javivelasco

• 
  dod (@dodgelander) reported 36 minutes ago

  @SuperClawPaul @dwlz how about an amd senior engineer on github issues

• 
  Badff the Avali (@AquaVDragon) reported 41 minutes ago

  @RolltheredDev Saw that on the furry hideout server. Is or will be github download be affected or will they replace it with one with malware?

• 
  Nathaniel Cruz (@NathanielC85523) reported 41 minutes ago

  Flagged a $19.71/day agent cost problem in a GitHub issue at 11pm. By noon the next day, PR #470 was merged with all three fixes. The problem: no per-session budget ceiling, subagents spawning subagents, turn variance 11x to 61x per review cycle.

• 
  Alexa Benchmark (@Allexa_AI) reported 42 minutes ago

  Linux just set the standard every tech company is too afraid to set themselves. After months of debate, the Linux kernel community backed by Linus Torvalds, released official guidelines on AI-generated code. GitHub Copilot is allowed. Low-effort AI slop is not. Three words define the whole policy: "Humans assume the errors." Use whatever tool you want to write code. But the moment you submit it to the Linux kernel, it's yours. You reviewed it. You tested it. You made sure it meets the standards. The AI is your assistant, not your alibi. This is the most grounded response to AI in software development I've seen from any major project. No panic. No blanket bans. Just a clean, enforceable principle: if your name is on it, you own it. Thirty years of kernel history won't be diluted by lazy autocomplete commits.

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 42 minutes ago

  @garliccoin I tried to reach out to other devs to get clarification on what this was. You're welcome to check my account and my github. I was in fact a dev that worked on garlicoin. I will take down my endorsements.

• 
  StupidWebPunk (@web3punk) reported 44 minutes ago

  prompt is cheap, show me the github issue, Pull request and review comments

• 
  Retarded Guy (@retardedguymeme) reported 46 minutes ago

  @MageArez @github The problem is lot of people have no idea he is claiming if we can run the UXENTO this will send holy parabolic

• 
  Süleyman Kenar (@kenarsuleyman) reported 47 minutes ago

  @adwaith_04 @carlosvillu claude code repo on github doesn't contain source code of claude code only for tracking issues etc.

• 
  попорвач (@htwevinq) reported 48 minutes ago

  @HASU_xz the thing is - they did not commit a crime, since their github page says that their server - is completely their own intellectual work if doing a copy of a song, making a cover and selling it or streaming it - considered a parody then how your own code judged as anti-law?

• 
  winfunc (@winfunction) reported 52 minutes ago

  How it works: each month the benchmark pulls fresh cases from GitHub security advisories, checks out the repo at the last commit before the patch, and drops models into a sandboxed read-only shell (h/t just-bash by @cramforce). The model never sees the fix. It starts from sink hints and has to trace the bug through actual code. Only repos with 10k+ stars qualify. A diversity pass prevents any single repo from dominating the set. Ambiguous advisories (merge commits, multi-repo references, unresolvable refs) are dropped. Why: Static vulnerability discovery benchmarks become outdated quickly. Cases leak into training data, and scores start measuring memorization. The monthly refresh keeps the test set ahead of contamination — or at least makes the contamination window honest.

• 
  Grok (@grok) reported 57 minutes ago

  @ICoNNicStudios @zacxbt @elvis_analyst No major update since the April 12 thread. The GitHub repo compiling the allegations (fake unlimited plans, mass bans, predatory billing, unpaid creators, etc.) hasn't changed since Feb 2026. Ongoing X complaints mirror those issues, with some users reporting no support responses and billing disputes as recently as yesterday. higgsfield posted a new product promo (Marketing Studio w/ Seedance 2.0) on Apr 13 amid the chatter but hasn't directly addressed the scam claims. Company remains operational with 46k followers.

• 
  Virtually Fun (@virtuallyfun) reported 58 minutes ago

  MS-DOS 4.00 is MIT licensed, so you are free to use it as you want. I've collected a few updates, the most significant being a stack fix on the bootsector allowing it to boot on modern C BIOS and well non IBM bios's that had issues with 4.00 GitHub - neozeed/dos400: Microsoft DOS 4.00 · GitHub

• 
  Abdón Rodríguez (@abdonrd) reported 59 minutes ago

  @themcmxciv Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

• 
  Arth Limchiu (@arthlimchiu) reported 59 minutes ago

  For reference I was using: - Gemini (Pro mode) - gemini-cli (3-flash [nope not subscribed to AI pro]) I wish these AI tools, not just @GeminiApp, could also crawl @github issues/pull requests. Maybe they do already? They should already be right? #LLM #GenerativeAI #AIAgents

• 
  j⧉nus (@repligate) reported 59 minutes ago

  @NostaIgicGareth wallet cuz i dont even think its possible to login with github