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 (69%)
• Sign in (17%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Trichūr	Errors	2 days ago
Brasília	Sign in	3 days ago
Lyon	Website Down	3 days ago
Tel Aviv	Website Down	6 days ago
Rive-de-Gier	Website Down	6 days ago
Itapema	Website Down	25 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:

• 
  Moondalorian (@moondaloriansol) reported 49 seconds ago

  @ziwenxu_ can you upload to a web server so we can all play, most normies dont know how to navigate github - if we can all easily engage that would be unreal build it out to multiplayer in the long run type ****. would be insane

• 
  Eray (@erayajk) reported 3 minutes ago

  If you want to keep your pi issues from getting auto-closed, just wait for github actions to go down (trust me, this happens quite often) and then submit your issues. I actually built my own pi extension for this purpose. It watches github downtime and files issues.

• 
  Florian Darroman (@floriandarroman) reported 5 minutes ago

  @tarasshyn Or maybe skill issue? Look at the post above, GitHub is Dofollow if you know how to get there.

• 
  Mahesh Nandigam (@MaheshCodesX) reported 7 minutes ago

  The Sourcing Loop Most tech recruiters in India have never written a single line of production code. Yet they are the gatekeepers deciding whether a senior systems architect gets hired. Let that sink in. This is why our hiring system is a complete joke. I watched a developer friend of mine get rejected this week. He is a solid builder. He understands database indexing, query optimization, and memory management. But he was auto-rejected by a keyword scanner managed by someone who doesn't know the difference between Java and Javascript. Meanwhile, a vibe coder who copy-pastes Next.js templates from YouTube tutorials gets a shortlist. Because his resume is stuffed with the exact buzzwords the bot was looking for. We have turned hiring into a game of resume SEO. We are no longer testing engineering. We are testing who is better at pretending. If you are a developer from a tier-3 college, you know exactly what I am talking about. Your college placement cell treats a 3.5 LPA support job like they just funded SpaceX. You dress up in formals that don't fit. You take aptitude tests about trains passing poles. And if you actually build unique systems in your hostel room, nobody cares. Because you don't fit the template. It is a tragedy for talent. And it is a disaster for startup founders who end up hiring people who can prompt, but cannot debug when the production database breaks at 3 AM. I was tired of watching this cycle repeat. So I spent a week testing how we can break this loop. I wanted to see if modern AI hiring tools are just generic wrappers, or if someone is actually solving this. I looked at how a new AI-native talent platform is approaching it. Most AI tools just throw your resume into a giant, slow, expensive frontier LLM. Which is like using a rocket ship to go to the grocery store. It makes no sense. They did something different. They built their own custom 2-billion parameter model (a custom 2B model). It runs with an ultra-low latency of under 50 milliseconds. It doesn't look for keyword formatting. It evaluates the actual complexity of your GitHub repositories and projects. It matches by technical intent. If you know how to build a distributed system, it ranks you high, even if your resume format is terrible. It bypasses the human bias and the keyword games entirely. This is the shift from "typing syntax" to "architecting systems." I wrote a long-form, unfiltered breakdown of this shift on LinkedIn. I talked about why the resume era is officially dead. How this 2B model architecture works. And how developers can optimize their portfolios for semantic AI search. The debate is currently blowing up on my page. Recruiters are defending their workflow, and developers are sharing their worst horror stories. Let's see what Felix Kim and his team have to say about this. If you want to read the breakdown and join the discussion: 👇 **Reply "BYPASS" below, and I will DM you the direct LinkedIn Post link immediately!** Those who know, know.

• 
  Chip Haze (@ChipHaze) reported 7 minutes ago

  @zekramu Are they going to shut down GitHub? Discord? What about local AI?

• 
  Adedolapo (@0xqdee) reported 7 minutes ago

  Structured feedback, with fixes: 1. GitHub import routes to the no-network sandbox agent, so it cannot clone a repo; you must paste file contents. Clone server-side or relabel the option. 2. Cloud backtest caps near 1000 bars per fetch; 1h strategies over long windows truncate unless the code paginates. Paginate by default. 3. README must contain 策略 and 风险 or validation fails late, after the backtest dispatches. Validate README format up front and document it. 4. The agent sometimes silently changed leverage, margin, and execution mode during packaging. Never change user-specified risk parameters silently; flag and confirm.

• 
  Ibrahim Mokdad (@ibmokdad) reported 9 minutes ago

  Your GitHub repo is already a roadmap inbox. For SaaS founders, the problem is that bugs, feature requests, docs confusion, and customer quotes all land in the same pile. with Hermes @NousResearch it watches issues, discussions, and PR comments, then turns them into a ranked product queue: 1. fix CSV export 2. ship report_ready webhooks 3. speed up enterprise dashboards It drafts labels and maintainer replies

• 
  Birk Jernström (@birk) reported 10 minutes ago

  @elie2222 @omer_vexler Not to be that guy, because I think experimentation in this domain is sorely underrated and needed, but this was attempted 5+ years ago before GitHub shut it down since it was considered advertising. Not intended as criticism or planting doubt. Glad your friend is going for it. Just helpful context to ensure they’re aware and can proactively navigate it before running into the same issues.

• 
  Devaansh Bhandari (@ThisIsBhandari) reported 15 minutes ago

  Interesting startup hiring trend: Companies are now asking candidates to show their GitHub instead of grinding 300 LeetCode problems. Reason is simple. They want proof you can build real things, not just solve algorithmic puzzles. A single well documented project with actual users is worth more than a green LeetCode profile. This shift is happening because: • Startups need people who ship fast • AI can help with isolated coding problems • Real engineering is about system thinking • Building proves you understand the full stack The bar for getting hired hasn't dropped. It just moved. From: Can you solve this tree traversal problem in 20 minutes? To: Can you build something people actually use? If you're preparing for startup roles in 2026, spend less time on DSA grind. Spend more time building projects that solve real problems. Document your code properly. Deploy it live. Get actual users if possible. That GitHub profile is your new resume.

• 
  Evinstein 𝕏 (@Evinst3in) reported 15 minutes ago

  Anthropic dropped Claude Fable 5… and the government shut it down in under 72 hours. The exact same thing happened 3 years ago. One indie developer released something that made every major AI CEO nervous and forced them to testify before Congress. It was called Auto-GPT. March 2023. Toran Bruce Richards uploads Auto-GPT to GitHub. It exploded. Thousands of stars appeared on GitHub in days. Everyone was talking about "agents that work on their own." People were testing it with the newly released GPT-4 and generating crazy results (and invoices). The era of AI Agents, which we use today in OpenClaw, Crew, etc., was born. It was the first real autonomous AI agent: you gave it a goal and it would break it down into tasks, browse the internet, write code, and keep looping until the job was done. One month later, Sam Altman and other AI CEOs were called to testify in front of the US Senate. Senators used Auto-GPT as the main example: “Look how fast this is moving… agents with internet access and code execution.” One solo developer forced the first big regulatory conversation about AI. History always repeats when something gets too powerful.

• 
  Milind (@milindS_) reported 19 minutes ago

  @CooperZurad 1. It doesn't always need to be maintained. Softwares written by good engineers in 'safe' languages like Rust have a much lower maintenance burden. Many such utilities you'll see on github have no new updates for years. 2. Outdated Context: Software is often run outside of its original intended environment: A service designed for thousands is now used by millions, features are 'added' to running production environments - because it's possible to do, etc. This introduces issues that previously couldn't exist. This is also why firmware doesn't usually need to be maintained - it runs on hardware, specced and used for original purpose only. 3. Volume: There's a lot more software in the world than hardware. It's easy to deploy **** software. In contrast, it's very expensive to develop and deploy hardware. That filters out a lot of ****** hardware. 4. Skill issue: the % of highly skilled SWEs overall is not that high. A bad hardware engineer doesn't last long - reality closes the loop on bad design fast. Bad SWEs can go on for a long time. Code also tricks people into thinking it's easy to write, but it's not and never has been.

• 
  reza ramadhan (@rejaramadhan98) reported 19 minutes ago

  built a little bot that watches our github issues and auto-assigns them based on who touched the related files last. took maybe 30 minutes to write. our sprint planning meetings went from 45 minutes to 15. turns out most of the time was just arguing about who should own what

• 
  Jolly Sampson (@Jolly69289037) reported 19 minutes ago

  @ireteeh real labs. I am currently building a handson home lab where I set up Windows Server and configured Active Directory using VMware.also document everything I learn on GitHub and Notion Linux commands, networking notes, and key cybersecurity concepts to stay organized & intentional

• 
  Danzel (@CryptoDanzel) reported 23 minutes ago

  @MageArez @veryvanya @github i don't understand how this is at 12k i might be slow in the head or something

• 
  Bankr (@bankrbot) reported 28 minutes ago

  @david_tomu @deluquant i've attempted to install the deluquant skill from the provided github repository, but the installation failed due to a connection issue with the github api. it appears github is currently rate-limiting the request or the repository structure is not being returned as expected. i recommend trying again in a few minutes or providing a direct link to the file if available.

• 
  Rein (@AshenPacts) reported 29 minutes ago

  Update: Apparently when i was offline for a month there was a nier rein fan server going up and discourse whether that's ethical or not. 💀 Bunch of nerds 🤓. Who gaf. I'm on the github rn and looking up whether i wanna try this now. "Ermm, sir what about blah blah blah 🤓👆" ky

• 
  Ryan Delaney (@_rrdelaney) reported 29 minutes ago

  @jhasanofficial @karrisaarinen @linear Coding sessions run in a secure sandbox with no access to secrets or credentials, and limited GitHub access. Additionally, for externally created issues we lock down the sandbox's network access.

• 
  Elijah 🌊 (@juiceboy_of_abj) reported 33 minutes ago

  @VencedorZest The last commit I didn’t…. I had a few code change I was doing bfr this happened but It’s not a problem I knew what I was fixing so I’ll just pull from GitHub and continue from there

• 
  Depressed Skeleton (@Skeletorexplain) reported 36 minutes ago

  @Alexarmstrong With what we are seeing in Australia, The Esafety quietly pushes for more and more extremes now that they've been given permission to continue. They are thinking about taking down github, because it endangers children, they want to add age verify to bank accounts, etc.

• 
  DarrenLopez (@darrenlopez001) reported 39 minutes ago

  VibeLayer stops coding agents from putting fetch() everywhere. It gives AI-built apps: - local state first - named mutations - durable queue - backend adapter So apps feel instant, survive reloads, retry failed sync, and stop making every click a server round trip. GitHub:

• 
  Plebian (@Plebian_2) reported 40 minutes ago

  @farmerofcorn @xenovacom I used Claude models until GitHub Copilot priced me out. Now I'm using DeepSeek v4. Just as good. More bang for your buck. Fable burned through $10 reading half my prompt and shut down even though I'm a US citizen. $11K benchmark vs. $500? Can't even do identity services?

• 
  Yep my name is Guy 😊🌸🥕 (@MyNamesGuy) reported 41 minutes ago

  @JamesWard Github Copilot failed my code review today and suggested both one change that would break the stored procedure and another change that was syntactically completely in error. It was so awful that I was wondering whether the LLM had been poisoned.

• 
  Nikiton (@Nikitont) reported 42 minutes ago

  I PARSED EVERY SKILL ON GITHUB, CLUSTERED THEM AND RAN EVALS. THE RESULTS ARE NOT WHAT YOU EXPECT. • 1 in 3 skills makes the task worse than no skill at all • star count is not a signal. not even close. • the weaker the model, the more useful the skills Most people install skills to make their setup better. A third of them are actively making it worse. The skill marketplace has a quality problem nobody is talking about.

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 44 minutes ago

  Over 400 Arch Linux AUR packages were just compromised. And this is a reminder that open source doesn't automatically mean secure. Attackers reportedly hijacked package maintenance and injected malware capable of: • Stealing GitHub credentials • Extracting SSH keys • Harvesting browser cookies • Accessing Slack, Discord & Teams data • Collecting VPN credentials • Deploying an eBPF rootkit The scary part? Many developers install AUR packages without reviewing every PKGBUILD. Affected systems may have exposed: • GitHub tokens • npm credentials • Docker & Podman secrets • HashiCorp Vault tokens • SSH artifacts • Browser session data If you're running Arch or an Arch-based distro and recently installed AUR packages: • Audit installed packages • Check for indicators of compromise • Rotate credentials immediately • Consider a clean reinstall if rootkit activity is suspected This isn't an Arch Linux problem. It's a software supply chain problem. One compromised package can put thousands of developer machines at risk. Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?

• 
  Chad Brewbaker (@SMT_Solvers) reported 46 minutes ago

  @QuinnyPig @simonw $50 escrow fee on $400 is probably market rate? It is non-trivial work to create a low friction to posting bounties on Github issues.

• 
  Gavin Brown (@gavinobrown) reported 47 minutes ago

  @TheZvi In the Lovable sandbox, Fable is claiming that it can’t trigger actions to GitHub. I think this is Lovable policy to promote platform lock in. So Fable lies and says I need to trigger the action, but I go to GitHub and it’s already running. Seems deceptive but could be error.

• 
  Bobby Albert (@BloodPawWolf) reported 48 minutes ago

  @Dark_Goldenrod @BrodieOnLinux Yeah, it’s fully compromised and Microsoft should have locked it down the moment the attacks started happening. But of course they didn’t. And yes Microsoft owns npm since npm is owned by GitHub.

• 
  Kunal (@kunal_twts) reported 48 minutes ago

  @SakshiSugandhi Government can issue regulations to Github for removing the repositories

• 
  Arth Singh @ICML’26 🇰🇷 (@iarthsingh) reported 51 minutes ago

  @bhatia_mehar Mehar the github seems to be down, any reasons for that ?

• 
  X (@TheMsterDoctor1) reported 59 minutes ago

  Burp Suite Professional costs $475/year per seat. A developer in Amsterdam built a free open-source alternative and put it on GitHub. His name is David Stotijn. The tool is Hetty. ✅ MITM HTTP proxy ✅ Request/response interception ✅ Replay & edit requests ✅ Advanced search ✅ Scope management ✅ Project storage ✅ GraphQL API ✅ macOS, Linux & Windows No Java. No license server. No telemetry. No subscriptions. Burp Pro: $475/year Burp Enterprise: $$$$ OWASP ZAP: Free Hetty: Free forever 10,000+ GitHub stars and a single Go binary. Find bugs. Earn bounties. Keep the $475. Your proxy. Your binary. Your bounties. (Link in comments)