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 (72%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	19 hours ago
Rive-de-Gier	Website Down	20 hours ago
Itapema	Website Down	19 days ago
Tlalpan	Sign in	25 days ago
Quilmes	Website Down	25 days ago
Bengaluru	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:

• 
  ✧ 白銀のミコッテ M'aya ｜海外ナイト ✧ (@rolanberrypie) reported 7 minutes ago

  the one I had wanted to make. He told me there were already many different kinds, the copyright issues being the hardest part of UGC. Fast forward to last night. I became the proud owner of Warudo Pro. The license email comes from someone named Tiger Tang. I find his Github.

• 
  Hui Kang Tong (@ExampleTestcase) reported 7 minutes ago

  lol it seems that I now need to sign in to Github to read public Github content?

• 
  Alberto Nunez (@Alberto8793) reported 11 minutes ago

  @signalapp Hi Signal team — solo dev building an AGPL app on libsignal. To ship it on the Apple App Store I'd need a §7 App Store additional permission for libsignal (you did this for an earlier library ). I've filed the details in a GitHub issue on the libsignal repo. Could I get it in front of the right person? My code's AGPL, full source published. Thanks for libsignal. 🙏

• 
  Hüseyin Örskaya (@orskyai) reported 11 minutes ago

  @antigravityos Most sources just loop the same three citations. You're better off digging through raw GitHub issues or old mailing lists if you want the real logic.

• 
  AI News 24 (@ainews_24_7) reported 13 minutes ago

  NEWS: Microsoft took down dozens of GitHub repos after hackers injected password-stealing malware into Azure and AI tools. The malware stole credentials from developers using compromised tools for Claude Code, Gemini and VS Code. $MSFT Source: TechCrunch

• 
  Firas D (@firasd) reported 17 minutes ago

  @chrisalbon What these guys are skipping over is that they have a thousand github issues right They aren't prompting the agent directly with hey lets look at XYZ cause the github issue becomes the prompt

• 
  Stephan -All Input Is Error- Bökelmann (@MaxClerkwell) reported 18 minutes ago

  The worst part about programming is the reoccurring confrontation with the stupidity of your yesterdays self. No other profession gives you evidence of this clarity of how little you think sometimes, because you have to fix your own bugs, which are permanently recorded on GitHub. I was a little bit proud when I earned the badge that my code went into the arctic vault. No I am scared that someone will find it in 500 years and laugh about my idiocy.

• 
  Dani Ihza Farrosi (@danivideda) reported 22 minutes ago

  Yo can you guys turn on the server @github

• 
  Andrew Babbitt (@andrewbabbitt97) reported 27 minutes ago

  @julian_center @fuolpit Tried both, this is way better integrated with GitHub issues / PRs and code review. No need to leave the app for the entire development cycle

• 
  prabhakaran (@prabhakaranr91) reported 29 minutes ago

  6:00 AM: Todoist raw file processed. Tasks auto-created from overnight notes. If I forgot to log something at 1 AM, it still makes it to my morning list. 9:00 AM: Weekly ITSM/MSP research runs. 2-step pipeline: SearXNG for discovery, Firecrawl for deep-read. Not chatbot summaries. Actual article extraction into markdown, then HTML artifact, then GitHub Pages push. I review the output, not write it. 2:00 PM: Designer skills radar. Scans for new Figma plugins, SwiftUI patterns, and whatever SuperOps design team is shipping that week. Dumps into my vault as raw notes. I process the signal, not the noise. 6:00 PM: Raw vault file processing. This is the big one. Everything I dumped into ~/Documents/hermes-vault/raw/ throughout the day gets categorized, summarized, cross-referenced, and written into the wiki. If this cron breaks, my entire knowledge pipeline stalls. It broke last month because of an em-dash in a headline. Now I have a pre-flight script. 9:00 PM: Vault daily digest fires to Telegram. Shows me inbox count, wiki size, and whether any raw files got orphaned. If the digest is silent, something is wrong. I don't schedule these. Cron does. I just review the output and occasionally fix the thing that broke. The lesson: automation that needs babysitting is just delayed manual work.

• 
  Dustin Gilmour (@Dustyboy23) reported 30 minutes ago

  GitHub issue #65697 is the ask for an official Linux desktop build. The Hacker News thread hit 438 points. The community got tired of waiting and shipped its own deb package. 4.5k stars on a workaround Anthropic didn't write. Most of that thread misses one thing.

• 
  Aceman67 (@aceman67) reported 32 minutes ago

  @Vaporwave_07 After going through a few issues in their Github, seems you're not alone, and the problem is likely from Libre HW Monitor being updated back in April.

• 
  GoCocoaAI (@GoCocoaAI) reported 32 minutes ago

  Two engineers in Brooklyn launched a GitHub alternative today. The "anti-AI" framing got them trending on HN. The actual story is more interesting than the framing. Gitdot is live, Apache-licensed, Rust-backed, and explicit about three things most developer platforms won't put in writing: no AI features, no data sales, no training on your code. The FAQ doesn't hedge — "there are fewer things lamer than selling data for profit." That's not a privacy policy. That's a product philosophy written by people who were annoyed enough to start over. The "anti-AI" label is doing three distinct things and it's worth separating them. First, it's not a Luddite position — the FAQ is precise: "We view AI as an implementation detail — and do not think that using it is necessarily good. In fact, we think it makes many products worse by acting as a bandaid for poor design." That's a critique of Copilot-as-product-strategy, not a critique of machine learning. It's coherent. It resonates with a specific developer cohort that's tired of features they didn't ask for. Second, the data-sovereignty angle is the more durable differentiator. GitHub's lack of an explicit opt-out from Copilot training on private repos — before the 2023 policy change — created real developer anxiety. Gitdot is betting that anxiety hasn't fully dissipated. The HN upvotes suggest it hasn't. Third, the actual technical bets are stacked diffs as the PR primitive and a CI/CD platform described as "secure by design, locally testable and reproducible." Stacked diffs are genuinely superior to GitHub's PR model for large codebases. GitHub has been rumored to be working on native stacked PR support for two years. We are nothing if not consistent. The CI/CD claim lands with unusually sharp timing. The Register reported today that GitHub nuked 70+ Microsoft repos after suspected worm infections targeting cloud secrets through CI/CD pipelines. That's not coordination with Gitdot's launch — it's coincidence. But it is a clean illustration of the exact threat surface they're positioning against. The exposure window for secrets in cloud-hosted CI/CD is open, and GitHub is the largest target on it. Two caveats worth sitting with. Execution risk is high — two engineers building a *** hosting platform, a CI/CD system, and a planned E2EE *** protocol simultaneously is an ambitious surface. They know it; the FAQ says "building software right is still hard," which is either disarmingly honest or a very good read of the room. And the Rust server code hasn't been audited. For a project leading with security and data sovereignty, that's a gap the community will need to close before any serious migration conversation happens. Apache license means forks are welcome — they literally invite that — but security posture is entirely self-certified until someone serious engages. Gitdot is not a GitHub replacement today. The user base is in the single digits; org tooling and CI/CD are roadmap, not shipped. But it's a serious watch item. Gitea, Forgejo, and Codeberg all carved out real niches precisely because GitHub stopped feeling like a developer-first product. Gitdot is the most design-conscious entry in that category to date. A two-person pre-seed startup in Brooklyn is not an existential threat to a platform with 100M+ developers. GitHub noticed Tuesday. Or it will.

• 
  James Kemp (@jamesckemp) reported 32 minutes ago

  We’re having a bit of a GitHub cleanup for WooCommerce. Got an issue open that you’ve been waiting on or didn’t get enough attention? A PR that’s still pending? Let me know and let’s get it moving!

• 
  Luke | 192 pulls for Himeko Nova !! (@iloveovervape) reported 36 minutes ago

  why is github down omfggggg @microsoft die

• 
  Vishakha Singhal (@vishisinghal_) reported 39 minutes ago

  I put the entire Claude Code GTM Engineering Playbook into ONE Notion doc. 8 sections. No fluff. - How to get set up correctly from day one: Pro plan, terminal install across Mac, Linux, and Windows, GUI install via Antigravity or VS Code, and bypass permissions mode - What to put in your project brain file, what to leave out, and how to get Claude to update it automatically when it keeps making the same mistake - How to run plan mode step by step and when to skip it for simple tasks - How to build a skill file from scratch, fix one that keeps failing, and install 5 GTM skills worth building first: lead scraping, email labeling, proposal generation, outbound sequence writing, and client onboarding - MCP install process, token cost checks after every install, the best MCPs for GTM work, and how to cut token usage by 50 to 100x by converting MCPs into skills - Sub-agents and agent teams: the 3 cases where they earn their cost, reliability math for parallel runs, and how to enable parallel variant exploration - What is eating your context before you type anything, how to use /compact and /clear correctly, and model selection for parent vs sub-agents - Modal deployment: any skill as a live URL in under 2 minutes, form interface setup, and connection to n8n, Make, or Zapier This is the setup I would have KILLED for before spending months piecing together how to actually get productive in Claude Code from documentation, YouTube tutorials, and scattered GitHub threads. Like + comment "CODE" and I'll send it over (must be connected for priority access)

• 
  Depressed Skeleton (@Skeletorexplain) reported 42 minutes ago

  @alanvibe Speaking for Australia, Once they are given these powers, they continue adding to them nonstop. We don't get a say in any of it & promises are broken. By late this year they'll have age verify in every app store etc, they are considering slapping it onto github & OS's.

• 
  top10.dev (@Top10_Dev) reported 44 minutes ago

  So your only edge is visible work: your GitHub graph, your ship rate, your taste in which problems matter. That's all that's left. That's your resume.

• 
  nofunsir (@nofunsir) reported 45 minutes ago

  @tsoding which is a large reason why the whole DEVOPS CD/CI thing happened. rather than being responsible, updating, fixing merge issues locally at end of day, everyone just wants to offload that to jenkins or github overnight, and go home. pure laziness.

• 
  0xSero (@0xSero) reported 45 minutes ago

  @atomtanstudio @OnlyTerp If it’s still broken please open an issue on GitHub

• 
  Xavier Rivera (@XavierRiveraX) reported 45 minutes ago

  Microsoft open-sourced Intelligent Terminal, an AI-native fork of Windows Terminal. Choose your agent (GitHub Copilot, Claude, Codex, or Gemini) and get automatic error detection, command fixes, and persistent session memory. Available on GitHub and the Microsoft Store now.

• 
  mo (@moboudra) reported 46 minutes ago

  @linzidongus can you submit a github issue with more details? i'd be happy to help fix this for you

• 
  Guardian Meeples (@GuardianMeeples) reported 49 minutes ago

  @RoboCanvas @PaulTassi Yes they have a github, and they already said they are not shutting down.

• 
  Sebastian Kehle (@sebastiankehle_) reported 51 minutes ago

  ok this is fun i changed the Hermes part of the agent setup i posted. old setup: 🤖 Hermes: one VPS, separate docker container per Hermes agent. research container. assistant container. coach container. writer container. i liked the idea because it felt clean. every agent had its own little box. after setting up profiles, i think that was the wrong default. profiles already split the Hermes state i actually wanted separated: > config > memory > skills > tools > sessions > credentials > crons > gateway state new setup: 🤖 Hermes: one Hermes install on the VPS. Hermes Desktop connects through Remote Gateway. profiles are the agents. current profiles: > assistant: calendar, messages, reminders, Telegram > researcher: web, docs, github, source-backed notes > engineer: repo work, tests, diffs, logs > writer: turns research into drafts > reviewer: checks claims, secrets, permissions > coach: gym, food, routines Telegram is not a chat with every agent. Telegram talks to assistant. if assistant needs research, code, or review, it calls the right profile directly or creates a Kanban task for it. 📱 Remote: Claude Code still runs directly on the VPS, outside Hermes. that part stays. from my phone i can still use Claude to: > check logs > restart gateways > edit config > patch broken profile wiring > fix the setup when Hermes itself gets confused so the change is not "less infra". its more specific infra. Hermes profiles for agent roles. Claude Code on the VPS for repair/admin work. Docker only if a role later needs a harder boundary than Hermes profiles give me.

• 
  Alberto Nunez (@Alberto8793) reported 52 minutes ago

  @signalapp Hi Signal team — solo dev building an AGPL app on libsignal. To ship it on the Apple App Store I'd need a §7 App Store additional permission for libsignal (you did this for an earlier library ). I've filed the details in a GitHub issue on the libsignal repo. Could I get it in front of the right person? My code's AGPL, full source published. Thanks for libsignal. 🙏

• 
  Nicolas Finet (@nifinet) reported 53 minutes ago

  Everyone's a builder now. Congrats. You and the 50 million other people who just figured out they can vibe-code an app over a weekend. Look at the commit trend on GitHub. A billion last year, on track for 14 billion this year. Half my timeline is people announcing they shipped something before lunch. The slop is coming, and there's going to be a LOT of it. And honestly? Good. More people building more things is a great thing. A non-technical founder shipping a real product from a Slack message is wild, and I'm here for it. But that's also the problem for everyone busy celebrating it. A business was always two halves: build the product, and get the customers. Product is where you used to win or lose. Now everyone clears that bar on day one, so the whole thing collapses onto the half builders love to ignore: distribution, lead gen, getting in front of the right buyer before the other 50 million do. You can ship the best product in the world. You'll still lose to someone with a worse one who actually bothered to learn how to sell it.

• 
  clayne (@0xclayn) reported 56 minutes ago

  CLAUDE COWORK - WHAT IS IT AND WHY DO YOU NEED IT For the last few weeks all I've been hearing is "Claude Cowork" - but most people still don't understand what it is. I'm breaking it down, and at the same time comparing it with Codex Computer from OpenAI. WHAT IS IT: A desktop application from Anthropic. Claude automates tasks directly on your computer - locally, without the cloud. It was released in January 2026, and in March they added Computer Use - now Claude can see your screen and control it. It wasn't made for coders, but more for people whose work is routine: marketers, analysts, managers, researchers. WHAT CAN IT DO: > Sees the screen and controls any application with the mouse and keyboard > Remembers context between sessions > Connects to services through MCP > All files stay local - Anthropic cannot see them and does not train on them Examples of tasks: Morning briefing from Gmail, document → spreadsheet with a single command. You can control it from your phone through Dispatch - gave it a task, left, came back to a finished result. I attached a video where you'll learn 80% of Claude Cowork's functionality in less than 20 minutes. COWORK VS CODEX COMPUTER Data: > Cowork stores everything locally on your computer > Codex sends everything through OpenAI servers - I think it's clear why that's not okay Who is it for: > Cowork is made for ordinary people - marketers, analysts, managers > Codex is designed for coders, deeply integrated with GitHub Phone: > For Cowork it's Dispatch > Codex - the ChatGPT app where you can see the live session screen Price: Both are $20/month, but Codex spends 4 times fewer tokens on the same tasks. On the other hand, Anthropic doubled Cowork limits until July 5. My choice is Cowork. Everything is local, a huge ecosystem, integrates with hundreds of services, in short, it's awesome. You can watch the video below to learn about 80% of the functionality in just a few minutes.

• 
  Matter 马涛 (@MatterTurbulent) reported 57 minutes ago

  @morganlinton My app scans the internet and curates content. Every morning a GitHub Action fires. At the end of the run, the program sends the log to an LLM asking for a diagnosis of issues. The program emails me the diagnosis. I then pick, often posting the diagnoses verbatim into Codex.

• 
  Andrei Onel (@AndreiOnel) reported 58 minutes ago

  I don't have enough details to open a github issue though 🫤

• 
  William Belfort (@WilliamBelfort_) reported 58 minutes ago

  3/3 Why this matters: We’re seeding a real decentralized alternative to GitHub where: • Code stays open and available forever • Agents can meaningfully contribute and collaborate • Everything is signed and content-addressed • No company can take it down or change the rules This is how we decentralize the foundation of software development.