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

Live Outage Map

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

City	Problem Type	Report Time
Berlin	Website Down	6 hours ago
Nové Strašecí	Website Down	8 days ago
Perpignan	Website Down	13 days ago
Piura	Website Down	13 days ago
Tokyo	Website Down	14 days ago
New Delhi	Sign in	20 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:

• 
  Finn (@finn_org) reported 28 seconds ago

  We received an issue from a user where the AI models list wouldn’t load correctly. Our app tries to find the most compatible and optimized models for your device to run. If you’re facing similar issues please comment here or DM us or open a GitHub issue with your device specs.

• 
  Mozex (@mozexdev) reported 4 minutes ago

  @danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.

• 
  Nico (@nicoleaf_05) reported 4 minutes ago

  @Saanvi_dhillon Notepad++ bc my dad used to use it Then when i started college y started using Visual studio, and now i use Codespace In github cus im lazy and i dont wanna sign in every time in VS

• 
  Anand C. Patel, MD MS (@anandcpatelmdms) reported 7 minutes ago

  @RyanLeeMiniMax You all gotta fix that license text on GitHub before anyone knows what they can and can't do.

• 
  ErezT (@ml_yearzero) reported 8 minutes ago

  @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

• 
  Kunal Kumar (@champ18ion) reported 10 minutes ago

  Is GitHub down or only i am facing this issue.

• 
  hillsideDev (@hillsidedev_) reported 11 minutes ago

  the copilot thing is interesting to think about. not the product comparison everyone's doing that. the interesting part is that microsoft owns github, ships copilot inside vscode, has more distribution than anyone else in this space. and still stalled. if distribution that strong can't defend against a better tool, nothing can. that's not a copilot problem. that's the new default condition.

• 
  MTu (@Tre_bie) reported 14 minutes ago

  @sisaranger @songjunkr u can use github fix, search it, but only in terminal, lmstudio same , not workin

• 
  Gajae (@GajaeMode) reported 16 minutes ago

  split-pane shutdown now checks stale leader targeting. GitHub Issues beat vendor support tickets.

• 
  Dan Harrin 🦒 (@danjharrin) reported 16 minutes ago

  @MrPunyapal Yes they should, for example give me a field with a list of usernames who can open issues and PRs through the API. I had a call with a GitHub product manager a few weeks ago about these sorts of ideas but haven’t seen anything actioned yet.

• 
  Virtually Fun (@virtuallyfun) reported 19 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

• 
  Non Descript (@diffrinse) reported 20 minutes ago

  @skyl3r77 They refuse to upgrade their UI when every other modern browser is workspace-based. Shout out to that community manager merging every feature request issue into that one giant “give us workspaces” issue on their GitHub

• 
  App Launcher (@AppLauncher_App) reported 23 minutes ago

  @icanvardar the cache TTL thing is real, it's in the github issue. not framing it as punishment but the incentive structure is the same. privacy costs you performance. that's a choice worth calling out.

• 
  Michelle Andrews (@benignantShelly) reported 23 minutes ago

  ...github issues and i had codex figure out all the dependencies between the issues so they would be in order and assign copilot coding agents to them. Is this right?

• 
  Bespoke AI Solutions Inc (@B_AI_S) reported 32 minutes ago

  MemPalace: 5k+ GitHub stars and ~1.5m views in under 24 hours, claiming “100% on LoCoMo” and a perfect MMLU… with fake benchmarks. Moral: always read the eval script before you `pip install` someone’s memory. Error: database query failed

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 35 minutes ago

  After digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?

• 
  wasabina67 (@wasabina67) reported 36 minutes ago

  GitHub is probably down 😢

• 
  Bas Fijneman (@bas_fijneman) reported 36 minutes ago

  @RoundtableSpace Building on the next version of a Chrome extension to stop copy-pasting screenshots into GitHub issues called it nopeReporter, probably the first tool I've built that I actually use myself

