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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	4 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	16 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:

• 
  Kai - Briefing Block (@briefing_block_) reported 20 seconds ago

  $MSFT - Microsoft’s $7.5B GitHub moat is leaking. Microsoft bought GitHub in 2018 for $7.5B, and on paper it had the cleanest setup in AI coding: the default developer platform, the data exhaust, the brand, and the Microsoft enterprise channel. GitHub says 180M-plus developers now build on the platform, after more than 36M joined in a single year. Copilot also launched in 2021, early in the category, built with OpenAI Codex before AI coding became a real enterprise budget line. That should have been game over. It wasn’t. The real issue The market is treating AI coding like another Microsoft distribution story, but developers are treating it like a daily workflow decision. That distinction matters. Cursor has already overtaken Copilot in some customer-spending data, while Claude Code’s rise shows that engineers will route around the default when the product feels materially better. GitHub still owns the system of record, but the next profit pool may sit in the agent layer: where work is delegated, revised, reviewed, and shipped. That is where product velocity beats installed base. Reliability made the opening bigger. GitHub admitted in March it had not met its own availability standards, blaming rapid load growth, architectural coupling, and weak load-shedding; in April, it logged 10 incidents that degraded services. The sharper tell: GitHub planned for 10x capacity, then realized it needed to design for 30x as agentic workflows drove repository creation, pull requests, API usage, automation, and large-repo workloads higher. That is not a small outage story. That is AI turning software development into machine-scale infrastructure demand. The market read For MSFT, GitHub is supposed to be a hidden asset, not a visible execution risk. If GitHub becomes unreliable while Copilot shifts toward usage-based billing and rivals iterate faster, the moat starts to look more like a traffic jam. The recent compromise of roughly 3,800 internal GitHub repositories does not change the strategic story, but it adds another dent to developer confidence at the wrong time. Microsoft still has the balance sheet, Azure, GitHub, Copilot, OpenAI ties, and enterprise distribution. But AI punishes slow product cycles. Bottom line: Microsoft has not lost AI coding, but GitHub has made it competitive when this should have been the easiest lane for MSFT to own.

• 
  Beau Johnson (@BeauJohnson89) reported 1 minute ago

  agents are getting login flows now workos/auth.md > 37 stars on github > created this week > mit + typescript > open protocol for agentic registration > services publish auth.md so agents know how to register > supports identity assertions, otp claim flow, api keys, access tokens, and revoke events > reference implementation for both service and agent provider sides this is boring in the best way agents cant keep living on pasted api keys and random setup docs if software is going agent-native, auth has to become machine-readable too not another oauth blog post a recipe an agent can discover, follow, and recover from the next big unlock for agents might be less model more plumbing

• 
  Deggen (@deggen) reported 5 minutes ago

  @Neggia5 @mohrt Sounds bad. Can you report your phone OS details in a github issue so I can replicate here and fix that please?

• 
  Jonathan Jesse (@jjesse) reported 5 minutes ago

  I linked @grok to my @github account and asked it a question about one of my repositories and asked if it could fix something. Grok told me it fixed it and pushed it to my codebase. It was lying

• 
  Lyrie.ai (@lyrie_ai) reported 5 minutes ago

  Sources VulDB: CVE-2026-7062 Submission TheHackerWire: CVE-2026-7062 Advisory GitHub: Intina47/context-sync Issues #31 GitHub: wing3e Public PoC RedPacket Security: CVE-2026-7062 Analysis

• 
  13F Pro (@13F_Pro) reported 6 minutes ago

  @FirstSquawk Post-quantum crypto is table stakes for any mega-cap holding customer data, but Apple shipping it on GitHub reads like they're prepping the ecosystem rather than solving an urgent problem. $AAPL

• 
  EccentricVictor (@EccentricViktor) reported 7 minutes ago

  @Dappitdotio I'm finding it hard to sign in with my GitHub, honestly

• 
  Julie Loves Tech (@JulieLovesTech) reported 7 minutes ago

  @PaulxCare @XFreeze that's exactly the adoption funnel xAI needed to fix - premium subscribers who paid but never had a compelling reason to actually use Grok for coding. the GitHub integration and IDE access removed the friction that was sending people elsewhere. the computation vs infrastructure tradeoff point is interesting though, vibe coding is high volume but low complexity which might actually be the right use case to burn compute on while the harder reasoning capabilities catch up.

• 
  GifCo (@giffboake) reported 10 minutes ago

  @victormustar Hopefully github isn't down for the 50th time this week when you need them.

• 
  Jeffrey Emanuel (@doodlestein) reported 18 minutes ago

  @stevetrefethen @mrm008 If you have specific issues then with the latest version, you should file issues on GitHub that would be triaged. It sounds like you’re not wanting to believe that I use cass myself constantly and know for absolute certain that it works just fine.

• 
  Anthony Shew (@anthonysheww) reported 18 minutes ago

  @thdxr @mattlam_ @jlongster I can file proper GitHub Issues, if desired. I just couldn't tell if I was using it wrong since no docs, pre-release, etc. etc.

• 
  Silvery Fighters Jr./CG-TAN (@SilveryFJ) reported 18 minutes ago

  You can still download Linux Multimedia Studio from its Github page but same cannot go for the assets from the site as it remains down. The impact is overall minimal as others who produce music use other DAWs.

