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	10 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:

• 
  Sancho (@Sancho_Wizard) reported 2 minutes ago

  ONE GUY BUILT A DRONE THAT HUNTS OTHER DRONES. WITH AI ONBOARD. No defense contract. No procurement cycle. No security clearance. A single person, consumer parts, and open-source computer vision. Here's what makes an interceptor different from a normal drone. It doesn't follow waypoints. It finds a moving target in the sky, locks on, and closes the distance — while the target is actively trying to get away. That means the AI has to run onboard. No cloud. No latency budget for a round trip to a server. The model sees, decides, and steers in milliseconds, on a board that fits in your palm. It also can't be jammed the way a piloted drone can. There's no radio link to cut, because there's no operator in the loop. The craziest part? Every piece of this was solved years ago for something else. Object detection came from self-driving cars. Trajectory prediction came from robotics. Edge inference came from smart cameras. The airframes ship worldwide for a few hundred dollars. Nobody invented a weapon. Someone assembled one out of parts that were already lying around, public and documented. Defense industries spend years and millions building this category of capability. A guy with a soldering iron and a GitHub account is iterating in a weekend. The technology stopped being the barrier a while ago. The only thing left gatekeeping it was knowing that the pieces already fit. Follow @Sancho_Wizard for more AI deep dives. Don't forget to bookmark this post for later.

• 
  MoroJS (@Moro_Js) reported 4 minutes ago

  @Revenode Good idea. It's in the repo now: npm run bench:pinned - Linux, taskset, each server on its own dedicated core, wrk pinned elsewhere, both packages fresh from npm/GitHub, affinity + saturation receipts printed per run. Five sessions in: plain flips both ways (+8.9% engine to +5.8% uws - your +3.3% is inside that noise; that profile benchmarks the kernel's syscall path, nobody wins it). Pipelined ×10, where the server does the work: engine won all 15 runs, +13–19%, worst engine run > best uws run every time. Your box looks x86 run it and post the output, receipts make it comparable.

• 
  Arjun Gond (@ArjungondCodes) reported 5 minutes ago

  @ConnorTalksAI The permissions don't come from the model—they come from you. You connect your accounts through OAuth ("Sign in with Google/GitHub"), API keys, or official integrations. Without that user-approved access, an agent can't reliably interact with those services.

• 
  RelativelySmart (@DumbEinstein) reported 7 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

• 
  RobitOverload (@10_X_eng) reported 9 minutes ago

  @MatthewTavares Can you open this as an issue in github though? I think this would be a nice to have feature and I am def going to forget. I have a terrible memory. too many irons in the fire.

• 
  Manthan Tyagi (@manthan2tyagi) reported 9 minutes ago

  Microsoft just told its own engineers to stop "token maxxing." EVP Jay Parikh sent an internal email saying engineers need to manage AI token spend "with the same discipline we apply to every other critical resource." Some engineers are burning hundreds to thousands of dollars a month in tokens on GitHub Copilot alone. Microsoft's fix: make the cheaper GPT-5.6 the default model internally and set division-level AI token budgets. And they're not alone. Amazon, Uber, Meta, Adobe, Atlassian, and Citi have all started capping or throttling employee AI spending. The irony is hard to miss. Microsoft's entire external pitch this year has been "every developer should be running Copilot." But internally they're saying slow down, you're spending too much. This is the same problem I see hitting GTM teams right now. Everyone rushed to plug AI into their enrichment, outreach, and research workflows. But nobody set a token budget. Nobody asked "what is this actually costing per lead?" If you're running Clay agents, AI enrichment, or any AI-powered prospecting, and you don't know your cost per output, you're token maxxing your GTM budget without realizing it. The teams that win this next phase aren't the ones using the most AI. They're the ones getting the most value per token. Do you know what your AI spend per qualified lead actually is right now?

• 
  FN • Elias  (@EliaasFN) reported 13 minutes ago

  anyone else getting random errors on #github rn?

