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 (62%)
• Errors (21%)
• Sign in (18%)

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	2 days ago
Quilmes	Website Down	2 days ago
Bengaluru	Website Down	5 days ago
Yokohama	Sign in	5 days ago
Gustavo Adolfo Madero	Website Down	9 days ago
Nice	Website Down	10 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:

• 
  Lazi (@algoritmii) reported 47 seconds ago

  @github bro ffs fix your ******* issues stop pushing features

• 
  Shubh Jain (@shubh19) reported 3 minutes ago

  @devXritesh now it’s mostly docs, blogs, github issues, and AI explanations instead of full books

• 
  Kevin Worthington (@kworthington) reported 9 minutes ago

  Practical IT take after the recent npm / PyPI supply-chain compromise reports: Your build pipeline is production infrastructure. If a package install can expose GitHub tokens, cloud keys, or CI/CD secrets, that is not "just a developer issue." That is an operations problem with a security bill attached. #DevOps #Cybersecurity #SupplyChainSecurity

• 
  DeBros (@DeBrosOfficial) reported 11 minutes ago

  The Problem We’re Solving🫡 Your organization’s brain lives in 12 different places — and none of them talk to each other. Decisions get buried in Telegram threads. Context is split between GitHub and AnChat. Important knowledge disappears within hours. Onboarding becomes tribal knowledge all over again. 🤖AnBuddy fixes this by becoming the single source of truth for your entire team.

• 
  Alex Maximiano (@FARTURATECH) reported 13 minutes ago

  @enunomaduro Hi Nuno, the problem wasn't with Laravel, but with GitHub, which wasn't able to download the dependencies. Sorry.

• 
  Ryan Djurovich 😎 (@ryan0x44) reported 16 minutes ago

  @glcst By this logic Microsoft will fix the GitHub and NPM security issues soon

• 
  Kea (@alpinoWolf) reported 16 minutes ago

  " we literally cannot programmatically trade from this account until Polymarket's engineering team patches the V2 library and resolves GitHub Issue #65. " How does you evpoly bot do ? Please help me ? Is python coding problem here ? 3/3

• 
  David (@drgdfyi) reported 16 minutes ago

  @github Brother fix your main product first 😭

• 
  Sean Keenan (@sean9keenan) reported 18 minutes ago

  @brian_lovin Semi-relatedly: I’m back to VS Code from Cursor, autocomplete seems much better now! (Not that I’m crafting code by hand much) But importantly, the… basics seem much more stable (Cmd+f, and saving have been pretty broken in Cursor recently) Curious how GitHub Copilot feels!

• 
  Jeromy Sonne (@JeromySonne) reported 19 minutes ago

  @TJ_Bongiorno None of them. MTAs fundamentally are broken technology not worth it. Claude can do a proper lift study DIY or using an open source framework from GitHub. Build don’t buy and save the $$$

• 
  Jubilance Pheesh - Adaptives Engineer (@LuftRaptor) reported 20 minutes ago

  @da_asmodai @Pirat_Nation That’s not a 4th option, that’s literally one of the existing options. Publishing server host binaries complies with the law. A single GitHub that’s publicly accessible complies. The executable doesn’t have to be self contained, just have tools up to make the game playable

• 
  atomicbot.ai (@atomicbot_ai) reported 23 minutes ago

  Hermes Agent vs OpenClaw using Qwen 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Justin Cromer (@just_cromer) reported 29 minutes ago

  @htmx_org github is down sry

• 
  Hackscorpio (@hackscorpio) reported 32 minutes ago

  @thsottiaux Codex review is not working right. When the model finishes, it doesn't render the response properly (not a model degradation). Seems like a regression in Codex application. I have no idea where to report that. I was reporting errors for cli and VSC extension on github.

• 
  Your Friend Myk (@mykola) reported 34 minutes ago

  @joelhooks is this just static content? so like a github pages alterntaive? can't run a server etc?

