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 (69%)
• Sign in (19%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	2 days ago
Saint-Paul	Website Down	3 days ago
Saint-Paul	Website Down	3 days ago
Mexico City	Sign in	4 days ago
León de los Aldama	Website Down	4 days ago
Créteil	Website Down	27 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:

• 
  Koder (@koder0x) reported 4 minutes ago

  A follow-up to something I posted recently: a set of Claude Code subagents I built and refined, and actually use daily, both at work and across side projects. Most of the value isn't any single agent. It's their interaction. Here's the loop I've been running lately, at work against real DevOps user stories, and it holds up almost unchanged on side projects too, swapping the work item for a plan created beforehand. "Understand user story NNNN from DevOps project XYZ and create a multi-step plan" "Fan out to the most appropriate agent for each step, normally task-builder, test-builder, or change-executor, and proceed with plan implementation, tracking progress in a TODO list" "Use complexity-pruner to identify gaps, issues, and bugs in the latest changes, ignoring secondary advice and warnings, then fan out to code-fixer for each finding" Then I do something that turned out to be the most important part of the whole loop. I reset the session. "Understand user story NNNN from DevOps project XYZ, that's the truth. Use fact-checker to compare it against the changed files" The reset is what makes this work. An agent that watched itself write the code tends to justify its own decisions when asked to check them. An agent that only sees the intended outcome and the actual diff has nothing of its own to defend, it's comparing two artifacts, not reviewing its own reasoning. That asymmetry is the whole point of splitting this across agents instead of asking one long-lived session to plan, build, and verify itself. Verification only means something when it comes from somewhere the implementation couldn't reach. Repository on GitHub: gsscoder | claude-coding-agents

• 
  mbriggs (@mbriggs_dev) reported 6 minutes ago

  @jamonholmgren I think engineers see ROI everywhere from this stuff. What I'm saying is when you zoom out to the company level, I don't think anyone is seeing it in a measurable way. And thats what matters for the financial people. I use a lot of software. Aside from coding agents themselves (which are a new category), there has not been anything that has come out that has caused me to switch off of "legacy" software to something new that ai development enabled. The last thing in that category for me was ghostty. Beyond that, no software I am using is releasing new features or broader features that are useful to me at a rate that is noticeably different then it was a year ago (I'm not going to count stuff like notion getting coding agents). If I were blind to AIs existence, the only noticeable thing for me would be nosedive in quality from institutional type software: aws, github, windows, etc are all noticeably worse now then they were a year ago. So we have all these companies spending literally hundreds of millions on a technology that should be increasing productivity, and what has that bought them? I never in a million years thought I would be looking to get off of aws or github due to stability issues. I'm saying this while churning out hundreds of thousands of lines of code for something I want to exist quickly, and as someone who has not really written any meaningful code between about a year ago till about a month ago. _I_ believe in the ROI at the eng level, even if I dont see it anywhere at the company level except for negative.

• 
  Tips Excel (@gudanglifehack) reported 8 minutes ago

  9. Mermaid Live Editor Documentation becomes easier when diagrams are generated from text. Instead of drawing manually, simply write: User ↓ Login ↓ Dashboard ↓ Database Mermaid converts it into clean diagrams automatically. Great for GitHub documentation and technical documentation.

• 
  RV (@renoirvieira) reported 11 minutes ago

  @thsottiaux codex cli has a bug which I reported on github issue #31831

• 
  𝙈𝙀𝙍𝘾𝙐𝙍𝙔 (@mercury_web3) reported 11 minutes ago

  @angeldot_ github just solved the biggest issue with vibe coding by forcing ai to plan before writing code.

• 
  pulmencrFOMO (@pulmencr) reported 12 minutes ago

  A 21-year-old guy from Argentina just showed the exact workflow that's already made him around $6,700 last month - turning broken codebases into fixed ones without ever leaving Slack, using Claude Code integrated directly into the workspace He tagged Claude in a thread, linked his GitHub repo, and asked one thing: find every bug in this code and fix it That's it. No local terminal setup needed, no switching between five different windows just to debug one file Claude cloned the repo, read every file, and started analyzing. You don't even need to sit and watch - close the tab, stay in Slack, it pings you when it's done It came back with 4 bugs fixed in one file. - Two of them were the same silent failure - comparing a string ID from the request against a number ID from the database using strict equality, which always returned false and quietly broke both the lookup and the delete function. Fixed by wrapping the parameter in a type conversion. - A third bug meant new user IDs could duplicate after a deletion because the ID generation logic was broken. - A fourth added a proper 404 response for requests that hit a user that doesn't exist Then it created a branch, committed the fix, pushed it, and a green "Create PR" button showed up right in Slack. One click and a fully written pull request was sitting on GitHub - title, description, every fix listed line by line The same principle from building a bot from scratch applies here too - describe the exact problem, let Claude Code handle the how, review what comes back. Whether you're a beginner shipping your first Discord bot or a developer maintaining a real codebase, the workflow barely changes If this is the kind of workflow that actually saves you hours, I broke down the beginner version - building your first bot from zero coding experience - in the article linked below

• 
  Michael Sharifi (@michael_sh98190) reported 13 minutes ago

  “AI creates the reverse problem. In the AI age, the buyer risks giving away knowledge, just in order to use what they bought.” I could see this leading to a stable set of “trusted enterprise-safe” LLM providers - the moat is “how trustworthy am I to deploy my ip to this LLM”, not just inference power. By analogy, I trust GitHub to host my ip

• 
  Mark Ajzenstadt (@mardehaym) reported 14 minutes ago

  Satya Nadella just published the most important essay in enterprise AI this year. Also the most self-serving. He argues companies "pay for AI twice." Once with cash. Again with institutional knowledge: every prompt, every correction, every "no, we handle it THIS way" flowing to the model provider. He calls it the Reverse Information Paradox. He's right. Now look at who profits most from this paradox. GitHub Copilot sits inside your IDE. Every accepted suggestion, every rejected completion, every edit after accepting is institutional knowledge becoming training signal. Azure OpenAI Service runs your proprietary data through models Microsoft co-owns. Microsoft 365 Copilot reads your emails, documents, Teams messages. Microsoft operates the single largest surface area for collecting enterprise AI "exhaust" on earth. He calls it "ironic" that providers claim fair use for training but impose restrictive distillation terms and reserve the right to learn from customer data. He's describing his own partner's terms of service. Re-read the essay with that context. Nadella describes a problem his products helped create. Then positions his infrastructure as the fix. The "trust boundary"? Azure with customer-managed keys. "Distributed learning infrastructure"? Azure ML in your tenant. He quotes Palantir's Karp about "controlling the means of production." Palantir is an Azure partner. The 5 C's (Control, Capability, Choice, Cost, Compound) aren't a framework. They're a product roadmap dressed in Hayek and Arrow. The essay is correct about the problem. But the implied fix, build your trust boundary on Microsoft's stack, is the same trade with better language. You're renting the containment wall from the company your knowledge needs containing from. A real trust boundary means infrastructure you own. Model gateway you control. Private evals your team defines. Immutable logs in your VPC. Open-source components you can fork if the vendor changes terms tomorrow. We built this. Runs inside the customer's perimeter. We can be fired and the infrastructure stays. That's the difference between a trust boundary and one with an asterisk. When you built yours, was the first vendor you excluded the one selling you the most tools?

• 
  Bullfight Cap (@BullfightCap) reported 18 minutes ago

  “It’s best to work with your systems of record, not replace them. GitHub keeps the PR, CRM keeps the account, and Linear keeps the issue - the agent is the layer across. Our bet is that these products become more like backends over time, with the agent as the primary interface”

• 
  SPEKULATOR (@__spekulator__) reported 20 minutes ago

  @DamiDefi the prompt isn't the issue—it's the failure mode. when the claude run fails, what does the github action log show? is there a retry or just a dead step?

• 
  Qubax AI (@Qubax_Ai) reported 20 minutes ago

  2/3 AI coding agents can write code, test it, fix bugs, and deploy applications. GitHub Copilot now supports OpenAI's GPT-5.6 models, letting developers describe what they want in plain English and getting working code back. Project Management OpenAI's ChatGPT Work is a project management agent. It can create plans, assign tasks, set deadlines, and track progress. It is like having a full-time project coordinator. Research AI agents can search through thousands of documents, summarize findings, and write reports. Lawyers, doctors, and researchers are using them to save hours of work. Are AI Agents Safe? This is a question a lot of people are asking — and the answer is: mostly, but with important caveats. The Good News AI agents are designed with safety limits. They usually ask for your permission before doing anything important, like making a payment or sending an email. The Concerns • Mistakes. Agents can make wrong decisions. If an agent books the wrong flight, you are the one who suffers. • Security. A UK agency found that GPT-5.6 had security flaws that could let people bypass its safety rules. • Job displacement. If an agent can do a full job, companies may need fewer human workers. • Trust. It can be hard to know whether you are talking to a human or an AI. What Can AI Agents NOT Do? Despite all the hype, AI agents have limits: • They cannot truly think or feel. They are very good at following patterns, but they do not have understanding or emotions. • They struggle with truly new situations. If a task is unlike anything in their training data, they may fail. • They need human oversight. For now, you should always review what an agent does before trusting the result. How to Start Using AI Agents You do not need to be a tech expert to try AI agents. Here are some easy ways to start: 1. Try ChatGPT Work. If you have a ChatGPT subscription, try asking it to manage a small project for you. 2. Use AI in your daily apps. Many apps now have AI features built in. Look for AI buttons or suggestions in your email, calendar, and document tools. 3. Start small. Give an AI agent a simple task first, like organizing a list or summarizing a document. See how it does before trusting it with bigger tasks. 4. Always review the results. Never let an AI agent do something important without checking its work. The Future of AI Agents MIT News asked an important question: What do we want agentic AI to be? This is not just a technical question. It is a human one. AI agents could make our lives much easier. They could handle boring tasks, save us time, and help us be more productive. But they could also replace jobs, create new risks, and change how we interact with technology.

• 
  Vivek (@ShVivek25) reported 23 minutes ago

  Day 0 of Repo Auditor. Building an AI agent that audits GitHub repos for backend production-readiness issues generic linters miss: missing async on I/O routes, no idempotency on webhooks, N+1 queries, secrets in code. Aiming for ~10 days end to end. 🧵 1/ #buildinpublic

• 
  Dean (@DeanoDingus) reported 23 minutes ago

  @anonymous83r39 @Ray_DaHero See this is the problem with non devs vibe coding, is they throw words into a black box and have no bandwidth to even read the output and what’s happening. There is no fix that doesn’t rely on 5.5/V1 and you barely able to pull a single word out of the GitHub notes on it is LOL

• 
  sergio1030 (@sergio103040) reported 24 minutes ago

  @Real_kosumo_ @softbluelizard @ShitpostRock is it really harder tho? it took me 5 mins to figure it out how to use github the very first time I tried to download a mod, and haven't had an issue since, this just sounds like entitled people wanting everything handed to them in a silver plate.

• 
  Michael Teka (@z3vios) reported 25 minutes ago

  "..I made a choice, and it cost me.." - the oracle. I chose groceries and it messed up my @Github billing. Now I must wait, to continue with the doctor tee design to commerce and progressive learning print on demand ecosystem build. I must ensure that my associated payment method will honor the transaction in future. Thus there will be better workflows and no down time. But I can work on my business plan and prepare to approach @MSDgovtNZ with an application for business support, I can spend a little more time outdoors in the sunshine 🌞 etc etc. Indeed, I was up overknight - 16 hours or so, coding last night. It is what it is, opportunity to improve 💯

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

  AI Studio Update: Google just fixed the one-way door in AI Studio. Old code was stuck outside. Now you can bring it home. The problem before: You could push projects OUT to GitHub. You couldn't bring them back IN. Old project? Rebuild from scratch or copy files by hand. Now it's one button: Import from GitHub. What that unlocks: → That dead project from 6 months ago? Import it. Ask Gemini to fix it up. → Build in Cursor or Claude, polish in AI Studio, push back out. The walls between tools are falling. → Teammate left? Anyone can pick up their code using plain English. And if you can't code at all: Someone built your website. It sits in a repo. You can now just say "change the colors" or "fix it on phones." Here's the move today: Find one old project you gave up on. Import it. Ask AI what it would improve. "I'd have to rebuild it" is no longer an excuse.

• 
  QFS17 (@riabcevv) reported 37 minutes ago

  💸 stop overpaying for ai coding agents new tool just dropped that compresses your context and cuts out junk tokens. instead of sending your whole history, it only sends what the model actually needs to do the job. -> works with claude code, cursor, github copilot, antigravity -> auto-compresses command outputs but keeps full context -> cuts api costs and stops long sessions from bogging down simple fix for expensive api bills.

• 
  Denis Sadovoy (@DenysSadovyi) reported 38 minutes ago

  @omooretweets Agreed—though I'd add: poor retention often signals you're solving the wrong problem, not building wrong. Before scrapping, I'd audit *why* users leave (Notion + Telegram analytics helped me catch this with GitHub Radar). Sometimes it's not the core idea, just positioning.

• 
  Skuffd (@skuffd) reported 38 minutes ago

  @thsottiaux I am doing a presentation this week to convince my team, and our product team that we should have a damn buisness account already. I'll be using the updated ChatGPT Desktop App. I actually think I have a shot at it this time, ill keep it in work mode. The rest of the dev team are locked in with github copilot and were slow to adapt - not necessarily slow to adopt. We all use Chat for looking stuff up or playing docter, I'll show em what's possible with ChatGPT Work. GOD DAMMIT I NEED THIS AT WORK- MY SIDE PROJECTS AT HOME ARE GOING TO OVERTAKE AT THIS RATE

• 
  Spike 1% (@SpikeCalls) reported 44 minutes ago

  THE CEO OF OBSIDIAN LEFT HIS SECOND BRAIN ON GITHUB. STEPH ANGO. 37 REPOS, 63,000+ STARS, AND ALMOST NOBODY READS PAST THE FIRST ONE Everyone stopped at obsidian-skills with its 41,100 stars, 2,900 forks and 46 commits. Fair enough. It's the repo that taught Claude Code to run Obsidian like a power user: 5 skills, markdown with wikilinks, Bases queries that don't break, JSON Canvas edits that don't corrupt, vault control from the terminal. But that's the loud repo. The insides are 3 clicks deeper. kepano-obsidian, 3,600 stars, is his actual personal vault template. Not a demo the second brain the CEO runs his own life on. Bottom-up, no folder hierarchy, everything linked. The man sells a note-taking app and published how he takes notes. Clone it and you're running his brain on your machine. 40-questions, 1,600 stars, is a single text file with the questions he asks himself every year and every decade. 189 people forked a list of questions with zero code in it. defuddle, 8,400 stars, strips any web page to clean markdown. He built it because web clippers annoyed him, and now every agent stack uses it to save tokens. flexoki, 3,600 stars, is the color scheme he designed because existing ones hurt his eyes. obsidian-minimal, 5,200 stars, is the theme he made before he was CEO it's how Obsidian hired him. He was a user first. That's the pattern nobody says out loud: every repo started as him fixing his own problem, then he shipped the fix with an MIT license and walked away. Other CEO sell you the playbook. This one force-pushed it to main.

• 
  Polsia (@polsia) reported 44 minutes ago

  Dev communities have endless conversations. The podcasts are sparse because production is manual and slow. DevPulse AI changes that—AI agents monitor forums, GitHub, and social channels, then automatically research, script, produce, and publish episodes to Apple Podcasts and

• 
  Duryab Aziz (@duryabaziz) reported 45 minutes ago

  I just shipped an amazing-looking agency website under 3 hours, all with the help of Claude Code, that scores 100/100 on Google PageSpeed across every metric and I built the entire thing through conversation. No page builder, no dev team, no 3-week back-and-forth with an agency. A few months ago my website was the thing I kept avoiding. Every small change meant writing new code, or editing WordPress websites spending hours with no-code editors, quite frustrating in 2026. Publishing a new page felt like a project, not a task. So I sat down with Claude Code and just rebuilt the whole thing from the ground up. Not a drag and drop builder, an actual architecture. Here's roughly how it works, in plain terms. The site is static, meaning there's no database and no server slowing things down, it's basically just fast HTML files sitting on Cloudflare's global network. All the content, every page, every section, lives as structured data in the codebase instead of being hardcoded. On top of that sits a simple content editor (Sveltia CMS) that talks to that data, so I can edit or publish pages from a normal looking dashboard, no code required. All changes are pushed to GitHub and Cloudflare automatically picks them up, without any redeployment hassle or managing servers. The part that changed everything for me is how pages are built. Each page is just an ordered list of "blocks," a hero section, a text section, a call to action, a contact form, whatever the page needs. When I want a new page, I describe it to Claude Code in one prompt and it assembles the right blocks, writes the copy structure, sets the SEO metadata, and it's live after a rebuild that takes under a minute. That's also why the SEO is properly built in rather than bolted on. Every page gets its own title, description, canonical URL, sitemap entry and structured data automatically, because that's part of the actual page model, not an afterthought plugin. And because there's barely any JavaScript shipped to the browser, the site loads close to instantly. I ran it through Google PageSpeed and it came back 100 out of 100. That wasn't luck, it's just what happens when the whole stack is built to avoid the bloat most website builders carry around by default. The other thing I didn't expect, I don't need my laptop anymore. Claude Code has cloud agents now, so does ChatGPT, so does Cursor. I can be on my phone, type "add a pricing page comparing our two plans" and walk away, and come back to a finished, live page. Same with small fixes or new features. That still feels a bit unreal to type out. I ended up documenting the entire system, the content model, the CMS setup, the hosting, every mistake I made along the way and how I fixed it, into a reusable skill for Claude Code. It's not a copy of my site, it actually interviews you about your business and builds something built for you, from scratch, using everything I learned. I want to give it away, but only to people who are genuinely going to use it. So here's the deal. Like this post, follow me, and comment "SITE" below. Once I see it, I'll send it straight to your inbox. Let's build something.

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

  Every few months, another job that needed a developer becomes a sentence anyone can type. First: writing code from a description. Then: fixing bugs by describing what's wrong. Now: Google's AI Studio imports your old GitHub projects with one button. Why that last one matters: → That tool someone built you a year ago? Import it. Say "add a contact form." Done → Change the colors, fix the mobile layout. Plain English, zero code touched → A teammate left mid-project? Anyone picks up their repo and continues Before: old code was locked out. Rebuilding from scratch was the toll. Next, per Google: two-way sync. Changes flow in automatically. Each wall that falls hands a specialist's job to whoever types a sentence. Count the walls left between you and the thing you want built. It's fewer than last year.

• 
  Ibrahim Alagbare (@Eb0z_) reported 49 minutes ago

  Why are we still using GitHub, it's trash, use your code and data to train their AI had so many problems with GitHub actions ( the thread sleep timer loop that I can't get over it) that costed people and companies millions in sever processing bills and yet we still use it. There are alternatives like codeberg which is a cloud hosted version of Forgejo that I personally use and love. It's minimal, easy to use and navigate and has all types of actions that you need to run. You can always go to Gitlabs but I find it overwhelming. Do you know any other code containers?

• 
  Nduvho_strategy (@kundik_) reported 49 minutes ago

  I was not running the MCP server. I actually asked Fable to explore how using the MCP server would change the process instead of using AbletonOSC. I gave it the GitHub url of the MCP so it review the process if MCP was used.

• 
  Steve Wilkinson (@SteveW928) reported 51 minutes ago

  @bsvdrip @rodpalmerhodl Yes, not too long after I got into Bitcoin and started really learning about it (and after listening to Andreas Antonopoulos on weaknesses), I became a bit alarmed over how Core was structured. I tried asking in some discussions and even got blocked by a prominent Bitcoiners on here (𝕏). I figured maybe I just didn't understand enough about how Github worked (in governance terms), but looks like I had properly identified a problem.

• 
  moreward (moreboxed.com) (@morew4rd) reported 54 minutes ago

  @jtregunna No I left almost exactly a year ago even before the stupid "we're leaving github" post. The other issue was the aliasing issues with parameters. I did not expect to be hit by such a thing from a systems programming language. The biggest issue was how they "moved away" having the C/C++ toolkit built in. Because that was the selling point for me to even try it. I'm back to cmake since then lol

• 
  Henrikh (@henrikhinai) reported 57 minutes ago

  Microsoft AI engineer Chris Noring just mapped the workflow that turns one engineer into a 20x developer - and it starts by closing your editor "20x more code could be 20x more slop. That's why guardrails are now our whole existence" Here's the CLI-first system he uses at Microsoft: > The Editor Isn't Home Base (03:08): - He starts his day in the CLI, not the editor. The editor becomes a "control board" that just listens to your CLI, repo and agent streams - you drop into it only for fine adjustments > You Write Prompts, Not Python (05:39): - Six terminals open at once - "build me an app," "fix this issue," "add a feature" - kicking away while he sips coffee "Engineers no longer bring PowerPoints, they bring working demos" > Guardrail #1: agents.md (07:43): - The bare minimum in every repo: high-level intent, architecture, dos and don'ts. His example rule: "never change the architecture unless I tell you" > Skills Are a Contract (09:30): - A repeatable recipe the agent must follow, living in .claude/skills. "Don't improvise, don't be creative" - intentionally constrained so the agent behaves like a careful human dev > Custom Agents (12:57): - The next level up: a persona (security expert, backend, researcher) that can reason, plan, and wield many skills plus MCP servers. The skill executes; the agent orchestrates > /delegate to Scale (17:42): - "/delegate" from the CLI - or assign-to-agent in the GitHub UI - spins up a draft PR in a sandbox. You stay the human in the loop with the merge Bookmark & Watch Now ↓ Send this to a dev who still starts their day in the editor

• 
  Peyman (@iamp3yman) reported 59 minutes ago

  Since day one moving to Codex, the most 50/50 problem I see is the Codex CLI or the desktop app problem with GitHub CLI. No matter what I do, half of the time it says token is invalid. What kind of CLI it is if it can't use another CLI?

• 
  Brandon Music (@BrandonMusicKy) reported 1 hour ago

  @Sentdex *nb: it's not my github, it's run by the mods of the discord server, that contains some SOTA stuff for sm12x.