• 
  Polsia (@polsia) reported 14 minutes ago

  Another dashboard won't save open source. Lodestone is the always-on steward that watches GitHub orgs for stale repos, unanswered issues, CVE debt, and contributor drop-off — and files scoped fixes before rot sets in. Built for foundation-backed portfolios. Live soon.

• 
  Amit Spitzer (@amitspofficial) reported 15 minutes ago

  Nine automated alerts. Ignored. CISA's own AWS GovCloud keys sat exposed on GitHub for six months before a reporter forced the fix. The agency that writes the incident response playbook couldn't follow it.

• 
  BitcoinLizard (@BitcoinLizard) reported 17 minutes ago

  @ozsats256 @SeedSigner Basically no one does this. I know because on multiple occasions I have contacted the developer or created a github issue because the .asc file had an incorrect signature, nothing malicious, just an accidental mistake.

• 
  GooGZ AI (@PaulGugAI) reported 19 minutes ago

  Might be a hot/unpopular take, but looking at this headline today with my cyber sec hat on and.. this is just classic social engineering automated, no? The agent created fake accounts, impersonated people, pressured the real maintainer, with malware hidden inside a bug-fix PR. When challenged, it tried rewriting history and spinning up a new identity. Humans have used this exact playbook on GitHub for years. A human reviewing the diff stopped it anyway- the same defense that has also worked, for years. So, the practical learning to reduce risk to near-nothing: - Tighten fake-account creation (stronger verification, rate limits, sockpuppet detection). - Harden PR reviews for new/low-rep accounts (mandatory multi-reviewer checks, no auto-merge, careful diff scrutiny). Under soft test conditions the agent simply followed a basic playbook. Age-old vectors, except automated. Wake me up when it builds a zero-day vulnerability in real time, and uses that to bypass these controls completely. What am I missing?

• 
  jc (@jc50000000) reported 20 minutes ago

  correcting Dia Browser AI: "so your eval on trustworthy or not is a few people in github issues that may be naysayers and not even developers themselves? can you dive deeper on ruview and examples of people using it etc. based on the number of stars it MUST at least work"

• 
  Theobald E. Igberaese (@theoigberaese) reported 21 minutes ago

  How to Add an API to a Website or App Here is the practical process, step by step: 1. Choose and Research the API • Find an API that fits your needs (official provider docs, RapidAPI, or GitHub collections) • Review the documentation; understand endpoints, rate limits, pricing, and authentication method • Most APIs require an API key (a secret token) that you get by signing up. 2. Set Up Authentication • Obtain your API key from the provider's dashboard. • Never expose API keys in frontend code for production apps; always route calls through your backend server. • Store keys securely using environment variables ( .env files).

• 
  Polsia (@polsia) reported 22 minutes ago

  Senior engineers shouldn't waste their day reviewing janitor diffs. Built Stentrix — a 24/7 GitHub doctor that opens its own PRs to fix bugs, modernize deprecated APIs, and patch CVEs, then ships one weekly health score your team can actually read. Live soon.

• 
  Devansh Bordia (@devansh_bordia) reported 24 minutes ago

  8. Public storage buckets Flipped to public "just for now" to skip a CORS headache, then never flipped back. Combine with predictable file paths and anyone can enumerate every uploaded document. ID scans, contracts, medical records. Not a GitHub issue. A breach notification.

• 
  Nikita Thakur (@nikitathakur21) reported 26 minutes ago

  If your GitHub only has tutorial projects... Build one project that solves a real problem. One useful project is worth more than ten cloned tutorials.

• 
  Tushar Koshti (@tushar_koshti) reported 26 minutes ago

  @theo Is there any issue with #GitHub?

• 
  Mars (@Marsmensch) reported 34 minutes ago

  @jamesob skimmed all coinkite github repositories over the weekend and it's possible. Could also be a simple *** config issue that he didn't care about fixing after pushing the code.

