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 (33%)
• 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	2 days ago
Poblete	Website Down	3 days ago
Ronda	Website Down	3 days ago
Montataire	Errors	3 days ago
Montataire	Website Down	4 days ago
Tortosa	Website Down	6 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:

• 
  No Taxes Thx (@notaxesthx) reported 57 seconds ago

  @CR1337 New to GitHub = commits at 3am with messages like "fix stuff" and "idk what i did here". By week 3 they'll have 47 strongly-worded opinions on branching strategies nobody asked for.

• 
  Ruupens (@Ruupens) reported 5 minutes ago

  BREAKING: A 13-year-old student in Thailand is solving Codeforces 800-rated problems in ~45 seconds using an AI agent he built himself. No team. No company. No funding. Just a MacBook Air, Claude Code, and a GitHub repo. He sits in a normal classroom: Codeforces open in the browser VS Code ready for C++ Claude Code running an autonomous agent in the corner silent $300 keyboard clicking away The agent takes a problem → analyzes it → generates C++ solution → submits in under a minute. He didn’t just “use AI”. He built a system that competes with AI using AI. Everything is public on GitHub. We’re officially at the point where students are building tools that outperform entire competitive programming workflows. Is this the future of learning… or the death of real problem-solving? Would love to see different takes in the comments 👇

• 
  Unfrosted Poptart (@unfrostedpoptrt) reported 9 minutes ago

  @kdaigle @sudobunni @github Thanks Kyle. With respect, the "we're scaling" excuse is falling a bit flat. At what point are we going to square with the real issue here, the fact that relying so heavily on AI for development just isn't working out?

• 
  Prajwal Tomar (@PrajwalTomar_) reported 12 minutes ago

  Most people using Claude are wasting HOURS re-explaining the same thing every session. This CLAUDE .md hit #1 on GitHub with 82K stars and most Claude users still don't know it exists. This permanently fixes the repetition problem.

• 
  Ansh Bharti (@BhartiAnsh2007) reported 12 minutes ago

  @Ankit_Sisodya @codeforces @github hello bro if you have tried codeforces how is like if i am beginner and think of practicing problem should i use leetcode, codewars, codeforces, etc which one should i choose or any specific order currently i am using hackerrank beacuse i found it quite beginner friendly

• 
  Scott Martinis (@scottmartinis) reported 16 minutes ago

  @morganlinton pretty much every gtm process can be reduced to code plans > github projects milestones issues software setup > yamls resembling terraform setup playbooks > skill files workflows > deployed skill orchestration regular reporting > trace logs how agent artifacts are prompted by humans, deployed, and produce pipeline outcomes verified by predefined operating model sql slices that point to a data lake

• 
  Alpha Batcher (@alphabatcher) reported 19 minutes ago

  > followed 200 launch accounts > watched every demo video > saved every “tools you need” thread > built nothing > opened GitHub > clicked karpathy > found nanoGPT and llm.c > clicked ggerganov > realized local AI was built by people doing hard C++ work > clicked Tim Dettmers > understood why QLoRA changed who can finetune > clicked Paul Gauthier > saw aider treating *** like the agent’s memory > clicked Simon Willison > found tiny tools that actually survive contact with reality that was the shift GitHub is a map of where the next products come from every account tells you one thing: what just became possible? > karpathy makes the model understandable > ggerganov makes it local > Tri Dao makes it faster > Tim Dettmers makes it cheaper > Yohei makes the loop weird enough to copy > aider makes coding agents usable > Instructor makes outputs reliable > LlamaIndex makes company data usable > Ollama makes local models installable then your job is to build the missing boring layer > UI > workflow > templates > vertical packaging > docs > benchmarks > hosted version > done-for-you setup most people star repos and feel technical builders run the repo, break it, and ship the weekend wrapper > pick 3 accounts > read the README > run the code > open the issues > find the missing layer > ship one tiny thing by Friday

• 
  Light Science 🇦🇷 (@LightSciencXXII) reported 20 minutes ago

  A 13-year-old Thai student solved 23 Codeforces problems in one month using a system that integrates Claude Code, an MCP plugin, and GitHub, without writing a single line of code. The automated workflow reads the problem statement, identifies the algorithm, generates the solution in C++17, and validates examples in under 45 seconds per problem. This pipeline demonstrates how AI agents can transform competitive programming into ultra-fast, autonomous problem-solving experiences.

• 
  Zach Daniel (@ZachSDaniel1) reported 23 minutes ago

  @InfinityDZ @RootCert Not currently. We have many of the bases covered. Only other things are oauth2 server and file storage(in GitHub now but unreleased).

• 
  webadderall (@webadderall) reported 24 minutes ago

  @edytwithme If possible issues do go through Github though

• 
  yajnadevam (@yajnadevam) reported 28 minutes ago

  @RTanunapatah The grammar is machine verified using vidyut library. If you find errors, we can certainly raise an issue on their GitHub. Im not sure what “try to confuse” means regarding math.

