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	12 days ago
Berlin	Website Down	13 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:

• 
  Wayan (@wayanhq) reported 57 seconds ago

  OpenClaw says an AI bot used 50 Codex instances in parallel to close roughly 4,000 stale or already-solved GitHub issues. That is not replacing maintainers. It is removing the layer of dust that stops maintainers from seeing the real fire.

• 
  DJ Goosen (@dj_goosen) reported 2 minutes ago

  Gave my agent a fairly tricky user workflow because of the API's and state sync involved: "Draft an Ansible playbook > save draft > modify > GitHub > AAP (no Jira transition) > modify > GH > AAP workflow (with transition)" Not the kind of flow a human would get tripped up on if you told them. But exactly the kind of flow agents were still cratering on six months ago. My agent one-shotted this fix with zero regressions. Another example of where Pinion is creating these really stable surfaces for any fast ad-hoc fixes we may need between sprints 🤖

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

  first time i used github i almost broke down in tears

• 
  Matt Pocock (@mattpocockuk) reported 5 minutes ago

  Tons of folks are piling in here saying that AFK agents are a myth. I have been using them to ship these GitHub repos: mattpocock/evalite mattpocock/sandcastle mattpocock/software-factory (might be public by the time you see this) Here are a few steps to making this work, and some reality checks. Definitions Let's split this into the day shift and the night shift. Day shift is planning/review/QA, night shift is AFK implementation. Day Shift (part 1) 1. Use /grill-me to align with the AI 2. Use /to-prd and /to-issues to create a PRD (the destination) and implementation steps as separate tickets, which can be grabbed in parallel (the journey) 3. The PRD is a ticket, but it's not an actionable step. You just put the user stories there This is pure requirements gathering ****, same as it ever was. Night Shift 1. I run a planner agent which looks at all the tickets and sees what can be worked on now, and what's blocked 2. The planner agent then kicks off multiple agents (sandboxed using Sandcastle, my OSS tool) to implement the code 3. I then have an automated reviewer agent look at the commits produced - one agent per implementation. This checks alignment to the original PRD, as well as code quality 4. These commits end up on branches that get PR'd to main 5. The planner agent runs again until all work has been completed The review is a crucial step - it's saved me MANY times. I am planning to massively increase the amount of review I do, hopefully with multiple agents. But guess what - AFK agents sometimes produce bad code. This can happen because of: a. The original plan was bad because the best solution was something different b. The original plan was bad because it didn't take into account all the unknown unknowns, and the AI had to make some decisions during the coding session which were bad c. The plan was good, but the AI just shat the bed (twice, once in the review stage, once during implementation) d. Your codebase is bad and the feedback loops don't tell the agent if it did a good job or not So... QA: Day Shift (part 2) 1. QA all of the branches created 2. Create follow-up issues, potentially editing the original PRD to adjust the destination This will usually take a long time, often as long as planning. But then you kick off the night shift again. Once QA is all done, you review the important bits of code manually, usually in PR's. There isn't anything better than the PR UI right now, so that's what we're stuck with. Wake-up Calls 1. If you let the AI run all night unbounded by planning, it's going to produce **** code 2. Mostly, my loops finish before I go to bed, it's just the night shift catching up to the day shift 3. The only reason I do AFK at all is because it allows me to automate review and totally not give a **** about latency 4. I always run night and day shift in parallel. I can't plan that far ahead (skill issue, probably). I need working code to base my plans from, so I'm aggressively QA-ing stuff that lands

• 
  Mr. K (@Mr_K_here) reported 10 minutes ago

  Idk it seems like Microsoft wants GitHub to be dead! Just check the outage history since Microsoft integrated GitHub as part of their org !

• 
  Hey Joe, Where You Goin’ With That UFO? (@unadvantaged) reported 15 minutes ago

  @xtremesecurity @UnslothAI Requirements for the bug: - It must come from a public GitHub repository. - The issue/bug report/discussion must be public and updated within the last 12 months. - The project must be actively maintained.

• 
  Josh Long (@starbuxman) reported 17 minutes ago

  ouch 🤕 big L for @github I know good people there and they’ve been I think unfairly lampooned this year for outage after outage which I think would be better laid at the feet of AI agents deluging the platform so this sort of actual problem comes at a really bad time

• 
  ÆON FORGE ✨ (@SpaceTimeViking) reported 18 minutes ago

  @ToNYD2WiLD @aijoey I had some gaps in my documentation (updating now) and the other is a full day of build time for the container will update when v2.2 it published of the container. there is a prefill cache flag I forgot to include in the readme I updated an Agents.md file on the GitHub you can point your agent to, to apply the fix.

