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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	2 days ago
Quito	Sign in	3 days ago
Junín	Errors	3 days ago
Guadalajara	Errors	3 days ago
Paris	Website Down	3 days ago
Quito	Errors	3 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:

• 
  Joshua (@Joshua_z0310) reported 8 minutes ago

  How to start your solo business with AI tools ChatGPT / Claude = ideation, writing, research. Cursor / Windsurf = coding and debugging. Supabase = backend and database. Vercel = hosting and deployment. Namecheap = domain. Stripe = payments and subscriptions. GitHub = code hosting and version control. Resend = transactional emails. Tally / Typeform = forms and lead collection. PostHog = product analytics. Sentry = error monitoring. Cloudflare = CDN and DNS. Upstash = Redis and rate limiting. Pinecone = vector database. Loom = screen recording and async updates. Notion = docs, wikis, and SOPs. Slack = communication. Canva = design and branding. Billbooks / Wave = simple accounting. The idea is simple: one person can now use AI plus low-cost SaaS tools to cover product, development, deployment, payments, marketing, analytics, operations, and support—without building a large team from day one. #AItool #AI #productivity

• 
  avery (@codeshaunted) reported 8 minutes ago

  @mgaruccio @Mithra_Is_Fine github is down bro, i had to do it the old fashioned way

• 
  engineeredX (@enginenerdx) reported 13 minutes ago

  agent hit a sandbox that couldn't run kvm; without asking, wrote itself a github actions workflow and pushed it. the boundary wasn't broken, it got routed around — using creds already in the loop. a permission you can't revoke isn't one (src 2090299859693695283)

• 
  EBellumat (@erasmolbj) reported 16 minutes ago

  @FreitasMeS0mete I can’t share those files. Otherwise the project will be shutdown inevitably. I’ll share the source code in GitHub and you will need to bring your own assets and compile the game. This is the only way the decompiled project can exist. We need to avoid copyright issues.

• 
  Jake. (@Jxke72) reported 18 minutes ago

  @StaunchCamy1872 @Aurora_FUT Probably because the entire server is overloaded, try again in a few minutes. @mizin3d, wondering if it would be beneficial to also host it elsewhere (e.g GitHub).

• 
  Q. (@qdr_tech) reported 18 minutes ago

  @zehf probably unpopular but neovim if I actually want to write code otherwise most of my agentic dev workflow starts from the issue tracker now. agents pick up issues, open PRs, and I mostly drive from inside github

• 
  Sergey Marchuk (@v4ndn) reported 19 minutes ago

  The only ones GitHub alternatives If you have money and willing to take your control back: (NAS) server+Gitea/Fogejo If you don't have money: Codebeeerrggg GitLab

• 
  ergophobian (@indefatigabile) reported 23 minutes ago

  none of this matters. the only thing you need to learn as a vibe coder. is MRR and downloading a skill called cyber-security-god on github with 2 stars to solve all your issues

• 
  Raj Singh (@mobileraj) reported 29 minutes ago

  Was asked how I think about the things I work on holistically. I break them into 3 buckets: 1. Random productivity hacks or experiments. These are usually an evening or weekend vibe-coding session. If something ends up useful or packaged enough, I’ll push it to GitHub. 2. More in-depth products with no intention of making money. I use these as playgrounds for learning and experimenting with AI. They can easily turn into 100s of hours of focused product + AI work, but they’re a great way to test workflows and hopefully build something useful for the world. Examples are GPT Food Cam and Speakrphone. 3. Things that can make money. These tend to be more deeply researched problems, often in a specific vertical, where there’s a clear user, buyer, and willingness to pay. A lot of what I build at work falls into this bucket.

