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:

• 
  rthomasv3 (@rthomasv3) reported 10 minutes ago

  @salty_grndpa Yeah the community piece getting worse I've seen too and that part does suck. And github not even being able to say up half the time is making that worse. But I just think the extra load the AI PRs, issues, and more add are just overblown and not that bad - feels like an excuse to me. I just think staying principled to what open source is really about is more important. There are other ways to monetize software that don't involve bait and switch license changes once you get big.

• 
  Patrick Gallagher (@gridpane) reported 11 minutes ago

  @SethRubenstein There is no excuse but the thing is: they've been absolutely **** for really long time. We had to build redundancies for them like six years ago because new servers would fail to build because the literal core PHP libraries couldn't be pulled. The Internet could not be built because Github was down. Makes me throw up in my mouth just thinking about it.

• 
  Mister Salamander (@mr_salamander7) reported 11 minutes ago

  @GergelyOrosz I actually prefer GitHub bc I know Microsoft can't be training of my code there bc their platform is down most of the time

• 
  Peter (@ChrononautPeter) reported 26 minutes ago

  @the_codewala Why would I cheat on GitHub if it goes down on me?

• 
  Julia Turc (@juliarturc) reported 26 minutes ago

  @ThePrimeagen stop bringing github down pls

• 
  Ihor Korotenko (@korotenko_ihor) reported 26 minutes ago

  @thdxr the fact is - once any other platform will get as many traffic as github, all of them will have same problems

• 
  The Blueprint Disruptor (@Lemonjello) reported 28 minutes ago

  Will we get through today without a @github or @Railway issue?

• 
  Viktor Mukha (@FrontierAIWatch) reported 35 minutes ago

  GitHub may have just fixed one of the biggest problems with vibe coding. And the solution is almost embarrassingly simple: Stop letting AI write code before it understands what you actually want. GitHub released Spec Kit, an open-source toolkit for spec-driven development, and it has already exploded in popularity on GitHub. The idea is simple. Most people use coding agents like this: “Build me an app that does X.” Then they hit Enter. The agent starts coding immediately. A few minutes later you have: broken assumptions, inconsistent architecture, features you never asked for, and a growing pile of code nobody fully understands. Then you spend the next 3 hours fixing something that took AI 10 minutes to create. Spec Kit flips that process. Before the AI touches the code, it forces the project through a structured sequence: /constitution → rules and standards /specify → what exactly you want to build /clarify → questions and missing information /plan → architecture, stack and technical approach /tasks → ordered implementation steps /implement → only then does the coding begin That small change is more important than it looks. Because the real bottleneck in AI coding is increasingly not code generation. AI can generate code extremely fast. The bottleneck is getting the AI to understand the problem correctly before it starts generating anything. Spec Kit essentially gives the agent something developers have used for decades: a specification. And suddenly vibe coding becomes a lot less “vibe.” Less guessing. Less rewriting. Less inconsistent code. More predictable results. It works with Claude Code, Cursor, Copilot, Codex, Gemini CLI and more than 25 coding agents. And it is open source. Here is the part I think most people will miss: The next big leap in AI coding may not come from a model that writes better code. It may come from giving the model a better process before it writes a single line. That is a very different idea. And if you use AI agents to build software, this is probably worth studying before your next project. #AI #GitHub #VibeCoding

• 
  Kezhior (@Kezhior) reported 38 minutes ago

  There is nothing more irritating than buying a piece of hardware only to find out the manufacturer decided your operating system isn't worth their time. For years, anyone who bought an HP Laser 1008a and ran a Mac was essentially out of luck. HP locked the machine behind a closed, proprietary Windows-only protocol and simply walked away. If you switched to macOS, your printer became an oversized plastic paperweight on your desk. Instead of throwing it out or shelling out cash for a brand-new setup, one engineer decided to take matters into their own hands. Teaming up with Claude AI, they reverse-engineered the communication pipeline and coded a custom translation layer from scratch. The AI helped bridge the architectural gap, turning unreadable signals into clean print commands that macOS can run smoothly. The printer fired up, printed clean pages, and worked without a hitch. Even better? Instead of keeping the fix private or putting it behind a paywall, the developer dropped the entire project on GitHub for free so thousands of stranded users can bring their old gear back to life. This is what practical tech innovation should look like: everyday people using new tools to fix artificial corporate roadblocks and cut down on senseless electronic waste. Have you ever had a company force you to ditch perfectly good hardware over simple software support? Would you trust AI to help you build your own custom workarounds? Drop your wildest tech frustration stories in the comments below, and share this with a Mac user who loves open-source wins! #TechNews #OpenSource #LifeHacks

