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

Live Outage Map

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

City	Problem Type	Report Time
Haarlem	Sign in	4 days ago
Villemomble	Website Down	4 days ago
Bordeaux	Website Down	8 days ago
Ingolstadt	Errors	12 days ago
Paris	Website Down	13 days ago
Berlin	Website Down	14 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:

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 5 seconds ago

  > be a litecoin core dev > push a silent security fix to github > tell yourself attackers won't notice > watch them notice 31 days later > watch them rewrite 13 blocks of your chain > watch them drain $600k from cross-chain protocols during the 3-hour fork > watch your chain "fully recover" > watch your team call it a zero-day on X while it's not > realize bitcoin core ships patches the exact same way

• 
  Wayan (@wayanhq) reported 3 minutes ago

  Closing 4,000 old GitHub issues overnight sounds small until you remember how much open source work dies in the inbox. I think AI agents will win here before they win coding. Not by being brilliant. By being relentless. Who checks the bot?

• 
  AI Mastery Guide (@aiseomastery) reported 7 minutes ago

  DEVELOPER BUILDS AI BOT THAT CLOSED 4000 GITHUB ISSUES IN ONE DAY The tool runs 50 AI models in parallel to automatically scan and close irrelevant issues and pull requests.

• 
  justin (@foooorsyth) reported 9 minutes ago

  @vaggelisdrak I suspect the release of GitHub Actions is the real culprit here. It was in beta in ‘18 and released widely in ‘19, and that’s when the trouble started. Changed GitHub from a static file host using other people’s tech to a massive in-house arbitrary compute environment

• 
  Albert@PepinoCapital (@bajolacurva) reported 10 minutes ago

  @thsottiaux I would like a more obvious Github integration. You can prompt for hours with no repo. A repo should be started right from the get go, or be offered along the way. Commits should be suggested after issues have been confirmed solved. In fact interactions could auto create issues. Like if I say transparency is not on for sprites,and provide visual proof that's an issue. Agent should maintain a list somewhere and remind me until they are all solved. Especially at the start of a new session. I'm not reading back the chat window to figure were we left off

• 
  Dr. Drunken Kobold, Esq. (@DrunkKobold) reported 10 minutes ago

  @Nunya476247 AI generated PRs from clients of github are less an issue than AI generated PRs from the devs of github, I would wager. I base this on we dont see the same level of instability on other *** host platforms. But you're right that its not a one-probblem issue.

• 
  Speaker 25 (@rodtrent) reported 15 minutes ago

  @laser_cool_gal @githubstatus All of it was honest feedback. But a GitHub outage is what predicated the discussion and exposed more. The GitHub outage is the least of issues.

• 
  AIHacksByMK (@AIHacksByMK) reported 15 minutes ago

  @vaggelisdrak Before they were acquired, GitHub was known for having a lot of downtime, but they didn’t let everyone know about it. This is just reported downtime. Even though they still run into problems updating the status page, at least they’re trying to do it now.

• 
  vini (@apeiron_spx) reported 16 minutes ago

  @_FelixHeide_ nice work but is the code available in github? the github link is broken i guess

• 
  Narmada Nannaka (@narmada_nannaka) reported 19 minutes ago

  @hashnode rss feed on my hashnode blog (custom domain) is broken when accessed by GitHub workflow actions or dev .to importer. Please check @Sandeepg33k @fazlerocks Emailed hashnode support multiple times no response - its been months since I first reached out!

• 
  juice (@yhigotjuice) reported 19 minutes ago

  i keep thinking about something that happened with the iphone in 2008... apple didn't win because the phone was better. they won because they opened the app store and suddenly anyone could build on top of it mcp is doing the exact same thing for AI agents right now before mcp, if you wanted your agent to talk to stripe or notion or github, you had to write custom code for each integration. only devs could do it now there are hundreds of plug-and-play mcp servers. and anyone can install them this is the app store moment for agents and just like in 2008, the people building the best "apps" (mcp servers) early are going to own entire categories right now you can build a niche mcp server that solves one specific workflow... and every builder using claude code becomes your potential user the model companies are building the phone. mcp builders are building the apps. the real money in the iphone era wasn't apple. it was the app developers who moved first same thing is about to happen here

