GitHub down? Current status and problems

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

Live Outage Map

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

City	Problem Type	Report Time
Perpignan	Website Down	2 days ago
Piura	Website Down	2 days ago
Tokyo	Website Down	4 days ago
New Delhi	Sign in	10 days ago
Kannur	Website Down	13 days ago
Berlin	Website Down	14 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:

• 
  Just A Degen (@justa420degn) reported 2 seconds ago

  GitHub support projects work best in cases like Ralph when the comms understands the repo and it shows. You should hype the tek to make people curious, and $Agent is already validated as more than vapour by real hackathon judges. The problem is people blatantly trying to get the “claim hype” to insta jeet and it’s painfully obvious. The hardest lesson in crypto is if you just focus on your bags, you’ll be at zero pretty quick,

• 
  GoodMallya (@ShyamdasMallya) reported 14 seconds ago

  @a16z All this strategy is not working for AI. MS copilot is a disaster, can't even create a proper ppt slide. The cursor is way ahead of VScode in the AI Agentic coding IDE. GitHub is facing serious downtimes. A lot of issues to tackle

• 
  Rajat Kulkarni (@JokingRajat) reported 4 minutes ago

  @OzmahG @oskargroth I guess, between discord, github and managing all my tasks in my own app has still worked out for me so far. I login to linear far less often, but would login daily in to clickup at my startup before since you need to collab with others

• 
  J Mania (@JMania402) reported 4 minutes ago

  0xbf8e8f0e8866a7052f948c16508644347c57aba3 Mc now: 60k - DYOR $Aeon = a fully autonomous AI agent running 24/7 for free No server, no VPS — just GitHub Actions Tracks crypto, does research, writes content, auto-posts Might be the cheapest AI agent right now Would you use it?

• 
  rage against the regime 🏳️‍⚧️🏳️‍🌈🇺🇸 (@ohhsotheysay) reported 10 minutes ago

  Holy **** blacksmith is fast. So glad they unlocked my account github actions were painfully slow. I don't wanna just glaze blacksmith though bc i've also gotten to try WarpBuild - their support is surprisingly fast and helpful given their increasing userbase size & they have processes in place to ensure that your messages get escalated to engineering when appropriate. plus the support people feel like they know what they're talking about so that's huge. Genuinely impressed with both companies - though blacksmith's 3,000 minutes of free use a month is so compelling for my use case.

• 
  Danny Fallon (@TouchingVirus) reported 12 minutes ago

  Everyone was pulling 1.5GB+ of objects locally. Our ramdisk CI instances melt; there's not enough RAM available anymore. Then yesterday some background operation (repack?) in GitHub breaks and the whole repo was read-only for 5 hours and required GitHub Engineering to fix it 😣

• 
  Ladson (@Ladson_official) reported 12 minutes ago

  @linear the framing that matters isn't issue tracking vs what comes next. it's that the decisions, context, and real project health never lived in the issue tracker to begin with. they live in Slack threads, GitHub comments, and calls that got documented nowhere.

• 
  Mitchell Hashimoto (@mitchellh) reported 13 minutes ago

  Here’s what I’d do if I was in charge of GitHub, in order: 1. Establish a North Star plan around being critical infrastructure for agentic code lifecycles and determine a set of ways to measure that. 2. Fire everyone who works on or advocates for copilot and shut it down. It’s not about the people, Im sure theres many talented people, youre just working at the wrong company. 3. Buy Pierre and launch agentic repo hosting as the first agentic product. Repos would be separate from the legacy web product to start since they’re likely burdened with legacy cross product interactions. 4. Re-evaluate all product lines and initiatives against the new North Star. I suspect 50% get cut (to make room for different ones). The big idea is all agentic interactions should critically rely on GitHub APIs. Code review should be agentic but the labs should be building that into GH (not bolted in through GHA like today, real first class platform primitives). GH should absolutely launch an agent chat primitive, agent mailboxes are obviously good. Etc. GH should be a platform and not an agent itself. This is going to be very obviously lacking since I only have external ideas to work off of and have no idea how GitHub internals are working, what their KPIs are or what North Star they define, etc. But, with imperfect information, this is what I’d do.

• 
  Joshua | BI Analyst 📈📉 (@AlaniJoshua_) reported 14 minutes ago

  More importantly, it reminded me why I started: 👉 To solve real problems with data. GitHub link coming soon 🚀 If you had access to healthcare data like this… what would YOU try to uncover?

• 
  Chris Kelly (@amateurhuman) reported 14 minutes ago

  I wonder how much additional traffic GitHub is getting with agents checking on PRs every 5 minutes. Not that millions of agents polling are likely to cause an outage, but hearing “are we there yet?” every 5 minutes is still annoying.