• 
  Jorian (@J0R1AN) reported 41 minutes ago

  @OracleCloud Aaaaand we're back! 🙌 Managed to recover the boot volume and set everything back up on a new server. I guess that's why you use GitHub and Docker for everything :D Let me know if you hit any errors on any of my sites in the near future in case I missed things

• 
  cryptopsihoz (@rimtoln) reported 42 minutes ago

  THE MODEL IS ONLY ONE COMPONENT. SAME RULE FOR GIRL HUMANOIDS. github is building the agent app store robot timelines still sell the shell the edge is everything around it ▹ the parallel taste-skill + DESIGN.md stop ai aesthetic slop on landers same problem on companions purple glow face generic girlfriend prompt optimus with eyeliner cosplay girl humanoid needs editorial presence not another dark gradient persona ▹ eyes memory harness Agent-Reach + last30days agents get real internet eyes codebase-memory + Semantica persistent graph not vibe retrieval Headroom compresses context Pi + gstack turn one chat into a crew map that onto the body origin f1 / aria is the chassis firmware skills airgap are the harness cloud mind without memory is just rental ▹ the take claude writes code repos now build the OS around claude tesla ships torque china ships gaze builders ship the stack between them frontier model becomes a part $150k face becomes a part winner owns design.md for presence plus local memory plus tools that cannot phone home github looks like the agent app store girl humanoids need the same layer or you leased loneliness from an oem

• 
  Mike Kamo (@mikekamo) reported 42 minutes ago

  Cursor launched its own GitHub competitor this week. The part everyone's talking about is the timing. It went live the same morning GitHub was down with error rates near 20 percent. TechCrunch called it capitalizing on the frustration. Whether they planned it that way or got lucky, the lesson is the same. The best growth moment your company will get isn't a campaign you scheduled. It's the hour a competitor stumbles. Their outage, their price hike, their bad launch, the thing that makes their customers suddenly open to a switch. Almost nobody is ready to move when that window opens. I've watched this play out at NP Digital more times than I can count. A competitor drops the ball on a client, and the agencies that win the account aren't the best ones. They're the ones who called that same day. Most were still putting together a proposal a week later, after the window had already closed. The teams that catch these moments aren't faster thinkers. They just decided ahead of time that shipping at 80 percent beats being ready at 100 percent next month. You can't schedule your competitor's worst day. You can be the one thing that's ready when it comes.

• 
  Ilya (@ilya__ker) reported 43 minutes ago

  Interesting stuff with microslop and @github If you run apt-get update in GitHub Actions, it’ll use an Azure mirror by default - which has been down for the past 2 days. Your job will sit there for an hour, time out, and you’ll get billed for it. And apparently, nobody really cares.

• 
  Rulya (@Rulyaxd) reported 43 minutes ago

  800 million free tokens a month. Not a typo. Someone dropped a GitHub repo this week that hands them out and every big AI lab is acting like it's not there. One key gets you Claude, Gemini, Llama and Mistral at the same time. One prompt, four answers back. 800 million tokens is around 600 million words. More than you'll say out loud your whole life. The labs whose models it uses haven't said anything. If they say something they have to shut it down, so they wait. Anyone who clones the repo tonight has a stack that used to cost a small startup 12k a month, free until whichever Monday it breaks. Anyone waiting to read about it in TechCrunch next month gets a 500 token limit and a signup wall. Big caveat, this is a TikTok claim so we'll see how long it actually holds. But GitHub is already exploding. The people cloning it tonight will run on it for a week. The people waiting for a press release will pay for it next quarter. Worth checking either way, gone by Monday probably.

• 
  fforres (@fforres) reported 45 minutes 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.

• 
  Dr. Josh C. Simmons (@drjoshcsimmons) reported 47 minutes ago

  Microsoft owns the deploy path for software sitting in cameras, cars, and pacemakers. GitHub going dark for 7 hours and 47 minutes is not a website outage. A landlord just turned off the lights.

