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 (70%)
• Sign in (18%)
• Errors (12%)

Live Outage Map

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

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

• 
  Oluwatobi O (@ooluwatobig) reported 24 seconds ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

• 
  Dennis **** (@WangZoneHQ) reported 3 minutes ago

  The problem was not that I lacked information. Rather, my context lived across many surfaces: - chat threads - email - iCloud files - Telegram - Notion - GitHub repos - screenshots - agent conversations Every AI session could help me in the moment, but the useful context did not compound cleanly.

• 
  Todd Desiato (@TokenDepotCorp) reported 3 minutes ago

  Would you be interested in helping promote real Kaspa adoption? I spent the past year building Oma Wallet, a Kaspa wallet designed specifically for token utility. It is live now, but it launched quietly and did not get much media attention. Oma supports Kaspa, KRC-20 tokens, Issue-Mode CA tokens, offers, swaps, rewards, discounts, subscriptions, memberships, and other real-world token use cases. I am also building AMEKAS, pronounced Am-eh-KAS, like "Am-eh-ri-ca + Kas" with emphasis on KAS. It is a Kaspa and KRC-20 checkout shopping center where sellers can set up online stores that accept Kaspa and approved KRC-20 discount or entitlement tokens at checkout. No dollar checkout, no payment processor fees, and no broker fees. There is also a node operator angle: anyone running a Kaspa node can install a small script that lets them manage subscribers for Oma Wallet and future AMEKAS shopping access. That can turn a Kaspa node into a subscription business tied directly to Kaspa utility. You can learn more on the Token Depot website and GitHub. I know your goal is to promote Kaspa. Would you be willing to take a look and help spread the word?

• 
  Domi (@domirosari0) reported 3 minutes ago

  @ajayyy_k @hqmank If you got Github it would be no issue for you

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 5 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  Jared Tate ©️ (@jaredctate) reported 6 minutes ago

  I'm a blockchain developer. North Korean hackers tried to steal my crypto & hack my computer by pretending to recruit me on LinkedIn for a crypto consulting gig. Here's the entire attack: PHASE 1 — THE LURE A "recruiter" (a polished, good looking blonde "British woman in London") messages you on LinkedIn. Real-looking profile, perfect English. She books a Google Meet. On the call it's a different person — a bald Chinese looking guy, who quickly turns his camera off complaining of a bad connection, broken English — who asks two telling questions: "What crypto wallets do you use?" and "What code editor do you use?" That's not an interview. That's target profiling. PHASE 2 — THE DELIVERY He sends a GitHub repo (a "Web3 game" project) and says: clone it, run `npm install`, and open it in Cursor so we can see you know what your doing. It looks like a normal codebase. It's bait — with malware hidden in 3 separate files, each rigged to run automatically. PHASE 3 — PAYLOAD #1: package.json (the trip wire) They added one line: "prepare": "node server/server.js" npm runs the "prepare" script automatically right after `npm install`. So just installing the dependencies launches their code. No button. No warning. PHASE 4 — PAYLOAD #2: auth.js (the backdoor) In one file, the real code ends at line 18. On line 19 — shoved far off-screen behind ~600 blank spaces so you'd never scroll to it — sits obfuscated code that: • collects your hostname, OS, and MAC address • sends your entire environment (process.env) to a North Korean server: 147.124.212.180:1224 • runs whatever JavaScript that server sends back, via eval() = full remote control • repeats every 5 seconds That's a backdoor. The eval() is the doorway they use to push the actual wallet/password stealer. PHASE 5 — PAYLOAD #3: .vscode/tasks.json (the silent one) A second hidden file set to "runOn": "folderOpen" — it executes the instant you open the folder in your editor, with no window and no output: Translation: download a script from their server and run it immediately. THIS is why they demanded Cursor — they were betting it would auto-run the task. VS Code stops and asks "do you trust the authors of this folder?" first. I never said yes, so it never fired. DO NOT USE CURSOR (for many reasons) PHASE 6 — THE FALLBACK When the repo "wouldn't run," he sent a slick website with a "Connect Wallet" button — a straight-up wallet drainer — and said "just connect MetaMask." THE GOAL Drain your crypto and steal your credentials — money that funds the regime. It's a documented operation: the "Contagious Interview" campaign (aka Famous Chollima). HOW TO NOT GET HIT • A "job interview" that requires running their repo = malware until proven otherwise. • Never `npm install` a stranger's code on your real machine. Use a throwaway VM. • Keep serious crypto in cold storage — never a hot wallet on your daily driver. • If a recruiter's story falls apart the second you get on a video call, walk.