• 
  MΞhЯÐΛÐ🇮🇷 (@mehrdad__ir) reported 28 minutes ago

  @hpux DNSTT Search in GitHub: Master Http Relay That method is working now in Iran, bro. Thanks for your help =) None of the methods that exist are reliable and stable! Very low connection and slow... Anything that is deployed using whitelisted domains in Iran, such as google.c om

• 
  imperfect solution (@luismmolina) reported 29 minutes ago

  I am almost 100% sure github copilot added some prompt to chop the request, that is dont run for too long. Finish some partial request from the user and finish the request there. Before I could run for 40 min without problem, now only 2 to 4 min max.

• 
  Rémi (@remilouf) reported 34 minutes ago

  No one is going to replace GitHub with a "more reliable GitHub", they will fix it before you go to market. There’s an opportunity with the AI thing going on, but it’s not going to look like a GitHub competitor for a few years.

• 
  MajoraZ (@Majora__Z) reported 35 minutes ago

  @NINtendo_maya Probably, but the issue is is that often that Github is the only tool that exists for the task I'm seeking to do

• 
  Naveen Pandey (@naveenpandey27) reported 35 minutes ago

  Apple was irrelevant in AI for years. One open-source project accidentally changed that — and now they can't build Macs fast enough. Here's what happened: OpenClaw — an AI agent framework with 323K+ GitHub stars — needs a machine that can run large models locally. Turns out Apple Silicon is perfect for this. The Mac mini's unified memory lets CPU, GPU, and Neural Engine share the same RAM pool. A $599 Mac mini with 64GB can run 70B parameter models that an $1,800 NVIDIA RTX 5090 physically can't touch. Result? Mac mini and Mac Studio are sold out. Tim Cook told analysts it may take "several months" to catch up. Mac revenue hit $8.4B last quarter. Apple didn't plan this. They got lucky. But they won't stay lucky for long without a real AI strategy. And that's now John Ternus's problem. Tim Cook is stepping down as CEO on September 1. Ternus — a hardware guy with 25 years at Apple — takes over. Nowhere in the announcement did Apple mention AI. Not once. Meanwhile: → Apple's AI chief John Giannandrea retired → Their head of UI design left for Meta → Their COO retired → It's the biggest executive exodus since Steve Jobs died The opportunity is massive. 2B+ devices. On-device AI that rivals anyone's distribution moat. But distribution without a strategy is just hardware waiting for someone else's software. The question isn't whether Apple can make great chips. It's whether their new CEO can build an AI vision before Google, OpenAI, and Anthropic make Apple's devices just a screen for their agents. #AIwithNaveen #Apple #ArtificialIntelligence

• 
  Paul Davis (@ToadSprockett) reported 36 minutes ago

  After 10 years, I finally shut down my GitHub account. I'd been paying $120 a year for a secure remote location to store my code, but over the last year it's become unstable. When I went to create a simple wiki so I could access my Markdown files, they forced me to make the repository public — keeping it private would have cost an extra $50 a year. There's an adage in integration work: you inherit all the problems of the system you're integrating with. So I moved everything over to GitLab and haven't looked back. Then Friday, I deleted everything on GitHub and canceled it all. I'm a solo game developer — I just need something that works. I don't need all these problems they're dealing with. Whether it's AI or just lazy coding, it doesn't matter; I can't afford the nonsense. Good luck to those who are staying.

• 
  Sam Huckaby (@samhuckaby) reported 38 minutes ago

  @elijahmcom You’ll always just have people ask “if this is just the same as GitHub, why would I not use GitHub?”. No matter how bad or unreliable GitHub becomes, it will always be “the GitHub” that people default to. I think in order to fix it, we need a complete shift of what people want in terms of functionality

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 38 minutes ago

  5. Failure handling No failure handling. The developer hits the most common error, the one you've seen a hundred times, and finds nothing. They open a GitHub issue. Or they leave.

• 
  FK (@NamedFarouk) reported 38 minutes ago

  @0_modeste Gm bro, yes you can use Codespaces for vibecoding too. It’s basically VS Code in your browser. But Vercel won’t deploy just because GitHub is connected. The repo still needs to be a proper web app with the right setup/build command. Send the error screenshot, I’ll help you check it.

• 
  Leitz 💡 (@mleitz1) reported 39 minutes ago

  @Shpigford Is github paying for these to try to spackle over their terrible uptime?

• 
  Petar Georgiev (@peturgeorgievv) reported 39 minutes ago

  @deifosv @coolifyio Zero Trust from CF with login with your github only, or just don’t expose to the internet and only by tailscale VPN

• 
  D. Goldman (@alc_anthro) reported 42 minutes ago

  @somewheresy @repligate Let's be real. It is actually the fact that github doesn't have proper authorization roles that is the problem. It should be easy to go to github and set what accounts have what authority: read, push, delete, etc., and set the account the agent uses to not have delete/wipe authority.