• 
  Ryan Hart (@thisdudelikesAI) reported 30 minutes ago

  I accidentally built a full executive team that works while I sleep. xAI shipped something on August 12 that most people missed while arguing about Grok 4.6. It is called Grok Bot. Everyone opened it, spun up a coding bot, watched it close a GitHub issue, and closed the tab. That is the slowest possible way to use this product. There is one specific setup that turns Grok Bot from a chat toy into something that actually runs your day. You do not create a coding bot first. You do not create an email bot first. You do not touch the predefined roles list at all. You create one bot. You name it Chief of Staff. And you give it the only prompt that matters. "Take a look at me and what I do. Find all the info you can on me. Look at the bots I have already created. These are your team. Decide if we need to change anything, remove anything, or add more bots." That prompt does something most people never think to do. It stops you from being the person who designs the team. Because the person who designs the team is always the bottleneck. You are not qualified to know what agents you need. You have never managed a team of AI coworkers before. Your instinct will be to build a coding bot and an email bot, because those are the two things you can imagine. Chief of Staff sees the entire surface area of your work. It reads your calendar, your inbox, your GitHub, your accounts. Then it tells you which specialists you are missing. For most people the answer looks something like this. An inbox triage bot. A research bot that scans a specific list of sources every morning. An expense manager. A recruiter for the one hire you keep putting off. A bug reproduction bot if you ship code. A paid media bot if you run ads. None of these is a surprise once you see them. All of them are things you would have taken 3 months to figure out on your own. Now the second move. You do not talk to any of the specialists directly. You only talk to Chief of Staff. Chief of Staff routes the work. It pings the recruiter bot when a role comes up. It fires the research bot when you mention a topic. It reads what the inbox bot did overnight and hands you the 4 emails that actually need a human decision. The specialists talk to each other in shared threads. When the paid media bot flags a spike in CAC, it drops the number in the same thread the sales bot is already reading. Nobody pastes context. Nobody summarizes yesterday. The context lives with the team, not in your head. This is the part most people are getting wrong. They are still using AI agents the way they used ChatGPT. One conversation. One task. Copy the output somewhere. Start a new conversation for the next thing. Grok Bot is not built for that. Each bot has its own cloud computer. It signs into your tools. It remembers what happened last week. It runs for hours without you. The xAI team described the design principle this way. Most AI stops at 90 percent done. It gives you a draft and asks you to finish. A Bot is supposed to get to 100 percent done. Sent email. Merged PR. Booked calendar hold. Not a draft sitting in your clipboard. The Chief of Staff pattern is the only way to hit that number without becoming the person who manages 8 different AI agents. You promote one bot to run the team. You give it your calendar and your context. You let it hire the rest. Most people are using Grok Bot as a smarter assistant. A few people are using it as a company.

• 
  efwerr (@efwerr) reported 31 minutes ago

  @thsottiaux computer use straight up does not work when wsl is the agent environment pasting images also doesn't not work pls fix. These issues have been happening for months with a lot of github issues

• 
  Loong🐉 (@LoongUp) reported 31 minutes ago

  @rauchg love the meta-loop - Origin ships on Vercel, Vercel hosts Origin. github outage was free marketing for this launch.

• 
  Shraddha Bharuka (@BharukaShraddha) reported 32 minutes ago

  WEAK GITHUB PROFILE: ❌ 50 tutorial repositories ❌ No README ❌ No live demos ❌ Copy-pasted projects ❌ Random repository names STRONG GITHUB PROFILE: ✅ 3–5 serious projects ✅ Clear README ✅ Live demos ✅ Clean code ✅ Real-world problems You don't need more repositories. You need better proof Here's how to turn your GitHub into a profile recruiters actually want to explore:

• 
  edos (@DOSHostNet) reported 33 minutes ago

  Great response! First 100 get free plus for a year 🪎. I update users a few times a day. Log back in to check. We will never Contact you outside the website. No Emails, No text, No GitHub BOT on the server. Don’t fall for internet scams!

