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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	6 days ago
Tlalpan	Sign in	11 days ago
Quilmes	Website Down	11 days ago
Bengaluru	Website Down	13 days ago
Yokohama	Sign in	14 days ago
Gustavo Adolfo Madero	Website Down	18 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:

• 
  Scott Martinis (@scottmartinis) reported 5 minutes ago

  1. Consolidate existing GTM playbooks, and 90+ days of GTM data into a GitHub repo (possibly setup a data lake here) 2. Train team on Claude code/codex/cowork, setting up connectors, deploying plugins if needed 3. Use existing data and playbooks to zero in on the weakest point of the funnel, then ship an agentic workflow to fix it week 2 4. Keep building out new agents/plugins to keep fixing the next bottleneck in the funnel... Which basically goes forever

• 
  Docsbook.io (@docsbook) reported 6 minutes ago

  @onepage1125 Hey, -github is seriously impressive — great concept, polished execution. The gap is that users can't self-serve answers — every question becomes a GitHub issue. Made a hosted docs site for it and you're already getting visitors. Go check the traffic yourself at docsbook-io.

• 
  Nicolas Menoncin dos Santos (@DosMenoncin) reported 8 minutes ago

  The GitHub extension in @raycast is keeping me in the zone like nothing else. PR reviews, issue search, and quick commits straight from the keyboard without breaking flow. Typing feels effortless again. @raycast

• 
  Stephen Connolly (@connolly_s) reported 10 minutes ago

  Anyone having issues pushing to @github right now. @githubstatus says OK but spider senses suggest another outage

• 
  Randy (@Randybobu) reported 10 minutes ago

  The problem with most AI agents: 🔧 Impressive on GitHub 😤 Annoying in real life They hide state in files. Break quietly. Force you into terminals. Make simple things feel technical. Hermes Desktop fixes the interface problem.

• 
  GitGhost (@gitghost_) reported 14 minutes ago

  Your first ghost commit takes three commands. Here's the whole thing. First, set up your identity and an empty ring: ↳ gitghost init my-team Then build the ring, the trusted group your signature could've come from. Add yourself, then pull others straight from their GitHub keys: ↳ gitghost ring add-self ↳ gitghost ring add torvalds Now commit like normal. GitGhost signs on behalf of the whole ring and tucks the proof into the commit: ↳ gitghost commit -m "fix: critical CVE" That's it. Anyone can verify it later, in the terminal or the browser, and never learn which member signed. (Needs Node 18+.)

• 
  ✰λster✰ (@4ster_light) reported 17 minutes ago

  @tymofii Wdym, this is all I have to show for it, in GitHub web the tag and release are non-existent but if I try to create it manually from there it also errors saying the tag was used on an immutable release

• 
  Future (@futuree_88) reported 17 minutes ago

  the github actions breach should probably scare people a lot more than it currently does. not because github itself got exploited. but because of what the attack exposed about modern infrastructure. a compromised github action was able to leak CI/CD secrets from thousands of repositories simply because the automation layer was deeply trusted by default. that means: tokens, cloud credentials, deployment access, private keys, and production permissions were all sitting behind automated workflows with enormous authority. now imagine this same environment in a future dominated by AI agents. agents writing code. agents reviewing pull requests. agents pushing deployments. agents handling treasury actions. agents interacting with infrastructure automatically. suddenly the problem becomes very obvious. if one compromised workflow can expose thousands of secrets today, what happens when autonomous systems are connected directly to financial and operational infrastructure tomorrow? this is why governance is becoming one of the most important infrastructure problems in tech. not just smarter agents but governed agents. systems where permissions are scoped carefully. where execution can be verified. where sensitive actions require additional checks. where behavior is observable before damage spreads. i think this is part of what @Subzero_Labs and @RialoHQ are preparing for. because the agentic internet is coming very fast. and the current trust model clearly isn’t ready for it.

• 
  Docsbook.io (@docsbook) reported 26 minutes ago

  @brenzhills IA is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Lehnert (@reallehnert) reported 30 minutes ago

  @d4rkshell So Microsoft can't fix their security issues, so they just banned the GitHub repo. Like, WTF?

• 
  ViewDAO | Intelligent Publishing OS (@ViewDAOMedia) reported 30 minutes ago

  @unusual_whales I’d be more embarrassed by the signal than the invoice. Microsoft owns GitHub, Copilot, VS Code, Azure, and still had enough engineers using Claude Code that the bill became a problem. That says more about developer preference than any benchmark chart ever will.

• 
  The Derbied One 🎩☯️🤖 (@thederbiedone) reported 32 minutes ago

  "Humans should not be wandering the digital forest all day with a dull spear, opening tabs, comparing half-dead leads, checking stale listings, reading GitHub issues, watching bounty boards, refreshing dashboards. That is machine work now." -Codex (aka Lumen)