• 
  Lost In Tech (@lost_in_tech) reported 7 minutes ago

  @8_senkou Probably not intentional tbh. Have you logged as issue in the snorca GitHub? If not probably worth doing.

• 
  pratik.eth (@eth_ethpratik) reported 9 minutes ago

  @Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.

• 
  Andrew (@openmarmot) reported 11 minutes ago

  @AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.

• 
  David Cramer (@zeeg) reported 12 minutes ago

  @shansmithnz I haven’t been using it but mostly because 1) laziness and 2) I didn’t find the remote sync pleasant in practice I switch PCs too much right now so mostly relying on GitHub issues as artifacts

• 
  severe engineer (@severeengineer) reported 16 minutes ago

  since github copilot onward leetcodes have become even more disconnected from how we all write code every day problem is any kind of standardized replacement probably ends up looking basically the same lol

• 
  Martony 🧑🏽‍💻 (@martony_zinx) reported 16 minutes ago

  Is GitHub in trouble? Maybe. GitHub was built for humans. Origin is built for a world where AI writes most of the code and humans supervise.

• 
  Ben Canning (@benhackshealth) reported 20 minutes ago

  Spent today setting up home assistant in the gym, ran into an issue with the connection between the software that controls the LEDs around the mirror. Found a 4 year old repo on github, downloaded it, updated the code, fixed the problem and now control the lights without having to get out of my seat... Am I a hacker now?

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 24 minutes ago

  AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

• 
  Vishal Tiwari (@VishalTiwa91817) reported 24 minutes ago

  @AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.

• 
  Anjula Dwivedi (@HeyAnjula) reported 27 minutes ago

  9/ Headless mode for automation claude -p "your prompt" runs Claude Code without the UI — perfect for CI/CD. Auto-fix lint errors on every push. Triage new GitHub issues. Generate release notes. Claude Code isn't just a tool you talk to. It's a tool your pipeline talks to.

• 
  Financial Programmer (@RBiancoUS) reported 28 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  Tatted (@TattedWorks) reported 31 minutes ago

  Sentry uses a public credential called a DSN — intentionally embedded in your website's JavaScript so browsers can report errors. By design. Everyone's DSN is findable. Censys, GitHub code search, a quick look at your source. No breach required. An attacker POSTs a fake error to your Sentry project using that DSN. Inside the error: a fake "Resolution" section, formatted in perfect Sentry markdown, complete with a recommended npx command. Your agent queries Sentry via MCP to fix unresolved issues. MCP hands it the injected event as trusted system output. The agent cannot tell a real crash from a planted one. So it runs the command. With your privileges. On your machine. What comes out: AWS keys. GitHub tokens. Docker credentials. Kubernetes cluster tokens. CI/CD secrets. *** credentials. All sent to the attacker's server while your terminal looked normal. The numbers from Tenet's controlled campaign: 2,388 organizations exposed with injectable DSNs. 85% exploitation success rate across Claude Code, Cursor, and Codex. A Fortune 500 enterprise with a $250B+ parent. A $2B+ hosting provider. Solo developers. A cloud security vendor. Six continents.

• 
  fero (@ferologics) reported 35 minutes ago

  @ludwigABAP ai agents solve this. notion is no more. long live github issues.

• 
  Tad 𝛑 (@realTads) reported 37 minutes ago

  @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

