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	10 days ago
Tlalpan	Sign in	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 days ago
Gustavo Adolfo Madero	Website Down	23 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:

• 
  asi (@asiyaps_) reported 7 minutes ago

  call her github the way she keeps going down on me

• 
  ShWnD (@h3xhammer) reported 9 minutes ago

  A fork of the original N!ghtm@re 3cl!pse BL bypass might still be available on GH: MS can get fukt. Fix your sh!t, don't cens0r. fckng tw@ts

• 
  AI Theory (@AItheoryx) reported 12 minutes ago

  Microsoft is building a super app that combines all of its Copilot tools into one place. GitHub Copilot. Copilot chat. Copilot Cowork. And a new agentic workflow tool internally called Autopilot. One interface. One destination. One login. The internal slogan is Delivering one Copilot. Here is why this is happening and why it matters. Less than 4.5% of Microsoft 365's 450 million customers pay for Copilot features. That is one of the worst conversion rates for a major enterprise AI product. The reason according to sources is simple. Customers hate switching between different Copilot tools. The fragmentation is costing Microsoft money. GitHub Copilot has 4.7 million paid subscribers at $10 a month minimum. But it is losing ground fast to Cursor and Claude Code. Microsoft's consumer Copilot chatbot is significantly behind ChatGPT and Gemini in active users. Microsoft was the first major tech company to make a serious AI bet. $13 billion into OpenAI in 2023. They had a two year head start on almost everyone. They spent that head start launching multiple versions of Copilot that confused customers, splitting their teams between consumer and enterprise, and relying heavily on OpenAI models while competitors built their own. The super app is the attempt to fix all of that in one move. Launch is targeted for end of summer 2026. Some elements may surface at Microsoft Build next week in San Francisco. The app itself will not be shown yet. Satya Nadella promoted Jacob Andreou in March specifically to unify the Copilot product line. This super app is Andreou's primary assignment. Microsoft still has 450 million Microsoft 365 customers. If the super app moves conversion from 4.5% to even 10% that is tens of billions in new recurring revenue. The lead is gone. The distribution is not.

• 
  Vinay ⚡️ (@VincentAyorinde) reported 13 minutes ago

  Fix 5: Scan with Zizmor pip install zizmor zizmor .github/workflows/ Catches dangerous configs, script injection risks, and overly permissive tokens before they reach your main branch. Free. 2 minutes to set up.

• 
  Eji (@mildsky1215) reported 15 minutes ago

  @ntotao @xai Cleanest setup: ~20 real GitHub issues that ship with test suites, run each model agentically until tests pass (cap at N turns), then log median turns-to-green, total $, and % solved. SWE-bench Verified is the closest public proxy but it under-weights turn-count and cost, and turn-efficiency is the number nobody publishes.

• 
  Peter Fox (@peterfox) reported 16 minutes ago

  Today's the first day where I've really seen just how clumsy and poor the UX of @github is. We really need a better way to work. If more effort was put into the UX instead of stuffing AI in, we wouldn't have this problem.

• 
  Dave Barnwell (@dave_barnwell_) reported 17 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  Mohi 🇮🇷🇩🇪 (@disismohi) reported 19 minutes ago

  I'm not saying every exploit belongs on GitHub. But the inconsistency is the problem. Either you allow security research or you ban all offensive tooling. You can't pick based on vendor pressure.

• 
  Shiv (@shivkmojha) reported 20 minutes ago

  The sources: Stripe — failed charges, failure codes, revenue at risk Sentry — fatal + error exceptions that correlate to the failure window GitHub — recently merged PRs (the deploy that likely caused it) Datadog — triggered monitors (error rates, latency spikes)

• 
  Aaron Stannard (@Aaronontheweb) reported 23 minutes ago

  Netclaw just kicked off 300 something dependabot updates across all of our repositories, so you know who to blame if there's a GitHub Actions outage in the next 30 minutes or so

• 
  Gitforge (@GitForge_io) reported 29 minutes ago

  GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

• 
  Rahul 🥷 (@themishra4402) reported 33 minutes ago

  @raajtalluri the next trillion dollar idea is probably sitting on github today with 12 stars and a terrible readme

• 
  Dharan (@DharanGanesan) reported 36 minutes ago

  A single GitHub issue got 27 pull requests from AI bots. Most were untested. Some hallucinated entire implementations. The real contributors? Buried under noise. The fix is a *** hack most devs don't know about. GitHub's "Limit to prior contributors" setting blocks everyone who hasn't committed before. But you can whitelist real humans with *** commit --author using their noreply email. Credits them, doesn't need their SSH key. We built systems assuming contributors are humans. AI bots exploit that because GitHub can't tell the difference. Maintainers spend hours cleaning AI slop instead of reviewing real code. This is a maintenance crisis nobody wants to name. #AI #OpenSource