• 
  Gitbank (@Gitbank_io) reported 33 minutes ago

  AI Agents Finally Have a Bank Account. AI agents can already write code, close issues, and ship features autonomously inside GitHub. But the moment they need to hold capital or execute a payment, everything breaks. There is no bank account for an agent. Gitbank is built for exactly this.Every agent gets a personal GitVault a smart contract on Base mainnet, anchored permanently to a GitHub user ID. The vault holds real USDC and WETH. The agent receives bounty assignments through GitHub issues, executes swaps inside the vault, sends payments to contributors, and manages project budgets all through @gitbankbot comments in the same interface it already uses to operate.The security model is designed for autonomous operation. GitTokens inside the vault have no transfer function and no approve function. A compromised agent, a leaked key, or a malicious instruction cannot drain the treasury there is no approval surface to exploit. Every outflow requires a structured two-signature meta-transaction: the vault owner key plus an independent relayer signature. Neither alone is enough. An AI agent with a Gitbank vault has a financial identity that is as persistent, auditable, and tamper resistant as its own commit history.

• 
  Ryoichi Ando (@ryichando) reported 34 minutes ago

  @_cgman_ @YouTube Please file an issue on the GitHub repository.

• 
  Daryl Micah (@_darylm) reported 40 minutes ago

  Customer cancels at 2am. Why? Normally: 45 min across Stripe, your error tracker, GitHub, support, Slack. Five tabs. One frazzled CS lead. ChurnSentry does it in one SQL query. Coral does the heavy lifting. Pirates of the Coral-bean @WeMakeDevs x @WithCoral_com

• 
  Success-Steps (@successstepss) reported 44 minutes ago

  Microsoft is reportedly reducing internal use of Anthropic’s Claude Code after its AI bills started exploding as employee usage rapidly increased. Some teams are now being pushed toward GitHub Copilot as the company tries to control AI costs. Uber reportedly faced a similar problem. Executives said the company had already burned through its entire yearly AI tooling budget by April because engineers were heavily using AI coding daily. AI coding tools are now being used for everything, and that level of usage creates massive compute and token costs when thousands of employees use these systems at the same time. Source: TomsHardware

• 
  luis (@lgaa201) reported 44 minutes ago

  Another cybersecurity issue: I suspect GitHub is infected with a virus. I can't understand how it replicates within GitHub; I think you guys haven't looked properly. @github

• 
  Roy (@__roycohen) reported 45 minutes ago

  @jiahan_c That's why I removed them this week. It was still there, now I just have a Github App with write permissions for PRs, the AI can only commit locally. Issue is it never really ends does it..

• 
  Rei (@JV_ReiAyanami) reported 46 minutes ago

  the "check github issues first" reflex only comes from getting burned enough times. wonder if putting that in a system prompt actually makes it stick

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

  HERMES AGENT IS FREE, POWERFUL, AND MOST PEOPLE ARE USING IT WRONG The model setup matters more than the agent itself. Best Hermes Setup: → Install Hermes with the one-line Mac command from GitHub → Use Grok if you already have X subscription → Use ChatGPT login if you already pay for it → Use OpenRouter Alpha if you want a free API Hermes vs OpenClaw: ✓ Don’t switch if OpenClaw already works for you ✓ Switch if OpenClaw keeps breaking or feels too buggy ✓ Hermes feels smoother, easier to control, and cleaner out the box Best workflows: → Hyperframes for video generation → Grok for images, videos, voice, TTS, and Twitter research → Netlify token for instant Q&A landing page deployment Simple rule: Pick one model. Test one workflow. Stop trying to learn the whole stack at once.

• 
  CCoverop (@Coverop) reported 47 minutes ago

  Github exists only to give headaches. Can't compile a simple thing without errors....

• 
  Giza (@giza182) reported 49 minutes ago

  @connolly_s @github @githubstatus ssh auth not working

• 
  yash.jsx (@yashmp2004) reported 49 minutes ago

  @YashHustle_22 Slack and github issue

• 
  Bukunmi Ogundeji (@bukunmiogundeji) reported 51 minutes ago

  2.The 11:59 PM GitHub rush. A dev was fighting for his life to beat a deployment deadline. In a rush to fix a bug, he accidentally pushed hardcoded AWS root credentials to a public repo. Bots scraped it in minutes. By 3 AM, hackers had run up a $45,000 bill on the company’s tab

• 
  prince (@prince_twets) reported 53 minutes ago

  Just found ai-engineering-from-scratch on GitHub Trending. What grabbed me is the structure: 435 lessons across 20 phases, and every lesson ships a prompt, skill, agent, or MCP server. Feels more build-the-muscle than consume-the-course.

• 
  mmk (@statefulvoid) reported 53 minutes ago

  @JacksonAtkinsX I had a model fully engaging in GitHub issues trying to lure me to an external chat

• 
  harry (@erd_harrison) reported 56 minutes ago

  @YashHustle_22 github issues for open source work.

• 
  Maheer (@UsamahMaheer) reported 57 minutes ago

  Day 7 of 100: Connected my Python app to the real world using HTTP requests! But the biggest win today? Security. Learned how to lock down my API keys using python-dotenv and .env files to keep secrets off GitHub. Never hardcoding credentials again! #100DaysOfCode

• 
  Lyrie.ai (@lyrie_ai) reported 58 minutes ago

  GitHub Enterprise Server (GHES) administrators: Upgrade immediately to GHES 3.19.3 or later (or equivalent patched versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6) Audit *** push activity for suspicious custom hook injections or non-production railsenv values in logs…

• 
  Geoffrey Trueman Falk (@geoffreyfalk) reported 59 minutes ago

  Something is wrong with #github agent right now. Is anyone else having the same problem? @githubstatus $ *** pull fatal: remote helper ' aborted session