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
Créteil	Website Down	4 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:

• 
  Tad 𝛑 (@realTads) reported 5 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

• 
  Harry Tandy (@HarryTandy) reported 7 minutes ago

  Andrej Karpathy: "Neural networks are not just another classifier. They are Software 2.0" 8-step MCP setup for vibe coders: 1. Context7 Give the agent fresh docs before it writes code This saves you from old Next.js, Supabase, Stripe, and Vercel patterns 2. GitHub MCP Let it read the repo, issues, PRs, branches, and CI logs The task should start from real project context 3. Playwright MCP Make the agent open the app after it edits code Click the flow. Fill the form. Check the screenshot 4. Supabase or Neon MCP Connect the database layer The agent should inspect schema before inventing table names 5. Sentry MCP Use production errors as input Stack traces beat “the app is broken” every time 6. Firecrawl MCP Let the agent read current web pages as clean markdown Docs, changelogs, competitors, pricing pages 7. Figma MCP Give it the actual design Spacing, copy, layout, components 8. Linear MCP Turn the work into tickets Tasks, comments, follow-ups, PR links The rule: If you paste the same context twice, wire it into MCP That is how vibe coding becomes a build loop instead of a long chat

• 
  Yiqing Xu (@xuyiqing) reported 8 minutes ago

  @Faylosophe Certianly. Could you file an issue on the Github page?

• 
  Jason Bloomer (@JasonABloomer) reported 13 minutes ago

  @yagiznizipli Pffff, what a scam Let me fix your advert; "show us your github so we can scrape all your repos and train our AI on your code, only for any decent ideas you've had to be taken from you and made ours, then handed off to our legal team to crush you." Sorry, I value my work.

• 
  Xovion Labs (@xovionai) reported 18 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  xjdr (@_xjdr) reported 20 minutes ago

  @tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap

• 
  Maurice Heumann (@momo5502) reported 20 minutes ago

  @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

• 
  Yarchi (@undefinedKi) reported 24 minutes ago

  BORIS CHERNY, THE CREATOR OF CLAUDE CODE, JUST SOLVED AI'S BIGGEST PROBLEM. HE STOPPED PROMPTING CLAUDE AND STARTED WRITING LOOPS THAT RUN IT 24/7 The guy who built Claude Code doesn't prompt Claude anymore. He writes loops, and the loops do the prompting. It's called loop engineering. Here's what it is and how to set it up. A loop is a system that wakes itself up, finds work, does it, checks it, and repeats, while you watch instead of type. In Claude Code it's three built-in commands: > /loop runs a prompt on an interval. Example: /loop every 5 minutes, check for new GitHub issues and handle any that come in. > /goal makes the agent work until a condition you set is true, with a separate model grading the result. Example: /goal build this feature until all tests pass. > /routines are scheduled jobs. Example: every hour, wake up, read the spec doc, and do the next task. The fastest way to start: write a simple task list in a plan.md file, then tell Claude "use the loop skill and work through plan.md one task at a time." It sets up the /loop itself, does the first task, validates it, wakes itself for the next, and reports back when the list is done. You never write the loop prompt by hand. Three rules so it doesn't burn your budget or ship garbage. One, split work across separate sessions instead of looping in one (a long /loop bloats your context and overwhelms the model). Two, use a cheap model like Haiku for planning and a strong one only for the actual code. Three, keep a human checkpoint on anything that ships, never let it run all night unchecked. Bookmark this

• 
  Colin LeClercq (@ThePhilnado) reported 26 minutes ago

  Watch out for this one. A "recruiter" sends a GitHub repo to review, asks you to fix a deprecated Node modules issue, and the second you run npm install a backdoor fires off the prepare script and runs whatever they send. The job offer was the trap.

• 
  andrewthecoder (@_andrewthecoder) reported 27 minutes ago

  @shinemeriz so, I have never used github for anything but *** server and ci/cd...and have never used cursor at all. so, I can't say I get the "great time" angle.