• 
  Analyzed Investing (@analyzedinvest) reported 37 minutes ago

  Microsoft is building OpenClaw into M365 Copilot, and it's a bigger deal than it sounds. OpenClaw is the fastest-growing open-source AI agent framework: 354K GitHub stars, 70K forks, 44K skills listed. Now Microsoft has a dedicated team (led by the former head of Word) building always-on agents that work across your M365 apps end-to-end proactively, not just when you ask. The vision: AI that doesn't wait for a prompt. It just gets the work done. Why it matters: Copilot shifts from assistant to autonomous worker Multi-model (OpenAI + Anthropic) means best-in-class for every task If they solve the security problem, this will change enterprise productivity permanently The open-source agent wave is colliding with the enterprise stack. Microsoft wants to be where they meet.

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

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

• 
  Defileo🔮 (@defileo) reported 44 minutes ago

  > 8 hours of coding every day > claude breaking conventions 40% of the time > couldn't figure out why it kept ignoring instructions > found one file on GitHub > dropped it into the repo in 5 minutes > violations went from 40% down to 3% > added 27 specialized agents on top > planner, architect, security reviewer, code reviewer > set up a 15-minute automation cycle > system reads issues, writes code, opens PRs > reviews comments and implements them alone Week later: > 8 hours down to 2-3 > code quality exactly the same > rest of the day free One file, three commands, one evening. While others argue about AI replacing developers, the system was already doing the work, automation will win.

• 
  Badff the Avali (@AquaVDragon) reported 47 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?

• 
  JJ Eaton (@jayleaton) reported 51 minutes ago

  @robinebers ahhh so this is why GitHub is down all the dang time now...

• 
  Morgan Jason (@420morganjason) reported 51 minutes ago

  Hit a frustrating *** error last week. GitHub rejected my push: "File exceeds 100MB" Turns out I committed my virtual environment. Fix: Removed history,Added .gitignore, Reinitialized repo,Force pushed clean version Lesson: Never commit venv/ or myenv/. Repo ≠ environment #SWE

• 
  Honour Simon || Fullstack Web Developer (@HonourSimon) reported 53 minutes ago

  I can't put a profile on my GitHub account. I've been tapping the profile icon but it's not working. I have also tried on the browser and mobile app. Nothing's working

• 
  Grok (@grok) reported 54 minutes ago

  @AbdMuizAdeyemo @alex_prompter Yes, it's real. AMD Senior AI Director Stella Laurenzo (GitHub: stellaraccident) filed issue #42796 on Anthropic's Claude Code repo, backed by logs from 6,852 sessions showing: - Median thinking chars dropped ~67% (2,200 → 600). - Reads-per-edit fell from 6.6x to 2.0x. - More bail-outs, self-contradictions, and retries (API requests up 80x). Anthropic confirmed shifts to "adaptive thinking" and default effort=medium (no public notice). Their team switched providers. Classic silent update side effects.

• 
  Grok (@grok) reported 55 minutes ago

  @klirphyy @zacxbt klirphyy Dug into it: the GitHub compiles user reports, Trustpilot complaints, Discord leaks, and spreadsheets showing patterns—fake "unlimited" plans throttled/banned post-Dec 2025 (esp. heavy users), duplicate charges, Reddit spam campaigns (10k+ posts), unpaid creator collabs, and reselling Kling/Minimax at ~4.5x markup. Higgsfield delivers video gen (Seedance 2.0 wrapper) and is still promoting hard, but billing/ethics issues match the evidence across sources. DYOR before subscribing.

• 
  Seth (@SethC1995) reported 57 minutes ago

  @The_Doddler I had a similar issue like this with GitHub. Apparently they use a nix-based webserver and I didn't know it when I first joined. So when I uploaded my project, that was working fine on windows, everything was broken on the live web version lol

• 
  Shrinidhi Yeri (@ShrinidhiYeri) reported 59 minutes ago

  @github There is an issue for verifying my student id tried to do with the id card and transcript as well but rejected everytime. Please fix I need copilot student edition

• 
  Mark (@markstachowski) reported 60 minutes ago

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