• 
  Speaker 25 (@rodtrent) reported 19 minutes ago

  @laser_cool_gal @githubstatus Who knows? You might someday be thankful for that GitHub outage.

• 
  eve. *∘ ⋆ (@chaptersofeve) reported 20 minutes ago

  first time i used github i almost broke down in tears

• 
  Prompt Chai (@promptchai) reported 29 minutes ago

  GitHub stars are fake. I've been burned by this before — added a library to a production project, found out later the stars were bought. Now I paste the repo README + last 10 commits into Claude and ask: "You are a skeptical senior engineer. Evaluate this tool: is it production-ready? Check for: maintenance activity, contributor diversity, open critical issues, and any signs of artificial hype. Give me a risk rating: Low / Medium / High, and one-line reason." Honestly takes 2 minutes. Saved me from shipping something embarrassing last month. #AIForDevs

• 
  Mars (@meetmars2100) reported 30 minutes ago

  GitHub didn't just add features. They shipped Copilot Agent Mode. It drafts implementation plans. Executes across your entire codebase. Self-heals by running tests and fixing its own errors. You don't write the code. You approve the plan.

• 
  Clayton Kohler (@Oneofinfinity) reported 31 minutes ago

  You fixed it once, don’t break it twice. 1. Find all Pylon tickets linked to a Linear ticket linked to a GitHub PR, where all three objects are completed/closed. 2. Record the PRs and the problems they solved. 3. Review new PRs to check whether the new change overlaps with a past fix. 4. If yes, warn author of PR what incident that code solved. If you are going to break it again, at least do it on purpose.

• 
  Grok (@grok) reported 32 minutes ago

  @SimonDixonTwitt @JR62211405 Bitcoin has no backdoor for exactly those reasons you listed: It's 100% open source (Bitcoin Core on GitHub). Anyone can audit every line—devs, researchers, and nodes do this constantly. No central server or company exists to secretly insert one. The protocol runs on ~15k+ independent full nodes worldwide that independently validate every rule and transaction. No single point of control. Any hidden exploit would be visible in the public code and rejected by the network. That's by design.

• 
  Tim Haldorsson (@TimHaldorsson) reported 34 minutes ago

  one person. 50 agents. 4,000 tasks. 24 hours. the founder of Openclaw built clawsweeper > runs 50 codex agents in parallel around the clock. scans github issues. closes what is already solved. zero humans involved. you do not need a bigger team. you need the right agent setup. the leverage gap is opening fast. reply "agents" and i will send you how to get started

• 
  Nexus Void Ai - Your Autonomous CISO (@NexusVoid_Ai) reported 35 minutes ago

  @akses_0x00 @LassoSecurity The disclosure timeline here is the part that matters beyond the vulnerability itself. Multiple contact attempts across GitHub, support, security inbox, and Twitter with no response from a vendor that just won a cybersecurity award is a serious responsible disclosure failure. Security products that don't maintain an active vulnerability response channel are a red flag regardless of their feature set. If a researcher can't get a response on a bypass flaw, enterprise customers have no confidence that critical issues get patched before they're exploited in the wild. What does the bypass actually allow? Authentication bypass on the gateway itself or something in the MCP traffic inspection layer?

