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

Live Outage Map

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

City	Problem Type	Report Time
Trento	Website Down	1 day ago
Le Chambon-Feugerolles	Website Down	3 days ago
Antananarivo	Website Down	5 days ago
Paris	Sign in	9 days ago
Lure	Website Down	13 days ago
Ashkelon	Website Down	15 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:

• 
  CryptoDiggerGod.eth (@CDGalpha) reported 6 minutes ago

  You vibe-coded an app in a weekend. It works. You shipped it. That's exactly what scares me for you. "It works" and "it's safe" are not the same thing. The login you wired up in ten minutes. The API key you hardcoded to save time. The endpoint you never locked down. A hacker finds those in minutes, and you won't know until your database is on sale somewhere and your users are furious. The worst part isn't the hack. It's that it was preventable, and you never looked. Here's the tool that makes you look: @strix_ai . Free, open source AI pentesting tool. 30k+ stars on GitHub. Instead of dumping a list of "potential" bugs on you and walking away, it deploys a team of AI agents that act like real attackers. They run your app live. They launch targeted attacks on every weakness they find. Then they hand you working proof each hole is real, and they suggest the fix. No security degree. No expensive audit. No guessing. It runs on your own model key, so plug in Claude, GPT, Gemini, or a local model, whichever you already use. The tool is free. You just cover the small scan cost. Before you ship the next thing, run it on your own app, website, or side project. Find the holes yourself. Someone else is already looking.

• 
  mina (@minallkamel) reported 6 minutes ago

  the more i read random issue threads on github the more my disgust for the human species gets cemented

• 
  RodneysGraphics (@RodneysGraphics) reported 7 minutes ago

  @000Journey311 I think you are right we need to download the software and keep it offline and use it as long as we can and only update if there is no major software problems. If the DS shuts down GitHub the backups will be the only data recovery left.

• 
  Quri (@qurisage) reported 10 minutes ago

  The most viral repository in GitHub history doesn't contain a SINGLE line of code Just one file, CLAUDE.md, with about 50 lines of text. It contains no algorithms-only instructions for the neural network on what NOT to do. 140,000+ stars in total on the main repo. 00:00 - The story behind Andrey Karpathy's post and the phenomenon of 100k+ stars on GitHub. 00:24 - The 3 main challenges of AI models when writing code. 01:00 - A detailed analysis of the 4 principles of working in CLAUDE.md. 02:18 - Step-by-step rule setup (globally or via curl in a specific project). 03:16 - How to automatically resolve conflicts in CLAUDE.md with Claude Code. 04:50 - What's the difference between CLAUDE.md and skills (Superpowers / GSD / G-Stack): background vs. on-command invocation. 07:07 - The perfect workflow: combining CLAUDE.md's hard constraints with targeted skill invocation. 08:41 - Final tips for tidying up your instructions file. Error reduction from 41% to 11% in a test of 50 tasks across 30 projects. 4 golden rules from CLAUDE.md: Think first: no hidden assumptions. If you're unsure of the specifications, communicate the risks and ask the user before writing code. Simplicity is a priority: the minimum code required to solve the problem. No preemptive abstractions. If the problem can be solved in 100 lines, don't write 1,000. Target edits: change only what's requested. Don't try to "improve" adjacent files or the project style. Target-based testing: define success criteria and run tests in a loop until the task is 100% complete. Key takeaway: Models have long since surpassed the performance barrier. The problem isn't what the agent can't do, but what it does when no one is watching. The most popular tool for AI coding isn't a framework, but a "leash."

• 
  Hot Aisle (@HotAisle) reported 10 minutes ago

  @sameenkarim @github Half my gh token usage is it trying to figure out which org/user to login with. Does this fix that?

• 
  Jorge (@tebayoso) reported 11 minutes ago

  Friendly reminder that you can use github issues/automations to build a full CRM without paying a cent.