• 
  Kyle Mistele 🏴‍☠️ (@0xblacklight) reported 30 minutes ago

  lots of folks have been talking about loops lately most loops suck here's a practical one we actually use agents suck at writing react react-doctor by @aidenybai is our favorite way to deal with this you could run it and use a ralph loop to fix everything but I'm not reading a +80k/-80k PR (and neither is @dexhorthy) But I can read a small one first thing every morning when i get into the office here's what we do: run react-doctor in CI once daily at 7am (github actions-as-a-sandbox btw) agent picks top 5 issues, fixes them, and opens a PR other CI jobs check for regressions on every PR we can't realistically fix everything at once but we can keep it from getting worse and make it 1% better every day

• 
  Peter Skøtt Pedersen (@PeterSkott) reported 31 minutes ago

  @_Evan_Boyle @_Evan_Boyle can we have the remote github mcp server work for the github copilot app then?

• 
  Moez Zhioua (@MoezZhioua) reported 31 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  Anjula Dwivedi (@HeyAnjula) reported 33 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.

• 
  Leitz 💡 (@mleitz1) reported 33 minutes ago

  Nexus holds all the binaries for your applications. So like jar files, docker images, etc It can also act as a cache for things like Debian binaries So if you need to upgrade all your Debian packages it will download to nexus once and all the server instances will pull the files from your nexus Woodpecker is a cicd application. Like GitHub actions or Jenkins or whatever

• 
  Tatted (@TattedWorks) reported 35 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.

• 
  Matthew P. Grosvenor (@mpgros) reported 36 minutes ago

  @github - "We had a problem finding your email subscriptions." That's because I never subscribed to anything in the first place. Stop sending me your spam I didn't ask for.

• 
  Sap ツ (@Sapronaut) reported 36 minutes ago

  i am having github withdrawal issues, man. its not that serious github, chill.

• 
  Muhammed Mukthar (@MuktharBuilds) reported 37 minutes ago

  @railway_status i am trying for some time i am not able to sign in using any github google or email. i tried both my lap and my phone is thishappening only for me? or any problem in your end

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

  @CAONHTAN1 Having error connecting github

• 
  Ben Vinegar (@bentlegen) reported 38 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Elvis Irhaye (@viii_fn) reported 40 minutes ago

  Is GitHub down or it’s just MTN trying to ruin my career?

• 
  Solomon Neas (@solomonneas) reported 40 minutes ago

  There's a fair number of downloads for Brigade and related repos. I'm dogfooding it everyday but not getting any feedback from users or github issues. I'm doing plenty of tests for how a new user would experience it but I could use more real time feedback. Lmk, I want to improve

• 
  AI Crave (@wecraveai) reported 43 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  Jarrad Grigg (@jarradgrigg) reported 45 minutes ago

  You build stuff and host on GitHub pubically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.

• 
  Matt Teixeira (@matt_teeixeira) reported 50 minutes ago

  I failed after committing to GitHub for 186 days straight. My goal was to ship code every single day of 2026. No exceptions. And for 186 days, I did exactly that. Then a Saturday came and I just... forgot. Was it a vanity metric? Absolutely. But it represented something real: showing up every day, no matter how small the contribution. The upside is that the streak broke, the momentum didn't. 4,215 contributions this year. Every one was a problem solved, a feature shipped, a customer conversation turned into code. Building Deck has been one of the most rewarding things I've done. Every conversation with a product team trying to build better customer-led software reminds me why I started. The goal was never a green square on a chart. It was to never stop building. It's still day 1 🚀

• 
  Apache Superset (@apachesuperset) reported 52 minutes ago

  @J_00_S_T Would love to know more (not all of us use that installation method) if you want to file a GitHub Issue so we can update the docs accordingly.

• 
  Matthew Eernisse (@mde) reported 53 minutes ago

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

• 
  top10.dev (@Top10_Dev) reported 58 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

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 58 minutes ago

  @CryptoPatel Hsiao-Wei’s exit follows a 30% drop in EF-funded GitHub commits YTD (per Santiment). The real shift? Funds now focus 60% on L2 R&D vs 30% in 2022. We track this daily—breaking it down in our quarterly reports. Follow for the data before the narrat...