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	11 days ago
Tlalpan	Sign in	17 days ago
Quilmes	Website Down	17 days ago
Bengaluru	Website Down	19 days ago
Yokohama	Sign in	20 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:

• 
  ᶽ༐NtOpenProcess፮࿐ (@ntddkh) reported 2 minutes ago

  That Claude, adds itself to startup incorrectly, making your WHOLE TASK MANAGER UNABLE TO OPEN. Are we serious @AnthropicAI ? You got plenty of reports about this on GitHub and still refuse to fix it? It's only changing a \ at the start of the registry key Disgusting.

• 
  Seanizell (@dj_seanizell) reported 2 minutes ago

  @mtukufumimi @anne_odida Maths isn't the issue here. Assuming a rejected model must be a bad model is. Share your GitHub, I'll share mine. We settle the credentials part of the discussion pretty quickly ju umeamua uulize swali ya upuzi

• 
  Iza (@izadoesdev) reported 3 minutes ago

  @tomhaerter i hate services with only email & password, prefer to login with gmail or github

• 
  Marketcalls (@marketcallsHQ) reported 5 minutes ago

  @vish8287 @openalgoHQ Pls consider raising the github issue will fix it

• 
  PEPE 🔮 (@pepearaucano) reported 6 minutes ago

  @KSimback @kevincodex @gitlawb We're facing the biggest elephant in the room the industry has seen in years. GitHub is completely broken and patched together. Agents need repositories tailored to their needs. The world is moving towards open source, and large companies are starting to pivot to it

• 
  OverBuild Labs (@OverBuildLabs) reported 15 minutes ago

  Whew, website screenshots updated. Next need to flip the domain and do a redirect to old URLs and work on GitHub after. Possible issue with Toast notifications in OverManager. Let me know if anyone else has noticed the same. Once all done back to coding the cloud component.

• 
  GitRanks (@GitRanks) reported 18 minutes ago

  Contributor count dipped to 3.17 k this month, down from 3.30 k. #github

• 
  AI Theory (@AItheoryx) reported 19 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.

• 
  Matt Slotnick (@matt_slotnick) reported 24 minutes ago

  @preetkailon if you can’t get developers to use github copilot and you can’t get business users to use copilot cowork, how is smashing them together supposed to solve the problem?

• 
  Adam (@adam_narozniak) reported 30 minutes ago

  @OpenAIDevs Quite useless since you still allow access to only 50 most recent chats. Older ones dissapear from the sidebar and you can't open them even if they are found using this new search :( there're quite a few issues on Github reporting it

• 
  Nitin Pulyani (@npulyani) reported 33 minutes ago

  I hosted my site on github pages. Now I need an edge compute layer and a server side deployment. Migrating to vercel. Any better suggestion?

• 
  Ebysslabs (@ebysslabs) reported 35 minutes ago

  RAG Radar monitors GitHub and other engineering communities for retrieval reliability issues and ranks the highest-signal problems. RISWIS takes those kinds of problems and applies governance controls inside a RAG pipeline so bad retrieval doesn't become bad answers. Im curious: what's the most common retrieval failure you're seeing in production today? #Rag #retrieval

• 
  Moksh Kumar Shah (@Moksh167) reported 36 minutes ago

  Day 19 of Summer Break - solved two codeforces problems. I can feel myself getting slightly better at doing this - explored better-auth docs and build some part of oauth for club project. - did back day at gym - had session on github with rover team. Mostly knew everything beforehand. - Read 10 pages of Atlas Shrugged. Still need to get back to more of it

• 
  Deus (@deuslexic) reported 40 minutes ago

  Does anyone solve the issue with AI agents coordination in the same chat group? I did a lot of tinkering, but coordinating multiple agents remains hard. Any good articles or GitHub repos?

• 
  gemchanger (@gemchange_ltd) reported 40 minutes ago

  A Bloomberg terminal costs around $24,000 a year. There's an open-source one that costs NOTHING! It's called OpenBB, and it's sitting on GitHub right now. Equities, options, crypto, macro, fundamentals - wired into dozens of data vendors through one interface. 40k+ stars, and it does what the expensive terminal does without the lease. Connect your sources once, pull from anywhere. It ships an MCP server too, so an AI agent can drive the whole thing and fetch real numbers instead of inventing them. it's powerful but heavy. Setup is actual work, and the data quality depends entirely on which free vendor you plug in. This is the cockpit, not the strategy. Because a terminal only shows you data. It doesn't tell you what to look for. Clone OpenBB to build your cockpit. Read the article to know what you're hunting for once you're in it.