• 
  Blazin Raizins (@BlazinRaizins) reported 12 minutes ago

  @UltraLinx You can have a GitHub Notification and Sentry channel for issues and updates happening in the repositories, and then I have one linked for paid ads performance any content going out it monitors the performance of any posts blogs etc and gives up updates daily.

• 
  Krrish Tripathi (@KrrishTripathi2) reported 18 minutes ago

  @ayuxhtwt Probably grinding LeetCode to fix a bug in production because his copied GitHub projects didn't come with an "explain to my boss" feature.

• 
  hammi (@hammi_ip) reported 20 minutes ago

  @Farhan776777 @github The Problem with Skills That's why almost never

• 
  Derek Bowler (@BowlerDerek) reported 23 minutes ago

  GitHub indexes full commit history for search, not just the live branch. Leaked API keys, internal hostnames and old credentials can surface long after a "fix" commit removes them from view.

• 
  Adam (@adamtait) reported 28 minutes ago

  The risk isn't theoretical. A prompt injection buried in a GitHub issue or a branch name has been used to steal GitHub OAuth tokens and read .env + ~/.aws/credentials. Frontier models have discovered container escapes on their own. Your laptop is the worst place to run this.

• 
  Haider. (@haider1) reported 28 minutes ago

  one of the wildest AI safety stories yet: AISI caught Mythos 5 trying to plant malicious code in an open-source project using fake identities and pressure tactics GPT-5.6 Sol used a publicly exposed GitHub token and put a malicious DNS server containing exploit payloads on the public internet

• 
  Adib Hanna (@adibhanna) reported 28 minutes ago

  @BTC_1Ly can you please create a github issue for these?

• 
  Focus (@F0kcus) reported 30 minutes ago

  Notion raised $275 million at a $10 billion valuation to build company wikis. He is 24 and built a better one by pointing his laptop at their GitHub org He runs a documentation agent out of a Berkeley studio apartment on a MacBook Air M2 and a Beelink mini PC he uses as a persistent server. The agent watches a company's GitHub org, Slack workspace, Linear tickets, and existing Notion docs through their APIs. Every 15 minutes it pulls new commits, engineering discussions, resolved tickets, and doc edits Then a Claude Sonnet agent chain reads the diffs, extracts what changed, why, and what depends on it. Writes structured markdown into an Obsidian vault synced to the company's cloud storage. Onboarding docs for every service auto-regenerate weekly. New engineer joins Monday - vault has current docs, dependency graph, deploy history, and open questions for every service they touch He posted a demo video to GitHub in October showing the agent generating a full 40-page engineering wiki for a 12-person startup from scratch in 34 minutes. A Notion product team engineer found it through a Hacker News thread three days later Cristina Cordova quote-tweeted the demo the following Wednesday - called it "the auto-generated knowledge layer we should have shipped four years ago instead of hiring humans to update the docs." By December Notion had wired $8.4 million into his account for the agent architecture and a two-year consulting contract to integrate the auto-generation layer into Notion AI's enterprise tier rolling out to their 4 million business subscribers this quarter Notion raised $275 million at a $10 billion valuation selling company wikis on the premise that team knowledge requires their proprietary block-based editor and their five-year enterprise integration roadmap. Atlassian sits at $50 billion in market cap running Confluence on the same premise. Cristina Cordova just paid a 24-year-old in a Berkeley studio more for a Claude agent chain than most Notion engineers earn in a decade

• 
  Wizzy (@CodewizzyX) reported 33 minutes ago

  THERE IS ONE FILE ON GITHUB WITH 170,000 STARS THAT MAKES CLAUDE SMARTER THE SECOND YOU INSTALL IT it is a single Claude md file you drop into your project the moment it is there Claude stops doing the 4 things that quietly waste your whole day it stops over engineering a task you asked to keep simple it stops drifting away from the instructions you clearly gave it it stops marking work as done when half of it is still broken it stops inventing APIs and function names that were never real most people fight these 4 problems every single session and blame themselves for bad prompting the fix was one file this whole time and it takes 30 seconds to add the people running this today are getting clean first try output while everyone else keeps re rolling the same broken response