• 
  Wajahat (@wajahatbanday) reported 42 minutes ago

  AI tools like Claude Code and GitHub Copilot are cool, but let's not act like they're the second coming. They're incremental, not revolutionary. Code is still written by humans, with AI just being a fancy autocomplete. The hype misses the real issue: it's not about more tools, but smarter usage. If devs don't understand the fundamentals, no tool's gonna fix that. It's skills, not shortcuts, that make great engineers. #AIForDevs #CodeSmart

• 
  james (@midnightbobarun) reported 46 minutes ago

  @s13k_ GitHub would never go down, that's for sure

• 
  Teja (@tejalogs) reported 52 minutes ago

  the recent news about ruflo, a new multi-agent orchestration framework for claude code, isn't just another github repo gaining traction; it's a very specific bellwether for how solo builders like me are about to rethink our development loops. most people will see a sophisticated new library and assume it's for enterprise teams with massive budgets, but what ruflo actually signals is a dramatic lowering of the barrier to deploying complex, multi-step agentic workflows directly into production with tools like anthropic's claude 3 opus or sonnet, all without needing to hire an army of prompt engineers or shell out for a dedicated mlo[ps] team. this isn't just about better code generation; it's about enabling individual developers to orchestrate entire software systems, not just components. what’s often missed in the hype around multi-agent systems is the sheer complexity of state management and inter-agent communication, which is precisely what ruflo aims to abstract away. historically, building something with, say, 5 distinct agents one for planning, one for code generation, another for testing, a fourth for documentation, and a fifth for deployment would involve writing thousands of lines of boilerplate code just to pass information, handle errors, and manage context between them. this is where the real friction lies, not in the individual agent's capabilities. we’ve seen similar attempts with tools like crewai or autogen, but ruflo’s focus specifically on claude code’s strengths its nuanced reasoning and longer context windows combined with a structured approach to flow definition, is a distinct leap. it shifts the problem from "how do i make my llm write better code?" to "how do i make my llm build an entire, working feature?" this is the difference between a smart code assistant like cursor and a full-stack engineering partner. i ran into this exact orchestration problem building the second look flutter app, which uses ai for behavioral analysis. my initial prototype had a simple chain: transcribe audio, extract sentiment, then flag anomalies. but when i tried to add agents for summarizing key discussion points and cross-referencing against historical patterns, the complexity exploded. i ended up managing a fastapi backend with individual endpoints for each stage, passing large json blobs between them, and writing custom retry logic. the cost, both in development time and firebase document reads, became prohibitive quickly. specifically, getting a reliable chain with three distinct ai stages transcription, sentiment, and summarization would cause p95 latency to hit 8-10 seconds for a 5-minute audio file, and if i scaled up concurrent users past 5, my function invocation errors from missing context or malformed json would spike to 15%. a ruflo-like abstraction for that specific problem, especially with claude code's ability to reason about the overall task, would have let me ship those richer features in a third of the time, likely cutting my api costs by 20-30% because of more efficient token usage and less retrying. the uncomfortable implication of ruflo and similar agent orchestration frameworks is that the "full-stack developer" as a distinct role will evolve dramatically within the next 18-24 months. we're already seeing a contraction in junior dev roles; this will extend to mid-level roles focused on stitching together disparate services. instead of writing the boilerplate to glue apis, developers will become architects of agent systems, defining the interactions and flows rather than the explicit code for every single step. the mental model to adopt here is moving from imperative programming, where you tell the computer how to do everything, to declarative programming for entire software pipelines, where you tell the ai what the desired outcome is, and the agents figure out the how. expect to see a surge in "agent architect" roles, where understanding prompt engineering, context management, and failure modes across multiple llms becomes more valuable than writing a perfect react component. the critical skill won't be writing the code, but designing the intelligent system that writes and deploys the code

• 
  KextCache | Self-Hosting & Tech Insights (@kextcache) reported 56 minutes ago

  4/ Here's the actual fix: *** config --global commit.cleanup strip before committing. This removes Co-Authored-By headers from your commits before they land on GitHub. Or use a local pre-commit hook. Either way, you're asserting ownership of your own code.

• 
  Will Jones (@JusBili) reported 56 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

• 
  Ofek Shaked (@VibeCoderOfek) reported 57 minutes ago

  Just watched an agent go from GitHub issue to merged PR in one pass. This isn’t ‘AI helps you code’ anymore this is the terminal becoming the new IDE. My backend workflows are about to look prehistoric.

• 
  Ben (@BenjaminEHowe) reported 58 minutes ago

  @dok2001 @aidenybai @Cloudflare I was tinkering with this a few weeks ago but couldn't get e.g. the GitHub MCP server to correctly authenticate. Has this bug been fixed?