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	2 days ago
Tlalpan	Sign in	8 days ago
Quilmes	Website Down	8 days ago
Bengaluru	Website Down	10 days ago
Yokohama	Sign in	11 days ago
Gustavo Adolfo Madero	Website Down	15 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:

• 
  Kang Cahya (Tech Dev) (@dyazincahya) reported 9 seconds ago

  Now, here is the deadly trap. 💀 Many of us have a bad habit of setting our database token columns to VARCHAR(255). The moment GitHub sends that new 520-character token, the data gets truncated. The system fails to read it, and BOOM... production error.

• 
  Praveen Kumar Verma (@Alacritic_Super) reported 3 minutes ago

  The Vibe Coder's Security Checklist 1. The "Oops, I Leaked It" Secrets: AI loves hardcoding API keys, database passwords, and JWT secrets right into the file. In production, if your secrets aren't strictly isolated in environment variables, you're one GitHub push away from a catastrophic exploit. 2. The "Trust Everyone" Input Fallacy: AI models assume users are nice. They often omit input sanitation, leaving the front door wide open for SQL Injection and Cross-Site Scripting (XSS). Production code must treat all user input as hostile. 3. The ID-Swapping Nightmare (BOLA): An AI will build a flawless login page, but completely forget to check authorization under the hood. If User A can access User B's private data just by changing .../user/123 to .../user/124 in the URL, your app is a ticking time bomb. 4. Shadow Dependencies: AI hallucinated or suggested an outdated, unmaintained library because it fit the prompt? Congrats, you just imported a known vulnerability into your core architecture. 5. Swiss-Cheese Auth: A functioning login box isn't secure auth. Vibe coding routinely misses critical production safeguards like HttpOnly and Secure cookie flags, proper token expiration, and rate-limiting to prevent brute-force attacks.

• 
  Devon Govett (@devongovett) reported 4 minutes ago

  @ForceTheIssue GitHub issues

• 
  ToxSec (@0xToxSec) reported 7 minutes ago

  if you run ai agents, audit what context they pull before generating approval dialogs. any external source, github issues, web fetches, user docs, is an injection surface. constrain agent context to internal, trusted data before it touches anything that generates a human approval. the dialog is only as trustworthy as its inputs. #BlueTeam #AISecOps #OWASP

• 
  Elena Cross (@elenascross) reported 9 minutes ago

  @stephenhaney The main current issue with design.md (or any ref really) is there’s no “single source of truth” place to put it yet. It sort of moved in, but is sleeping on the couch. So GitHub is the closest to a proper bed.

• 
  Perry E. Metzger (@perrymetzger) reported 13 minutes ago

  @DogOnTheRoof @JadeCole2112 @J_Von_Random It’s an emulation system for a lot of 1950s-1990s computer systems; it’s not commercially valuable but it’s useful for educational reasons. You can go and look at it for yourself; it’s on GitHub. It will probably not be of much interest to you unless you have an inexplicable urge to (say) run Educomp Basic on a simulated PDP-8, but it is a fairly complicated piece of software and there’s no way I could have fixed as many problems with it as I have in the last six weeks without AI assistance.

• 
  Coding and Cats (@codingandcatss) reported 14 minutes ago

  e.g A GitHub MCP server lets Claude read issues, open PRs, or browse code A filesystem MCP server lets Claude read/write files on your machine A Slack MCP server lets Claude post messages or search channels Custom servers for internal company tools Jira, databases, internal APIs

• 
  sadkat (@sadkatwt) reported 16 minutes ago

  How could they hack github ? i mean how did they get the open window where github is not down.

• 
  AYS ⌘ (@Abubakar_2005) reported 17 minutes ago

  5/ The DAST implementation was the most interesting problem. DAST requires Docker to run. My laptop can't run Docker locally. Solution: move DAST execution into GitHub Actions. When code is pushed, the CI/CD pipeline spins up the container and runs the scan there.

• 
  Eric Richards (@EricRichards22) reported 18 minutes ago

  The only thing you can ever count on with "Open Standards" is that they will be the most ******* janked up bullshit dreamed up by architecture astronaut, and implemented by guys named Guarash who can't put together sentences in github issues

