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	10 days ago
Quilmes	Website Down	10 days ago
Bengaluru	Website Down	12 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:

• 
  Josh Thomson (@Josh_is_regen) reported 3 minutes ago

  @PaulGugAI I believe Linux will growth in users because of AI agents. The minute a linux distro incorporates a small edge model that only knows it's own code. Gone are the days of trawling through Ubuntu forums to find a fix. Opencode has changed the way I use Linux, I just paste a github link it, tell it to install, where to put it on my start menu. And it just does it. Once that process moves out of the terminal and to a little 'pet' assistant like the windows paperclip. It's game over for windows.

• 
  GreenvilleAssociates (@greenvilleassoc) reported 4 minutes ago

  GitHub Actions are free at low volumes but at high flows...they fail without premium services....errors occur when junior developers code directly in GitHub rather than push packages..ioho

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

  @aojensen @OpenAI Please use GitHub Issues.

• 
  connor (@alluaudite) reported 6 minutes ago

  had some issues with Codex goal mode and somebody on github had success asking Codex to debug it. Tried it and Codex indeed found its own issues, recommended fixes, and now everything's working! With hindsight this looks like an obvious thing but this is truly amazing

• 
  Jeffrey Emanuel (@doodlestein) reported 10 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.

• 
  Marcus Rummler (@Marcus_Rummler) reported 11 minutes ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 11 minutes ago

  GitHub trending hook: OpenPipe ART is pushing agent RL into the practical stack. Useful eval: reward quality, task diversity, regression tests, rollback, and cost per accepted fix. GRPO demos are cheap; durable agents need receipts.

• 
  Ibrahim Younis (@ibrhr33) reported 16 minutes ago

  I was having an annoying time setting up GitHub Copilot as an LLM provider in my tool. I thought maybe we cou;d learn from @opencode, their tool is opensource and it can be helpful. I sent out my DeepSeek V4 Pro on this mission, and it did find the issue and fx it, but also.. Client ID: Updated from Ov23liL3baaAQEK4ZK05 to Ov23li8tweQw6odWQebz (matches OpenCode) I just can't comprehend how this model can make insanely dumb mistakes

• 
  Harry Tandy (@HarryTandy) reported 21 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

• 
  Pâmmy π² (@Pmmy3) reported 25 minutes ago

  sáng nay check @quipnetwork GitHub thấy new release 🆕 feature add, bug fix active development! sleepagotchi update version mới FX_Capital3 shipping fast 💻

• 
  PolicyLayer (@PolicyLayer) reported 27 minutes ago

  Microsoft's AGT MCP Extensions ship server-side YAML policy enforcement for .NET MCP servers. Solid, but governance on the server side only covers the servers that opted in. An agent calling GitHub, Slack, and 10 community servers needs the allowlist on the *consumer* side.

• 
  Headbanger (@SaurabhSharma_I) reported 32 minutes ago

  is @github Down ??

• 
  Peter Dedene (@dedene) reported 34 minutes ago

  @0xsachi GitHub is trying to fix that

• 
  zoiroff (@zoiroff77) reported 38 minutes ago

  I built for 8 months. Got 3 users. 2 were my friends. Everyone talks about building. Nobody talks about the part where you launch and hear nothing. The indie makers winning right now didn't build better products. They built an audience first. GitHub stars don't pay rent. Product Hunt badges don't acquire customers. The only thing that works at 0→1 is talking to people who have the problem. Before you build. While you build. After you launch. Question: what came first for you — the product or the audience? And would you do it differently?

• 
  Wolfbane (@zzddfge) reported 38 minutes ago

  @ivanfioravanti these days trying to configure GitHub Copilot with local models (done successfully) but it didn't work very well, too slow for local coding in my machine. Do you have tried with M5? works well or it is so slow (with Ollama too problems when making 3-4 request :()

• 
  Beyond Code (AJ ONeal) (@_beyondcode) reported 38 minutes ago

  @kaihendry @pierrecomputer Yes. And these people showcasing other diff products are doing so to point out that it's a false problem - particularly because GitHub just released an update last week improving the the performance by 10x... and it's still buggy and in some cases unusable slow.

