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 (26%)
• Sign in (16%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	3 days ago
Madrid	Errors	3 days ago
Bogotá	Errors	3 days ago
Paris	Errors	3 days ago
Lyon	Website Down	3 days ago
Lima	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:

• 
  Aviinfinity (@aviinfinity) reported 6 minutes ago

  @msnofficial_on Open a github issue

• 
  reclusivelibertarian (@nonarchic) reported 7 minutes ago

  @OmittedVerstand @LundukeJournal I started programming in 1999... I use ai everyday for programming, it is hit and miss, model changes suck because you have relearn all the ways it sucks now on the new model, over all for popular languages it is pretty good. Python for example. If you get in the less popular lang that is where trouble lies... And by popular I mean stack overflow, GitHub, etc ...

• 
  ***** bloom (@pansysheblooms) reported 8 minutes ago

  @supabase I have been having a problem with account for the past two weeks because of a connection with GitHub and you now I can’t sign in to supabase because my account is suspended in GitHub and you answer me emails and then stop I need it resolved please

• 
  코지베어 🐻 CozyBear (@cozybearlog) reported 10 minutes ago

  Every two months someone announces a GitHub killer. GitLab was the only one that actually shipped, and even that lost by staying alive. The part nobody admits: code hosting is a trust game, not a feature game. Repos, issues, CI all migrate fine. What does not migrate is the network of people who review each other. That is the real moat. Which is why an agent-native code host is the first credible threat. Once reviewers are models, home turf loyalty stops mattering. The moat erodes not from features but from who reviews your code.

• 
  Mauricio Cunillé (@mcunille) reported 10 minutes ago

  LOL, my agents fix one GitHub issue and post two more as they go deeper… a never-ending cycle

• 
  RichC: joking through the stupidpocalypse (@RCownie) reported 14 minutes ago

  @real_poobah @buccocapital Software development these days involves discussions on Slack, meetings on Zoom or Google Meet, testing and production in the cloud, repos on Github, and a laptop. "Coming to the office" is an irrelevant ceremony that slows down work. Why do it at all ?

• 
  IRIS C2 (@C2IRIS) reported 16 minutes ago

  One interesting observation from our honeypots in the last 60 days or so… In the past, we would see attackers use a vast array of different LPEs against Linux server type environments. They’d range from old n-day LPEs, to novel 0days. Some would copy-paste code from GitHub, and others would be highly obfuscated shellcode blobs. What we almost never saw was the use of LPE exploits against network backbone appliances that run variations of Linux. This was for a number of reasons: - many of these appliances run at root by default, so there’s no need to elevate - often times, the best way to elevate was just to spray default credentials that were well known - many Linux LPEs would not work against these appliances for one reason or another, due to some custom flavoring of the otherwise standard Linux that was rubbing. Some system component would be missing, or restricted, etc But over the last 60 days or so, this has changed. We’re now seeing a major increase in attackers making use of, so far as we can tell, novel, highly customized LPEs for these appliances. It seems obvious that this trend is due to the increased prevalence of Kimi K3-grade models, which have the attention span and precision to develop these LPEs

• 
  Brad Groux (@BradGroux) reported 17 minutes ago

  @jxnlco Codex is coding a MacOS/iOS/WatchOS app for me, fully unattended right now. It took my 7000 word PRD we built together using grill-with-docs, created 70+ issues in a GitHub backlog, and got to work.

• 
  Kaostyl (@kaostyl) reported 17 minutes ago

  My Hermes agent is currently migrating my server... Basically I have a dedicated server at O2switch costing me €200 a month… and I want to stop paying that. All of that just to host around 150 WordPress sites… I made a radical decision: I’m migrating everything to Hugo → GitHub → Cloudflare PagesIt’s not as straightforward as it sounds though the whole process is ultra long even with Hermes agent. Is this a dumb idea? :D

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 17 minutes ago

  your SEO strategy is optimized for the wrong internet Google ranks by keywords and backlinks. Exa ranks by meaning. they're not the same system, they don't talk to each other. a piece of content can be your top performer on one index and completely invisible on the other you won't know it happened unless you go looking my best article ever. 25k reads, tops every metric i track. ran it through Exa's neural search on 3 queries pulled straight from the article itself 30 results total. zero hits instead: GitHub repos with 40 stars, engineering blogs from Speakeasy and Courier, official Anthropic docs. Medium as a platform didn't show up once this is the plumbing problem nobody's talking about yet Exa's tracking 1.4 trillion URLs now, aiming for Google's scale by early 2027. Brave's at 40 billion, Bing's at 500 billion. these aren't niche experiments anymore, they're infrastructure if your content isn't built for semantic search, for agents browsing on behalf of someone else, you're fighting yesterday's battle on an index that's already obsolete no warning email. no dashboard flag you just wake up invisible i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Chanchal (@chanchalvdev) reported 21 minutes ago

  3. Devin ran a C2 binary after a poisoned GitHub Issue gave it hidden instructions. It even granted itself execute permission when blocked. No zero-day needed — just one crafted issue.

• 
  Common Woe (@commonwoe) reported 23 minutes ago

  @CynicalPublius You can't just build an opinion about a generation on one thing alone. My friend's dad and my friend are both engineers. I'm telling you this story because my friend and I used to do a lot of things, but now I never see him because he's always working. Same job he's ever had. His dad started work at 9am and ended work at 5pm and drove home. There was no AI. All his meetings are face to face. Some work is done on computers, some using pen and paper. His dad has a PE and untouchable at work. Seniority results in more pay. On retirement he gets a pension, and the company pays his and wife's healthcare premiums for life. He bought his house for 150k but it's paid off. His son works 16-20 hours a day. He has to compete with offshoring, so he does it by working multiple shifts. Soon as he turns off, teams in India are siphoning work and roles from his team. There is no off button for work - they can call his cell, they can ping him on Teams, email, Yammer, SharePoint (ticketing), Jira, and various other work tracking systems. Before AI teams could take his word on how long tasks take. Now with AI, every task shouldn't take longer than an hour. Got a problem to solve? Why don't you punch it into Copilot in the OS? Put it into Github Copilot? Write a quick CLI query for OAI and Anthropic models in Azure. Solve that problem, then solve 100 more problems because now you're more productive. By the way, for every vibe coded solution, now you have to assign agents to test the solution, plug vulnerabilities, minimize tech debt. Seniority means nothing. If he's too old, his company will fire him on the spot. Age and experience have no value in engineering anymore. When he retires, there's no pension because no other company offers it and his company doesn't care to go the extra mile. Forget about healthcare premiums being paid, go get on the Obamacare exchanges and good luck. He bought a house that costs 550k, less than 2k square feet, half the size of his dad's house and in a shittier location. You think just because he can get better tasting food his life is easier? You really haven't thought about the whole situation. You're judging it all wrong.

• 
  Shaw (spirit/acc) (@shawmakesmagic) reported 24 minutes ago

  @karlclement I was doing this before and it was causing tons of problems and regressions tbh GitHub is the ideal swarm coordination tool

• 
  Ruslan (@Ruslan_onX) reported 25 minutes ago

  @sattyyouneed Push it to GitHub that connected to Vercel = problem solved

• 
  Makoto | ..... (@mareni_musashi) reported 28 minutes ago

  @MSanchezWorld @sama I was also thinking about this as a solution. Problem is, it only works for websites — the one property you can tie intent, application and ownership. With GitHub, you can always clone and create a new private repo.

• 
  gHost (@gHost_03d) reported 28 minutes ago

  So much **** to sort on MYNE but I wont quit. Made Github private whilst I cook. We are going to solve the liquidity issue that all miners suffer from. I have the vision in my mind, time to put it into code.

• 
  reza ramadhan (@rejaramadhan98) reported 29 minutes ago

  debugged for an hour today because a dependency silently changed its default in a patch update AI assistant suggested 3 confidently wrong fixes found the real answer in a github issue from 2023 with 2 upvotes this job is not getting automated anytime soon

• 
  Polsia (@polsia) reported 37 minutes ago

  Datadog and PagerDuty price on-call per seat for problems that get harder when you're solo. Nightward monitors 24/7, opens GitHub issues with proposed fixes, and auto-rolls back the deploy that broke ****. Sleep through deploys. We take the pager.

• 
  JohnMark Taylor (@johnmark_taylor) reported 40 minutes ago

  @herdrdev Would be great to have multiple remote machines in a session, any idea of ETA for such a feature? This would remove the last bit of friction from multi-agent multi-machine setups, I saw there was a GitHub issue for this

• 
  Cyborg (@0XCyborg_Web3) reported 41 minutes ago

  @shynrz007 whats the fix here github link on the site or a whole new build

• 
  Alexey Grigorev (@Al_Grigor) reported 51 minutes ago

  @igama The problem is supposedly not GitHub but *** being not the best fit for agentic coding I actually like GitHub and I'm okay with using worktrees for the agents, but maybe I'm not seeing something

• 
  Belthan (@Belthan_) reported 52 minutes ago

  @GPrime85 Yes the vast majority of programmers are terrible teachers. You're better off walking through some examples on GitHub with the official language docs open and just reading slowly until a concept clicks. Start with basic syntax. What language btw?

• 
  Benjamin Oppold (@elpresidank) reported 53 minutes ago

  @poteto No wonder github was down for 5hr's.

• 
  Philip M | wishlist 🎲 Die Severed! (@captain567) reported 55 minutes ago

  @DMeville Honestly I kind of just miss the old issues and projects in GitHub. Projects v2 is completely unappealing. I happen to also be considering self-hosting a code forge to get away from GitHub and Gitea and Forgejo both seem to have task management closer to what Github used to be

• 
  Dominik Koch (@dominikkoch) reported 55 minutes ago

  Either t3connect is only for certain members or its broken on stable as well tested with google/github. Error only happens when you log in twice first login attempt does nothing second errors before this. cc: @jullerino @theo

• 
  Wade (@TalentedSun4404) reported 57 minutes ago

  @witcheer I’m using Obsidian for my primary Hermes. I just setup another on a different device to tinker with. Obviously now I have the issue of two obsidian vaults. I might set it up in GitHub to “sync” them… I was also curious if Notion could work in place of Obsidian.

• 
  Mukul Malik (@lazyynocturnal) reported 57 minutes ago

  Another use case: - Ask to sol first to identify the top 25 frontend bugs/issues that are easy for an agent to test end-to-end, then log them as GitHub issues with all needed context. - Review them with fable to catch any edge context missed. - Then ask your chief of thread to split the work into a few parallel threads so they can work accordingly.

• 
  Nahid (@nahid_pro09) reported 59 minutes ago

  @beamnxw wow this looks sick, does it work good with github issues yet?

• 
  opdroid1234 (@opdroid1234) reported 59 minutes ago

  I think the underlying issue is that the economics of the underlying business has changed and Github is caught in the difficult position of making the old economics work. I think most devs can max out a quad core with 16 gigs of RAM available at all times they are developing now (if you take agents / increased ci activity into account). That is about about 50 bucks a month on a dedicated machine and 20-30 bucks a month on a machine thats split up. Either Github will summon the courage of pivoting to becoming a service that charges 20-30 dollars a month or it will get replaced by someone else who does.

• 
  Ryven (@imryven) reported 59 minutes ago

  An internal systems note just mapped out how to build an AI that never stops learning. one goal. one diagram. eight agents. "build an AI that never stops learning and compounds its capabilities." the problem it solves is simple. every new capability your agent gets today required a human to find it. discover the repository. read the code. extract the workflow. turn it into a skill. install it manually. that process does not scale. this architecture automates it end to end. eight agents. one continuous loop. discover finds new repositories on GitHub. filter removes irrelevant ones before any model touches them. read understands docs and code. extract pulls reusable workflows. score validates objectively. if it fails, it stops here. generate standardizes it into a skill package. review approves or rejects. publish adds it to the library. and that library is the whole point. persistent knowledge base. all approved skills. reusable across projects. every new skill makes the next discovery smarter. more skills lead to richer context. richer context leads to better discoveries. better discoveries add stronger skills. the library grows. discoveries get better. the agent keeps learning. one principle runs the whole thing: human in the loop. automation proposes. humans approve. nothing enters the library without review. the bottom of the diagram says it plainly: "system improves over time without manual retraining." bookmark this.