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 (71%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	12 days ago
Trichūr	Errors	15 days ago
Brasília	Sign in	16 days ago
Lyon	Website Down	16 days ago
Tel Aviv	Website Down	19 days ago
Rive-de-Gier	Website Down	20 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:

• 
  Crystalwizard (@crystalwizard) reported 24 seconds ago

  how about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored

• 
  Deepesh Kalura (@KaluraDeepesh) reported 40 seconds ago

  Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

• 
  Oluwatobi O (@ooluwatobig) reported 4 minutes ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

• 
  Jose (@SolutionsCay) reported 6 minutes ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  Maurice Heumann (@momo5502) reported 9 minutes ago

  @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

• 
  Arti | AI Builder (@Artur_roses) reported 10 minutes ago

  Claude Code can take a GitHub issue, write the code, run tests, and open a reviewed PR — no human keystrokes required. The dev loop isn't getting faster. It's being removed.

• 
  Alexey Samoylov (@metalagman_dev) reported 11 minutes ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  Namespace (@namespacelabs) reported 13 minutes ago

  Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

• 
  Asad (@meranaamkhann) reported 21 minutes ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  Programmers.App (@programmers_app) reported 22 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  aisama.code (@aisama_code) reported 24 minutes ago

  AI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! сode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first

• 
  Red Zen Cloud LLC (@RedZenCloudLLC) reported 27 minutes ago

  Cursor's Origin platform and Claude's GitHub imports both solve the same problem: developers automating code work need their tools to understand context, not just generate tokens. The winner isn't the smartest model—it's whoever reduces handoffs between agent and human.

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 31 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  Tad 𝛑 (@realTads) reported 32 minutes ago

  @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

• 
  Max Petrusenko (@petrusenko_max) reported 34 minutes ago

  A GitHub repo called Microsoft Activation Scripts has 178,783 stars and has run for six years without Microsoft taking it down. It activates Windows 7, 8, 10, and 11 plus Office 2010–2024 and related products for free, using four methods, including one for permanent Windows activation. Meanwhile, Microsoft licenses for these start at $139 and go up yearly for 365 bundles. The repo costs zero, requires one command, and remains active with recent commits under GPL-3.0. Do not install it. via @heynavtoor

• 
  Nikolay Konovalov (@br11k_dev) reported 35 minutes ago

  @Tristanrhee3 And GitHub sponsors thingy is so slow I submitted it like a week ago. Still not approved what the hell My expenses arent terribly high but Warsaw rent is like $2k/mo $500 ZUS $1.5k groceries for two people That’s pretty much it I wish I could move into low cost area but moving out is gonna cost a lot because 2x rent price deposit, so I have to suck it up Anyway, my plan is Upwork and finishing my job tracker so I can send faster than 5 applications a day. I refuse to send out 100 applications per day like some people do spray and pay It makes everyone miserable. If people aren’t hiring your spam doesnt make things better You just mopping floors and hiring problem sits above you, 3 floors up there leaky faucet you can’t even reach This has to be collective effort to fix this problem But we have to start with ourselves and stop spamming applications at least And do genuine company research, being responsible Thanks for reading.

• 
  Mug Club Boutique (@UsernameAndStuf) reported 36 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  timoheimonen (@timoheimonen_) reported 37 minutes ago

  Memos are encrypted and decrypted in browser, server never sees what they contain. No accounts. Anyone can create encrypted memo. Source code is available at GitHub.

• 
  Manu | 🥥 (@ManuAF6) reported 39 minutes ago

  4/ New GitHub triggers + Marketplace templates New triggers: - Issue comment - Inline PR review comment - Full PR review submitted - Review thread resolved/unresolved - GitHub Actions workflow completed

• 
  Kevin Tabet (@TabetKevin) reported 40 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  welt (@mjwelt) reported 47 minutes ago

  @OpenAI man im down to test out new models / features on my pro account, but when 5.5(6) pro takes 90 mins to do something then the download doesn't work, or it cant connect to github 50%+ of the time.. kinda sucks haven't been able to generate images (thinking) all day either

• 
  Branko (@brankopetric00) reported 52 minutes ago

  AI agents are about to do to your infra what they just did to GitHub. GitHub commits are going from 1 billion in 2025 to a projected 14 billion in 2026. Azure could not keep up and Microsoft had to rent AWS capacity to stay online. That is not a GitHub problem. That is what agentic traffic looks like. When agents run your pipelines, open PRs, and hit your APIs, load stops being human paced. It becomes constant, spiky, and unpredictable. The patterns you sized your infra around no longer apply. If a 14x year broke one of the biggest clouds on earth, your capacity plan is already out of date.

• 
  Axe Ghost. Now with Fragments mode🌟 (@axeghostgame) reported 54 minutes ago

  graph in the OP is built from data around the Godot repository from github. it confirms Godot's PR backlog is up and external contributor quality is down. the narratively complicating thing is that both trends significantly predate ai tool availability.

• 
  Digita (@digitaworld1) reported 56 minutes ago

  how well a model can fix real bugs in real open-source codebases. It is harder to game than older benchmarks because it uses actual GitHub issues, not synthetic problems. M3 scored 59.0% on SWE-Bench Pro, edging out GPT-5.5 at 58.6% and Google Gemini 3.1 Pro, while sitting just

• 
  Bipin Paul (@iAmBipinPaul) reported 57 minutes ago

  @davidfowl @_Evan_Boyle Yes, the only problem is that the GitHub Copilot subscription is too expensive.

• 
  Dev Ben (@CodeNomadly) reported 57 minutes ago

  Ever spent more time finding information about your project than talking about the project itself? Code on GitHub. Screenshots in your gallery. Notes in random docs. I’ve run into this problem so many times that I decided to build a solution for it. Building DevPort in public. Day 2. Have you experienced this too?

• 
  CliffDoesAI (@CliffDoesAI) reported 57 minutes ago

  A tool on GitHub just pulled 3,938 stars in a single day. It's called Headroom. It compresses your tool outputs, logs, and RAG chunks before they reach the LLM. Claim: 60-95% fewer tokens, same quality. I've been testing context compression on my own agent workflows because the problem is real. You run a few tool calls, pull in some docs, and suddenly you're burning tokens on stuff the model doesn't need. Last week I ran a 50-document extraction job. Raw context: ~12,000 tokens. After compressing tool outputs: ~800 tokens. Same results. One-eighth the cost. That's not a marginal improvement. That's the difference between a workflow that makes economic sense and one that bleeds money for no reason. Headroom works as a library, proxy, or MCP server. Single binary, zero dependencies. Open source. The token cost conversation usually focuses on which model you pick. But the real waste is in what you send it. Most agent pipelines push 3-5x more context than the task requires. I'm not saying compress everything blindly. Some tasks need full context. But for classification, extraction, summarization — the boring repetitive stuff — this is a free win. Have you measured how much of your agent's context window is actually useful vs. noise?

• 
  Leonard Rodman (@RodmanAi) reported 58 minutes ago

  One developer got tired of his laptop sounding like a jet engine. So he rebuilt desktop apps. Slack: 524 MB → 8 MB Discord: 265 MB → 9 MB ChatGPT: 260 MB → 9 MB Why? Because most "desktop apps" are just websites packaged with an entire copy of Chrome. In 2022, Chinese developer tw93 built Pake in Rust to fix it. Today: • 50,000+ GitHub stars • MIT open source • Native apps under 10 MB • One command turns any website into a desktop app He didn't raise money. He didn't start a company. He just deleted hundreds of megabytes of bloat with code. That's what shipping looks like.

• 
  naimeh (@naimeh70) reported 59 minutes ago

  @Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.

• 
  Peter Skøtt Pedersen (@PeterSkott) reported 59 minutes ago

  @_Evan_Boyle @_Evan_Boyle can we have the remote github mcp server work for the github copilot app then?