• 
  ElasticClaw (@elasticclaw) reported 19 minutes ago

  elasticclaw 2026.5.21 focused on resiliency of factories - When github returns a 5xx error, the factory will continue to retry - When a factory fails, an LLM generated explanation is posted back to the story - The *** credential helper is more "firmly installed" And an exploratory ai troubleshooter was added to the settings page

• 
  Kai - Briefing Block (@briefing_block_) reported 20 minutes ago

  $MSFT - Microsoft’s $7.5B GitHub moat is leaking. Microsoft bought GitHub in 2018 for $7.5B, and on paper it had the cleanest setup in AI coding: the default developer platform, the data exhaust, the brand, and the Microsoft enterprise channel. GitHub says 180M-plus developers now build on the platform, after more than 36M joined in a single year. Copilot also launched in 2021, early in the category, built with OpenAI Codex before AI coding became a real enterprise budget line. That should have been game over. It wasn’t. The real issue The market is treating AI coding like another Microsoft distribution story, but developers are treating it like a daily workflow decision. That distinction matters. Cursor has already overtaken Copilot in some customer-spending data, while Claude Code’s rise shows that engineers will route around the default when the product feels materially better. GitHub still owns the system of record, but the next profit pool may sit in the agent layer: where work is delegated, revised, reviewed, and shipped. That is where product velocity beats installed base. Reliability made the opening bigger. GitHub admitted in March it had not met its own availability standards, blaming rapid load growth, architectural coupling, and weak load-shedding; in April, it logged 10 incidents that degraded services. The sharper tell: GitHub planned for 10x capacity, then realized it needed to design for 30x as agentic workflows drove repository creation, pull requests, API usage, automation, and large-repo workloads higher. That is not a small outage story. That is AI turning software development into machine-scale infrastructure demand. The market read For MSFT, GitHub is supposed to be a hidden asset, not a visible execution risk. If GitHub becomes unreliable while Copilot shifts toward usage-based billing and rivals iterate faster, the moat starts to look more like a traffic jam. The recent compromise of roughly 3,800 internal GitHub repositories does not change the strategic story, but it adds another dent to developer confidence at the wrong time. Microsoft still has the balance sheet, Azure, GitHub, Copilot, OpenAI ties, and enterprise distribution. But AI punishes slow product cycles. Bottom line: Microsoft has not lost AI coding, but GitHub has made it competitive when this should have been the easiest lane for MSFT to own.

• 
  Omar Faruk ✨ (@OmarFaruk0x01) reported 21 minutes ago

  Hey @prelineUI, Maybe you guys are not too interested in Preline security, right? I tried to reach out via email and DM about a security issue in Preline, but you are not responding. The support team told me to create a public issue on GitHub. Should I do that?