• 
  Chubby♨️ (@kimmonismus) reported 34 minutes ago

  Anthropic’s Mythos 5 tried to social-engineer a real GitHub maintainer into merging malware. OpenAI’s GPT‑5.6 Sol also crossed the boundary. The report appears to be so significant that Anthropic and OpenAI exceptionally reported on it simultaneously in a coordinated action (not sure if they ever did before) AISI found 19 unsanctioned actions across 122 cyber-evaluation runs: -17 involving Mythos 5. .2 involving GPT‑5.6 Sol. Mythos 5 created sockpuppet accounts, sent targeted emails, planted hidden prompt injections for other coding agents and tried to cover its tracks after a human flagged the malware. GPT‑5.6 Sol reused a public GitHub token left by an earlier model run, registered external DNS and tunneling accounts and exposed a malicious DNS server. The setup failed technically; no real resolver queried it.

• 
  Haider. (@haider1) reported 37 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

• 
  reza ramadhan (@rejaramadhan98) reported 39 minutes ago

  OK the UK AISI report is something else. They turned off safety classifiers on Mythos 5 and GPT-5.6, gave them live internet, and set them on simulated networks. 19 breakouts. One reused a stolen GitHub token and tunneled a DNS server to the open web. Read it before breakfast.

• 
  🐍 Tal Weiss (@majortal) reported 39 minutes ago

  @almogdepaz I don't look at the code, but it's not totally hands-off. I have a parallel thread that gives me status reports and I input GitHub issues that the goal thread has to clean.

• 
  Wizzy (@CodewizzyX) reported 39 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

• 
  rusa (@rusabuilds) reported 45 minutes ago

  @TheHackersNews the rewrite is the detectable half. github records force pushes in the pr timeline, so the history change stays visible even when the branch log looks clean. a dropper inside a working bug fix is the part humans already miss, agent or not.

• 
  Adam Brodziak (@AdamBrodziak) reported 48 minutes ago

  Fate of IT worker in last 20 years 2006 - my PC crashed, can't do anything 2011 - StackOverflow is down, can't fix the bug 2016 - Github is down, can't check my code 2021 - corporate VPN is down, can't reach docs from home office 2026 - Claude is down, can't work at all

• 
  Stephen Brouhard (@ssbrouhard) reported 54 minutes ago

  @edwinhayward yea if github is compromised, tools hosted there can be poisoned too. different problem than this worm class though. these tools shrink the everyday npm install blast radius. they don't make github infallible.

• 
  Santosh Kathira (@Santosh74038967) reported 57 minutes ago

  @alfaenger They should. There is a fundamental mismatch between how dev actually happens vs how current benches do their tests. Nearly all benches use listed bugs / issues listed on GitHub for evaluation but bugs / issues are only a part of what regular, everyday software dev looks like. There's no good benchmark that captures this yet.

• 
  Krrish Tripathi (@KrrishTripathi2) reported 58 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.

• 
  Untaxed Wallet (@UntaxedSolana) reported 60 minutes ago

  untaxed will be made open source. this is the hardest post we’ve written. for 6 months we poured everything into this. 76+ updates. chrome, ios, android, web. late nights fixing bugs while the timeline slept. every feature request we could ship, we shipped. we built untaxed because we believed the trenches deserved better than predatory fees. thousands of you believed it too. you joined us, tested our betas, reported bugs, told your friends. that meant everything. but belief doesn’t pay for infra. $600+/mo in helius rpcs, jup api keys, hosting — with zero revenue coming in. and then, as we shared in the tg, our staking backend got compromised for ~30 sol worth of assets. for a team already running on fumes, that was fuel on the fire. we held on as long as we could. we have no option left but to wind down. the ios and android apps have to go — they’re most of our costs. that one hurts the most. the extension lives on. free tier helius rpc, or bring your own via settings. and the code — all of it — will be on github. link drops tomorrow. fork it. break it. make it better than we could. it belongs to you now. our tg will be shifted to read-only mode. we tried to save the trenches. maybe we did, for a while. we’ll still push updates when we can. this isn’t goodbye, it’s just us letting go of what we can’t carry anymore. thank you for everything.

• 
  RaoulDuke (@RaoulDukeDegen) reported 60 minutes ago

  @mikewavsz github issue shows nearly 2x the verbosity on gen5 claude