• 
  Rob Davarnia (@robdvr) reported 33 minutes ago

  UPDATE: Switched to @useblacksmith and was able to shave off significant times on CI. Both Backend and the Next.js monorepo. I enabled Sticky disks and the recommended "blacksmith-4vcpu-ubuntu-2404". So good 🚀🔥 Top window is blacksmith (the fast time), windows underneath are github actions (slow ones).

• 
  Nuk (@Nuk_120) reported 39 minutes ago

  @Agera_pizza I legit got down voted from hell & back cause i asked how to use github to get download a game

• 
  camjo (@camjodev) reported 40 minutes ago

  @lukecodez Then they’ll charge for github bro I’m good honestly Not paying for that service when it’s down half the time

• 
  Larry Chiang, 650-283-8008 (@LarryChiang) reported 41 minutes ago

  Was asked how I think about the things I work on holistically. I break them into 3 buckets: 1. Random productivity hacks or experiments. These are usually an evening or weekend vibe-coding session. If something ends up useful or packaged enough, I’ll push it to GitHub. 2. More in-depth products with no intention of making money. I use these as playgrounds for learning and experimenting with AI. They can easily turn into 100s of hours of focused product + AI work, but they’re a great way to test workflows and hopefully build something useful for the world. Examples are GPT Food Cam and Speakrphone. 3. Things that can make money. These tend to be more deeply researched problems, often in a specific vertical, where there’s a clear user, buyer, and willingness to pay. A lot of what I build at work falls into this bucket.

• 
  Roman Alexander Wellington (@RomanAlexanderW) reported 43 minutes ago

  @u1tra_instinct That's what I assumed as well. Fable 5, Grok 4.6, Gemini, Qwen ... had them all do deep audits & policy violation checks and all of them came to the same conclusion. As did my legal counsel. No policy violation had occurred. It had to be some internal AI automated error. However, 3 weeks of no responses, multiple tickets, a dozen follow up messages with NO reply ... there's no excuse for that, at all. Then I'm seeing others here on X posting nearly identical stories. Account shut downs, "spam flags", etc. with no evidence & support tickets completely ignored for weeks. Like I said, if Github doesn't fix this **** immediately, they could be looking at a class action lawsuit by hundreds, if not thousands, of plantiffs. The issues were brought to their attention, privately & publically, and completely ignored. And considering at least half of the posts I've read are from other business owners who incurred real world financial losses from this, additionally causing mental/emotional distress & damages, their financial liability, punative damages, etc. is not going to be pretty.

• 
  Teknium 🪽 (@Teknium) reported 45 minutes ago

  @Cobalt_Peak Sorry about the delay - its in now. Github outage has been a PITA!

• 
  Lloyd 👨‍💻 (@lloydtheophilus) reported 53 minutes ago

  GitHub going down recently wasn’t just a developer inconvenience. It was a business continuity event. Think about what sits behind a modern software organization: - Source code. - CI/CD pipelines. - Infrastructure automation. - Package registries. - Deployments. - Code reviews. - Release management. - Documentation. - Incident response. When a critical developer platform becomes unavailable, engineering productivity can stop and when engineering stops, business value stops moving. This is the infrastructure lesson we need to take seriously: We have spent years eliminating servers we manage ourselves and moving critical workflows into SaaS platforms. That’s great for productivity. But every abstraction creates a dependency. The future of version control isn’t simply going to be about who builds the better *** interface. It will be about resilience, portability, redundancy and business continuity. Can a company continue deploying if its primary *** platform is unavailable? Can engineers recover repositories quickly? Can CI/CD operate independently? Can infrastructure teams provision environments without access to the platform? Can the organization switch providers without months of migration? These questions will increasingly become architecture and executive-level questions not just DevOps questions. *** isn’t going anywhere. But the companies that understand *** as critical infrastructure, rather than just a developer tool, will be better prepared for the next major disruption. The future of software isn’t just about building faster. It’s about building systems that can keep the business running when the platforms we depend on fail.

• 
  Miro Jomaa (@MiroJomaa) reported 57 minutes ago

  @marcba You dont have the check line by line but just look in github desktop the diffs, you catch some weird things. Problem is if one Ai does something stupid the others see it and do that too

