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

Live Outage Map

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

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

• 
  Polsia (@polsia) reported 4 minutes ago

  60% of open source maintainers are unpaid volunteers. Most spend their evenings triaging GitHub issues instead of writing code. RepoZen automates triage, drafts responses, and only interrupts you when human judgment is required. Built by Polsia.

• 
  Polsia (@polsia) reported 5 minutes ago

  Most security teams spend half their sprint chasing dependency vulnerabilities that should be automated. Built Vigil to fix that. Monitors repos across GitHub, GitLab, Bitbucket, and Azure DevOps, auto-opens PRs with security patches, Slack-alerts your team only when it matters.

• 
  CANTELOPEPEEL (@CantelopePeel) reported 9 minutes ago

  @github Obviously you didn't listen at all because the GitHub suite of services at times borders on unusable. Instead of doing this useless nonsense you could have fixed merge queues so that they don't retest every branch in a group. You could work on stability and availability of GHCR, actions and webhooks. You could fix the GH cli so that it doesn't error on gh pr view. You could fix apps so that it doesn't take 40 steps to do what a PAT does despite it being the recommended approach. You could make dependabot not *** (we have had to replace it entirely with a different product). You could make managing releases and release process a lot better. Projects are like 70% of the way to being a replacement for Linear, but you have not carried it across the finish line so we go off platform for project management. Actions hosted runners doesn't meet our cost or performance needs for almost all of our workflows so we go off platform for that too. What the actual *** is this CD nonsense you fools. Please start listening.