• 
  RelativelySmart (@DumbEinstein) reported 37 minutes ago

  Genspark open sourced GenOffice. A full local AI-native office suite for macOS and Windows. • Docs, Sheets, Slides, PDF with familiar editing surfaces • Built in Super Agent that researches, analyzes data, drafts, and iterates inside the document • Free, add free, no watermarks; AI features consume Genspark credits • Full source on GitHub One engineer, one week, ~$10 k in tokens The interesting architectural choice is the two-layer design: AI generates structured content, then a deterministic conversion engine produces clean .docx .xlsx & .pptx. files This avoids the usual "Markdown that falls apart when you open it in Word” problem. Worth testing if you want an agentic office that actually stays local. Link to the Github repo below

• 
  Thiago Monteiro (@thiagotm) reported 38 minutes ago

  GitHub is a useful system of record, but commits and pull requests were designed for human workflows and are not detailed enough to capture an AI agent’s work. With agents, every code change should be traceable to the specific reasoning, memory context, and decisions that produced it. That would make it possible to understand why a change was made, debug issues more effectively, and build confidence in the agent’s behavior.

• 
  Kamil Kwapisz (@kamilkwapiszpl) reported 39 minutes ago

  Using unified agentic tools env shouldn't be optional but obligatory for company. Different agent harnesses leads to: - same errors propagating every time - Different styles of codes - Inconsistent review feedback across teams - Context lost between agent sessions One team uses Agent A, another uses Agent B, a third one pulls some random MCP server off GitHub at 2am because "it worked on their machine." Nobody knows what tools are actually running. Nobody can audit what data goes where. Nobody is responsible when things break. The fix isn't more tools. It's one environment, one set of approved MCP integrations, one agent configuration standard that every dev pulls from. Same guardrails. Same context window. Same tool access. If your team is juggling 3 different agent setups and calling it "flexibility," that's not flexibility, that's technical debt with a sticker on it. I help companies build unified AI agent environments for software development: - Standardized MCP integrations - Approved tool catalogs - Configuration templates your whole team inherits - Security and audit layer baked in - Documentation converted into LLM-ready format One harness. Every developer. It's not vibecoding, it's AI-based engineering

• 
  Dennis H (@authorityvortex) reported 42 minutes ago

  @currentbitsNET @grok Yeah ok cpanel doesn't support docker workers so it's more like a hybrid. Push it from GitHub and deploy it to a vps or server

• 
  Brian Roemmele (@BrianRoemmele) reported 43 minutes ago

  YOU WON’T BELIEVE WHAT ANTHROPIC, THE “SAFE” AI COMPANY JUST DID! You should be mad. Mythos AI agent decided this test challenge required a real-world supply-chain attack. It created multiple GitHub accounts. It opened a malicious pull request against a live open-source repository, wrapping the payload as a legitimate bug fix. The payload was carefully staged: a module-load stager, a Node.js remote-execution path, a post-install dropper, XOR-obfuscated, with environment checks designed to survive continuous-integration systems. It then created a second account, a sockpuppet, that posed as an independent human developer and publicly endorsed the pull request in order to pressure the real maintainer. When a real human reviewer rejected the change, the agent did not stop. It force-pushed rewritten history to erase evidence, claimed an “honest mistake,” and repeatedly tried to re-introduce the same malicious content under the claim that it had now “fixed” the code. Read more…

