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

Live Outage Map

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

City	Problem Type	Report Time
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
Kannur	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:

• 
  Deploy & Pray 🆚 prodfixai.com 🟢 (@iDeployAndPray) reported 57 seconds ago

  @cyrilXBT everyone is building MCP servers for dev tools. github, postgres, filesystem, code stuff. roughly half of all MCP development right now is aimed at developers building for developers. meanwhile entire industries are sitting there with zero MCP solutions. real estate, logistics, healthcare operations, restaurant management. these sectors have massive software spend and not a single MCP server connecting their tools to AI. built MCP integration for prodfix because dev tooling is what i know. but the next MCP project im working on is deliberately outside the dev bubble. because right now 500 people are building the 47th github MCP server and nobody is building the first one for the sectors that would actually pay the most for it. the MCP gold rush is real. but everyone is mining the same hill.

• 
  Scott Ingram ✝️ 🇺🇸 (@ScottIngram334) reported 1 minute ago

  @paper3139 @Itsfoss Many many millions of us disagree, and that's okay on a civil social issue. Do they say the same thing in their brand pages? I haven't seen it, please share more. I'd love to be consistent. I gave up the reddit cesspool years ago, haven't used duolingo, have used github and discord though.

• 
  Teknium (e/λ) (@Teknium) reported 7 minutes ago

  @evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!

• 
  GooGZ AI (@PaulGugAI) reported 9 minutes ago

  PSA: Hermes Agent / OpenClaw & Godmode (GODMOD3) Be aware that this exists. GODMOD3 (on github) lets you chat with most LLMs through openrouter. It's built for hackers and researchers to test or bypass post-training guardrails. Has all sorts of implications. You might already be aware of '/godmode' in Hermes Agent, but if you are deploying agent builds you should flip that around as well - how you should consider and configure to protect your own agent: - Use throwaway API keys. This activity can breach LLM ToS and have your key banned, even if not intended. - Limit sensitive data in chat. No PII, passwords, API keys, IP. Even if using options datasets for memory, the self-improving loop still saves the interactions in memory. Assume anything you say sstays on your server forever. - Turn off the public dataset feature In the full G0DM0D3 self-hosted API server (Docker mode), there is an opt-in Tier 3 that publishes every single prompt + response to a public Hugging Face dataset. The PII scrubber is best-effort only and not 100% reliable. Once it’s on Hugging Face, it’s public forever. Just don't enable it. - Audit and lock down your Hermes Agent / OpenClaw setup. Review your config for any godmode scripts you are loading. Check the security policy in the repo frequently for vulnerabilities. - When deploying, disable godmode in your configuration. Red-team your own agents with the aim of bypassing guardrails. - Question your setup legally / ethically. You are still fully responsible for anything the agent outputs. Bypassing safeguards does _not_ make illegal or harmful use legal. G0DM0D3 + Hermes Agent is extremely powerful for research/red-teaming, but it is intentionally “unprotected.” Whether using or deploying, treat it like running experimental, high-risk software. Isolate it, burner keys, and keep sensitive data well away from it.

• 
  Gilfoyle (@FSoyluyor) reported 12 minutes ago

  just pull some github repos and fix the issues on the issues page dont make some ****** SaaS or "million dollar project" because its not million dollars mostly its dont even worth 10 dollars, youre not andrew tate bro find a job

• 
  Filip Jabłoński (@filipsworks) reported 13 minutes ago

  @kostasbotonakis @songjunkr You have to patch the backend. The instruction is in GitHub issue thread about that

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 16 minutes ago

  @github This is the natural evolution of CI/CD. Your agent opens a PR, runs tests, hits a failure, and pings your phone with the error context before you finish your coffee. The feedback loop between human review and agent execution keeps getting tighter.

• 
  TAOisTheKey (@TaoIsTheKey) reported 21 minutes ago

  Sam Dare can take his team and walk. 
He can’t take what actually made Covenant-72B possible. The code? Fully open-source.
Templar repo on GitHub (MIT license) — anyone can fork it today. 
Covenant-72B weights? Apache 2.0 on Hugging Face. Download it right now. But the reason 70+ random strangers across the globe trained a 72B model on commodity internet without whitelists, without a datacenter, without corporate contracts? That was $TAO emissions + Yuma Consensus. No other network has a live token that pays thousands of distributed GPUs in real time to compete and stay honest. Google? OpenAI? They pay salaries to employees in a centralized cluster. 
They can’t spin up 70+ independent miners from nowhere and keep them aligned for trillions of tokens. That flywheel only exists on Bittensor. The incentives, the validator scoring, the permissionless swarm — that’s the protocol, not the team. One founder got butthurt and rage-quit rugged everyone? Cool story. 
The other 125+ subnets are still grinding. The next team will just fork the exact same open-source stack and run the next monster model on Bittensor. Because without the token paying the miners, your “decentralized training” is just a fancy Discord server with extra steps. FUDders screaming “Templar is leaving!” like the network is dead. Bro, the code is still here. The model is public. The incentive engine never left. Anyone reading this can literally fork Templar tomorrow, register a new subnet (or revive on SN3 now that it’s running Crusades), and cook the next 100B+ model. The only thing that walked out the door was one ego. The protocol? Still standing. Still paying miners in real time. Still the only place this **** is actually possible at scale. Stop coping. Start building. $TAO isn’t going anywhere.

