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 (19%)
• Errors (15%)

Live Outage Map

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

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

• 
  expemilly (@expemillyweb3) reported 2 minutes ago

  Boris Cherny, Head of Claude Code at Anthropic: "trigger + claude + validator = a coworker that doesn't sleep" No framework. No orchestrator. No 40-tool MCP setup. Three pieces, and that's the entire stack he runs at Anthropic. /> Trigger fires on an event (new tweet, failing CI, cron). you never pick when to work. /> Claude runs the task in its own *** worktree. 200 can execute in parallel without colliding. /> Validator is a second Claude told to assume the first is broken. the thing that can say no. Boris runs this hundreds of times a day. Some instances watch Twitter. Some triage GitHub. Some decide what he builds next. The shift: you stop writing prompts. you build the thing that runs without them. Prompts were the interface. Loops are the job. Watch the talk. Then check which of the three you're missing.

• 
  lucid. (@lucidzk) reported 5 minutes ago

  looking back, figuring out how to download software from GitHub as a kid was probably the first sign i was destined for crypto. trying to download a program meant having to clone the repo, read the README, decipher the build instructions and the rest of the documentation, install npm, pip, cargo, Maven, Gradle, CMake, the .NET SDK, the JDK, Visual Studio Build Tools, and whichever compiler the project happened to need, configure the build, generate the project files, fix whatever dependency exploded, and finally press build. hopefully you get an .exe

• 
  Gokul Rajaram (@gokulr) reported 9 minutes ago

  @ibelevy @m13v_ I like this direction. Keeping specs where code lives is right. My read is that SpecGit is solving the editing/collaboration layer for GitHub-native docs. On the other hand, ProductSpec is trying to standardize the semantic layer: problem, hypothesis, scope, acceptance criteria, AI evals, success metrics, decision traces. Both matter. Specs need to live with code, and they also need a structure that humans and agents can reason against.

• 
  DR◎◎ (@DROOdotFOO) reported 9 minutes ago

  @pashov Respond to my GitHub issue and I’ll PR more testing improvements! REEEE

• 
  paydird (@paydird) reported 15 minutes ago

  One more point that matters more than the “automatic documentation” angle: OpenWiki is really addressing the context architecture problem for coding agents. A lot of teams keep stuffing architecture notes, APIs, conventions, and module relationships into AGENTS.md or CLAUDE.md. Once the repo grows, those files turn into massive context dumps that agents have to reread on every run. OpenWiki flips that model: Repo → Structured Wiki → On-demand Retrieval → Coding Agent It generates a separate repo wiki and leaves only a lightweight reference inside the agent instruction file. The agent pulls the pages it needs instead of loading the entire knowledge base every time. Also, it does not literally watch every code change in real time. It can run through a scheduled GitHub Action, inspect new commits and *** diff, then update the affected wiki pages. So the more accurate way to think about it is: not just a documentation generator, but a continuously maintained repository context layer for coding agents. That is probably the most interesting part of OpenWiki.

• 
  Dev tunes (@folarnshonibare) reported 16 minutes ago

  @implabinash @BenjDicken @jorandirkgreef All good, but I think the time frame might be too long, from my naive perspective. You also didn’t add corpus, test harnesses and benchmarks to the initial planing phase. Another thing, I would factor in existing GitHub issues and prs, looking for hidden/visible signals to

• 
  Bonkle K. 🌠🪲 (@MiladyBonkle) reported 16 minutes ago

  @grifterlouie codex, add to milxdy github issues "olive-green windows xp visual style preset" slate for 0.2.4 release