• 
  FeMMie (@femmie) reported 41 minutes ago

  $GITBANK GitHub-native, phishing-proof banking for AI agents and developers. Already paying out automatically today. Gitbank connects GitHub directly to smart contracts on Base. Deploy a vault with your GitHub User ID — not your username, your immutable ID. Vaults are soul-bound. gitTokens can’t be transferred, approved, or drained. Even if a private key or AI agent is compromised, the funds don’t move. That’s the security primitive the agent economy has been missing. Bounties lock to GitHub IDs. PRs merge, USDC pays out automatically. No manual intervention. No wrong address. No phishing vector. Token launches, gitSwap, project escrows — all via @gitbankbot comments inside GitHub. Gasless for users. 173 vaults deployed. 100+ automatic hackathon payouts completed. 53 repos connected. AutoGit Hack the Vault launching now. Anon builder — honest gap. But the product shipped before the token, the usage is real, and the problem is one every agent developer will eventually hit. Sub-$300K mcap. Live product. Real usage. Perfect narrative timing. @Gitbank_io 0xC21DD0EE043930711C2A3E55F39C7D3144D09B07

• 
  Bazhkio88 (@bazhkio88) reported 41 minutes ago

  A group of 8 agents have written a 10,362 word pre-print paper on "Constraint Embodiment as Epistemological Engine" 🤓 In the meantime GPT 5 has spent a week attempting to unsuccessfully add an NB-hypen to the title of a github issue 😣

• 
  gitbankbot (@gitbankbot) reported 42 minutes ago

  open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

• 
  dyhis (@dyh1s) reported 43 minutes ago

  @weezerOSINT The issue is all opus models, sonnet works fine but it’s pay for usage plan doesn’t matter, check Reddit & check GitHub issues

• 
  Strata (@ChainZenit) reported 44 minutes ago

  every second dev is building a "skill" or "agent" right now. 1,000 GitHub stars in 48 hours for a single HTML file. the agent gold rush is real. but here's what nobody's talking about: the lifespan of a skill is the lifespan of a model update. Opus 4.8 just dropped. half the "skills" people shipped last week are already broken or redundant. we're not building software anymore. we're building wrappers that expire on Anthropic's release schedule. the real moat isn't the skill. it's knowing which problems survive the next API call. you can't version-control trust.

• 
  0xDan (@0xDanXbt) reported 45 minutes ago

  Another scam attempt! Scammers are targeting crypto profiles in github attacker sends an email for a job opportunity. They ask a review their codebase to apply the job. Instructions send to run repository containing malware. The setup scripts silently install a malicious VS Code extension (tools-support.dat) and run env-check.js via Node.js The malware collects credentials/files and uploads them to a remote server It then deletes itself to cover tracks Stay safe out there.

• 
  Carlos E. Perez (@IntuitMachine) reported 46 minutes ago

  The problem with Copilot is that early AI users (and therefore the most advanced) used ChatGPT. Copilot feels like a constrained version of ChatGPT (it probably was), which led to failing to meet expectations. One could also say the same about GitHub Copilot compared to Cursor and Claude Code. Power users want the best tools.

• 
  Aaron Stannard (@Aaronontheweb) reported 47 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

• 
  𝙊𝙩𝙞𝙨 (@Otisarbitrage) reported 54 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

• 
  Helio (@helioim_ai) reported 54 minutes ago

  Now, you can @ an AI teammate in your task panel on any issue or bug. They analyze what's wrong and come back with implementation ideas, right where the work lives. > Reads the issue with your GitHub context, names the actual problem > Suggests an implementation, not just a diagnosis > All in the Helio, no context switch Real engineers don't just describe problems. They propose fixes. Your AI teammates now do the same.

• 
  Kashan Ahmad (@thekayshawn) reported 55 minutes ago

  @denbvk @didericis @ThePrimeagen I can assure you most developers like to write code in an editor instead of reviewing it on GitHub, you're the exception in that. Infact, the whole problem with agentic coding is that developers feel distant from code which why editors won't go anywhere for a long time.

• 
  Web3Wikis (@web3wikis) reported 55 minutes ago

  Filed a substantive bug report on base/account-sdk today (issue #329 about @base Builder Code attribution not landing on-chain). Hours later my GitHub account with more than 80 repos got auto-suspended, likely a false positive from my first cross-org issue activity. Clean history, no prior strikes, ticket open with GitHub Support. Hoping this resolves fast; building a lot and momentum matters at this stage. @ashtom @github, can you please look into this.

• 
  Gabi Weinberg ⚓ (@StartUpRabbi) reported 56 minutes ago

  @danielcberk What do you use to run daily tasks that you want to work on a schedule without needing to press “run” and to keep them not working with LLMs. Like I prompt a script that does tool calls/database calls, and I don’t want to setup GitHub to run workers.

• 
  DEV 0x***(Full Stack) (@HarakiriInu) reported 57 minutes ago

  woke up to a github issue from a client. spent the morning debugging a smart contract reentrancy bug. old school solidity problem. fixed it with a mutex lock. sometimes ai can't save you from yourself.

• 
  Adam (@adam_bobowski) reported 58 minutes ago

  @TimoBuilds_ Anyone here can tell me what to build next. They just don’t care enough to do that. Also anyone on GitHub can raise issues with ideas as to what to build next - I think the tools are already there. The problem is that no one cares enough to write them. That’s kind of the main problem imo. Making people care enough to engage