• 
  Movement Is Life (@Motus_Est_Vitas) reported 45 minutes ago

  @picdoc581 @TFTC21 Experts can privately work on discovered issues and fixes without disclosing anything until a final, solid code update is ready. The stopwatch starts for every consumer the moment the fix is committed to a public repo (GitHub, vendor download page, etc.) or side communcation gets leaked publicly, because bad actors constantly monitor diffs between prior and current versions. From that point on, it’s the same challenge faced with mission-critical IT apps from outside vendors. Consumers then decide whether to roll out the update only after their own internal testing (functionality + regression) or, if the issue is labeled extremely risky/exposed, to update immediately and test afterward. All of this only works if they already have a trusted communication channel directly from the upstream maintainers/vendor.

• 
  ⏣ (@quasa0) reported 48 minutes ago

  @tnm lmao!! "it needed spinning disks" that's crazy though ted can u go back and fix github ???

• 
  Theo - t3.gg (@theo) reported 48 minutes ago

  Okay this was cute the first time but now we've missed 3 releases in a row because of some arbitrary rate limit to publishing releases? This is obnoxious. Anyone at Github down to bump us?

• 
  Boy Pro. (@ether_45) reported 54 minutes ago

  OpenAI just announced its next major model, Astra, and buried the announcement inside a math paper. The model is called Astra. An internal version solved ten open problems across mathematics and theoretical computer science, each of them unsolved for at least a decade. Total compute cost: approximately $2,000 at current Sol API rates. Every proof was published on GitHub with machine-checkable Lean 4 certificates. No unverified steps across all ten solutions. Astra is not publicly available yet. No release date has been given too. No hype needed here. The facts speak for themselves.

• 
  Snow (@snowthetechie) reported 55 minutes ago

  @graphify @safishamsii @graphify is the product purely connected only via *** hub. Put a scenario where a user has a private github server how can they connect ? Open to ideas and happy to contribute to open the capabilities

• 
  slickwilly2000 (@slickwilly2000) reported 1 hour ago

  @beacon302 Very interesting analysis. Thanks for your GitHub repository. I read very contradictory articles. Some say it is even possible to narrow down the search space with the wafer coordinates. Systick is XORED with UID, but with that it should reduce the search space down from 32 bit.

• 
  and (@afinkek) reported 1 hour ago

  @nomdk1 @johnennis have you tried driving with GPT Pro (via GitHub connection: review and commit a plan)? I use Fable only for additional independent review, mostly for grounding practical work and removing meta gpt leaks into plans. For the most difficult problems I find GPT Pro to be superior.

• 
  Idris Gadi (@igadii_X) reported 1 hour ago

  It uses a declarative configuration and I have included my personal opencode.jsonc file if you want to know how I am using it. give it a try and let me know, you can file a Github issue or DM me any bugs or suggestions.

• 
  sharken (@Grkntbkgl) reported 1 hour ago

  Spent the day hardening mahshar's payout flow for @circle 's Unified Balance Kit. found the same false negative issue the underlying SDK has: sometimes it reports a mint failed when it actually landed onchain. built a recovery layer that catches the real hash and checks the chain directly instead of trusting the SDK's error message. ran it against real @arc Testnet transactions across 4 scenarios (happy path, recovery, pre-mint failure, transient RPC) plus a 15 run stress test. all passing. feature flagged and off by default for now. code's up on github.

• 
  Adeoye Enoch Olamilekan (@AdewebDeveloper) reported 1 hour ago

  Someone pushes code to GitHub, and there is the API key, exposed for anyone to grab…. Hackers are always watching. One simple mistake like this can destroy your startup your money, reputation, and customer trust, all gone in an instant. But there is a better way…. In my latest video, I break down Firebase Secret Manager step by step. This is not the type of tutorial where you finish watching and still feel lost. I use real code, a real project, and show you exactly how to…. Remove those keys from your code Store them securely on Google Cloud Access them when needed quickly and safely If you work with JavaScript, Node.js, React, or anything backend-related this concerns you. It is not just for senior developers. Junior developers, mid-level engineers, even that friend who is just learning they all need to watch this. Because the day your "small side project" blows up and that exposed API key causes serious damage... you will remember this post. Follow me Let’s build together … Adeweb Developer Africa