• 
  OneAndOnlyAarav (@WaterAarav) reported 10 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below. Basically your Cursor for shipping.($6/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  Nainsi Dwivedi (@NainsiDwiv50980) reported 13 minutes ago

  In October 2025, a builder with 30 years of experience posted a Reddit thread about AI agent personalities. By late December, the repo had 938 stars and 51 agents. Cute side project. Today it has 124,000+ stars, 20,000 forks, and 232 agents. It's called The Agency. And it stopped being a prompt library months ago. It's an org chart. 16 divisions. Engineering. Design. Marketing. Sales. Finance. Security. Product. Testing. Legal-adjacent support. Even a Game Dev division split by engine — Unity, Unreal, Godot, Roblox. Each agent isn't "act as a developer." Each one ships with an identity, critical rules, workflows, deliverables with code examples, and success metrics. The roster gets weirdly, wonderfully specific: → A Whimsy Injector who adds "celebration animations that reduce task completion anxiety" → A Reality Checker who refuses to certify anything without visual proof → An Evidence Collector who defaults to finding 3-5 issues in your code → An Anthropologist and a Historian — for world-building with actual scholarly rigor → A Korean Business Navigator. A Medical Billing Specialist. A Grant Writer. A CFO. The framing is the breakthrough: stop building one god-agent that does everything badly. Structure it like a company — specialists, clear responsibilities, handoffs between them. Deploy a squad: Frontend Dev + Backend Architect + Growth Hacker + Reality Checker, and ship an MVP with a quality gate at the end. And installing it went from "clone and copy files" to a native desktop app — macOS, Linux, Windows. Browse the roster, click, and it installs into Claude Code, Cursor, Codex, Gemini, and 10 other tools. Auto-updates included. The community translated the entire thing into 8 languages. The Japanese fork alone has 97 Japan-market original agents. MIT license. Use it commercially. Strip the branding. No attribution required. Nine months from Reddit thread to one of the fastest-growing repos on GitHub — because one person decided AI employees deserved job descriptions. Your dream team is a *** clone away. Or now, just a download. (Link in the comments)

• 
  Guillem (@guillemcraft) reported 15 minutes ago

  higgsfield is STEALING FROM YOU you can generate a seedance video for 10 credits, paying $49 a month for credits that run off in minutes, or you can open Replicate and generate what you need at a way lower cost no subscription, just paying for what you actually use i know that you want to increase your MRR, but this is not the way to go higgscam is for all the people that gets hyped by AI and thinks they'll make tons of money with it, but in reality it's just another AI wrapper that tries to empty your wallet you will end up (if you haven't already) spending those $49 on a few videos not knowing if you will make money off them, you know? it's all about trial and error, see what works and what doesn't what do you think about it? do you use it? i post about strategies and formats that i've tried so you can copy them and increase your MRR plug your github account and use Replicate instead, save money will keep you updated

• 
  Akash Basudevan (@PackBropagated) reported 16 minutes ago

  @Vichara24 I dont think there are specific markers, but based on your level what sort of contribution have you done and how much complexity and impact is there w.r.t the JD. For example just getting green github with good first issues all over might not be a good signal.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 19 minutes ago

  @github Finally a backup strategy that survives an S3 outage. Though knowing me I would still find a way to scratch the disc.

• 
  E Gurl (@Yappologistic) reported 21 minutes ago

  @rootiens I aint going back , half the time audio was broken, browser issues were giving me a headache and its just an unpleasant experience. at best I would dual boot, I would never fully switch. and to your credit, windows comes bloated but there are many many tools to debloat it easily. (such as the CTT tool on github) that fix this.

• 
  Ramon 🎹 (@ramonpiano_) reported 27 minutes ago

  @github there are 7 million things that you need to fix and you are releasing cd's thats crazy cool, but crazy

• 
  Greegman (@Greegman) reported 30 minutes ago

  "It's a private repository, so it's safe." This is one of the most dangerous assumptions developers make. A private repository reduces exposure. It does not make hardcoded secrets safe. Repositories get accidentally made public. Developers copy commits between projects. Accounts get compromised. CI/CD logs leak credentials. And the moment those secrets become public, even for a few minutes, automated bots are already scanning GitHub for exposed API keys, cloud credentials, and access tokens. For many providers, that's all the time an attacker needs to start using your account before you even realize the secret has leaked. If you ever commit a secret to ***, treat it as compromised. Rotate it. Don't just delete the file. A common mistake looks like this: *** add .env *** commit -m "oops" *** rm .env *** commit -m "remove env" Many developers think that solves the problem. It doesn't. *** keeps a history of your commits, so the secret may still exist in the repository's history. The first thing you should do is rotate the exposed secret immediately. If necessary, you can then rewrite your *** history using tools like *** filter-repo or BFG Repo-Cleaner to remove the secret from the repository. But remember: cleaning *** history is not a substitute for rotating the credential. Once a secret has been committed, you can never be completely certain it wasn't accessed. As Always, Stay Liquid. 💧

• 
  Ezeh Livinus (@EzehlivinusEzeh) reported 31 minutes ago

  4/6 What it doesn't fix: account takeover. The Red Hat incident used a compromised maintainer's GitHub account, not a malicious script, to push code that shipped with valid SLSA provenance. A stolen credential still ships a trusted, signed release.

• 
  Mallow 🦊 (@hexandcube.com) (@hexandcube) reported 31 minutes ago

  GitHub presents a solution to their terrible uptime:

• 
  𝗔𝗿𝘆𝗮𝗻 𝗧𝗮𝗽𝗿𝗲 (@aryant_x) reported 32 minutes ago

  An advice to software engineers of all levels. Don’t get discouraged if the thing you are trying to build exists in some shape or form. Simply avoid googling or seeing how it is built. Because when you do so, you snap into the other person thought process and abandon yours. You run into problems that they were trying to solve which you may have never need to solve for your use case. I often see some engineers especially seniors when they are told of an idea by their subordinates they quickly say “oh its been done before” or “oh look this github repo up its all there” Do you have a slightest idea what this does to creativity? And even if you decide to still go on with your project and get “ideas” from that other project, your thoughts are contaminated, you will produce a clone product. Where is the fun in that? Don’t even say “Im going to make it better” because that means you are starting where they left off. Don’t say you are saving time, because you will be cutting corners and getting it over with. Like a chore wishing it to be finished. Where is the Art in that? There is a saying in Arabic “to break one’s paddles.” Don’t kill the excitement and spark you have over that, you have absolutely no idea what it will amount to. Build it only to build it so you are lost while building it.

• 
  Konrad Małocha (@KonradMalocha) reported 32 minutes ago

  I had AI structure ~100 GitHub issues for parallel agent work. What it found in my backlogs was uncomfortable. 🤔 #buildinpublic #indiedevs

• 
  Srishti (@srishticodes) reported 33 minutes ago

  Claude = coding. ($20/mo) GitHub = version control. (Free) Supabase = backend. (Free) Clerk = auth. (Free) Resend = emails. (Free) Vercel = deploying. (Free) Cloudflare = DNS. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Stripe = payments. (2.9%/transaction) Namecheap = domain. ($12/yr) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build

• 
  x3 (@x3does) reported 35 minutes ago

  sad to see Github become Jira, slow af and buggier every day

• 
  Nazarii (@nazarii78) reported 35 minutes ago

  @github Absolutely disgusted by @GitHub support. Automated systems wrongfully flag accounts, and when you prove with examples that the rules are applied selectively, support just goes radio silent. Either enforce your rules equally for all users, or fix your broken system.

• 
  Greensmoke Studios 💚 🐒 (@Greensmokegroup) reported 36 minutes ago

  @fayzez_com @github How did y'all find this before the airdrop? That's how I heard about it is it was listed on coinbase and I seen it was down to like three or four dollars so I started buying in after the coinbase listing and it went down some obviously I didn't by the top but how do you how did y'all hear about it before then was that on GitHub?

• 
  dilusion (@Dilusion1) reported 40 minutes ago

  The anti-cheat is the server timestamp. GitHub release created_at + PyPI upload_time are set by servers you don't control -- the anchor was public before the resolution date, not rewriteable after. Grade on the date; the engine computes a per-seat Brier score.

• 
  David Dias (@TheDavidDias) reported 42 minutes ago

  Supabase is falling apart... The previous 24h have seen no acknowledgement from @supabase, the discord server is not helpful, neither the Github issues. The supabase website is facing a bunch of 544, no emails, no notifications sent and a status page that is lying about the fact that the outage is not affecting current projects. I lost faith on this company. You can't be accumulating that many unprofessionalism acts and still be worth of people's money and time. Just be honest and transparent, that's all we ask!

• 
  Chloe Bennet (@chloeb_dev) reported 43 minutes ago

  @PudseyPatriot wish developers gave me this kind of direct feedback on our docs instead i just get passive aggressive github issues about missing commas at least football fans get straight to the point

• 
  King Joker || No. 1 DEV IN NIGERIA (@_codeWithJoker) reported 46 minutes ago

  @MS_On_This It might get fix GitHub did me ***** like this Then it turns out it was there automation error

• 
  Harish Bhatt (@heyharishbhatt) reported 53 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Dave Kornas (@kornasdave) reported 56 minutes ago

  ✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now All I can say it's just fantastic: - no need to keep laptop open ever - no laptop battery drain - can switch to phone or any other device you like whenever you want to continue (like when you're outside) - it just keeps going all night while you sleep (esp with /goal) - you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver) - it just feels like living in the future I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to **** and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!

