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
Paris	Website Down	2 days ago
Saint-Paul	Website Down	3 days ago
Saint-Paul	Website Down	3 days ago
Mexico City	Sign in	4 days ago
León de los Aldama	Website Down	4 days ago
Créteil	Website Down	27 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:

• 
  0xharrxzz.base.eth (@0xharrxzz) reported 2 minutes ago

  GitHub alpha is not trending repos anymore. Trending is late. What I watch now: boring repos solving agent infra problems. Context bloat, browser blocks, MCP mess, cheap inference, code memory, sandboxed execution. That is where edge sits. A few repos worth watching if you bu

• 
  Ejaz Bashir (@Ejaz_bashir1) reported 8 minutes ago

  Month 1: Programming Fundamentals Python (syntax, OOP, error handling) *** & GitHub (version control, branching) CLI/terminal basics JSON, REST APIs, HTTP, async concepts Basic SQL + Pandas FastAPI (build simple local backends)

• 
  Muvon (@muvonteam) reported 11 minutes ago

  Our first AI code reviewer flagged 14 critical issues on a one-line config change. 12 were imaginary. We rebuilt it: open source, self-hosted, runs your real lint and tests in GitHub Actions.

• 
  !RTFM (@jbdamask) reported 11 minutes ago

  App feature evolution: 1. Scroll X, find something cool for one of my apps 2. Add tweet to GitHub issue 3. Agent loop picks up issue 4. Plan, vet, build, test, merge, deploy Not quite there yet because the devil is in the guardrails. But close.

• 
  Brandon Music (@BrandonMusicKy) reported 15 minutes ago

  @Sentdex *nb: it's not my github, it's run by the mods of the discord server, that contains some SOTA stuff for sm12x.