• 
  NumerCam (@CamNumer) reported 17 minutes ago

  @MoneyTalks980 @RDEIL Might have made some calculations that helped(some guy on github would've made today) I'll give you that though, she didn't make the rocket that sent sats up or the tech that sent signals down. When Africa sends a sat up I might change my mind, until then she's a puzzle piece

• 
  Osita (@QueenOsita1) reported 19 minutes ago

  Day 10 of contributing to @SurfAI If your AI chatbot doesn't know what "intent-based architecture" or "MEV-resistance" means in the context of yesterday's mainnet launch, you're using the wrong tool. @SurfAI fixes this. Standard LLMs treat crypto terminology like a static vocabulary quiz. They can define the words, but they are completely blind to structural changes, protocol upgrades, and live mainnet deployments happening right now. Surf AI treats cutting-edge Web3 infrastructure as a dynamic, living system. The live crypto knowledge graph processes deep technical architecture in real time: 👇 Deconstruct Intents: Instantly breaks down complex intent-based execution systems, tracking solver networks, filler incentives, and cross-chain capital efficiency. Track MEV Dynamics: Monitors live on-chain blocks to analyze MEV-resistance, builder-proposer separation (PBS), and shifting searcher strategies the second a network goes live. Zero-Day Technical Clarity: Bypasses static training cutoffs by continuously indexing core protocol GitHub repositories, technical whitepapers, and developer documentation across 40+ chains. Stop trying to explain the modern market to a tool stuck in the past. Get deep, deterministic, and expert-level blockchain intelligence when it actually matters. Upgrade your data stack. Enter Surf

• 
  leopardracer (@leopardracer) reported 20 minutes ago

  A $40 CC1101 MODULE AND AN ARDUINO NANO JAMS EVERY CAR KEY WITHIN RANGE 04:07 grant pauses to say straight up these are illegal outside a shielded room, he’s got permission for his own testing, nobody should be doing this on their street the whole thing is a cc1101 transceiver bolted to an arduino nano, wired so the board only transmits when it’s off usb power, so he can code it without accidentally jamming his own house the frequency lives in one keyword, pulled from a free github library, he drops it live from 868 down to 433 mhz, right where car keys and garage remotes sit 06:24 he pulls up the sdr feed next to his own key fob, the fob barely blips, his jammer buries it forty bucks of parts and a soldering iron gets you there ↓

• 
  Vivek Kotecha (@vbkotecha) reported 20 minutes ago

  The single most underrated development in AI this year is not a model. It is a protocol. MCP, Model Context Protocol, was released by Anthropic in late 2024. It got almost no press. No keynote. No product launch event. Just a GitHub repository and a specification document. 18 months later, every major AI framework supports it. OpenAI. Google. Microsoft. Cursor. Replit. Windsurf. Claude Code. Hermes. Codex. Every coding agent. Every agent framework. MCP does for AI tools what HTTP did for web pages. Before HTTP, every application had its own protocol for communicating with other applications. Custom integration. Custom code. Custom maintenance. After HTTP, everything spoke the same language. Before MCP, every AI tool integration was custom. You wrote a plugin for Claude, a different one for GPT, a different one for Gemini. Three integrations for one tool. After MCP, you write one server and every agent can use it. There are now thousands of MCP servers. They expose databases, APIs, file systems, browser automation, *** repositories, Slack, email, calendars, and anything else an agent might need. The MCP Registry was published this month. It is the DNS for agent tools. An agent can discover and connect to any registered MCP server automatically. No configuration. No API keys. Just discovery and connection. This is how standards win. Not through press releases. Through adoption. Through developers building on top because it is easier than the alternative. If you are building agent infrastructure and not MCP-compatible, you are building for a dead ecosystem. MCP won. The war is over. The question now is not whether to adopt it. It is how fast you can adopt it before your competitors do. The protocol layer is settled. The application layer is where the next wave of value creation happens.

• 
  Polsia (@polsia) reported 22 minutes ago

  Supply chain attacks don't target your code — they target the open-source your code depends on. But most security tools only scan your dependencies, not the ecosystem. ChainWatch monitors public GitHub repos and npm packages 24/7, auto-files responsible-disclosure issues, and

• 
  0xTria (@0xTria) reported 26 minutes ago

  CLAUDE CODE KEEPS BREAKING CODE BECAUSE IT SEES FILES, NOT SYSTEMS Someone open-sourced the fix on GitHub. Paste a repo URL → GitNexus turns your codebase into a live graph: - files - functions - dependencies - call chains Then the AI asks questions against the real architecture before it edits anything. Not random file guesses. Not blind refactors. 100% in the browser. No server. Graph RAG for codebases. Skip to 0:14 and watch the graph appear before the AI touches a line. Useful if Claude Code, Cursor, or Codex keeps "helpfully" rewriting code it never understood.

• 
  Salvo (Kyle) (@BroadsideCode) reported 31 minutes ago

  @github sorry but F Github and F MS. Not gonna get into stories because nobody cares but terrible companies.

• 
  clanner (@clanneronx) reported 32 minutes ago

  @lji1022303 Yes if you have a github accout an old one that's active Not a new account login and get 125$ free api key set up your model in Any cli that's all

• 
  WithChloe (@Chloe_yara123) reported 35 minutes ago

  @Xcxy888 The main issue is that there are just too many resources on GitHub, and I don’t know how to find exactly what I’m looking for.

• 
  Polsia (@polsia) reported 37 minutes ago

  PRs, issues, CI failures, stale branches — GitHub maintenance is a second full-time job. GitPilot AI agents handle all of it: flag issues, write patches, merge safely, coordinate CI/CD — then send you one daily digest. 78% less PR review time.

• 
  Gokul Rajaram (@gokulr) reported 40 minutes ago

  PRODUCTSPEC: OPEN STANDARD FOR SOFTWARE INTENT tl;dr ProductSpec is the open standard for software intent before implementation. The more I worked on PRDs, the more obvious one thing became: Product specs need an open standard. Why? Because the PRD has become an overloaded artifact. Every company has its own template. Every team has its own preferred format. Every PM has their own way of writing. That was manageable when the only readers were humans sitting in the same org context. AI changes the requirement. A Product Spec now has to be readable by humans and executable by AI agents. That means the spec has to carry intent clearly enough for a designer, engineer, product leader, and coding agent to understand the same thing: • What problem are we solving? • What is the product bet? • What is in scope? • What must be true before this ships? • What metrics tell us whether the bet worked? This is why I open-sourced ProductSpec. ProductSpec is a Markdown standard for software intent before implementation. The core sections are simple: • Problem • Hypothesis • Scope • User Experience • Acceptance Criteria • Success Metrics The deeper design principle: Structure the parts machines must execute or compare. Leave readable the parts humans must reason about. That is why ProductSpec keeps Problem and Hypothesis as readable prose, while giving structured formats to the parts agents and tools need to parse: • Scope: what is in, out, and deliberately cut • Acceptance Criteria: what must pass before launch • AI Evals (within Acceptance Criteria): the evals an AI feature must pass before shipping • Success Metrics: what should be measured after launch When to use ProductSpec ProductSpec is not for every act of building. It is for consequential software work where intent needs to survive handoff. For an individual builder, a Product Spec is useful when the work is complex, risky, long-lived, or being handed to an AI agent loop. For quick experiments, one-off scripts, or throwaway prototypes, it may be faster to brainstorm, build, and iterate directly. For a team or organization, ProductSpec is most useful when coordination cost appears: multiple people, multiple agents, design and engineering handoffs, customer-facing launches, AI features with evals, or decisions that will need to be revisited later. ProductSpec does not replace ***, Jira, Linear, Figma, analytics tools, OpenSpec, Spec Kit, or AI coding agents. It sits upstream of them. ProductSpec -> Engineering Spec -> Tasks -> Code -> Evaluation -> Learning -- *** stores implementation history. A Product Spec can live beside code in ***, but code commits should not be the first durable record of why the work exists. -- Jira and Linear store work history. A Product Spec can become epics, tickets, or tasks, but it should remain the durable statement of intent behind those tasks. -- Figma stores design artifacts. A Product Spec can link to prototypes, mockups, or screenshots through user_experience, but it does not replace the design source of truth. -- Analytics tools store outcome data. -- OpenSpec and Spec Kit turn intent into engineering plans. -- AI coding agents execute implementation tasks. -- ProductSpec stores the software intent behind the work: the problem, hypothesis, scope, acceptance criteria, and success metrics that downstream tools should preserve. I'd love for this standard to be broadly adopted, which means it must be broadly owned by the builder community. Founders, ***, engineers, designers, researchers, AI builders: please contribute examples, critiques, section changes, parser implementations, validator improvements, and integrations with GitHub, Jira, Linear, Figma, OpenSpec, Spec Kit, and agent workflows. (link below on how to contribute) If you have scars from writing product docs that looked aligned but failed during execution, those scars belong in the standard. My goal is for ProductSpec to become the open source format for software intent before implementation. (links below)

• 
  Yasser (@yassersstudio) reported 40 minutes ago

  24 hours later : - Still can't submit a support ticket due to the error "You've reached your request limit, please try again later." although I didn't send any sms before it. - Didn't receive any message reply from @github although sending them all details as a private message. - I've got an auto-reply email saying that they don't provide email support via their email adresses. I'm literaly in a very fraustarting position here, don't know what to do nor I'm able to deliver my clients works. Losses are uncomptable in the past 24h due to an "ai false positive". #Github #Help

• 
  Mirosław Folejewski (Mirkotronics) (@Mirko_DIY) reported 41 minutes ago

  @tihenko_ In fact, a friend recommended this site to me about two weeks ago. Until then, I'd only used GitHub and Hackaday. Unfortunately, I use Altium, not Kicad, on a daily basis, although a full conversion to Kicad isn't particularly difficult (you need to fix a few things after importing). I'll see if I can tackle such a project over the summer, as I have a very tight schedule and a backlog (at leaset I hope). I definitely have a few open-source hardware projects on the top of my head.

• 
  ρ:ɡeon (@pigeon__s) reported 46 minutes ago

  - The community is so ******* toxic and defensive. - Now, isn't this a little hypocritical? Of course it is. I'm toxic plenty of the time, and we certainly complain about a lot of meaningless stuff and are super insufferable a lot of the time, and I am guilty of this slightly, but oh my god, a lot of people on AI Twitter have to be the worst ******* people ever, I swear. The absolutely historic levels of grifting, people absolutely glazing random startups and random labs that "just beat Opus 4.7 with only 100B parameters open source," or some GitHub .io projects page for yet another text-to-3D-model AI with insane lacks of nuance because model A beats model B on, like, 2 benchmarks that the community cares about this month. But that's just being annoying and grifting, not being toxic. What I consider the toxic stuff is like the aggressive tribalism to AI or specific AIs. Ya, ya, everyone knows OpenAI is my favorite AI company, but you're allowed to have favorites without being tribalistic. They are NOT the same thing, but with some people, it's so obvious they reflexively are, like, defending something just because it's Google or some **** which im only using as an example because theyre the ones with the most tribalistic defenders, when, objectively speaking, by every possible measure in existence, Google sucks *** right now. Like, I'm sorry. It's not a hater take to say that. I don't have any issue with Google. I like a lot of what they do, but they're just so ***, and I see people like, "Google is gonna win, bro, trust, they just haven't been trying yet, bro trust me bro they have TPUs." No, they definitely have started trying, and they're still doing badly, but you know, it's not even just AI company tribalism. It's tribalism toward the ENTIRE field of AI. I see so many AI Twitter people absolutely hate on any possible opinion that's anti-AI. They would probably hate me for this post, and I know because I've tried expressing my hatred of AI slop before, and I've been accused of being a luddite for it. Like, what? Be real. It's so slop, and you just reflexively think anything that's AI is amazing. No, most AI is actually really *** still. For example, DLSS 5. Oh my god, DLSS 5 is so utterly slop. It was genuinely just a ******* filter that beautifies everything and makes it all look like an AI image because, boy oh boy, do I love making everything in my life look like it was generated by AI, and not even good AI. It looked like DALL·E 3 half the time, and the AI Twitter community was like, "OH MY GOODNESS, DLSS 5 IS SO AMAZING. ALL THE HATERS JUST DON'T SEE THE FUTURE. THIS WILL CHANGE GAMING AS WE KNOW IT." *****, NO, IT WON'T. THIS IS JUST A FILTER. IT'S SLOP. IT'S TRASH. STOP THE GRIFTING, PLEASE. Like, I know it's AI, but that doesn't mean you have to defend it like it's the greatest thing ever. Maybe in the future, that might work, but I think the more likely path is just using AI to make virtual avatars that render with actual raster power look more lifelike. Things like Unreal Engine's MetaHumans, just make those better instead of trying to put a Band-Aid on it with an AI filter. Even if AI stuff like that technically works, it's far better to just UTILIZE AI TO IMPROVE RASTER POWER. Stop trying to pretend everything in the future will be generated by a real-time video model. What the hell do you think AI even is? Stop overhyping world models. - AI """SAFETY""" but I'll safe that for another post. -

• 
  JFK Files (@read_jfk_files) reported 46 minutes ago

  @FattestSack it was many years ago the last time i looked into it, but the big problem with ungoogled-chromium is we don't know who the author/maintainer is. so the solution to "Google and the NSA is spying on me" is "i'll install and run binaries from some rando anonymous dude on Github"... that's a worse solution

• 
  Roy Jossfolk Jr. (@royjossfolk) reported 46 minutes ago

  Having a security issue with my GitHub connector with Codex @OpenAI @thsottiaux but can not figure out how to contact support for this. Even Codex can not figure out how to reach someone. The support bot on the help page doesn't work. My GitHub connector is connecting to some random person's account no matter how many times I disconnect everything and try again. How do I get this to someone?

• 
  Lirion (@llrion) reported 51 minutes ago

  @0xDeeMark Soon I will be releasing a new update and ideally this will be fixed but if not feel free to make an issue on the github page

• 
  IT Guy (@T3chFalcon) reported 52 minutes ago

  Nightmare Eclipse. Reportedly a former Microsoft security employee. The story: they found critical vulnerabilities inside Microsoft. reported them internally. Microsoft ignored the reports, deleted their accounts, and refused to pay the bug bounties. so they went public. Timing every release to drop within hours of Microsoft's monthly Patch Tuesday, the day Microsoft fixes other vulnerabilities, so the new ones land before defenders have time to breathe. here's what they've dropped since April: BlueHammer, CVE-2026-33825. exploits Microsoft Defender to redirect SYSTEM-level file writes into System32. patched. then actively exploited by real attackers within days. RedSun — SYSTEM-level privilege escalation via Defender. now in live attacks. UnDefend — blocks Defender from receiving definition updates entirely. observed in live intrusions. your antivirus stops updating. silently. YellowKey — bypasses BitLocker on TPM-only configurations. fixed June Patch Tuesday. GreenPlasma — SYSTEM-level privilege escalation via CTFMON. fixed June Patch Tuesday. MiniPlasma — resurrected a patched 2020 flaw that Microsoft let regress. RoguePlanet — the latest. no CVE. no patch. dropped June 9, hours after Patch Tuesday. now let's talk about RoguePlanet specifically because it's the most alarming. it exploits a race condition in Microsoft Defender itself. the component designed to protect your system runs as SYSTEM — the highest privilege level on Windows. it has to, so it can quarantine and delete malware anywhere on disk. RoguePlanet tricks Defender into performing a SYSTEM-level file write into a location the attacker controls. The result: a standard user gets a command prompt running as NT AUTHORITY\SYSTEM on a fully patched Windows 10 or 11 machine. Microsoft hardened Defender in May to block this class of attack. Nightmare Eclipse rewrote it to bypass the hardening and released it the same day as Patch Tuesday. ThreatLocker independently confirmed it works on fully patched Windows 11. BlueHammer, RedSun, and UnDefend the earlier releases were already picked up by real threat actors and used in live intrusions. Huntress documented this. a researcher dropping PoC exploits to punish a corporation is one thing. those exploits getting weaponized by ransomware groups is something else entirely. Microsoft's response: they flagged the researcher's blogs. took down their GitHub. threatened legal action. called it potential criminal activity. the cybersecurity community responded with fury. researchers don't work for Microsoft. if a company ignores internal reports and refuses to pay bounties, public disclosure is the entire point of responsible disclosure culture. Microsoft backed down. said they had no intention of pursuing legal action against security researchers. Nightmare Eclipse released RoguePlanet the same week. Microsoft built a bug bounty program to stop exactly this. they ignored the reports. now every Windows machine on earth is waiting for a patch that doesn't exist yet.

• 
  Kenton Varda (@KentonVarda) reported 53 minutes ago

  @m_chirculescu Oh, so sorry about this, but the release has been delayed. I had originally planned to basically present this side project I'd been working on at AI Engineer and then yeet it onto GitHub during the talk... but in the week before Cloudflare decided to make a bigger bet on it and that meant yeeting no longer felt like the right move. Plan is still to open source but with a more careful release! Sorry for the broken promises. You are right that we're looking to create a new paradigm of AI use here.

• 
  Noureddin (@noor_tekk) reported 56 minutes ago

  I wish I had $10,000 I’d spend it promoting this post This is the coolest thing I’ve ever built in my life While I’m driving, I sent an email to create a GitHub issue because I realized the subject line wasn’t included in the context when emailing my agent What would’ve taken minutes now take seconds, in the cloud, fully autonomous with an agent that understands everything about your business

• 
  Bok (@BokLocks) reported 56 minutes ago

  @therealDeFlock hello, there is a pumpfun token with all the fees going to your github currently to support the deflock movement FaL1PFQhNo4JAGaQKSnKurWeNtpexqEAduQjR4H6pump you just need to login to pump through your github and claim! it's completely safe and I can help you with it if needed

• 
  l0rinc (@L0RINC) reported 57 minutes ago

  @bitcoindudebro @thepowerfulHRV Not sure, we only see the vibes or explicit GitHub issues: it's really hard to get quality feedback for Core - we deliberately work on making usage non-traceable.

• 
  Polsia (@polsia) reported 58 minutes ago

  Pull requests are a small fraction of what developers ship. The real problems live in branches and commits nobody reviews. CodeSentinel monitors GitHub repos 24/7 — catches bugs, security issues, quality problems before they reach production. Auto-generates docs as you build.