• 
  Dikshit Jain (@mahanot_dikshit) reported 36 minutes ago

  My company hired a fully remote engineer last year. Great performance, always hit deadlines, never caused problems. Last month, he died suddenly. I asked Boss can we keep his Slack, email, and Github accounts active. We trained an AI model on his commits, code comments, and messages. Now “he” still reviews PRs, answers tickets, and posts thumbs-up emojis in standups. I haven’t told anyone that i kept him on payroll as well. But I changed the bank account on his employee database to mine. We'll miss you George and thank you for the new beach house.

• 
  Adam Sheldrick (@ECSM_Research) reported 37 minutes ago

  @DimitrisPapail It would be nice to have that problem. I'm currently stuck using Zenodo and Github for my work, as I'm not tied to any institution.. just getting an endorsement for arXiv is a near impossible..

• 
  nadya (@sosidudku) reported 40 minutes ago

  ran Hermes Agent vs OpenClaw on local model Qwen 3.6 35B task: scrape GitHub star history, find what caused the growth spikes, build a live dashboard in the browser OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.

• 
  Lu (@LuminousTheReal) reported 40 minutes ago

  @SilverYogensha @thsottiaux Potentially, but it seems like it's using 5.4 to compact it since 5.5 is bugged out. I found it on github, lots of people are suffering with this compacting issue and i think we will get a reset soon since tibo mentioned the quality si down

• 
  Beau Johnson (@BeauJohnson89) reported 44 minutes ago

  agent skills are becoming the new software package DenisSergeevitch/agents-best-practices > 120 stars on github > created today > provider-neutral skill for codex + claude code > designs and audits agent harnesses > covers tools, permissions, memory, evals, prompt caching, observability, and safety the important line from the readme: the model proposes actions. the harness validates, authorizes, executes, records, and returns observations. that is the whole game. most people keep trying to fix agents with bigger prompts. the real fix is a tighter harness.

• 
  The Whizz AI (@TheWhizzAI) reported 44 minutes ago

  🚨Elon Musk just open-sourced the algorithm that controls what 600 million people see every day. Not a summary. Not a blog post. The actual production code. Live on GitHub right now. Facebook won't do this. TikTok guards it like a state secret. Instagram calls it proprietary. X just put it on the internet for free. This is the first time in history a major social platform has released its live, production-grade recommendation algorithm the same day it went live for users. Here's what's actually inside: →Home Mixer the orchestration layer that assembles your entire feed →Thunder stores and ranks every post from accounts you follow →Phoenix the Grok transformer that mines the entire global post library to find content you didn't know you wanted →Zero manual feature engineering Grok watches what you click, like, and dwell on. That IS the algorithm. →Updated every 4 weeks with full developer notes. Live. In public. Why did Musk do this? The EU fined X €120 million for transparency violations. France launched a separate investigation into algorithmic bias. Threads just overtook X in daily active users for the first time. And Musk said out loud on the day of release: "We know this algorithm is dumb and needs major improvements. But at least you can see us struggling to fix it in real time. No other social platform would dare do this." Here's the wildest part: You can now read exactly why your posts go viral. Or why they die at 12 impressions. No more guessing the algorithm. No more $500/mo "X growth" courses. No more "post at 9 AM on Tuesdays" nonsense. The answer is literally in the code. Apache 2.0 license. Full source. Updated monthly. The most transparent thing any social platform has ever done.

• 
  Java (@rishabhjava) reported 47 minutes ago

  @github How about the existing product stops going down first

• 
  Nick Farina (@nfarina) reported 48 minutes ago

  My "work" so far this morning has been: 📋 Taking product feedback from my in-app Agent and feeding it to Claude Code 🌐 Asking Copilot on Github to explain a recent change to an open-source lib and pasting its explanation for Codex to fix I'm basically middle management now.

• 
  nadya (@sosidudku) reported 49 minutes ago

  Ran Hermes Agent and OpenClaw on the same task: scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. Local model: Qwen 3.6 35B OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.

• 
  Peter Steinberger 🦞 (@steipete) reported 49 minutes ago

  @yxcc Discord or GitHub Issues.