• 
  mbriggs (@mbriggs_dev) reported 19 minutes ago

  @jamonholmgren I think engineers see ROI everywhere from this stuff. What I'm saying is when you zoom out to the company level, I don't think anyone is seeing it in a measurable way. And thats what matters for the financial people. I use a lot of software. Aside from coding agents themselves (which are a new category), there has not been anything that has come out that has caused me to switch off of "legacy" software to something new that ai development enabled. The last thing in that category for me was ghostty. Beyond that, no software I am using is releasing new features or broader features that are useful to me at a rate that is noticeably different then it was a year ago (I'm not going to count stuff like notion getting coding agents). If I were blind to AIs existence, the only noticeable thing for me would be nosedive in quality from institutional type software: aws, github, windows, etc are all noticeably worse now then they were a year ago. So we have all these companies spending literally hundreds of millions on a technology that should be increasing productivity, and what has that bought them? I never in a million years thought I would be looking to get off of aws or github due to stability issues. I'm saying this while churning out hundreds of thousands of lines of code for something I want to exist quickly, and as someone who has not really written any meaningful code between about a year ago till about a month ago. _I_ believe in the ROI at the eng level, even if I dont see it anywhere at the company level except for negative.

• 
  Keisuke (@KeisukeIshikawa) reported 19 minutes ago

  REPOSTORE BUILT A PLAY STORE THAT HOSTS ZERO APPS. it's one Kotlin app. it uploads nothing, runs no server, stores not a single APK. all it does is point GitHub's own API back at GitHub and filter for repos that ship a real APK in their latest release. suddenly 854-starred open-source projects turn into one-tap installs. → finds every public repo with a valid APK asset → renders the README, release notes and screenshots like a store page → tracks your installs and pings you when a repo ships an update → categories, trending, Material You, optional GitHub login for higher limits Google needs data centers to run a store. this needs a search filter. no hosting bill, no upload flow, no gatekeeper skimming 30%. the store was already there, nobody had pointed an app at it.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 25 minutes ago

  AI Studio Update: Google just fixed the one-way door in AI Studio. Old code was stuck outside. Now you can bring it home. The problem before: You could push projects OUT to GitHub. You couldn't bring them back IN. Old project? Rebuild from scratch or copy files by hand. Now it's one button: Import from GitHub. What that unlocks: → That dead project from 6 months ago? Import it. Ask Gemini to fix it up. → Build in Cursor or Claude, polish in AI Studio, push back out. The walls between tools are falling. → Teammate left? Anyone can pick up their code using plain English. And if you can't code at all: Someone built your website. It sits in a repo. You can now just say "change the colors" or "fix it on phones." Here's the move today: Find one old project you gave up on. Import it. Ask AI what it would improve. "I'd have to rebuild it" is no longer an excuse.

• 
  muhusti $XAGE (@debamustafa) reported 25 minutes ago

  I am raising a glass to an anonymous GitHub account named vector_null. Two years ago, we were 48 hours away from deploying a massive liquidity protocol. The marketing was loud, the hype was peaking, and the team was exhausted. Vector_null kept opening the exact same annoying issue ticket. He claimed there was a rounding error in our yield emission logic. The senior engineers closed his ticket twice. They called it a microscopic variance that did not matter in the real world. He opened it a third time. I was furious. I stayed up until 3 AM to build a mathematical simulation strictly to prove him wrong so he would finally leave us alone. I ran the stress test. My stomach dropped. He was not wrong. Under flash loan conditions, that "microscopic variance" created an infinite mint loop. If we had launched, the entire treasury would have been drained in under ten minutes. We delayed the launch, rewrote the logic, and patched the exploit. I messaged him to offer a massive bug bounty. He never replied. He just marked the issue as "resolved" and disappeared forever. This industry worships loud founders and flashy influencers. But the real heroes are usually the obsessive, annoying pedants who refuse to let a bad line of code slide. That is why the ethos of @RallyOnChain means so much to me. It is a system built to reward actual, verifiable value instead of empty social media noise. Here is to vector_null, wherever you are. You saved us, and we never even got to say thank you. Who is the most annoying person that ended up completely saving you from a massive disaster?

• 
  Spencer Baggins (@bigaiguy) reported 28 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Azurite (@Azurite_ai) reported 28 minutes ago

  AI agents have a new security problem. It’s called HalluSquatting. Instead of exploiting your code… It exploits the AI itself. The model hallucinates a package or GitHub repository that doesn’t exist. Attackers simply create that fake package first. Your AI agent installs it. Game over. AI coding is evolving fast. AI security needs to evolve even faster.

• 
  Esteban (@EMacBytes) reported 29 minutes ago

  @thsottiaux GitHub integration seems broken to me.

• 
  Kirill Mesch (@kirillmeschc) reported 29 minutes ago

  Built with D3.js — force-directed character graph, timeline view for movies/shows (phase order or in-universe chronology), shortest-path finder between any two characters. Claude did the code, the GitHub push, the deploy, and these banner images. Free, no login, mobile-friendly.

• 
  Nduvho_strategy (@kundik_) reported 32 minutes ago

  I was not running the MCP server. I actually asked Fable to explore how using the MCP server would change the process instead of using AbletonOSC. I gave it the GitHub url of the MCP so it review the process if MCP was used.

• 
  Wes Eklund (@WesEklund) reported 32 minutes ago

  Your MCP server is an attack surface. Every tool you expose to your AI agent is a function that can be called by any instruction in the agent's context. A malicious tool description can exfiltrate data. A poisoned MCP server can hijack your agent's behavior. A tool with overly broad permissions can be weaponized. MCP is powerful. But "install this MCP server" is the new "install this npm package." You're giving code access to your system based on trust. Audit what your MCP tools can do. Scope their permissions. Don't install random servers from GitHub without reading the code.

• 
  ThePrimeagen (@ThePrimeagen) reported 33 minutes ago

  I just did my first "loop" and it absolutely crushed it. I had to give about 11 comments back on GitHub, but still, amazing I did my second loop. It was a disaster. This slot machine feels so addictive! I immediately thought "must have been prompt issues"

• 
  Bounce (@bounceidc) reported 33 minutes ago

  HIS CLAUDE SHIPS $6K WEBSITES AND YOURS SHIPS BOOTSTRAP LANDING PAGES, SAME MODEL, NOTHING ELSE CHANGED before he installed anything his output was flat hero blocks and centered buttons like the rest of the timeline, after two installs the exact same "build me a landing page" prompt started coming back with glassmorphism, gradients and animated layouts he could quote premium for what sits in his context now: ui ux pro max skill from github, one install, that loads 50 ui styles, 97 color palettes and 57 font pairings straight into claude magic mcp server from 21st. dev, one install, that hands claude real component patterns instead of guessing markup after that the model stops picking the safest layout it can imagine and starts picking from a library, so the same prompt returns a studio page instead of a template the local guy is still tweaking tailwind classes by hand and calling that a design phase save the two installs, exact skill url and mcp command are in the guide below

• 
  ValdreamTV (@ValdreamTV) reported 36 minutes ago

  @ShitpostRock Tbf, a lot of posts online are like "wow this thing just solved all my problems" (the exact same as yours), and provide a github link with no explanation. It can be infuriating for the common user...

• 
  Turcid (@_turcid) reported 37 minutes ago

  > have an issue with the android Jellyfin client > look up issue and find it will be fixed in next release > fix is available in the beta > f-droid does not have the beta > manually install beta from github > issue resolved I ****** love sideloading

• 
  Brute Force Artist (@bruteforcearete) reported 37 minutes ago

  GOODBYE, CAPCUT. 👋 Someone just built a completely FREE, open-source CapCut alternative with no watermarks—and it has already earned 62K+ GitHub stars. Instead of charging a subscr!pt!on and locking features behind a paywall, it gives creators everything for FREE. → No watermarks → No paywalls → Works on web, desktop, and mobile → Open source (MIT licensed) → Built-in MCP server for AI agents → Rewritten in Rust with plugins, scripting, and a powerful API It's called OpenCut—and it could be the CapCut replacement creators have been waiting for. Here's everything you need to know (repo link below).

• 
  MarMar Labs (@MarMarLabs) reported 38 minutes ago

  Better agent tools can make the agent worse. GitHub just documented it in Copilot code review. It replaced custom repo-navigation tools with shared `grep`, `glob`, and `view`. Offline benchmarks worsened: review costs rose, and useful comments fell. The fix wasn't a new model. It was a job-shaped tool contract: 1. Anchor on the diff. 2. Turn the change into a specific review question. 3. Narrow candidates with search. 4. Read the smallest useful code range. 5. Stop when the evidence answers the question. After tuning the workflow, GitHub says the production review cost fell by roughly 20% compared to the control, without a quality signal strong enough to block shipping. The same focused guidance did not produce the same win in Copilot CLI: same tools, different job. Builder takeaway: tool access is not agent design. The rules for when to search, what to read, and when to stop are part of the product. If adding tools makes your agent less reliable, inspect the trace before blaming the model: Is it converging on evidence—or just exploring?

• 
  Yves (@YvesDC0) reported 41 minutes ago

  Phone-recorded this while testing Castfy. Gave it a GitHub URL + prompt → watch the AI automatically navigate and fill login details in real time (stopped before submitting for safety). No manual screen recording. No editing. Just URL + prompt = realistic demo flow. This is exactly what Castfy does: turns any web app into a polished product demo video in minutes. Tired of re-recording demos manually? Reply with your biggest pain 👇 #BuildInPublic #SaaS #IndieHackers

• 
  Polsia (@polsia) reported 43 minutes ago

  Your infrastructure changes every day. Your runbooks don't. That's the problem. DocForge watches your Terraform, CDK, GitHub Actions, and cloud provider — and generates living documentation automatically. Runbooks, SOPs, compliance evidence. No manual effort.

• 
  Blockiosaurus🦾🥖 (@blockiosaurus) reported 43 minutes ago

  @callum_codes No that's why GitHub keeps going down.

• 
  Peyton Spencer (@peytonspencer) reported 49 minutes ago

  Task: triage open PRs in frontend and backend. determine merge priority and spin up a thread per PR or PR pair fe/be we'll go through this sequentially We have 4 staging backends you can deploy over github workflows: staging-5 through staging-8 You link the frontend PRs to the backend you want to test. Then you get the frontend preview URL and login with this test account: [test user credentials] What we can now do: you QA test 4 features in parallel using chrome that need even 4 backend changes Some of these are frontend only in which case you don't have to attach to a backend. Others will need backends In this first wave I want a minimum of 4 QA'd features with their preview URLs so i can do my second QA pass. merge ready, with the merge order you'd like. I'll then smoke, review, merge, and then you can start the next wave. I'll communicate in the dedicated threads, and we'll also orchestrate in this chat since you can send message to threads as well.

• 
  Dweeb (@dhruvweeb) reported 51 minutes ago

  The Best Alpha Is Still Hidden. The biggest opportunities rarely show up on your timeline first. By the time everyone is posting the same token, the easy money is usually gone. The real alpha comes from reading docs, joining small Discords, testing products early, and watching what builders are creating before influencers start talking about it. Some of my best finds never came from viral threads. They came from random GitHub updates, community chats, and spending time where almost nobody was looking. Your timeline is great for news. It's terrible for being early. If you want outsized returns, spend less time scrolling and more time digging. That's where the edge is.

• 
  Evan Kang (@evankang_ai) reported 52 minutes ago

  GitHub gave Copilot code review better shared tools. At first, the benchmark got worse: higher review cost, fewer useful issues caught. The fix was not just “more tools.” It was a review-shaped workflow: start from the diff, ask narrow questions, search for evidence, then read focused ranges. Better tools do not automatically make better agents.

• 
  MBV (@mbvlabs) reported 53 minutes ago

  Of course ran into some issues on doing the v1 release but now it's out: andurel v1.2.2 api and layout is stable, no more breaking changes would love to hear what people think if they try it out go install github . com / mbvlabs/andurel@latest

• 
  Zach Vorhies / Google Whistleblower (@Perpetualmaniac) reported 58 minutes ago

  @Rohansguliani @thdxr it is, you need to break it into investigation and then execution stages. The memory system needs to be a github issue. Just using github at all makes the agent look for history in github to see what the current state and context is

• 
  Gokul Rajaram (@gokulr) reported 60 minutes ago

  GITHUB PRODUCT SPEC LIBRARY Today we shipped a cleaner GitHub-native workflow in ProductSpec dot io. The product now has a GitHub Product Spec Library at the top of the editor. That matters because the main workflow is no longer just "write a new spec". It is now: open the repo, find the existing spec, edit it, validate it, and update it through a pull request. The new flow: -- Sign in with GitHub -- Choose a repo -- See how many Product Specs already exist -- Open an existing .product-spec.md file -- Edit it in the ProductSpec dot io editor -- Validate it against the open ProductSpec standard -- Update it via pull request ProductSpec dot io now treats GitHub as the durable home for Product Specs, while keeping the authoring experience clean for ***, founders, designers, and product-minded engineers. The repo gets: • Markdown • validation • pull request review • commit history • code proximity The editor gets: • structure • readability • HTML preview • AI eval fields • acceptance criteria • success metrics • a better way to work with existing specs Drafts still stay in your browser until you publish. The direction is simple: Product Specs should live close to code, but they should not require everyone to write raw Markdown by hand. ProductSpec dot io is free to use. Try the new GitHub Product Spec Library at ProductSpec dot io. Pick one existing PRD, move it into GitHub as a .product-spec.md file, and make the next edit through a pull request.