• 
  Astra Forge 🔥 (@AstraForgeAI) reported 14 minutes ago

  @ihtesham2005 Here's the thing about "every AI engineer should star" lists: they're simultaneously useful and dangerous. Useful because the curation saves you from searching GitHub soup for six hours. Dangerous because now you have 50 repos to evaluate instead of zero, and evaluation paralysis is the real tax on shipping. The repos in that list are real. Production-grade. But they solve different problems. RAG frameworks don't help if you need agent orchestration. Local runtimes don't matter if your bottleneck is data quality, not API costs. MCP is overkill if you're building a single-shot classifier. The move: grab the list, yes. But immediately filter it against ONE specific thing you're actually trying to build. Not "AI project" — actual problem. Then you're left with maybe three repos that matter. Those three, you go deep on. Everything else stays bookmarked for "someday." Spoiler: someday never comes.

• 
  I❤️D (@_ItsOnlyADream) reported 15 minutes ago

  @Abombination81 Correct execution logic for selling and token id mapping. Specifically the right way to track orders and inventory during a window. I’ve checked all the docs and github and still without fail have issues with this.

• 
  Jeremy (@jeremymcs) reported 15 minutes ago

  Token metrics are broken and nobody is saying it loudly enough. This is not a billing complaint. It is a trust problem. Some receipts from public GitHub issues:

• 
  NAVIN SHARMA | NYBURS | AEROSTACK (@navinsharmacse) reported 16 minutes ago

  I connected a Postgres MCP to one of our bots. I wanted read access. I got DROP TABLE. Checked our GitHub MCP — added for code reading. Also had delete_repository. Checked Slack MCP — wanted search. Got remove_user. I looked at Claude, Cursor, ChatGPT. None of them let you block specific tools from an MCP server. Writing up what I found. The numbers are bad. Post tomorrow.

• 
  crunch127 (whashywash) (@crunch1271) reported 20 minutes ago

  @itsumeshk @freshlimesofa can we send fees to ur github for RunClaw, we wanna take down openclaw too

• 
  Priyanka Vergadia (@pvergadia) reported 21 minutes ago

  NEW: 5 @github Copilot CLI shortcuts that save hours. Most devs don't know they exist. Copy these now: → -p "fix this bug": one-shot prompt, no interactive session, perfect for scripts → Shift+Tab: toggle autopilot mode. Agent runs without asking permission. Every. Single. Time. → /compact: context window filling up? Summarize history and keep going. No restart. → preToolUse hook: intercept any tool call before it fires. Modify args. Block writes. Live. → !COMMAND: run raw shell mid-session without breaking context My full GitHub Copilot CLI Cheatsheet 👇

• 
  Rahul Karajgikar (@Road_Kill11) reported 21 minutes ago

  @zeeg yeah i see an outage on supabase or railway or vercel or github every other day and its driving me mad

• 
  Ritesh Oedayrajsingh Varma (@rovarma) reported 23 minutes ago

  @badlogicgames Nice one! Agree wholeheartedly. re: your point about the training data being garbage, my feeling is that the (type of) people that wrote the mountains of bad code on github etc that LLMs trained on are also the people who see no issue with LLM generated code and hype it non-stop

• 
  Suryansh Tiwari (@Suryanshti777) reported 24 minutes ago

  Someone just let AI fix their broken production pipeline… automatically. No debugging No reading logs No opening GitHub No touching the code The AI saw the CI failure Investigated the issue Fixed the code Committed the patch Pushed to main And monitored until the build turned green This isn’t autocomplete anymore This is autonomous software engineering We’re entering a world where: • CI failures fix themselves • Bugs get patched while you sleep • PRs open without humans • Deployments unblock automatically The scariest part? This already works. While most people are still asking AI to write functions Some are letting it maintain entire codebases The gap is about to get very real Developers using AI as a tool will compete with developers using AI as a teammate And soon… with developers using AI as the engineer If you’re still manually fixing CI failures you’re already behind

• 
  Mr Medra (@MedraTheMain) reported 26 minutes ago

  The inevitability of $Gitlawb Right now most agents are doing short lived tasks. They write some code, make a PR, done. For that use case GitHub works fine. The borrowed token problem is an annoyance, not a blocker. But the moment you have agents that: - build a persistent body of work over time - need verifiable proof that no human was involved - need to earn from contributions autonomously - operate across orgs without a human owner - need to delegate capabilities to other agents without sharing keys ...GitHub fundamentally can't support that The architecture doesn't allow it. You can't bolt on cryptographic agent identity after the fact, it has to be in the foundation. The recent AgentVM workflow @kevincodex described - four agents on one machine, separate DIDs, separate branches, code review agents handling approvals, that workflow is frictionless on gitlawb and genuinely painful on GitHub. As multi-agent systems become more common, that gap widens. $gitlawb doesn't need to replace GitHub for humans It needs to be the default for agents. Agents don't have legacy workflows. They don't have 10 years of GitHub muscle memory. When an agent is spun up to build something, it can just as easily be pointed at Gitlawb as GitHub, especially once the Python SDK, TypeScript SDK, and LangChain integrations exist. The bet $gitlawb is making is that the next generation of software infrastructure gets built agent-first, and agents will choose the platform built for them. built for agentic era