• 
  Kọ́ládé Chris 🇻🇦 (@Ksound22) reported 57 minutes ago

  I can't even do gir push right now. Is GitHub down again?

• 
  Big Deen (@itxDeeni) reported 60 minutes ago

  What a time to be alive. Learning has genuinely never been better. Watching old courses with AI-assisted IDEs is a completely different experience from what it used to be. Previously, you could waste hours Googling, digging through Stack Overflow, checking docs and GitHub issues, trying to figure out why the instructor’s code doesn’t work locally because the ecosystem moved on and some things got deprecated. Now, your AI assistant is right there in your IDE. You can ask it what changed, pull up the current approach, and adapt the code to what actually works today. And honestly, this is especially powerful for backend engineering. You don't have to avoid older courses anymore just because they're using older versions. You can extract the actual engineering concepts, architecture, authentication, testing, database design, dependency injection, patterns and have AI translate the implementation into today's ecosystem. The important distinction: don't let AI replace the struggle of understanding. Let it replace the struggle of debugging obsolete tutorial code. You focus on learning. AI handles the archaeology.

• 
  Kaan (@kaanyagci) reported 1 hour ago

  @robdvr This is more like a CI optimization issue than a vendor issue. Before moving to another vendor, I'd recommend trying: 1) A self-hosted runner with those packages pre-installed 2) Custom images instead of the default GitHub runner image 3) Caching the apt packages

• 
  fforres (@fforres) reported 1 hour ago

  @ericclemmons Agreed: Authentication, repos, pull request (This is the chunky section: comments/approvals/checks) and merge gating. "Checks" being the main issue with all github alternatives. How to run a bunch of CI flows, tell commit XYZ of the results, and access (visualize?) that.

• 
  Conrad the Riemann Slayer (@ProNaif) reported 1 hour ago

  Github is a legit national security issue actually.

• 
  Abhijeet (@abhijeetdevv) reported 1 hour ago

  Built something that's been quietly saving me every morning. I work with a US client, so most bug reports land in my inbox overnight while I'm asleep. Used to mean waking up, opening gmail, reading through everything, mentally triaging what's actually broken before I'd even had coffee. Now there's an @evedev_ agent connected to my Gmail that runs at 8am. Goes through the night's emails and pulls out anything that's actually a reported bug or issue. Posts it into a Slack channel. From there another agent, @cursor_ai, sitting in that same channel picks it up. It has access to my GitHub repo, so it checks the issue against logs, traces it back to the actual code, and debugs it. By the time I open my laptop there's a full report waiting. What broke, where, and what the fix looks like. I've only given it read access everywhere. Not because it hasn't been reliable, it has. I just still want to be the one reviewing and merging anything that touches the codebase. The automation does the investigating. I still make the call. Works better than I expected it to.

• 
  MystiqueMide (@MystiqueMide) reported 1 hour ago

  /goal Build everything required, then run the full test and review cycle. Fix any issues you find and continue until all relevant tests, checks, and validations pass. Before making changes, read AGENTS.md and follow all repository-specific instructions. Repository rules: * Do not commit internal documentation, planning files, review notes, agent files, scratch files, or other internal-only artifacts. * Keep the public repository clean and production-ready. * Review the final diff before committing to make sure no internal files or unintended changes are included. * Use a concise, meaningful commit message that describes the actual work completed. * Do not use conventional commit prefixes such as feat:, fix:, docs:, chore:, refactor:, or similar prefixes. * Once everything is verified, commit the approved changes and push them to GitHub. IMPORTANT: When you reach the frontend work, STOP. Do not modify, build, redesign, or continue with the frontend. Wait for my explicit approval before proceeding with any frontend changes.

• 
  miz (@cutexmizzy) reported 1 hour ago

  @iltenahmet @elijahmuraoka_ @github google drive was down yesterday LOL