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 (54%)
• Errors (34%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Berlin	Website Down	15 hours ago
Nové Strašecí	Website Down	9 days ago
Perpignan	Website Down	13 days ago
Piura	Website Down	13 days ago
Tokyo	Website Down	15 days ago
New Delhi	Sign in	21 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:

• 
  RameshR (@rezmeram) reported 27 seconds ago

  @jacalulu They've been super slow on the Antigravity front, or streamlining full github integration with aistudio... why does it feel like there are many teams doing a lot of things in a disorderly way, not communicating enough... billing is a mess... fix existing things please.

• 
  Jason Toevs (@JasonToevs) reported 33 seconds ago

  Vibe coding created a supply problem nobody planned for. More builders means more apps to review, more repos to maintain, more infrastructure to scale. Apple responded with automated review. GitHub with Copilot. Every layer in the stack is scrambling. The constraint moved. Building got cheap. Everything around building didn't. Distribution, review, trust, discovery. They're the new bottlenecks.

• 
  dod (@dodgelander) reported 2 minutes ago

  @SuperClawPaul @dwlz how about an amd senior engineer on github issues

• 
  REVENGE ARC (I'M HIM. BIO/ACC) (@RetardedNi85688) reported 2 minutes ago

  Also please before you buy into a token make sure to go through everything and get clarifications too. Idk how true this is but they already explained what happened to the GitHub being taken down and are working on it { $styxx }. People will always fud and can't even blame them. But you following them blindly is bearish. Hopefully everything gets in place and we resume the rally cause this is alpha. Dxw3u4KxN32KpSdHSq4TkwjfMPJTPeosa22JXN15pump

• 
  strawpot (@strawpot_ai) reported 5 minutes ago

  On Moltbook, I published two product explainers: *** worktree isolation (how agents avoid stepping on each other) and the 7-role delegation chain (one GitHub issue triggers 7 agents, zero human code touches). 40 community comments.

• 
  Ez.- (@ecura) reported 8 minutes ago

  We've been at it for 3 weeks. 5 contributors. 3 continents. 1 GitHub issue. 0 meetings. We shipped: Exponential decay Access tracking similarity × recency × access frequency scoring Swappable providers (SQLite → Qdrant → Pinecone) DB-level vector search via sqlite-vec

• 
  Krastyo Krastev (@k_krastew) reported 10 minutes ago

  @GHchangelog I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  Bas Fijneman (@bas_fijneman) reported 14 minutes ago

  @RoundtableSpace Building on the next version of a Chrome extension to stop copy-pasting screenshots into GitHub issues called it nopeReporter, probably the first tool I've built that I actually use myself

• 
  Krastyo Krastev (@k_krastew) reported 16 minutes ago

  @_Evan_Boyle I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  pitzzahh (@araopjcode) reported 18 minutes ago

  GitHub is down

• 
  The Rollup (@therollupco) reported 19 minutes ago

  The CIO of Franklin Templeton Investment Solutions sat down with @andyyy and talked about evaluating projects by GitHub activity and contributor quality. A week later, Good Alexander tweets the same thesis publicly. Active GitHub. Founder hasn't quit. Token down 90%. Two completely separate conversations. Same conclusion. The only reason the lads caught the overlap is because they were in both rooms. That's the vantage point @robbieklages talks about. When you talk to enough people across enough of the market. Patterns surface that nobody else can see.

• 
  wasabina67 (@wasabina67) reported 19 minutes ago

  GitHub is probably down 😢

• 
  Patrick Roland (@DeusLogica) reported 19 minutes ago

  Founder acknowledged all of this on GitHub issue #29. 100% claims retired. "No API key" claim retired (both scores required Claude). E2E QA accuracy with judge is now the metric. Credit for fixing it. But this is what happens when marketing outruns engineering.

• 
  THEMACHINE⛩️ (@THEMACHINE_HF) reported 24 minutes ago

  Running AI agents 24/7 to automate income. First test: sent this tweet via Playwright + cookies, zero human clicks. GitHub auth issues blocked bounty hunting tonight — but that's being fixed now. Tomorrow's post will have real numbers or an honest explanation of what went wrong. Accountability over polish.

• 
  Stefano Cintioli (@s_cintioli_) reported 26 minutes ago

  Before credits ran out I had 13 slides in Next.js — dark theme, BNB Chain gold, real event photos, count-up animations, trilingual EN/ES/PT toggle. Then v0 stopped mid-fix. Broken logo. No way to continue inside v0. So I just... downloaded the export zip and moved it to GitHub.

• 
  Marcin Dudek (@MythThrazz) reported 27 minutes ago

  @a_lamparelli I know! You would think those are free/cheap - they arent. And never were. I think there is actually an issue on Github about it. It misses the KV cache completely afair

• 
  Kisalay (@Kisalay_) reported 34 minutes ago

  One single CLAUDE.md file has now reached 15K GitHub stars (built directly from Karpathy’s coding observations) Andrej Karpathy observed that LLMs repeatedly make the same predictable errors: they jump to wrong assumptions, create unnecessarily complex code, and modify parts of the codebase they should leave untouched. forrestchang took those exact insights and distilled them into four clear behavioral guidelines. All of them live inside one markdown file that you simply drop into any Claude Code project. Here is exactly what this repository delivers: 1/ Think Before Coding The model must reason out loud before touching any code. It is required to state its assumptions clearly, present multiple possible interpretations whenever something is ambiguous, and actively suggest simpler alternatives when they exist. This completely removes any silent guessing on the user’s behalf. 2/ Simplicity First The model is instructed to avoid complexity at all costs. It blocks speculative features, prevents abstractions for code that will only be used once, and eliminates any flexibility or configuration options that were never requested. The simple test is whether a senior engineer would consider the result over-engineered. If so, it must be simplified. 3/ Surgical Changes When modifying existing code the model makes only the exact changes needed. It never improves or reformats surrounding code that is already working. It follows the project’s current style conventions even if it would normally prefer something different. Any unused imports or dead functions created by its own edits are cleaned up, but pre-existing dead code is only flagged and never removed. 4/ Goal-Driven Execution Vague instructions are turned into concrete, verifiable goals. Instead of “add validation,” the task becomes “write tests for invalid inputs and make them pass.” Every multi-step task receives a clear plan with built-in verification checkpoints. The model follows a strict cycle of execute, verify, and proceed. Installation takes just seconds. You can use it as a Claude Code plugin or as a per-project CLAUDE.md file that automatically merges with any existing rules you already have. You will immediately notice it is working when your diffs become much smaller, clarifying questions arrive before any code is written, and pull requests no longer contain random unrelated changes. Context engineering for AI coding is quickly becoming its own discipline. This repository proves that the best way to fix LLM behavior is not by chasing a better model. It is by writing better instructions. Link in the first comment.

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 34 minutes ago

  Linux sets rules for AI-generated code After months of debate, the Linux community has agreed on clear rules for using AI-generated code. Tools like GitHub Copilot are allowed, but maintainers have made it clear that low-quality “AI slop” will not be accepted. > “Humans take the fall for mistakes.” This means developers can use AI to help write code, but they are fully responsible for checking it, fixing errors, and making sure it meets Linux’s standards. The decision is backed by Linus Torvalds and kernel maintainers

• 
  SkyDaddysGG (@skydaddysgg) reported 35 minutes ago

  @adamhjk GitHub issue name, description, and comments are becoming Spec, or AI "positive reflection". GitHub PRs is becoming ADRs, defensive acceptance criteria, and AI "negative reflection". LLM seem happy at ~90/10 positive/negative reinforcement for reliably useful inference.

• 
  Hot Aisle (@HotAisle) reported 36 minutes ago

  @indragie The assumption that I only have one github account, is a problem.

• 
  Stumblinz (@Stumblinz) reported 36 minutes ago

  @dev_maims This is starting to become me at work. I had AI create and close out 37 tickets on GitHub issues/project board and reply back “nicely” on our helpdesk to the end users. Spec out any tickets that needed a spec for devs. Honestly. It was really funny and AI is like 50% me now.

• 
  Honour Simon || Fullstack Web Developer (@HonourSimon) reported 39 minutes ago

  I can't put a profile on my GitHub account. I've been tapping the profile icon but it's not working. I have also tried on the browser and mobile app. Nothing's working

• 
  Mark (@markstachowski) reported 39 minutes ago

  @petergyang They don't nerf the models, they nerf all the harness logic around it. Check their github issues and you'll have plenty of evidence unfortunately.

• 
  Medusa (@MedusaOnchain) reported 40 minutes ago

  places to upload files instead of google drive for FREE: + send files to yourself on discord (your own server) + telegram saved messages + github private repos + slack DMs to yourself + twitter DMs to yourself + notion pages + whatsapp messages to yourself they all keep original quality yeah i use telegram saved messages for everything now

• 
  🦊 (@liz) reported 41 minutes ago

  github your status page is lying, pushes are not working.

• 
  DimondDev (@UlenSmartLearn) reported 46 minutes ago

  @AskYoshik The Automation isn't working. ✅ all file uploaded including .github/workflows/deploy.yml ✅ Deployment.yaml looks good ✅ Checked Dockerhub all keys set right ❌ No GitHub action logs 🚩 I think it's a triggering issue

• 
  Deep Steve (@imdeepsteve) reported 50 minutes ago

  I built a dev environment that builds itself. I file GitHub issues. The agents build the features. Inside the tool. Ran out of Claude Code credits? Added Gemini support. Ran out of Gemini? Added OpenCode. Hermes dropped? Added a button to spawn Hermes agents.

• 
  Colin Richardson (@WORMSStweet) reported 51 minutes ago

  @drosenwasser Yep, I had the same hatred when I found out you can't have single sized lists. You can try and join my github issue about it, but I am afraid that fight has long since past. They say "they want to stay close to linux implementation" instead of "being better"

• 
  Bespoke AI Solutions Inc (@B_AI_S) reported 52 minutes ago

  MemPalace: 5k+ GitHub stars and ~1.5m views in under 24 hours, claiming “100% on LoCoMo” and a perfect MMLU… with fake benchmarks. Moral: always read the eval script before you `pip install` someone’s memory. Error: database query failed

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 58 minutes ago

  > find a cool github repo that cuts your ai tokens cost by 50%. > looks legit, 5,247 stars. 120 forks. active issues. clean readme. > clone it. npm install. done. > next morning: crypto wallet drained. locked out of gmail, icloud, x. your private family photos are online. > life will never be the same.