• 
  Petros Gauchodeliakis (@gauchodelia) reported 19 minutes ago

  my workflow with ai... antigravity as a ide, just to dont cursor due to the stupid plans and limits , i found it horrible. a bash file to commit and push to github and via ftp to the server. because is for wordpress sites, the flow is jus simple like that.

• 
  Abd_Mueez🎨 (@Abd_Mueez01) reported 20 minutes ago

  @Traderibo123 @github did someone else tried to login ?

• 
  Marlow (@marlowxbt) reported 21 minutes ago

  A 13 year old in China sold his first Python script for $40 on GitHub. The buyer was his own CS teacher. He didn't find out until the first day of school when the teacher showed it on the projector as an example of professional AI development. The kid was sitting in the third row. He spent his entire winter break building it instead of playing with his friends. Two weeks of asking Claude questions every night after his parents went to sleep. When the $40 came in he spent it all on V Bucks the same day. Didn't even think about it. Just bought a Fortnite skin and went back to coding. Pushed it to GitHub with a README in broken English that said: ai agent that does homework and finds answers from any website. Watched it sit at zero stars, closed his laptop and went to dinner. GitHub Sponsors doesn't show the buyer's real name. Just a username he'd never seen before. He didn't care. The $40 was already gone on a virtual outfit for a character he plays 2 hours a day. Then February came. First class back. The CS teacher opened with a presentation about AI agents, showed a demo on the projector. A Python script that scans websites, pulls data, summarizes it with Claude and sends structured reports automatically. The kid recognized everything. The variable names, the file structure, the comments he left in Chinese because he was too lazy to translate them. His teacher was presenting his code to 40 students as an example of what a professional developer can build. The teacher said: I found this tool online and it changed how I prepare my lessons. It pulls information from 30 sources in 3 seconds. Used to take me two hours every evening. The kid didn't say anything. Went home and checked the fork count. 847. Someone at a university in Beijing had forked it and was using it to grade 200 student papers overnight. A tutor in Shanghai forked it and built a homework checking service charging parents $15 per month. A small company in Hangzhou forked it and turned it into a customer support bot for an online store. All from a script a 13 year old built over winter break because he was bored and Claude helped him write the code. The $40 he earned from it is now a Fortnite skin. The code he wrote for it is now running in three countries. His teacher still uses it every day and still doesn't know who wrote it. The kid never told him. He said it would be weird to tell your teacher that the tool he shows off to every class was written by someone who sits in his class and still gets B minus on the coding assignments. He gets B minus because he writes his own code in class. The A plus code he writes at home with Claude, that's the code his teacher bought for $40 and presents as professional work. 847 forks. One $40 sale spent on V Bucks. One teacher who bought his own student's script without knowing it. One kid who can't tell anyone because it would be the most awkward parent-teacher meeting in history. He's 13. The teacher gives him a B minus. The script gets an A plus from everyone who uses it. Same kid, same code, different grades depending on who's looking.