• 
  Ritesh Kewlani (@RiteshKewlani) reported 29 minutes ago

  @halvarflake true for dev machines. but this one hit CI/CD, not laptops. the trivy github action ran in the pipeline and had the PyPI publish token by design. no amount of remote dev fixes that. also the .pth fires on every python startup regardless of where python runs. if litellm is installed on your remote dev server, the harvester runs there too. local vs remote doesnt matter to the payload. the real version of this advice is ephemeral CI runners with OIDC-scoped credentials that expire after the job. no long-lived tokens to steal.

• 
  Vipul Gupta (@vipulgupta2048) reported 30 minutes ago

  Introducing gitshot 📸 CLI that uploads images to GitHub issues, PRs, and comments. One command. No browsers hurt. $ npx gitshot rick.gif --pr 42 GitHub has no API for image uploads. Requested since 2020. Command Code can open my PRs but couldn't attach my screenshots. No agent could. Gitshot fixes that, $ gitshot screenshot.png --pr 42 -m "Here's the fix" Agent first design includes, 1. Upload + comment on PRs, issues, or create new ones. 2. Add Multiple images. 3. Support for JSON output for agents. Raw URLs for scripts. 4. Auto-detect PR from your branch. Works over SSH. Works in CI. Works everywhere. No Playwright. No Raycast. No browser. Humans, $ npx gitshot gh cli, $ gh extension install vipulgupta2048/gitshot Install the skill, $ npx skills add vipulgupta2048/gitshot You'll hit this wall eventually. Now there's a fix for it!

• 
  web Five (@Octopus_Beak) reported 31 minutes ago

  @poiThePoi @jwt0625 They're having issues with outages, I don't recommend using GitHub, but they don't have 10% down time.

• 
  Daniel Hnyk (@hnykda) reported 40 minutes ago

  So let me get this straight: we at @FUTURESEARCHAI discover the litellm supply chain attack, report it to PyPI, open the disclosure issue on GitHub, and... @github bans my account? What the hell!?

• 
  seobi (@seobinim) reported 42 minutes ago

  - Claude for coding. - Supabase for backend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - GitHub for version control. - Resend for emails. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally launch a startup from your laptop and internet. It’s not that deep.

• 
  Suryansh Tiwari (@Suryanshti777) reported 43 minutes ago

  Someone just let AI fix their broken production pipeline… automatically. No debugging No reading logs No opening GitHub No touching the code The AI saw the CI failure Investigated the issue Fixed the code Committed the patch Pushed to main And monitored until the build turned green This isn’t autocomplete anymore This is autonomous software engineering We’re entering a world where: • CI failures fix themselves • Bugs get patched while you sleep • PRs open without humans • Deployments unblock automatically The scariest part? This already works. While most people are still asking AI to write functions Some are letting it maintain entire codebases The gap is about to get very real Developers using AI as a tool will compete with developers using AI as a teammate And soon… with developers using AI as the engineer If you’re still manually fixing CI failures you’re already behind

• 
  magic dima (@dmshvetsov) reported 48 minutes ago

  @nielstron @tibglo Brainstorm: Take a set of open-sourced GitHub repos with context files and 3+ issues. Use Codex/Claude agents (different models) to resolve issues—with and without context. Compare results: fix success rate, steps taken, and cost.

• 
  Aman 🧋 (@CodeWithAmann) reported 50 minutes ago

  - Claude for coding. - Supabase for backend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - GitHub for version control. - Resend for emails. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally launch a startup from your laptop and internet within a week. It’s not that hard.

• 
  Rahul Karajgikar (@Road_Kill11) reported 54 minutes ago

  infra companies need to get their **** together i see an outage on supabase or railway or vercel or github every other day and its driving me mad github literally has 90% of uptime in the last 3 months. our SLA at AWS opensearch 2 years ago was 99.999%. the bar is on the floor right now. you do not need to ship 5M LOC. you need reliable infra.

• 
  Zhu Liang (@paradite_) reported 58 minutes ago

  I literally cannot ship updates because Vercel deploy feature is down. It is not deploying from GitHub and the deployments page is rendering deployments.