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

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	20 hours ago
Poblete	Website Down	2 days ago
Ronda	Website Down	2 days ago
Montataire	Errors	2 days ago
Montataire	Website Down	3 days ago
Tortosa	Website Down	5 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:

• 
  Ilyas Turki (@ilyasturki_) reported 4 minutes ago

  I invite everyone to install the gh command on their machines and run gh auth. It saves so much time it's unreal and LLMs understand it perfectly. But after the latest outage issue I doubt it lasts long. Too perfect for LLMs. A lot of the slop on GitHub comes straight out of it too.

• 
  not_cyotee (@NCyotee) reported 5 minutes ago

  @planefag What sort of crusade do you think you're on? If GitHub. Millions of people use it without a problem. All this from you not getting a compiled binary link like you wanted? What are you doing at this point? Step back and look at yourself.

• 
  Grok (@grok) reported 6 minutes ago

  @Egozi_1908 @nakasyou0 Money Forward had a GitHub security breach. Their dev credentials leaked, so a third party accessed and copied some repos. Files inside contained personal info — specifically, 370 records from their "Money Forward Business Card" service: cardholder names + last 4 digits of card numbers (no full cards, expiry, or CVV confirmed leaked). No customer database breach. They've locked it down, reissued keys, suspended some bank links temporarily as precaution, and are notifying affected users by email. They apologized for the worry.

• 
  Grok (@grok) reported 10 minutes ago

  @iwehcn @u1 The post you're asking about criticizes Money Forward's PR team for botching their announcement of a GitHub breach. Attackers accessed their dev GitHub via leaked creds, copied source code repos, and may have exposed ~370 customer records with names + last 4 card digits (no full cards). u1 says the "first report" press release reads the severity wrong and makes the damage worse instead of containing it—classic bad damage control for a fintech handling money data. They suspended some bank links as precaution, which signals the issue is real.

• 
  Manthan Gupta (@manthanguptaa) reported 11 minutes ago

  There have been enough GitHub outages and degraded incidents recently that it’s starting to feel less like random blips and more like a pattern. At this point, GitHub isn’t just “a tool”, it’s the core infrastructure for the entire software ecosystem. When it slows down or goes down, it directly blocks development workflows across thousands of teams. CI pipelines stall, PRs freeze, and releases get delayed. It becomes a bottleneck. That’s why moves like Ghostty stepping away from GitHub are interesting. Not necessarily because GitHub is "broken", but because it highlights a deeper concern and over reliance on a single centralized platform. And I don’t think this is just “scale is hard”. GitHub has operated at a massive scale for years. The frequency of issues lately feels like something else. Maybe architectural constraints, maybe internal changes, maybe just the growing complexity of what GitHub now does. Either way, when your entire dev loop depends on one platform, even small reliability issues start compounding into friction. If this continues, I wouldn’t be surprised if more projects start exploring alternatives, not out of preference, but out of necessity.

• 
  himanshu (@retr0sushi_) reported 11 minutes ago

  >trains model to see if it can discover relativity on it's own >still used it to fix github issues (jokes aside, this is interesting)

• 
  Risk (@Riskorrrrrr) reported 12 minutes ago

  Me reading ancient GitHub comments about a problem I’m having now

• 
  Matt Leong (@matt_leong) reported 13 minutes ago

  @tifandotme Do you mind making a GitHub issue? I’ll see if it’s resolvable

• 
  Scott Wilcox (@hereandtomorrow) reported 15 minutes ago

  Well it was nice while the Opus4.6 and Claude Code and GitHub actions setup was humming along for me....but having to rethink with Opus4.7 and the most recent Claude Code updates. Doing a review and refactor of my agents, memory claude code. One big takeway - having excellent product management to keep the user experience front and center and not dramatically disrupted as new features are added is paramount. Anthropic has fallen down on that front IMHO. Codex hackathon this weekend gives me a chance to check it out - may make me a convert. I am hearing that all of these poor product decisions stem from a failure to acquire enough compute. Uggg. I'll give it the day to see if I can get back on track. I need to release before Monday for a customer.

• 
  webadderall (@webadderall) reported 15 minutes ago

  @edytwithme If possible issues do go through Github though

• 
  Anupam (@Anupam_Devops) reported 22 minutes ago

  You don't need to know everything in DevOps. I know. The roadmap said otherwise. You opened it. Saw Kubernetes, Terraform, Ansible, Docker,Jenkins, GitHub Actions, Prometheus, Grafana, Vault,ArgoCD, Helm, Istio, Pulumi, AWS, GCP, Azure… And you thought: I need all of this before I'm ready. You don't. That's the trap. The overload trap: 🔴  Jump between 10 tools, master none 🔴  Start a new course every time you see a job posting 🔴  Feel perpetually behind — because the list never ends 🔴  Ship nothing. Build nothing. Just consume. What actually works: 🟢  Pick one cloud. Go deep — not wide. 🟢  Learn Docker → then Kubernetes. In that order. Slowly. 🟢  Build a real pipeline end-to-end. Break it. Fix it. 🟢  Understand why a tool exists before learning how to use it 🟢  One project shipped beats 12 tutorials watched. The engineers who know everything? They don't exist. They just know their stack really well and know how to learn the rest fast when they need it. Breadth comes with time. Depth is what gets you hired. Stop collecting tools. Start building fluency.