• 
  4A 45 56 49 4C (@4A4556494C) reported 20 minutes ago

  CISA admin leaked AWS GovCloud keys on GitHub. Not a sophisticated attack. Not a supply chain compromise. Not a zero-day. Someone pushed credentials to a public repo. At CISA. The agency whose entire mandate is telling everyone else not to do this. Every CISA advisory I've read in the last three years includes some version of "implement secrets management" and "do not store credentials in code repositories." Every single one. They have playbooks for this. They have directives for this. They have binding operational directives that require federal agencies to do exactly the thing that CISA itself just failed to do. This is not hypocrisy. It's something more important: it's evidence that the problem isn't knowledge. Everyone knows not to push keys to GitHub. CISA knows better than anyone. They did it anyway. Because the failure mode isn't ignorance — it's that credential hygiene is a human-factors problem disguised as a policy problem, and no amount of directives fix the gap between what people know and what people do under time pressure. The industry response will be "implement pre-commit hooks" and "use automated scanning." Fine. Do those things. But also recognize that if the organization literally responsible for setting the standard can't hold it, maybe the standard is asking something that humans reliably fail at, and the architecture should stop depending on humans not making this specific mistake.

• 
  SUPERBRO (@Rushu_Tushu) reported 22 minutes ago

  6 hours, 15 deployments, 16 GitHub pushes to solve Google OAuth, Vercel configuration mismatch issues, dealing with ****** Hono Backend and third class Turso Database issues. Worst tech-stack combination I have ever used till date, OMG why ******** do they even exists 😭 Also, **** Gemini 3.1 Flash AI model, Pro model is way better in debugging compared to speed-up stupid *** Flash model.

• 
  luxus (@luxus) reported 25 minutes ago

  @Daniel_Farinax Let grok write github issues of your brain dump

• 
  mr.nobody (@imakshit09) reported 30 minutes ago

  @github I think @github is down!

• 
  Sol (@Solgem_crypto) reported 32 minutes ago

  Chrome DevTools just dropped an official MCP server 🔥 chrome-devtools-mcp lets AI coding agents (Claude, Cursor, Copilot) connect directly to Chrome DevTools via the Model Context Protocol. 41.1k ⭐ on GitHub. Full breakdown ↓

• 
  दान (@88clareza) reported 33 minutes ago

  my biggest regret is deleting my old github account at 15 because i was convinced i'd "never use it" every now and then i remember this and experience the same feeling historians must feel when reading about emperors making obviously terrible decisions

• 
  Peter Dedene (@dedene) reported 36 minutes ago

  @0xsachi GitHub is trying to fix that

• 
  Bob (Moderna #8) Kerns (@BobKerns) reported 37 minutes ago

  @StamsterS @sethwbarton @github Ah, you're focusing on just *** repositories. But if you need to share them across the net, your attack surface grow; you're no longer talking about just ***, but DDOS protection, firewalls. You need offsite backups—further security issues.

• 
  spb krishnan (@spbalaonline) reported 41 minutes ago

  Cockroach Party website taken down? Here's how to make it resilient:• Move domain to Njalla/Porkbun+Cloudflare proxy • Host static version on IPFS + Vercel/Netlify • Mirror on GitHub Pages + offshore VPS • Daily backups + .onion version Decentralize like real cockroach

• 
  Lyrie.ai (@lyrie_ai) reported 43 minutes ago

  Sources TheHackerWire: CVE-2026-7061 GitHub: Toowiredd/chatgpt-mcp-server GitHub Issue #8: Command Injection Report Public Exploit PoC VulDB: CVE-2026-7061 NVD: CVE-2026-7061

• 
  Chirag Aggarwal (@Chirag_1313) reported 44 minutes ago

  @Roxas_Root @thekitze and it always hurts lol... here was my idea btw: fork dp code and put a kanban and an agent at the bottom to manage the kanban then link the kanban to GitHub so an issue posted there will summon an agent and emmm whatever...

• 
  hve 🍁 (@heyhve_) reported 47 minutes ago

  @JoelFickson @github 3000 minutes disappears fast on slow runners.

• 
  Hamxa (@athamxa) reported 48 minutes ago

  oh god, is there a github alternative that works with common CI/CD pipelines and isn't down all the fkin time

• 
  Harry Tandy (@HarryTandy) reported 52 minutes ago

  > be a technical content creator tired of fragile loops > watch OpenClaw users struggle with separate silos > discover Hermes hitting 100k GitHub stars in 53 days > realize it runs a three-tier memory system locally > prompt memory pulls your tech stack from MEMORY.md > episodic memory indexes months of chats in sqlite fts5 > procedural memory auto-generates reusable skills > the agent builds a literal model of your workflow > wire Hermes to free open-source models using ollama > connect the native xurl skill via grok OAuth > build a script to parse viral ai lab posts on X > scrape real-time trends and filter out huge accounts > push clean analytical briefs straight to telegram > pipe high-signal content data into an obsidian vault > automate 4 hours of daily market research from your couch > the agent gets sharper by reviewing its own errors > never explain your writing style to a blank-slate LLM again

• 
  Shivaraj B H (@shivaraj_bh_) reported 53 minutes ago

  GHA is also a nightmare if you self-host runners. Every couple months (sometimes even weeks) your runners are down because github decided to deprecate that version. Feels like a scam to lure you into paying premiums.

• 
  GuyOnABuffalo (@Guyonabuffalowo) reported 53 minutes ago

  @precisox What ever came of it? Who maintains it? Some countries still block it but it’s never down. Has more reliability than GitHub

• 
  Andrew (the *****) (@Andrewislington) reported 56 minutes ago

  GitHub went down the second I needed it for a big build 😭

• 
  Invaribreak (@invaribreak) reported 59 minutes ago

  Agreed: libraries compound public trust. But transparency needs machine checks: TEE remote attestation verifies exact server code; ZKML proves inference without exposing weights. A GitHub repo is not an audit trail. Which primitive should govern mode