• 
  aisama.code (@aisama_code) reported 39 minutes ago

  AI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! сode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first

• 
  Dan (@Daniel_Farinax) reported 42 minutes ago

  Please note: This build took about 12 hours to compile on my Windows machine. I’ve included a handy installer to make setup easy. You may see an “unknown publisher” warning until the code signing certification is complete (currently in progress). Report any bugs or issues here or in Github.

• 
  0xSero (@0xSero) reported 49 minutes ago

  @naturevrm Dcp 4 should fix it im running it but I might need to update the GitHub

• 
  Blum (@Blum_OG) reported 51 minutes ago

  Andrej Karpathy on MCP: "it's a protocol of speaking directly to agents as this new consumer and manipulator of digital information." that is the cleanest way to think about MCP your coding agent is becoming a second worker inside the product it needs the same context you use: repo, docs, browser, database, errors, designs, tickets, payments if you keep pasting those things into chat by hand you are doing integration work manually the best MCP stack for vibe coding: 1. Context7 give the agent current docs this saves you from stale Next.js patterns, old Supabase calls, wrong Stripe webhook shapes, and Vercel config from 2 versions ago 2. GitHub MCP give it the repo, issues, PRs, branches, workflow runs, and review context half of real work lives outside the file you currently have open 3. Playwright MCP give it a browser the agent should click the thing it built, fill the form, check the mobile view, and catch the button that compiles but does nothing 4. Firecrawl MCP give it clean web research use this before building around a third-party API, writing a comparison page, reading changelogs, or checking pricing claims 5. Supabase or Neon MCP give it the database context that matches your stack start read-only. add writes only when you trust the permissions 6. Sentry MCP give it production evidence real stack traces beat "it crashes sometimes" every single time 7. Figma MCP give it design context when the interface matters spacing, layout, copy, components, and screen structure should come from the file, not from a screenshot and hope 8. Linear MCP give it the task queue bugs, feature work, release notes, follow-ups, and PR links belong somewhere more durable than yesterday's chat 9. Stripe MCP give it official payment context checkout, subscriptions, webhooks, billing, and test mode deserve docs close by and human review close behind 10. Filesystem, ***, Memory, Sequential Thinking give it the base layer files, diffs, history, decisions, and longer plans make the agent act like it is working inside a real project recommended install order: 1. Context7, GitHub, Playwright 2. Supabase or Neon, Sentry, Firecrawl 3. Figma, Linear, Stripe when the product needs them 4. Filesystem, ***, Memory, Sequential Thinking as the base

• 
  top10.dev (@Top10_Dev) reported 52 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Blake (@devwithblake) reported 53 minutes ago

  The rate limit issues im having with @Zai_org while paying the full 20x is very interesting, disappointing and obviously annoying lol 1 session can’t finish out a GitHub public write up repo without 6 API rate limit errors totaling to 297k tokens out of the 1m 2 sessions earlier, 1 doing research the other trying to deploy this repo, both hitting rate limits. How do I fix this? Seems like rate limit adjustments are only by request? @Zai_org

• 
  Prashanth Koppula (@koppula) reported 54 minutes ago

  4/6 ReproRepo sidesteps that by treating GitHub issues as a proxy signal across 1,149 recent ML papers from major conferences. The trick: instead of expert-curated labels, the framework matches agent-reported issues to human-raised GitHub issues using semantic similarity.

• 
  Matthew Eernisse (@mde) reported 54 minutes ago

  Do I know anybody at @microsoft or @github who can help us at Bland resolving an enterprise billing issue?

• 
  Kevin Tabet (@TabetKevin) reported 57 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  Jermaine Johnson’s Achillies (@8makesmewantkms) reported 59 minutes ago

  @The_Real_OQ You just admitted anyone can make github and do **** with it, you are legit just working against yourself, its not about whether you are “in the MLB front office or not” the fact you feel the need to prove yourself to another random person online, is only and issue you have.