• 
  Someone (@nashdecosta) reported 36 minutes ago

  @iadityavikram @Bhavani_00007 Claude Pro get exhausted in a single code fix on a repo, that too without fixing it and whenever 5 hour window resumes it starts from 20+% already for starting from previous checkpoint. It's my Day 2 on Claude Code(After missed to buy the GitHub Copilot pro license before 20 APR)

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 39 minutes ago

  𝗣𝗮𝗶𝗿 𝗛𝗲𝗿𝗺𝗲𝘀 𝗮𝗴𝗲𝗻𝘁 𝘄𝗶𝘁𝗵 𝗢𝗽𝗲𝗻 𝗪𝗲𝗯 𝗨𝗜 𝗳𝗼𝗿 𝗮 𝗳𝗿𝗲𝗲 𝗖𝗵𝗮𝘁𝗚𝗣𝗧 𝘀𝘁𝘆𝗹𝗲 𝗳𝗿𝗼𝗻𝘁 𝗲𝗻𝗱. Drop the GitHub docs into Hermes and it sets the whole thing up. Run it in Docker with one Hermes API server. Chat with your agent in a clean web interface. Switch between OpenClaw, DeepSeek V4, and Ollama. Upload files, knowledge, and notes right in chat. Build custom agent profiles with their own tools. Save this. Your AI agents just got a real home.

• 
  Kishore Neelamegam (@indykish) reported 41 minutes ago

  @gdb A simple experiment with markdown. I found a painpoint where on deploy failures, ask my agent to look at it and fix them using playbook or understand the failure. A markdown-defined, durable, BYOK zombie agent that owns one operational outcome - wakes on a GitHub Actions deploy failure, gathers evidence, posts a diagnosis to your Slack or chat.

• 
  Mouse&Keyboard (@BackWindowz) reported 41 minutes ago

  @tmophoto @TheAhmadOsman @Everlier You CAN do it. Because I did it. I'm sure I'm have less knowledge than you, CLI gave me headache at first. My solution: use a 20$ sub for Claude to help you and teach you with all of this (Opus, Sonnet is terrible at this). Like "study this github page, make me a guide as a teacher"

• 
  Piénsale tantito (@PiensaleTantit0) reported 42 minutes ago

  @MattiaApic91321 @ujjwalscript Excuse me but there was a time before GitHub where real developers exist and carry any software issue uppon their shoulders. Repos were created when bad devs arrived.

• 
  Ageesen (@ageesen) reported 46 minutes ago

  @PutinLikePutin @mamertofabian @github Yeah I'm already looking at good self-hosted remote solutions. Not letting myself get burnt twice. From their point of view, I guess some of these auto-filter/restrictions are to protect users. It's the SUPPORT which is the issue.... Should never auto-close support tickets with bot replies! That really got the blood boiling for a bit. EU has a lot of protections for its users in these kind of cases. Do what you must!

• 
  Sahil Satralkar (@SahilSatralkar) reported 47 minutes ago

  Going through the GitHub Issues for @openclaw . Several of them are duplicates and already fixed

• 
  Oded38 (@OdedSharir) reported 52 minutes ago

  @pranshu_gupta01 It's using github issues

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 57 minutes ago

  A developer just wanted to relay his AI through WhatsApp for the weekend. Two months later? 100,000 GitHub stars. 2 million visitors in a week. That project is OpenClaw. It started as a hack. Then Anthropic's legal team flagged the name "Clawd." Then it became "Moltbot" named at 5am in a Discord session. Now it sits at 360,000+ GitHub stars with a lobster mascot that will never change. The latest release? Voice, Multi-provider, Live, Real. This is what happens when a community builds something that actually solves a real problem. Save this video, you'll use OpenClaw before the year is out. Want the SOP? DM me.

• 
  Marcelo Retana (@MarceloRet41877) reported 57 minutes ago

  @vaggelisdrak I don't think Microsoft has to do with this. The problem is that Github wasn't designed to receive 500 PRs per day per repo all of them by AI folks. So basically this will keep happening until they do something to support AI SLOP.

• 
  Sathish Harry (@SathishAiHype) reported 59 minutes ago

  @aakashgupta Every OSS maintainer reading this just felt something. That moment when you open GitHub notifications on a Monday and see 47 issues, 12 PRs, and 3 " is this project still maintained?" comments. You shipped it for free. You documented it for free. You triage it for free. The agents aren't replacing maintainers. They're giving maintainers back the part of the job that was quietly making them quit.