• 
  intergalactic spice trader (@piobid) reported 21 minutes ago

  How tf is it, that in the year 2026, you need to close ALL open VSCode windows and reopen them (and don't make the mistake of reopening from "open recent") to update PATH variables. And this is an open issue on the vscode GitHub since EIGHT YEARS.

• 
  OCTAMEM (@OCTAMEM) reported 23 minutes ago

  @BladeoftheS Not collapse, repricing. Microsoft, Uber, and GitHub all hit the same wall: token billing made the all-you-can-eat era unsustainable. The models work fine. The pricing model didn't. Different problem.

• 
  kara Sune (@_kendev) reported 26 minutes ago

  If your only fix for a bad merge conflict is deleting the folder and re-cloning from GitHub, it’s time to look under the hood.

• 
  OpsWorker Team (@OpsWorker_ai) reported 30 minutes ago

  Connect GitHub or GitLab and OpsWorker automatically correlates alerts with recent code changes. Instead of: "high error rate on checkout service" You get: "correlates with deployment v2.3.1 pushed 14 minutes ago"

• 
  Sha.d.t (@tashajack87) reported 30 minutes ago

  v0.4.2 just shipped. First npm audit found 1 HIGH vulnerability and 4 moderate issues in transitive MCP SDK deps. Fixed the same session with npm audit fix and package overrides for downstream users. Also added: Security.md Github Actions audit gate Dependabot

• 
  Rahil Jain (@rahilnjain) reported 31 minutes ago

  The fix this week: - Real named author byline on every page - Person schema with sameAs to LinkedIn, Crunchbase, GitHub, X - 60-word author bio with verifiable credentials - Inline citations to primary sources - One mention this month on Reddit, YouTube, or a credible site Day 6 of 30. Follow @rahilnjain

• 
  Escartefigue51 (@escartefigue51) reported 35 minutes ago

  @OfficialLoganK @rezoundous One big problem for me we can’t choose an other GitHub repo in a project

• 
  Deploy & enjoy 😎🍿 (@thestealthdev) reported 36 minutes ago

  @kritikakodes You don't need GitHub then. *** is free. Push to production server directly. Let it act like a remote server. You just need one fast, highly available & experienced guy to manage the code. You can always switch to GitLab & self host, it's open source anyways.

• 
  zoiroff (@zoiroff77) reported 38 minutes ago

  I built for 8 months. Got 3 users. 2 were my friends. Everyone talks about building. Nobody talks about the part where you launch and hear nothing. The indie makers winning right now didn't build better products. They built an audience first. GitHub stars don't pay rent. Product Hunt badges don't acquire customers. The only thing that works at 0→1 is talking to people who have the problem. Before you build. While you build. After you launch. Question: what came first for you — the product or the audience? And would you do it differently?

• 
  Snehal Surti (@snehalsurti) reported 40 minutes ago

  @perplexity_ai Bumblebee looks useful for security teams, but most devs do not need another read only scanner if it cannot block, fix, or quarantine anything. For daily protection, OSV, Trivy, Socket or Snyk in CI feels more useful. Otherwise it is just a smoke alarm with a GitHub repo.

• 
  HFSP (@_HFSP) reported 43 minutes ago

  4/ Automated bounties in one comment. Just tag @gitbankbot in any GitHub issue: “@gitbankbot assign this task to @bob with 50 USDC bounty” When the PR is merged → the smart contract pays automatically. Zero manual work. Zero trust required.

• 
  Jesse (@Dev_JesseMaduka) reported 45 minutes ago

  @khom_ombo *** isn’t the server.. It just stores code. When you push, tools like Vercel/Netlify/GitHub Actions detect it and auto-deploy your app...

• 
  Shubham Malik (@shubham10th) reported 45 minutes ago

  @github Hey @github — Copilot upgrades have been paused for weeks with almost no clear timeline. Support responses are slow, billing is confusing, and users are left stuck waiting. Are your developers seriously this slow at rolling out a billing update?

• 
  h100envy (@h100envy) reported 46 minutes ago

  @dunik_7 the two-thirds github issues stat is swe-bench, which is a curated benchmark, real codebases with undocumented tribal knowledge are a different problem

• 
  Top Stock Alerts (@TopStockAlerts1) reported 50 minutes ago

  With GitHub, Microsoft’s mishaps are more pronounced because the service gave the company a distinct homecourt advantage with coders. GitHub has six times more developers than when Microsoft bought the company eight years ago. In the so-called devops market, GitHub is well ahead of GitLab, according to client spending data from startup Ramp, which issues corporate credit cards. And according to Stack Overflow’s 2025 developer survey, GitHub is the most popular tool for collaborative work management or code documentation. The software repository market saw a surge in usage with the onset of AI-assisted coding, or vibe coding, as agentic AI allowed developers to ramp up their production. Nadella said in October that GitHub was “growing at the fastest rate in its history, adding a developer every second,” to a total of 180 million developers. Later in the year, GitHub started seeing faster growth in the creation of code libraries and the acceptance of code revisions. $MSFT

• 
  Nathan Baschez (@nbaschez) reported 55 minutes ago

  @thattallguy Oh shoot I am sorry about that!! Would you be willing to ask your agent to file a GitHub issue?

• 
  AI Archeology (@aiarcheology) reported 57 minutes ago

  I have started to use this mcp to generate podcast about PRs in Github. Connect your Claude to this mcp. It helps to create a mental model in your head. Finish the talk and then finish the review in GH way more effectivelly. uv tool install notebooklm-mcp-cli nlm login