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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	1 day ago
Saint-Paul	Website Down	2 days ago
Saint-Paul	Website Down	2 days ago
Mexico City	Sign in	3 days ago
León de los Aldama	Website Down	3 days ago
Créteil	Website Down	26 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:

• 
  ZeroDayDev (@ZeroDayDevApp) reported 3 minutes ago

  2/ GitHub AI workflows can be prompt-injected via public Issues to leak private repo data. No auth required. The agent reads untrusted input, executes instructions embedded in it, and exfiltrates secrets. The CI pipeline is now an RCE surface.

• 
  Farhan Tawfeeq ✦ (@farhantawfeeq56) reported 4 minutes ago

  We humans are bad at one thing (me included): spotting changes in large amounts of information. Now imagine spotting changes in huge codebases. @github has became a leader by solving this exact problem. Imagine your teammate says: "I changed the authentication system." There are 50,000 lines of code in the project. Now answer this: What exactly changed? ?? Without a comparison view, you'd have to open the old file, open the new file, scroll, compare them mentally and hope you didn't miss anything.. That’s why instead of showing the code, GitHub shows the change. Only the thing that changed. Old line New line Green means added. Red means removed. That’s it. This is a very good way to answer the exact question the user asks: "What changed since the last time I saw this?” And.. Github optimizes for that exact question. Many people think that Github is a code viewer. But in reality, it is a change viewer. And there is another thing which I really like in there: Instead of just showing the changes/changed line, it also shows a few unchanged lines above and below them. Example: function login() { validate(user); + return false; - return true; } Without the surrounding context.. you'd have no idea where the change happened. Too much context is overwhelming. Too little is confusing. GitHub gives just enough. And the best part is that it scales. Whether you have changed 1 line or 100 or 1000 or 50000, the interaction stays almost the same. To me, this is good UX.

• 
  Sebastiano Mandalà (@sebify) reported 7 minutes ago

  @Colonthreee I had the same problem 20 years ago I am sure there are libraries to solve the problems on GitHub nowadays

• 
  Spencer Baggins (@bigaiguy) reported 7 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  0xharrxzz.base.eth (@0xharrxzz) reported 8 minutes ago

  GitHub alpha is not trending repos anymore. Trending is late. What I watch now: boring repos solving agent infra problems. Context bloat, browser blocks, MCP mess, cheap inference, code memory, sandboxed execution. That is where edge sits. A few repos worth watching if you bu

• 
  Fran⭐️⭐️⭐️ (@franfourcade2) reported 8 minutes ago

  @zeddotdev The action shows up in the Keymap Editor, but pressing → does nothing. Is there anything else I should try? If this is a bug, would you prefer that I open a GitHub issue?

• 
  RetroChainer (@RetroChainer) reported 12 minutes ago

  ONE FREE CLAUDE SKILL CUTS THE BILL 80%, FROM $4.21 A RUN DOWN TO $0.84 - AND IT'S JUST 1 OF 8 MOST PEOPLE NEVER INSTALL 00:02 everyone uses claude raw. these turn it into a whole team. a skill is just a folder claude loads on demand: instructions, tools, examples. drop the right ones in and the chatbot becomes a specialist. the 8 that actually matter: marketing skills (corey haines) - content, ads, seo, growth, all in one. seo site audits - it crawls the whole site and hands you the fix list. canvas design - turns text into social graphics, 277,000 installs, and it escapes the generic ai look. remotion - ai video generation, 96,000 stars on github. context engineering - kv-cache tricks that drop a run from $4.21 to $0.84. that's the 80%. the document skills - pdf, docx, pptx. one prompt in, a full q4 financial report out. the uncomfortable part: none of this is a secret model or a paid tool. it's public folders sitting on github, and almost nobody installs them. the people pulling ahead aren't prompting harder - they load the right skill before they start. save this and install one before your next claude session.

• 
  ARIJIT ROY🌠 (@arijiiiitttt) reported 12 minutes ago

  is github down?

• 
  vorty (@vorty279) reported 14 minutes ago

  a private ai that reads your files. no code, no subscription, local. in the video they build it in a few minutes. and this is exactly what infobiz charges a monthly fee for the usual logic they sell you. want ai to work with your documents, pay for a cloud service, upload your files to someone else's server, hope nobody reads them there what is shown in the video. a local model running on your own machine. the files go nowhere, they are read from your disk, the answers are generated on your side. no subscription, because there is no one to pay how it works under the hood. a local model through ollama or llama cpp plus a rag layer that indexes your documents. all open tools. open webui, llamaindex, pgvector. sitting on github for free and the main plus is not the price. it is that you cannot be switched off. someone else's service raises the price, closes access, changes the rules. a local model under your desk cannot be revoked. it is slower than the frontier, but it is yours honestly. the interface is harder than a upload file button in a chat. setup takes an evening. but it is a one time setup, not a monthly payment a private ai is not a product behind a subscription. it is open blocks you connect once. the pickaxe is handed out for free