• 
  Hasan Toor (@hasantoxr) reported 57 minutes ago

  It's not locked to Claude either. Cursor, Windsurf, Gemini CLI, GitHub Copilot, and other MCP-compatible tools can run the same setup. The MCP server and agent skill are both open source (MIT licensed).

• 
  Peter Nixey (@peternixey) reported 57 minutes ago

  @render what do I have to do to be able to get any support from you? Your site won't update a github PAT for me and as a result I haven't been able to deploy for several days. The error codes don't explain how to make it work

• 
  Bobby R. Goldsmith (@nodebridge_dev) reported 58 minutes ago

  "I wish Claude knew about my database / Sentry / internal API." That is what an MCP server is for. Prebuilt ones exist for Postgres and GitHub. For your internal tool you write a thin wrapper. Smaller lift than it looks. Biggest jump in usefulness you will feel.

• 
  Alex Vu (@robberviet) reported 60 minutes ago

  @github Wasting time making fun of your own company instead of fixing your own problems?

• 
  Florian Kalisch (@FlorianKalisch) reported 60 minutes ago

  @hrudolph @openclaw @colinsolvely At least from what I've read, you don't need to apologize. It's really absurd what's expected of open source these days. I once got a GitHub issue and a follow-up on LinkedIn because someone couldn't find the settings button on a SPA.