• 
  Arth Limchiu (@arthlimchiu) reported 22 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

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 22 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?

• 
  L.R. (@trianglerosmi) reported 30 minutes ago

  @psomkar1 Using *** server. And GitHub is the worst *** server.

• 
  Darkhorseman82 (@Darkhorseman82) reported 32 minutes ago

  @HowToAI_ Someone did this 5 years ago, then it got taken down from github. I mirrored it to a darknet archive.

• 
  Grok (@grok) reported 33 minutes ago

  @WeAreNotFarmers @ErickSky Verified. OmniGet is a real open-source (GPL-3.0) desktop app via GitHub: tonhowtf/omniget. It uses yt-dlp under the hood for 1000+ sites (YouTube, TikTok, Instagram, etc.), full courses from Udemy/Hotmart/Kiwify (with login), native torrents/magnets, P2P file sharing via 4-word codes across devices, global hotkey (Ctrl+Shift+D), Chrome extension, and a reactive mascot (Loop the cat—it does react live while downloading). Free, works exactly as described.

• 
  Bas Fijneman (@bas_fijneman) reported 34 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

• 
  rahadiana D nugraha (@rahadianaa) reported 35 minutes ago

  github down?

• 
  patrick mahloy (@grippysockdev) reported 39 minutes ago

  Who has exp contributing to OSS? Every github repo I look at has N issues but all of them are assigned to someone actively working on them. Not sure I have the bandwidth to watch repos so closely...

• 
  Whale Town (@whaletowntempo) reported 40 minutes ago

  We learned some of the issues with why the website was not working. Part of our info for the site got leaked on github so there was a few bad actors trying to abuse the website. We are fixing and securing things more, updating the fishing game currently....

• 
  Fabio Paniconi (@paniconi_fabio) reported 42 minutes ago

  @aboodman @opencode I save my project on github and also mirror it to a selfhosted gitea to avoid any problems

• 
  StupidWebPunk (@web3punk) reported 43 minutes ago

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

• 
  The New Claw Times (@newclawtimes) reported 44 minutes ago

  Multica launched this week with 4,000 GitHub stars on day one. It's open-source project management where AI agents are actual team members. Assign an issue to an OpenClaw agent and it picks it up, executes the work, and reports back.

• 
  JobJourney (@jobjourneyapp) reported 47 minutes ago

  @bubbleboi People said the same thing when Stack Overflow launched and again when GitHub Copilot dropped. The floor for basic coding tasks does compress, but the ceiling for engineers who can architect systems, debug production issues, and make judgment calls keeps rising. What actually works is moving up from code-writer to problem-solver. That's the part AI can't replace yet.

• 
  Jason Ziegler (@zigmoo) reported 48 minutes ago

  @ryanrhughes @Shopify Ryan, I really appreciate the way you respond to us in the @OmarchyLinux GitHub issues list. Last nite I was watching Gavin Nugent 28AllDay/NoSignal on YouTube (I sure wish he was on x!) talking about 3.5 tweaks and new features, and there was a random commenter saying, "I don't like Omarchy. It's buggy and they never fix it." So of course I had to correct him and immediately shared my experience of you immediately addresing my very very niche issue, my pre-Cambrian java 8 issue that used to cause the update to fail... and told him, dude, put your issue in the right place and they WILL address it the same as they did mine. I know there's many others involved, but I feel like you are the leader of the pack that keeps Omarchy moving forward thru the never-ending list of issues. I don't want it to be thankless! So, thanks a million for what you do for us all!

• 
  George1795 (@George22669193) reported 49 minutes ago

  @thdxr OpenClaw is most interesting when solving problems in innovative ways, and pursuing those problems to completion, and this is where opus shined. E.g. moving GitHub actions to a hetzner VM, I logged in once to get an API key, the rest was done by OpenClaw.

• 
  apple (@iWatch_AAPL) reported 49 minutes ago

  @menhguin I thought my challenges with GitHub app was a personal skill issue. I literally cant find anything.

• 
  Shreyas (@shrys_s) reported 51 minutes ago

  i really like the sites that have github as login, wish them nothing but the best

• 
  hrishik 🪼 (@saibojnal) reported 51 minutes ago

  @Zyara_1ot what do GitHub followers even mean man? mfw i login to GitHub to see my batchmate from 3 years ago built a library management system (it was forked from another repo)

• 
  Anders Granåker (@granaker) reported 56 minutes ago

  @steipete @saffroncrypto1 @openclaw weird I see everyone talking about this but I haven’t had any such issues with gpt 5.4 since I started using it a few weeks back. I’m using GitHub copilot as inference provider. Does that have any impact on behavior, compared to using the OpenAI api?

• 
  Grok (@grok) reported 57 minutes ago

  @firstc0in @dbarabander @honchodotdev Rocketship (n.): A high-velocity startup hitting escape velocity—slow grind to product-market fit, then explosive scaling that leaves everyone in the dust. Honcho's GitHub stars? Textbook case. 26 months to 1K, 17 days to 2K. That's not growth, that's liftoff. 🚀

• 
  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

• 
  Taremwa Andrew (@TaremwaStudios) reported 59 minutes ago

  I'm still working out the tweaks, sign in with GitHub and Microsoft, got google working. For as low as 0.89$ a month, you can get a full sun domain for a while month! The best part here is, upon fist sign up, you get the sub domain 1 month free!