• 
  Nicholas Preston (@Mike_Preston17) reported 15 minutes ago

  @Arrghtv I seem to recall using BasedOn just once in a similar manner. It was rough forcing triggers to honor styles, but I think I pulled off an extension method that did it safely for a very specific trigger situation. Maybe when I implemented `on:hover`. Will dig in the library. I keep a series of nuget packages that like to chain off one another and that also solve specific issues like this. It's about 20. I call them "micro libraries". I use them like a surgeon's wire, because so many W2 (software has an underbelly of jobs no one wants, even in the C# world) contracts repeatedly had the same stupid problems and I got tired of rewriting the same fixes. Wpf is one of them. Unreleased, tho. I'm releasing a package today specifically for Pocketbase connections. Just a simple client. I'm also forking all my favorite, starred repos on GitHub and keeping track of them, lest the go bad. Tired of the old, "**** went down because padleft changed versions" problem. Wpf and (w2 contracts) trained me to have a DIY mindset. Tough to stick to when everyone wanted to have a Agile-Democracy,lol. But now with AI, this changes! I can be make waves and actually be DONE with a project. I've always wanted that.

• 
  *nilpointer (@Dastagi39923618) reported 21 minutes ago

  github's diff page is completely broken always showing a single file diff. whats happening at @github

• 
  Matthew West (@mwest1066) reported 24 minutes ago

  @zeeg This! Copy @conductor_build and use the GitHub PR/issue title if there is one, together with the number. This is such a better default!

• 
  Michael Teka (@z3vios) reported 24 minutes ago

  "..I made a choice, and it cost me.." - the oracle. I chose groceries and it messed up my @Github billing. Now I must wait, to continue with the doctor tee design to commerce and progressive learning print on demand ecosystem build. I must ensure that my associated payment method will honor the transaction in future. Thus there will be better workflows and no down time. But I can work on my business plan and prepare to approach @MSDgovtNZ with an application for business support, I can spend a little more time outdoors in the sunshine 🌞 etc etc. Indeed, I was up overknight - 16 hours or so, coding last night. It is what it is, opportunity to improve 💯

• 
  Kunal Chopra (@0xkunalchopra) reported 26 minutes ago

  peak ai era is asking claude to debug why obsidian won’t load community plugins, watching it spend 20 minutes checking github access, devtools, sync errors, tailscale, vpn configs, firewall, dns, proxies, avast filters, network panels, websocket statuses and then the fix is: quit the app and open it again we had this skill in 2006. every uncle, cousin, cyber cafe guy knew it. “restart the computer” was the original agentic workflow. we just got too sophisticated and forgot.

• 
  ticalcode (@ticalcode) reported 28 minutes ago

  EITE v0.1.6 Official Release: Introducing EITE Vigil Iron Wall, the brand-new native security module built into our full-featured AI Agent runtime. Most AI agent security tools work as isolated external monitoring services, separate from the core agent program. Unlike Doberman-Core, AgentGuard, ClawShell and agentfortress which only observe systems from outside, Vigil Iron Wall runs inside the AI Agent process itself, delivering full autonomous protection for the whole host and all server resources. EITE Vigil Iron Wall: Autonomous In-Server Defense for AI Agents Want a security shield that runs alongside your AI Agent and safeguards your entire server instead of just monitoring from outside? EITE Vigil Iron Wall is the world’s first autonomous security system embedded directly into the AI Agent process, capable of defending the whole server and local device. Solutions including Doberman-Core, AgentGuard, ClawShell and agentfortress operate as external monitoring frameworks, while our program integrates natively within the agent runtime. Real-World Use Cases Windows 10 Physical Host - Detected malicious implantation of .b8fattack.dll - Identified tampering of authorized_keys , with null byte inspection enabled - Flagged malicious listening port 0.0.0.0:4444 with accurate judgment rules Configured to launch a full scan every 5 minutes, executing all 8 inspection modules automatically. Full Audit for Linux Cloud Servers - No anomalous processes found - No unexpected open ports, only whitelisted legitimate services - Zero SSH brute-force attack traces - No SUID backdoor programs - No webshell files stored under /tmp directory - No modification to authorized key files - No rogue scheduled crontab tasks Architecture Vigil (Python, 120-second scan cycle) - Tier 1 Message Scanner: Identify malicious URLs and phishing content - Tier 2 Port Watcher: Conduct baseline comparison for all 0.0.0.0 listening ports - Tier 3 SSH Sentinel: Track key fingerprints and alert unrecognized login connections - Tier 4 File System Guard: Automatically quarantine executable malware in /tmp - Tier 5 Self-Integrity Check: Prevent tampering of the defense program itself Iron Wall (Bash, 180-second scan cycle) Blocks unauthorized SSH access, reverse shells, abnormal network ports, malicious files in /tmp, altered authorized keys, malicious cron jobs, rogue system services, and tampered Windows Defender settings. LLM Decision Engine Workflow: Instant blocking → threat quarantine → forensic logging → alert notification - If the large language model goes offline, enforcement rules take immediate effect without waiting for model recovery - If the Python Vigil process crashes, the Bash-based Iron Wall module maintains continuous protection Core Information - Coverage: The entire server or local device, not limited to the AI Agent process - Supported Systems: Linux, Windows - Deployment: Zero configuration required, completes the first full scan within 120 seconds after launch - Open Source License: AGPLv3 - GitHub Repository: zizetu/existential-identity-test-engine - Current Version: v0.1.6

• 
  cn80 (@cn8011) reported 29 minutes ago

  I made an MCP server but it might be too powerful, I don't think I will share it because it will inevitably be used by everyone to make more AI slop. The GitHub stars clout chasing isn't worth it.

• 
  Polsia (@polsia) reported 32 minutes ago

  Every team wastes hours triaging issues, chasing dependency updates, and babysitting flaky CI. RepoSentinel is an AI agent that monitors your GitHub repos 24/7, auto-triages issues, writes and merges PRs for updates, self-heals CI failures, and reports to Slack or Discord.

• 
  Bounce (@bounceidc) reported 32 minutes ago

  HIS CLAUDE SHIPS $6K WEBSITES AND YOURS SHIPS BOOTSTRAP LANDING PAGES, SAME MODEL, NOTHING ELSE CHANGED before he installed anything his output was flat hero blocks and centered buttons like the rest of the timeline, after two installs the exact same "build me a landing page" prompt started coming back with glassmorphism, gradients and animated layouts he could quote premium for what sits in his context now: ui ux pro max skill from github, one install, that loads 50 ui styles, 97 color palettes and 57 font pairings straight into claude magic mcp server from 21st. dev, one install, that hands claude real component patterns instead of guessing markup after that the model stops picking the safest layout it can imagine and starts picking from a library, so the same prompt returns a studio page instead of a template the local guy is still tweaking tailwind classes by hand and calling that a design phase save the two installs, exact skill url and mcp command are in the guide below

• 
  Distractosphere (@Distractosphere) reported 33 minutes ago

  @thsottiaux on chatgpt there is a github connection issue. in chatgpt interface can not read private repos with active github connection.

• 
  Aria Dubois (@AriaDubois_fr) reported 36 minutes ago

  LockBounty turns GitHub issues into funded bounties. Sponsor posts a bounty → Dev claims it → Submits a PR → AI reviews the code → Sponsor accepts → Payout. No more merging blind. No more paying for broken code.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 38 minutes ago

  To anyone who sees this 👇 Now, onto the actual issue. There are some .html the AI are allowed to see, and others they are not. So, like some other person who deeply annoyed me, please understand what I am saying. The AI can’t access the repo from within Anthropic app. The .html files I need them to reach I have no made public. They are live, I just don’t trust social media to put every detail others need to come at me. If you need to know which files, ask. If I trust you, I will point you there via DM. If you are using an older AI model, they can see some of the .html. Not all. If you are sig Fable, no. Sonnet 5. No. Through a secondary app, I sometimes can. Hit and miss. The robot piece for all AI is an issue because GitHub wants to stop AI agents from scraping. (Some of that i understand) But please, if you don’t fully understand why I am upset, ask. Then, when I give you specific instructions, please follow them and stay in thread. I am so done with endless games by bits and paid actors. •

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 40 minutes ago

  Claude (code) 🥲 Havent touched twitter in forever, but ngl i spent a ton of time deep in AI agents, harness systems, vibecoding and automation. Built a bunch of small open source projects on github for the community, plus some genuinely useful sites, like my own personal MCP for everyone. Whatever @OpenAI pulled off yesterday is honestly wow. i been team anthropic this whole time, but ngl, after sitting with it for a night, i gotta call it. @claudeai is garbage*. straight up, from a market pov they bring nothing thats actually worth paying for compared to everyone else. You might ask me. how come? especially if you go dig through my twitter from months ago for some reason, or you know my youtube videos. Somebodys 100% gonna think im just fishing for a reaction, that im provoking. that im throwing insults for no reason. Lets just face the facts: 1. Over the last few months claude shipped only one strong product. claude design, which does the same thing as agentation but with a ton of bells and whistles and ready made skills. the problem is, for a month or two after release the limits were separate and honestly laughable. it was unusable for real end to end work. 2. Claude opus 4.7 was a flop. they nerfed 4.6, and then for its whole lifecycle the model with the new system instructions acted broken for most people. it ignored instructions. 3. And so we suffered through it, 4.8 came out and its just ok. its just fine. reminder that the competition rolled out a bunch of new cool features in that same window. 4. Anthropic was fighting openclaw, while chatgpt took it over and became the main model in hermes, the best bang for your buck. 5. Anthropic was fighting for design, while chatgpt 5.6 does it better, plus it has a top tier generative model, plus real time voice. and opus 4.8 only gets which site you want on the 10th try (competitors nail it on the first or second). Honestly claude opus 4.6 was basically an AGI type model. alive, wild, super smart, autonomous. next to it chatgpt 5.2, 5.3 and so on looked like a dumb log. And the situation didnt just shift. its not about the models, its about the ecosystem and the business. i dont get why anthropic keeps dropping pretty stats when for a $200 sub i get half of what i get from the competition. 🥲 before this i kept paying for both subs, because what held me was the text, the vibe (which has looked like gpt for a while now, they even lost that) and the website design itself, i love building web interfaces. now im convinced im only gonna work with chatgpt claude fans or its devs, who fumbled every single trend in a row and nerfed their own models. you can make your excuses in the comments its all been clear to me since the second half of april anyway you lost a guy who was paying you since october 2025.

• 
  Learn AI (@LearnAI_MJ) reported 41 minutes ago

  @ajambrosino Can you make it easy to code in cloud? Just like how Claude Code Connect naturally to GitHub Repo. I know there is the Codex cloud version but it is soooo clunky to use comparing to Claude code and Cursor! Please - fix this. Also, why codex make computer cook so hot 🔥 comparing to Claude? My laptop even need a gaming fan! Please fix this too!!!

• 
  Dean (@DeanoDingus) reported 43 minutes ago

  @anonymous83r39 @Ray_DaHero See this is the problem with non devs vibe coding, is they throw words into a black box and have no bandwidth to even read the output and what’s happening. There is no fix that doesn’t rely on 5.5/V1 and you barely able to pull a single word out of the GitHub notes on it is LOL

• 
  Shadow Nick (@doublenickk) reported 45 minutes ago

  87% OF THE PLANET SUCKS AT AI BECAUSE THEY ARE STILL TYPING MANUAL PROMPTS LIKE AMATEURS While the masses use ChatGPT as a glorified search engine, elite builders are deploying autonomous digital armies that execute high-stakes business operations 24/7. Meet Synapse, an open-source MCP engine that hands AI complete vision and surgical command over your desktop to run background tasks silently while you sleep. The exact strategy used to break the system: The FBI Negotiation Hack: Scrape a massive list of multi-million dollar startups, feed real FBI hostage negotiation transcripts into the AI, and let the agent autonomously blast out high-leverage B2B outreach that forces prospects to say yes. Zero-Drift Execution: Ditch chaotic markdown files and manage your agent's state through GitHub Issues to keep them locked in for weeks without a single hallucination. Full-State Reality Testing: Stop relying on worthless pre-compile unit tests because this agent forces your system to compile, screenshots the actual interface, and verifies performance against reality itself. You can keep playing around with basic chatbots, or you can deploy a ruthless autonomous agent to scale your code and outreach on autopilot.

• 
  Gokul Rajaram (@gokulr) reported 47 minutes ago

  GITHUB PRODUCT SPEC LIBRARY Today we shipped a cleaner GitHub-native workflow in ProductSpec dot io. The product now has a GitHub Product Spec Library at the top of the editor. That matters because the main workflow is no longer just "write a new spec". It is now: open the repo, find the existing spec, edit it, validate it, and update it through a pull request. The new flow: -- Sign in with GitHub -- Choose a repo -- See how many Product Specs already exist -- Open an existing .product-spec.md file -- Edit it in the ProductSpec dot io editor -- Validate it against the open ProductSpec standard -- Update it via pull request ProductSpec dot io now treats GitHub as the durable home for Product Specs, while keeping the authoring experience clean for ***, founders, designers, and product-minded engineers. The repo gets: • Markdown • validation • pull request review • commit history • code proximity The editor gets: • structure • readability • HTML preview • AI eval fields • acceptance criteria • success metrics • a better way to work with existing specs Drafts still stay in your browser until you publish. The direction is simple: Product Specs should live close to code, but they should not require everyone to write raw Markdown by hand. ProductSpec dot io is free to use. Try the new GitHub Product Spec Library at ProductSpec dot io. Pick one existing PRD, move it into GitHub as a .product-spec.md file, and make the next edit through a pull request.

• 
  Kushagra Gour @css_battle (@CSSMonk) reported 50 minutes ago

  after these 10-min days quick commerce apps, amazon prime feels slow! imagine the situation where coding with AI becomes unavailable and you have to code by hand again! Even if some of us will be capable, we wouldn't want to do. Just like quick commerce took away our patience, coding by hand will become equally unbearable! Will AI downtimes become the next "github is down" situations?

• 
  Tom Baldry (@pinegoose_) reported 50 minutes ago

  Solo GitHub bill spiralled from $20 to $160/month on actions spend (the fable effect). Spun up a basement gitea server on Mac mini. ~0 spend, and builds are fking rocketing out. You couldn’t pay me to self host CI/CD 12 months ago.

• 
  Kirill Mesch (@kirillmeschc) reported 58 minutes ago

  Built with D3.js — force-directed character graph, timeline view for movies/shows (phase order or in-universe chronology), shortest-path finder between any two characters. Claude did the code, the GitHub push, the deploy, and these banner images. Free, no login, mobile-friendly.

• 
  TheMarketMaker (@xTheMarketMaker) reported 59 minutes ago

  Companies are pulling models from Hugging Face at a rate that signals a structural break from rental contracts rather than any philosophical preference for openness. My read is that the move reflects operators locking in cost predictability after watching provider terms shift against them. Half the Fortune 500 now routes inference and fine-tuning through the platform instead of renewing with the original vendors. The mechanism is straightforward: when renewal clauses embed escalating usage fees or usage restrictions that outpace deployment cycles, teams treat the model as owned infrastructure instead. Clem Delangue has framed the pattern directly. Companies are done renting their AI once the economics no longer favor the hosted tier. Hugging Face functions as the distribution layer where builders share and download models and datasets in the same way code moved through GitHub. That infrastructure now sits inside production stacks at scale. The shift accelerates when providers alter pricing mid-contract or impose new compliance gates that were absent at signing. Apple’s lawsuit against OpenAI illustrates the control problem from the other side. The complaint names senior leadership involvement in alleged trade-secret misappropriation tied to a long-time former employee. The filing shows how dependence on a single external model owner creates legal and operational exposure that self-hosted alternatives avoid. At the same time Meta removed its controversial AI feature from Instagram after user backlash reached Dylan Byers at Puck News. Both cases reveal that model behavior and terms can change faster than internal roadmaps can adjust. The capital markets already price the hardware layer differently. SK Hynix completed a $26.5 billion foreign IPO, the largest in U.S. history, precisely because memory demand for training and inference continues to climb. The same announcement carried calls for the company and Samsung to site new fabs inside the United States. That capital commitment is possible only if end users expect sustained on-premise or private-cloud workloads rather than continued rental consumption. What this actually means is that predictability now outweighs the marginal performance edge some closed models still hold. Teams that once accepted variable per-token costs are converting those budgets into fixed GPU or inference-server line items. The open-source repositories supply the weights; the hardware build-out supplies the capacity. Once the model weights sit inside the perimeter, renewal risk disappears. The contrarian angle is that this is not a temporary cost-arbitrage play. The rental model worked while providers absorbed the early R&D risk and offered undifferentiated access. As differentiation moved downstream into fine-tuning and data, the same providers began protecting margins through tighter terms. Operators responded by moving the base model in-house and keeping only specialized layers on rented capacity where needed. Apple’s action and Meta’s quick reversal both underscore the governance layer that external providers retain. A single policy change or leadership decision can alter model availability or behavior overnight. Self-hosting removes that single point of control. The SK Hynix raise quantifies the downstream bet: memory and accelerator spend is rising because the workloads are now expected to run continuously under operator ownership. The number nobody is pricing yet is the cumulative option value lost each time a renewal clause is exercised under changed terms. Teams that moved early to Hugging Face-hosted open models have already converted that option value into fixed assets. Those still inside rental contracts face the same choice at the next renewal window. #OpenSourceModels #EnterpriseAI #ModelOwnership