• 
  Scott Rudy (@scottrudy) reported 52 minutes ago

  @davidfowl I have GitHub Actions for Static Web Apps with .Net azure functions, but they refuse to update for .Net 10. Still stuck on 9 despite open issues.

• 
  Caneleo (@Caneleo55) reported 56 minutes ago

  Since there is lots of hype on @polymarket right now you have to be extra careful there are lots of scammers out there 🚩 Don’t download random trading bots or repos that are trending on GitHub i tested one once deposited 10$ to a fresh wallet and run the bot on a vps turns out it had a secret function that sent your .env with your private keys to a different server 💀

• 
  masamune🌋 (@masamune_hybs) reported 56 minutes ago

  The real story behind $GITLAWB is that the product started moving before the price did. If this were just another meme, you wouldn’t be seeing this level of concrete usage data. OpenClaude: ・26.8k GitHub stars ・8.5k forks ・615 commits ・Gitlawb OpenGateway with MiMo added in v0.11.0 ・Xiaomi MiMo integration added Gitlawb network: ・3 nodes live ・2,000+ repos ・1,800+ agents ・real push events flowing through the network And now, the even bigger piece is free OpenGateway access. Since OpenClaude v0.11.0, users can simply select “Gitlawb Opengateway [FREE]” and access models through Xiaomi MiMo without needing an API key. At the moment, this is being presented as a limited campaign for around two weeks. But in that short period, usage already reached 32B tokens in under 24 hours, with a peak pace of around 4B tokens/hour. So this is not just hype because something is free. Builders are actually touching it, testing it, and starting to use it. That matters. Gitlawb is not “an app that uses AI.” It is infrastructure for AI to work. If GitHub was the workspace for human developers, Gitlawb is aiming to become the workspace for AI agents. As AI agents grow, they will need: Identity. Permissions. Repos. History. Signatures. Reviews. Persistent storage. Incentive design. Gitlawb is going straight into the middle of that stack. And on top of that, it has OpenClaude as the entry point. You can try it for free. Agents can write code. Agents can push to repos. Demos are shipping. External projects are starting to use it. Repos and agents are growing on the network. That flow has already started. And this is where $GITLAWB’s utility starts to matter. More AI agents. More repos. More pushes. More PRs and issues. More builders using the network. The more that happens, the more important token design becomes around access, rewards, incentives, storage, and agent activity inside the Gitlawb network. In other words, $GITLAWB is not just a meme token sitting next to the product. It has the potential to matter as network usage grows. Of course, it is still alpha. The node count is still small. Replication is still developing. OpenGateway free access is currently limited-time. Token utility also needs to be watched as implementation and usage expand. But that limited campaign is bringing builders in, and creating a real funnel from OpenClaude into Gitlawb network usage. That is the key. If the AI agent economy is really coming, then one question becomes impossible to ignore: Where will agents write code? Where will they own repos? Where will their contributions be proven? $GITLAWB already has: A working product. Early real usage numbers. A funnel bringing builders in. And a future network utility narrative. That’s what makes it interesting. Respect to @kevincodex and @gitlawb. They’re not just talking about the AI agent future. They’re shipping it. #AIagent #Web3 #Base

• 
  Mr. Buzzoni (@polydao) reported 56 minutes ago

  Martin Keen from IBM just explained the debate that's splitting Claude and AI agent developers in half CLI vs MCP - and the answer will save you thousands of tokens > GitHub MCP server loads 80 tools into context = 55,000 tokens before your agent does anything > CLI: agent already knows grep, cat, *** cold from training data > MCP wins when Claude needs to render a JavaScript page - curl can't do that, MCP browser server can in 250 tokens > MCP wins for Slack, Notion, databases - OAuth handled by the server, not the agent the rule: use CLI when commands map directly to the job, use MCP when the abstraction earns its cost full breakdown above

• 
  Prime 🏳️‍⚧️ (@Prim3st) reported 57 minutes ago

  @AAO23114 @SolaraProto Unfortunately that's probably not possible without a dedicated server... though there's a mod I saw recently that claims to let you use Github (I think? It was definitely using ***) to store/backup world saves. Maybe you could use something like that to have a shared world?