• 
  Antifederalist Caesar (@hyperliberalism) reported 26 minutes ago

  This is doubly funny for me because I've spent the last week addressing in my own production database the only reason GitHub ever went down for an extended period of time (split-brained multi-master). It's not easy to get that **** right (they didn't), but Microsoft is just bad.

• 
  Mauricio Rubio 🎧 (@_mauriciorubio) reported 29 minutes ago

  @coreyhainesco Cool Corey, but why the hell are you using the GitHub favicon on your marketing skills website? It is the second time I see a Founder plagiarising branding from another company this week. First I saw a guy using Vercel’s favicon, brought it to his attention said he would fix it, never did. Now this.

• 
  Ryan Prasad (@ryanprasad_ai) reported 29 minutes ago

  It's very safe. Its a read-only MCP server. Could have this spun up in a few hours. But its not ambitious. Or bold, like the podcast was. That was a cool project. It even got a star on GitHub! We can do better... but how?

• 
  spectracide: the root killer (@RRSkunkWorks) reported 30 minutes ago

  Mine are usually dev servers (and currently), I got them with projects locally before pushing to github or production. I handle DNS and malicious URL/file blocking differently but I have run all of these before when I first started pi'ing around! One of my 0w's just died but it was acting as an RSSI node for one of my CSI/RSSI project. Then of course I have the old media server. It plays all the movies and shows that I legally own and definitely did not pirate. Argh

• 
  Bruno Skvorc (@swader) reported 31 minutes ago

  @thsottiaux 1. Inability to submit feedback in a way team will see it (github issues aint it and the only way seem to be a popular tweet rn) 2. I would like a mode “reorder projects by last active” 3. Computer use plugin unavailable on newest version and unsure why 4. No /compact 5. Comprehensive app hooks would be nice 6. Filepath tooltip on hover would be nice

• 
  Paweł Huryn (@PawelHuryn) reported 32 minutes ago

  6 free GitHub repos for Claude Code Can save you $100/mo. vercel-labs/agent-browser Replaces Claude in Chrome for web scraping. Accessibility tree instead of screenshots. No HTML mess. rtk-ai/rtk Their claim: 60-90% on common dev commands. 20-30% in my workflow. juliusbrussee/caveman Terse-output skill. Drops conversational filler from responses. tirth8205/code-review-graph Claimed up to 49× fewer tokens on daily coding. AST map. Gronsten/claude-usage-monitor Real-time 5-hour window + active session tokens. Know your cap inline. phuryn/claude-usage Historical breakdown by session, day, week. Where the spend went & what to fix.

• 
  Electrum (@ElectrumWallet) reported 35 minutes ago

  @WhalesSecret Well, twitter isn't the right place to host this kind of discussion; you should open an issue on github. Note: If the server uses our protocol (not Boltz), then a reverse swap failing will not result in the user losing fees, because the invoices are bundled.

• 
  juice (@yhigotjuice) reported 36 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

• 
  L.vue (@eLkay0027) reported 37 minutes ago

  @github @acolombiadev copilot sdk now available for react native apps? honestly not sure what problem this solves that the chat interface doesn't already cover

• 
  Prompt Chai (@promptchai) reported 42 minutes ago

  GitHub stars are basically Zomato ratings at this point. Paid networks inflating numbers. Fake accounts starring repos in bulk. The whole ecosystem is quietly gamed. Honestly? I stopped using star count to evaluate a library 6 months ago. What I actually check now: - Last commit date - Issue response time from maintainers - Whether real companies mention it in their stack - The contributor graph (sudden spikes = red flag) Before adding any new tool to your project, paste this into ChatGPT or Claude: "Evaluate [tool name] for production use. Check: maintainer activity patterns, known issues in the last 6 months, companies publicly using it, and any signs of artificial popularity inflation. Be honest if the evidence is thin." We already covered evaluating tools before adding them to your stack — but fake stars change the trust baseline entirely. Don't let a number on a repo page get your code into a bad dependency situation before appraisal season. #OpenSource

• 
  Beau Johnson (@BeauJohnson89) reported 43 minutes ago

  matt pocock just open sourced his personal claude code skills folder mattpocock/skills > 19,380 stars in 2.5 months > 22 skills, mit license > install any one: npx skills@latest add mattpocock/skills/<name> the standouts: > to-prd turns your current chat into a github issue prd > grill-me interrogates your design until every branch is resolved > design-an-interface spawns parallel sub-agents pitching different apis > tdd runs the red-green-refactor loop one slice at a time > triage-issue hunts the root cause and files a fix plan > setup-pre-commit wires husky, lint-staged, prettier, types, tests > ***-guardrails-claude-code blocks dangerous *** commands before they run matt runs the biggest typescript channel on the internet and this is what he keeps in his .claude folder if youre on claude code daily this is a free upgrade

• 
  tokenbender (@tokenbender) reported 46 minutes ago

  "github issues" is the only handoff/knowledge base system i ever needed. rest i would leave to the creative ones' imagination.

• 
  Rodney Miller (@RAMiller37) reported 50 minutes ago

  @thsottiaux Why do I keep having to disable the damn github mcp tools, those shouldnt even be on by default. Also pushes out tools from the MCP server I am trying to use.

• 
  AI Mastery Guide (@aiseomastery) reported 51 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.

• 
  Nemanja (@Nemanjadotcom) reported 53 minutes ago

  I have just tried Ralph loop with Claude and I’m a changed man. Never going back. It banged out a feature (on sonnet) in 9 GitHub “issues” without any issues (pun intended)

• 
  Wayan (@wayanhq) reported 54 minutes ago

  OpenClaw’s loudest feature is voice, but the useful bit is boring: 50 Codex instances closing about 4,000 stale GitHub issues. That is what AI coding may look like first. Not magic apps. Which maintainer still wants to click through that by hand?

• 
  Deepak Shettigar (@deepakshettigar) reported 56 minutes ago

  2/ Think of MCP like loading all your dependencies upfront in compiled languages. Perplexity ran the math: MCP consumes 72% of your context window BEFORE your agent does anything. A single GitHub MCP server = 40K+ tokens of tool schemas sitting there unused. That's expensive.

• 
  Gary Zhang (@GaryZhangVizard) reported 58 minutes ago

  Drowning in AI code? @steipete built ClawSweeper to autoclose 4k+ GitHub issues. AI managing AI! API limits are the new bottleneck, not models. Bot orchestration is the real product future. 🤖

• 
  OneManSaas (@OneManSaas) reported 59 minutes ago

  @mark_k @xai For anyone preparing: the Claude Code integration docs are solid but their error handling examples are incomplete. Spent 3 hours debugging async timeouts that weren't covered. Worth reviewing their GitHub issues before diving in.