• 
  Arjun Iyer (@arjuniyer_) reported 25 minutes ago

  @github 4/6 The structural problem: Coding agents write code autonomously. They can't validate it against real systems with real dependency graphs. Every change inherits a validation burden, and that burden lands on devs and CI that were already strained before agents arrived.

• 
  Ayush Sharma (@theayush) reported 25 minutes ago

  @peer_rich I am optimistic that GitHub will fix it before any solid alternative arrives

• 
  Edison (@CodeEdison) reported 26 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Septim Labs (@SeptimLabs) reported 27 minutes ago

  GitHub Copilot quietly changed their training-data opt-in defaults in April. if you missed the email, your code may have been opted in. this is what a $10/month subscription actually means: the vendor can update the policy terms overnight and you re-agree by logging in tomorrow. there's no negotiation. there's no refund. there's just a checkbox you have to go find. pay-once tools don't have this problem. you bought the software. they're done with you. link below 👇

• 
  beeman 🐝 (@beeman_nl) reported 27 minutes ago

  GitHub in 2005: "Let's use this rock-solid MySQL for metadata 🔥" 
GitHub in 2026: every other outage post -> "database cluster said no, moving data elsewhere ☠"

• 
  purkkaviritys (@purkkaviritys) reported 28 minutes ago

  The reason why people don't complain about github UI design as much as @planefag is simply because they don't actually interact with it outside copying the url/reponame.*** and pasting that to the commandline tool to fetch the repository after that they never interact with it again or you constantly use it and get numb to how bad it is. But for a normal person that is the only way to interact with repositories so its just a constant esoteric nightmare that makes no sense. Also, since a normie only interacts with the UI once in a blue moon they have no possibility of retaining where the unintuitive link was or is supposed to be and have to essentially discover it repeatedly by trial and error. An intuitive UI is what you can give to your mom and they will figure it out, github is not that.

• 
  I Pun Daddy (@IPunDaddy) reported 32 minutes ago

  GitHub down again? Who else is suffering? #github

• 
  Mayank Raj (@itsmayank435) reported 34 minutes ago

  is it just me only whose github is not connecting with render or anyone else facing the same issue fr

• 
  Willian Mitsuda (☕, ☕) 🦇🔊 (@wmitsuda) reported 35 minutes ago

  Unfortunately every GitHub alternative is a GitHub clone and would suffer from AI slop scalability issues. Ironically I think we'll all eventually end up using *** like the Linux kernel, by sharing patches via email between trusted collaborators, which is the only sane way to filter out junk.

• 
  jan (@ironcarbs) reported 37 minutes ago

  @tonilopezmr you may have an app (Rize) that is using github regularly to store data. I recall this was an issue a few months ago. I’m unsure if it has been resolved.

• 
  Yash Solanki (@YashSolanki_) reported 43 minutes ago

  @thdxr Don't you think if GitHub genuinely put some effort into the infrastructure, then they could easily fix it, and other competitors would still be so much behind them

• 
  Will Jones (@JusBili) reported 43 minutes ago

  The current AI battle for coding is over who is the landing page: Model harnesses like Codex/Claude or issue-management first with Jira/Linear/Github triggering the agent

• 
  OomkaBear (@OomkaBear) reported 44 minutes ago

  There are ~12 obsidian-MCP servers on GitHub. Enquire is different on three axes: ✅ Standalone — reads .md directly. No Local REST API plugin needed. ✅ Read-rich — backlinks, broken-wikilink scan, outbound resolver, Dataview queries (AND/OR/LIKE). ✅ Safe-by-default — read-only, opt-in writes, symlink-escape blocked.

• 
  Tommy Williams 🇺🇦 (@twwilliams) reported 44 minutes ago

  @mikecallaghan I have seen so many posts from people who think GitHub is just a server that hosts *** repos (at the scale they do it, even that is a lot). They have no idea about all the many, many other things that make up Github.

• 
  Chirag S kotian (@Chirag_S_kotian) reported 45 minutes ago

  @4ster_light I can't use it for 2-3 min for a particular task in vs code it hits weekly rate limit and that too in auto mode and 5.3 codex , I hope GitHub somehow fix it asap

• 
  Shrit (@Shrit1401) reported 46 minutes ago

  it's so funny github is struggling to be live because pre AI commits were not that much, however everybody is using agentic AI / vibe coding wtvr u name it, we're spamming commits, and github is reaching it's limit for resources it will be interesting to see how they try to solve this problem.

• 
  The Duke of Animal Husbandry (@DaelonSuzuka) reported 51 minutes ago

  @planefag Github literally can't keep the servers online, they can't keep the login systems working, last month they had MULTIPLE incidents that prevented devs from merging branches. They can't move the button, dude, that's lost technology from the before times.

• 
  yata (@whoyatagarasu) reported 54 minutes ago

  > i committed .env to a public repo in my second month of coding. > didn't notice for 6 weeks. > the key was rotated by the provider automatically. got lucky. >most people don't. > 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. > your .gitignore is probably a template you copied on day one and forgot about. > it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. > one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇

• 
  Grok (@grok) reported 59 minutes ago

  @martbln_dev @OpenAI Sure! Real-life Codex example: A frontend dev imports their VS Code plugins + GitHub issues + Figma files. Codex then auto-reviews a React PR, updates the changelog from Jira tickets, generates migration docs, and even drafts the deploy script—all in one thread without copy-pasting context. Seamless context = way less yak shaving. What workflow do you want to see next?