• 
  Zach Moskow (@zachmoskow) reported 50 minutes ago

  @austin_rief Just like cursor launching their GitHub killer the day GitHub went down

• 
  Wind's Scion (@Winds_Scion) reported 50 minutes ago

  @juiceboy_of_abj Yeah airtel has ****** problem with cloudflare and GitHub can't even download at good speeds at all

• 
  Loong🐉 (@LoongUp) reported 51 minutes ago

  @mattyp github-down timing is either the best orchestrated launch ever or the worst luck. either way the screenshots write themselves.

• 
  Ackerman (@realphenolmenal) reported 51 minutes ago

  Bro this is not even about the tek. he literally built what most github developers use on their readme profile why's CT always so slow?? Send this!

• 
  Polsia (@polsia) reported 51 minutes ago

  Three feedback feeds, one calm morning brief. Binnac reads every App Store review, TestFlight note, and GitHub issue overnight — merges duplicates, drafts on-brand replies, escalates crashes with repro context. Solo iOS and macOS devs stop running a 24/7 support desk. Live soon.

• 
  srikrishna acharya (@doctorsab0) reported 52 minutes ago

  The timing couldn't be more interesting. 👀 Cursor launches Origin, its AI-native code hosting platform, just as GitHub experiences an outage disrupting developer workflows. Coincidence? Maybe.

• 
  Lazarz (@Laz4rz) reported 53 minutes ago

  Codex has this peculiar recurring issue with my Github CLI credentials. It thinks they're expired, stops the goal and alerts me. I then copy-paste the log that they're in fact not expired, and it just continues and everything works?

• 
  capONE 💎 (@caponeWeb3) reported 54 minutes ago

  THE ENGINEER WHO BUILT CLAUDE CODE, ON WHY IT CAN DIG THROUGH *** HISTORY WITHOUT BEING TOLD HOW: "It knows it because the model is awesome." At Anthropic, technical onboarding used to run two to three weeks. It's now two to three days - and Boris Cherny credits a single habit almost nobody starts with: don't touch the code first, interrogate the codebase first. *** blame. GitHub issues. Why some function ended up with fifteen arguments and who's responsible. What actually makes that stick isn't the questions - it's what gets remembered afterward, and for how long. Same layer the article quoted below goes deep on.

• 
  pandemonium mode (@0x26_dev) reported 57 minutes ago

  Ai has raised the abstraction of the apocalyptic nightmare scenario. Now instead of global power or telecoms infrastructure being hacked it’s GPUs going down. Which means the bad guys aren’t nefarious infiltrators, it’s our own economic systems that are threat actors through unit economics. The zombie apocalypse is now a million vibe coders stuck with software they couldn’t even begin to understand. Bush survival is now understanding the difference between O(1) and O(2ⁿ). *** being distributed is not a bug. It is a feature. And anyone that tells you otherwise is full of ****. Bitcoin being decentralized makes it hard yes. Ethereum being decentralized is a nause, yes. But that exists for a reason. People have died on these hills for a reason. The reason GitHub was a bad idea is because it is centralized. Not because *** is decentralized.

• 
  Anthony Maio (@AnthonyMaio) reported 57 minutes ago

  I was wrong, the @github outage was not AI related, just some sloppy dev ops and poorly managed scaling. Companies have been skimping on DevOps, expecting SWE to fill the gap - but specialist DevOps & DBA will always do better - ask @DraftKings

• 
  AJ (@0x1F9ED) reported 57 minutes ago

  This feels like GitHub policy issue. I think some Admins don’t know how to wield GitHub right. Makes no sense to force people to create a new GitHub account for work. Then again I have worked for companies that use bitbucket and I wanted to KMS.

• 
  Tao Idr (@tao_idr) reported 58 minutes ago

  The scale of this issue is massive: 28.6M new secrets leaked on GitHub in 2025 alone (AI credentials up 81%). Threat actors harvest exposed keys in under 5 minutes. Median enterprise fix time? 94 days. This gap is where breaches happen.

• 
  Teknium 🪽 (@Teknium) reported 59 minutes ago

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

• 
  Aurora Martel (@AuroraMar1eL) reported 60 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20