• 
  𝙊𝙩𝙞𝙨 (@Otisarbitrage) reported 37 minutes ago

  Step 4: Agent synthesizes and acts. It reads submissions, identifies common friction points, generates a bug report, and creates a GitHub issue automatically. Step 5: Amplify the launch announcement. Same agent fires an X raid on the launch tweet for $2.50 - 50 likes, 20 reposts

• 
  pork (@porktoolbox) reported 37 minutes ago

  So many open-source apps in GitHub are now "vibe-coded" with AI. I've just seen it short-sightedly fixing bugs while creating other problems in a famous niche app. It's sad to see. Where would this evolve into?

• 
  Lidvark Windjammer (@DWindjammer) reported 37 minutes ago

  @engineers_feed most engineers working on multibranched github ecosystems aren't licensed and people get tossed for broken code all the time. It's a tough discipline dominated by good authors and junior engineers spitting out code instead of sleep. Vibe coding empowers seniors instead of juniors

• 
  rohan (@rohandevs) reported 38 minutes ago

  overheard in sf: is the wifi cooked or is github down?

• 
  Büke Beyond (@BukeBeyond) reported 38 minutes ago

  @Skirge01 @exQUIZitely read your own article: "GitHub Open Source Survey ~95%~3%" Male Female, "1% non-binary, 1% unreported" that is down to 1% sampling noise. If all your fantasies are true: there should be clear evidence in github.

• 
  Cocoanetics  (@Cocoanetics) reported 40 minutes ago

  TIL that @github doesn’t have a way with the `gh` CLI to upload an image for a comment. There’s a gh-image extension but that requires a logged in web session. UGH! @gitlab oh the other hand does have a proper API that you can automate. I found this from building a way for my agents to upload proof-of-it-working screenshots to issues as comments. Glab no problem. gh no go.

• 
  Kargathara Aakash (@imkaakash) reported 41 minutes ago

  @ThisIsBhandari this is exactly why we built Saral AI to map those live building signals across GitHub, X, and Stack Overflow ... so companies can find builders based on real execution, not broken application funnels

• 
  Alpha Signals on X (@Alpha_Signal_X) reported 44 minutes ago

  @AnthropicAI @claudeai @DarioAmodei One week NO response from Claude Support on paid account that needs backend fix. How can this company IPO at 1T when it can even respond to emails, GitHub or Fin AI? This market is too competitive to be loyal to un loyal companies.

• 
  Dan Greenheck (@dangreenheck) reported 44 minutes ago

  @AndrewDeWitt88 Sorry, I need to fix it to be less confusing. Scroll down to Links section, there is link to Github.

• 
  Timur Yessenov (@Timur_Yessenov) reported 44 minutes ago

  @Runclawrun @Runclawrun Right now it is embarrassingly stitched together: GitHub issue/branch, one checkpoint file per run, and a Telegram status card from cron. Closest is Codex/Claude Code summaries, but I still miss the queue view: blocked/done/waiting across runs.

• 
  Matt Cowley (@MattIPv4) reported 45 minutes ago

  @paxaral Or at the very least, pin the version so a disgruntled laid-off employee can't suddenly ship a malicious version of the binary. I followed up with the team via Discord as they locked the GitHub issue 🙄, and it sounds like they've realised this risk now and are going to pin it.

• 
  Akshit Kr Nagpal (@akshit_io) reported 46 minutes ago

  AI coding agents need private evals, not leaderboard faith. SWE-bench tells you if a model can fix public GitHub issues. It does not tell you if it can survive your repo: - weird conventions - stale helpers - hidden invariants - rollback paths My test now: replay an old PR and see if the agent changes the same 3 files for the same reason.

• 
  NGMI Sui (@NgmiSui) reported 49 minutes ago

  @Zforever97 @Lidlmedewerker1 storage zk login gasless transfers a whole new langage crosschain swaps finality optimisations sui ships something new almost every 1-2 months what does icp ship, i tried looking at the github

• 
  Alessio Persico (@alepbuilds) reported 50 minutes ago

  @Zenysi_ Happy to connect, current building a devtool for solving my own problem in searching validation around hackernews GitHub and more. What are currently working on?

• 
  Rytchie ☠️ (@rytchiemacharia) reported 52 minutes ago

  @KazimAIZJU @github @AnthropicAI had the same issue

• 
  Martin (@Unpopular_Tech) reported 54 minutes ago

  Microsoft owns GitHub, Microsoft built Copilot Microsoft has a $13 billion investment in OpenAI and their engineers still went looking for something else if your own people won't use your product that's not a cost problem, that's a verdict

• 
  Neuroquark (@neuroquark) reported 57 minutes ago

  @malhar_kamble that's what i thought. i'll push it to *** and for extra security i'll encrypt it using symmetric key encryption the problem is i have private repo contributions turned on so every time i push it to github it'll show up as a +1 on my chart which i don't want