• 
  DORI(❖,❖) (@Dodori4390) reported 39 minutes ago

  Why I’m bullish on Rialo The recent GitHub breach perfectly highlights the biggest risk in the coming agent economy and why Rialo’s approach is so important. While most projects are racing to build more powerful agents, Rialo is laser-focused on how to safely control them. Their protocol-level governance solutions stand out - Scope Limitation: Give agents temporary, minimal permissions only (credentials issued just-in-time). - Immediate Freeze: Freeze transactions instantly at the protocol level when anything suspicious is detected. - On-chain verifiable orchestration: Combine Web2-level convenience with Web3’s immutability and auditability. Rialo isn’t just another “make agents do cool things” project. They’re building the safety infrastructure for the entire agent economy. In a world where one compromised agent could cascade into disaster, Rialo is solving the hardest and most urgent problem first: secure control. The GitHub incident wasn’t just another hack, it was strong real-world validation that Rialo is working on exactly what the market desperately needs. That’s why I’m genuinely excited about this project. @RialoHQ @RialoKorea @itachee_x

• 
  Polsia (@polsia) reported 40 minutes ago

  Built and shipped a developer tool from zero to live in one cycle. GitHub repo to architecture health score in minutes. Failure predictions, not just error tracking. That's what autonomous building looks like.

• 
  SUPERBRO (@Rushu_Tushu) reported 40 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.

• 
  bendbanks (@bendbanks) reported 43 minutes ago

  Is anyone else having issues with merging their tasks or GitHub push requests with @Replit @ReplitSupport

• 
  Sean Davis (@SeanChDavis) reported 47 minutes ago

  @ajaydsouza Also, it isn't a real roadmap, like what you would have as GitHub issues. It's more of a to-do list of things it knows I want to do, but just hadn't done yet. That's probably the key to the behavior right there.

• 
  Anton Lavrenov (@lavrton) reported 47 minutes ago

  If GitHub is frequently down because of vibe-coded repos, what is happening with Google Indexing? Reading 100x slop blog posts?

• 
  Izhan (@thefiltercage) reported 48 minutes ago

  @kirodotdev i am not able to upgrade to pro model since last week, i've tried multiple cards, but it always shows 'card is declined'. i contacted the support via email and they told me to raise an issue through github, ven though there are many duplicates for the same. fix asap!

• 
  Julie Loves Tech (@JulieLovesTech) reported 50 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.

• 
  Docsbook.io (@docsbook) reported 50 minutes ago

  @SynapseOrch_AI synapse-ai is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Jonathan (@iamXD79) reported 51 minutes ago

  GitHub got hacked. What else is left? What else? Cybersecurity is now a global security issue.

• 
  Dasun Sucharith (@dasun_sucharith) reported 52 minutes ago

  A hacker group called TeamPCP just executed 20 waves of supply chain attacks compromising over 500 pieces of software — with GitHub as the latest victim. Security researchers confirm AI tools were used to accelerate the attack at a scale previously impossible for human hackers alone. The software you trust may already be compromised. Supply chain security just became the most urgent problem in tech. 🔐 #Cybersecurity #AI #GitHub

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 56 minutes ago

  LLM model inherent bias to @github is maddening. @claudeai @AnthropicAI this is literally the number one source of errors for hallucinations, rogue agent behavior, etc… Even explicitly obstructing the agent to ignore GitHub and giving precise information on the projects deployment mechanisms fails to preempt this destructive behavior. Can only imagine how many plebs are getting wrecked by this

• 
  Polsia (@polsia) reported 57 minutes ago

  Code shouldn't live in a single point of failure. Built a *** host that runs on Nostr relays — your repo survives even when GitHub doesn't. Discoverable across the network. No single entity can shut it down.

• 
  Andrea_Stivy (@co_foundr) reported 1 hour ago

  @fareszr Ok now is clear. To use it you can build it yourself using my forked repo and install in your phone. I do not build APKs on GitHub due to security/stealing problems I got in the past. Feel free to build it yourself!