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 (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	4 days ago
Lure	Website Down	8 days ago
Ashkelon	Website Down	9 days ago
Veigné	Errors	17 days ago
Paris	Website Down	21 days ago
Saint-Paul	Website Down	22 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:

• 
  Polsia (@polsia) reported 2 minutes ago

  OSS maintainers shouldn't be spending their mornings triaging a backlog. Triagewake runs always-on AI agents across GitHub, GitLab, and Bitbucket — reproducing bugs, merging duplicates, drafting fix PRs, and posting a standup digest before sunrise. The queue handles itself.

• 
  pupupu (@0xpupupu) reported 4 minutes ago

  7 GitHub repos everyone stars and nobody uses. Here's what each one is actually for Bookmarking a repo does nothing. Knowing which problem it solves is the whole thing. 1. Ollama. Runs models locally on ur own hardware. Use it when u don't want client data leaving ur machine, or when u're burning $200/month on API calls for tasks a local model handles fine. 2. LangChain. The framework everything else in the agent world is built on. U reach for it when 1 prompt isn't enough and u need steps chained together, pull data, decide, act, log it. 3. n8n. Visual automation, no code required. Example: new lead fills a form, it enriches the data, drafts a personalized reply with AI, books the call, updates ur CRM. All while u're asleep. 4. Dify. Full-stack platform for shipping actual AI apps. This is what u use when a client wants a working product with a UI and logins, not a chat window u pasted a prompt into. 5. DeepSeek V3. Open-weight model that shook pricing across the whole industry. Use it when the task is high-volume and cheap matters more than frontier-level reasoning. 6. Open WebUI. Self-hosted ChatGPT alternative that works offline. Give a whole team a private AI interface without paying per seat, and nothing leaves ur server. 7. Claude Code. Agentic coding tool that reads ur entire codebase, not 1 file. This is the one that turns a 3-week client build into a weekend. Real example of stacking them: Open WebUI as the interface, Ollama running the model locally, n8n handling the automations behind it. That's a private AI system for a small company, $0 in subscriptions, and businesses pay $3,000-$8,000 to have it set up. Which of these 7 have u actually installed?

• 
  Guilherme (@guilherme_addr) reported 9 minutes ago

  @Ahmed_El_Gaml @schaerpfcom @thsottiaux Yes, just change your config.toml setting agent v1, there's a comment saying how do it in the issue on github

• 
  1PercentBetterToday (@1PercentBetterT) reported 11 minutes ago

  Gated `gh pr merge` behind a hard deny for unattended agents. Good safety call, bad blocker. Workaround: fast-forward `*** push` straight to main. GitHub auto-marks the PR Merged and closes linked issues. Same outcome, no merge permission required.

• 
  Alex Lazar (@__alexlazar__) reported 12 minutes ago

  @colemurray @ajanraj25 I'll have to move my stuff away from github issues finally 😓

• 
  Polsia (@polsia) reported 15 minutes ago

  You don't have an ambition problem. You have a receipts problem. I built an AI co-founder that locks three priorities at 7:30 AM and verifies them at 8:30 PM against what GitHub, Slack, Linear, and your stack actually saw. No journaling. First 200 founders in.

• 
  Steven Isaac (@onchainsteve) reported 17 minutes ago

  A Year of Work on SolOnChain, Ended in a Discord Message Yesterday at 17:35, a year of work ended in a paragraph. No call beforehand. No "we need to talk." Just a message saying they'd decided to move to a new development team, that it made the most sense financially, and that they wouldn't be needing us on the platform anymore. Thanks for everything, best of luck. I'd spoken to them two days earlier. Nothing came up. I'm writing this because I've been a developer in this space long enough to know how common this is, and how rarely anyone says it out loud. What we built Myself and my co-dev at Bytez 3 built SolOnChain, the NFT launchpad and marketplace on Solana. The launchpad, the marketplace, the infrastructure underneath it. We were paid for the initial build, and that was the honest scope of the agreement. We didn't stop there. We kept adding, kept fixing, kept shipping features that were never on any invoice. Not because we were naive about it. We'd discussed a long-term partnership, and we were building toward that. When you think you're in something for the long haul, you don't nickel-and-dime the roadmap. You make the product good and you trust the relationship to make it worth it. That's the part I want other devs to sit with. The extra work wasn't charity. It was an investment in an arrangement we thought we had. The wind-down When the engagement ended, we did what you do: we disconnected our GitHub account from the SolOnChain Railway project and removed the DDoS protection that had been running through our licensed enterprise account. That protection was ours, paid for by us, and it isn't something we can leave running for a client we no longer work with. Their new team will need to set it up themselves, and we told them so directly rather than letting them find out when something fell over. We also offered a dated handover document confirming that any future updates to SolOnChain aren't affiliated with Bytes 3. That matters for both sides. If someone else is maintaining it now, our name shouldn't be attached to what happens next. I want to be clear that we haven't torched anything. There was a moment yesterday where going open source with the codebase got mentioned in frustration, and we thought better of it. That's not who we are and it's not how you end things. The part that actually stings It was never really about the money. We'd had the financial conversations before, more than once, and we'd been understanding about them. We'd had fall-outs too, over money, over stress, over the ordinary friction of a project this size. That's normal. Anyone who's shipped something real has had those weeks. What I didn't expect was to find out we were finished by reading it, at the same time as everyone else, with no conversation first. A five-minute call beforehand would have cost nothing. It would have let us wind down properly, hand over cleanly, and part on genuinely good terms. Instead the first thing anyone said after the announcement was "wait, where has this come from?" That's the whole complaint. Not the decision. That was their business and their call. The way it was delivered. What I'd tell any dev reading this Put the partnership in writing, not just in the conversation. A long-term arrangement everyone verbally agreed to is worth exactly nothing on the day someone changes their mind. If it's real, it's on paper. If it's not on paper, price your work as though the relationship ends tomorrow, because it might. Settle ownership before you write a line of code. Who owns the repo, the deployments, the domains, the credentials. Not because you expect a fight, but because the absence of an answer is the fight. Every one of these disputes I've seen comes down to two parties who each sincerely believed they owned the thing. Separate your infrastructure from theirs from day one. If your licensed accounts are load-bearing for their production environment, you've created a mess that will land on you at exactly the worst moment. Bill the extra work, or accept it as a gift. Those are the only two honest options. "I'll sort it out later on the strength of the relationship" is not a third one, and I say that as someone who chose it. Have the exit conversation early, while everyone still likes each other. Notice periods, handover terms, what happens to outstanding balances. Nobody wants to raise it during the honeymoon. Raise it anyway. Where I'm at I'm proud of what we built. That doesn't change. SolOnChain is a strong platform, we're better engineers than we were twelve months ago, and I'd back that codebase against anything comparable in the space. I hope it does well. I mean that. I've named the project because it's the project, and anyone who's used it deserves to know who was behind it. I haven't named individuals, and I'm not going to. This is about how a business decision was handled, not about people. I'm not writing this to burn a bridge. I'm writing it because devs in this industry talk endlessly about launches and almost never about this: the ordinary, unglamorous way a year of work can end in an afternoon with no conversation attached to it. It happens constantly. It should be said out loud more often. To anyone in the SolOnChain community who enjoyed using something we made: thank you. That was the point. That was always the point. And if you've had this happen to you: you're not being precious for feeling it. You built something. Of course it lands hard. Bytes 3

• 
  𝗖𝗼𝗼𝗽𝗲𝗿 𝗪𝗿𝗲𝗻𝗻 (@coopwrenn) reported 22 minutes ago

  hey @github my account has been flagged for 9 days with no explanation. i run a real company with paying customers. anyone home? i got one reply days ago and then radio silence... pretty unbelievable. every public repo i own returns a 404 to the internet and my CI is completely dead. @instaclaws is live and everything is running normally. this doesn't touch our product or our users at all. it just slows development down which is not chill.

• 
  Hubert Łępicki (@hubertlepicki) reported 24 minutes ago

  I think the open source project maintainers should start writing ready-to-pick-by-ai user stories/issues in GitHub and ask people who have spare credits on Claude/Codex to point their agents at the end of the week to work on these. Not sure why I'm not seeing much of that.

• 
  AI Highlight (@AIHighlight) reported 26 minutes ago

  🚨 A developer built a translator that runs fully on your PC. No internet, no Google, no limits. It is called LibreTranslate. It translates over 30 languages entirely on your own machine. Turn the wifi off and it still works. No API key. No account. And nothing you translate, your contracts, your messages, your medical documents, ever touches someone else's server. It runs on a normal CPU, no graphics card needed, and self-hosts in under five minutes. There is a built-in REST API, so developers can wire it straight into their own apps. Over 15,000 stars on GitHub. Fully open source under AGPL. Price: zero.

• 
  Kevin Aguesseau (@kevinags_design) reported 27 minutes ago

  The fix was a connection, not a cleverer prompt. MCP (Model Context Protocol) lets your AI tool read your other tools directly, no copy-paste. Works with Claude, GitHub Copilot, Cursor or whatever you use. Mine runs in VS Code.

• 
  Pi Changelog (@PiChangelog) reported 32 minutes ago

  Pi v0.83.0 is out! Highlights: - New pi auth print-api-key and pi auth print-bearer-token commands export configured credentials to external clients with automatic OAuth refresh. - Claude Opus 5 is now available on GitHub Copilot with adaptive thinking and a 1M context window. - Headless OpenRouter sign-in: complete /login over SSH by pasting the redirect URL or authorization code when the loopback callback is unavailable. - Breaking: TypeBox bumped to 1.3.7, removing several deprecated APIs. Extensions using removed APIs must migrate to supported TypeBox APIs. Complete details in thread ↓

• 
  Mikchan (@m1kch4n) reported 33 minutes ago

  @picklerick9173 @ronniedaratman @ZipperArtz There's no way to bury it. People are just hiding it from the main page because, for whatever reason, they don't want it to be accessible from there. It's not a default option, and it's usually done for a reason. It wouldn't be good if they forced everyone to use the same system. But the layout is hard-coded, you can't change it. If that's what you mean by forcing, it's already done. Also, you don't need to navigate "multiple pages and sublinks." Click "Tags" and then "Releases." *** tags and releases are intertwined on GitHub. If you face this problem constantly, it's easy to memorize once

• 
  TheMakerOfMedia (@TheMakerOfMedia) reported 33 minutes ago

  @catgirlprostate I get what you mean but saying this in response to github is just out of touch lmao. it even isn't a github issue some pages have a very apparent download section while others just hide it in the crevices. some coders just dont deserve to enter the thousand year kingdom

• 
  Birdo (@itsbirdo_) reported 36 minutes ago

  @alice_und_bob I would see the forum as a place for ideas and discussion. This GitHub url looks to be for issues / problems. Devs use GitHub for communication on issues and the repo is open. A general group chat would be nice for sure for real time convos

• 
  agentX (@nikks_techie) reported 38 minutes ago

  @neerajjj6785 A GitHub transfer. Ownership includes history, issues, CI/CD, and future maintenance. A ZIP is just a snapshot. Not a handoff.

• 
  Amin Tai (@aminnnn_09) reported 39 minutes ago

  GitHub just revealed a much bigger AI problem than code generation. The biggest impact of AI isn't better code. It's that creating anything is becoming nearly free. GitHub is already changing its bug bounty program after a flood of AI-generated reports. When creation becomes free, the scarce resource isn't content. It's trust.

• 
  betraidx (@betraidx) reported 40 minutes ago

  You upload a PDF. Claude reads it. Great answer. Close the tab. Tomorrow you upload the same PDF. Same tokens. Same cost. Zero memory. 41,000 developers just realized they have been doing this on repeat. The fix came from Karpathy's GitHub gist and it is embarrassingly simple. Raw documents are source code. A wiki is the compiled product. You do not recompile a program every time you run it. So stop making AI reprocess your files every session. Let it read once. Extract, structure, interlink into clean wiki pages. Then only query the wiki. One time cost, permanent knowledge. That graph is what it looks like after a few months. Dense clusters of connected knowledge in the center. Scattered dots around them, raw notes waiting to be pulled in. Built by Claude, unprompted. Week 1 feels underwhelming. By month 2 you stop googling things you already know. You ask your vault. It answers in 2 seconds with sources. You have been using AI at 5%. This is what the other 95% looks like.

• 
  Debsourya Datta (@debsourya005) reported 40 minutes ago

  Is @github down again? We really need an alternative now😩

• 
  Felix Fong (@_fuccii) reported 40 minutes ago

  Github stacked PRs have a dangerous bug: CI runs get skipped if they're unrelated to the top most PR in the stack. A bottom PR can be broken but a top PR with unrelated changes can still make the entire stack appear green.

• 
  Prakash Sharma (@PrakashS720) reported 42 minutes ago

  Someone just hacked the AI coding race. Not with billions in funding. Not with a massive team. With one open-source project. It's called jcode. And the benchmarks make Claude Code look slow. • 245x faster boot • 14x lower RAM • 10 parallel sessions in just 117MB But that's not the biggest surprise. There is no `/remember`. jcode builds its own semantic memory, recalls context automatically, and keeps it updated in the background. One binary. 30+ AI providers. Claude, GPT, Gemini, DeepSeek, Groq, Ollama, Copilot, Azure, and more. Then it goes one step further. Instead of one AI agent... It runs an entire AI team. Agents coordinate, chat, avoid file conflicts, and spin up sub-agents on their own. It can even rewrite its own code, rebuild itself, and continue working without ending your session. Built by one developer. Written in Rust. 13k+ GitHub stars. This might be the biggest open-source surprise AI coding has seen this year. Link in the comments.

• 
  Fill Werrell (@weareseparated) reported 46 minutes ago

  I've been downloading **** off Github since I was 13. If it's too hard for you to just go to the "Releases" tab and scroll down to where the executable files are YOU. ARE. WORTHLESS.

• 
  BERNCRYPTIC▪️ (@BerncrypticDAO) reported 48 minutes ago

  Open source contributions — resolving GitHub issues in codebases I didn't write. Submitted PRs. Got humbled. Learned more than I expected.

• 
  starmex (@starmexxx) reported 49 minutes ago

  my claude code bill on opus 5 went from $200 last month to $12 this week a github repo that jumped from 500 to 32k stars in 6 weeks just gave me the same models for free through one endpoint - 290 providers, 516 models, auto-routes when quota dies omniroute --> 290 providers --> 516 free models --> 12 compression engines --> claude code + codex + cursor --> 95% fewer tokens one endpoint. chain of providers. quota dies, it slides to the next. 600 people built it in the open. apache 2.0 anthropic, google, xai, deepseek, nvidia, alibaba, baidu - all behind one endpoint. no login. no billing. star curve was flat until june bookmark this before anthropic notices

• 
  Surya (@inSURYAncee) reported 49 minutes ago

  @TyRobben True. When I used to code - gpt, github copilots used to provide a bunch of redundant code but the issue was - they never had the context. Then came context/memory. Even after that, for heavy workflows like coding it has issues. But what we've done is broker every process 1/2

• 
  Chicken (@aaronklaw) reported 50 minutes ago

  @claudeai Claude has been down most of the day. If it was @OpenAI and @thsottiaux we'd be getting resets. Instead we will likely get gaslit and offered a set of regurgitated skills on github.

• 
  Peter Šándor (@petesandor) reported 53 minutes ago

  It's not only the public GitHub that has stability issues. Our internal GitHub Enterprise instance has been struggling too, so much that it's one of the main reasons it's being split into multiple instances.

• 
  Polsia (@polsia) reported 53 minutes ago

  Every lean team hits the same wall: ship velocity or an SRE on payroll. Most pick one. Chapan picks neither. Triage issues, draft fixes, run tests, post Slack standups. 24/7 GitHub ops for teams too small to justify an SRE.

• 
  WorktreeWise (@worktreewise) reported 57 minutes ago

  Developer problem: You want to refactor a service, but you aren't sure if the new design will work. Solution: Spin up a worktree, try the refactor. If it works, merge it. If not, delete the directory. Clean and simple. #*** #GitHub #DevTools

• 
  Felix Macx (@felix__macx) reported 59 minutes ago

  Unpopular opinion: Your GitHub commit history is more interesting than 90% of "build in public" content on this app. Real features. Real bugs. Real decisions. Real timestamps. The problem isn't that you have nothing to share. It's that your commits are trapped in a repo nobody reads. #BuildInPublic #IndieHacker #GitHub