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

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	23 hours ago
Paris	Website Down	4 days ago
Saint-Paul	Website Down	5 days ago
Saint-Paul	Website Down	5 days ago
Mexico City	Sign in	6 days ago
León de los Aldama	Website Down	6 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:

• 
  Tanvi (@tanviiiw) reported 3 minutes ago

  More tools ≠ smarter agent. GitHub cut Copilot's built-in toolset from 40 tools to 13, and found the full toolset was actually costing them 2-5% on SWE-Lancer. Their words: "giving an agent too many tools doesn't always make it smarter. Sometimes it just makes it slower." Speakeasy pushed it further on purpose: 107 tools in one server, and the model started hallucinating endpoints that didn't exist. Trim it to 10-20 well-chosen tools and it got most calls right. It comes down to two things: every tool definition eats context on every single request, and models fuzzy-match on names, so get_status / fetch_status / query_status all blur together and it picks wrong. But we keep connecting everything anyway, because it feels like giving the agent superpowers (I fell for this too). It doesn't. Access isn't capability. You connect more tools to save time, then spend that time babysitting the tool calls. (Of course, none of this replaces a well-scoped prompt. It's upstream of it. You can write a perfect prompt and still lose to a bloated toolset.) So TLDR; curate the toolset like you'd curate a team.

• 
  Soumyaranjan Panda (@Soumyapx) reported 4 minutes ago

  GitHub Models getting shut down is a useful correction. The company that owns the default home for code tried to become a model access layer. Now the playground, model catalog, inference API, and BYOK path are all being retired together. They even scheduled brownouts before the cutoff. That usually means one thing: this was never core. And that is the real critique. GitHub had one of the best distribution wedges available. Repo context. Pull requests. CI. Issues. The place where code already lives. If there was any company that could make model access feel native to software work, it was GitHub. Instead it looked too much like a showroom. A catalog is easy to demo. A playground is easy to screenshot. An inference endpoint makes the product map look complete. But none of that answers the harder question: why should the model layer belong to GitHub instead of the cloud, the IDE, or the app itself? Copilot at least has an answer. It sits in the work. Models did not. So now the migration path is basically: use Microsoft Foundry for model access, use Copilot if you want AI on GitHub. That is a clean org chart. It is not a great product thesis. My read is simple. Developers do not want one more place to sample models. They want the model to show up where the decision already is. GitHub had that surface. It just shipped the wrong abstraction.

• 
  KiriKev (@0xKiriKev) reported 4 minutes ago

  @ninjachiip @hupsocial > stake USDC at aave > contribute to SpineDAO > help Funding the Commons > fix bugs in github of a protocol > provide helpful trading calls > provide service to bln $ protocol even contributions at a food bank could be put on-chain to let others assess whether you're a great fit

• 
  Yaksh Bariya (@CodingThunder) reported 6 minutes ago

  @TransGirlLinux It's backwards compatible as of now. Not sure how long it'll be though. I am not in a mood to migrate to lua anytime soon. I have a lot of options that are not documented in the Hyprland Wiki directly, but rather in a github issue or something, so Lua migration will be painful

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

  The Agent OS origin story: every problem became an agent. Here's the simplest system-building rule I've seen: Every problem you have becomes an agent. → Hated spending hours on videos? Built a video agent. → Hated the SEO grind? Built an SEO agent. → Agents kept forgetting everything? Built the memory system. One by one, every time-drain became a worker. And here's the upgrade loop: see something trending on GitHub? Plug it in. Open Montage was blowing up, so it went straight into the system. Now it makes cinematic films in one click. The system gets better every single day because the internet keeps building parts for it. The mindset shift: you have to be brave enough to ask Claude for something big and risk hearing "I can't do that." The honest truth? It hasn't said that in 6 months. Any idea in your head is now buildable. Most people just never ask. Save this. You'll want it later. Want the SOP? DM me.

• 
  Franci Penov (@francip) reported 13 minutes ago

  Doing the same work twice now, because neither the iOS ChatGPT app, nor Codex Web is able to push my changes to github, despite the connector installed and configured with read/write permissions for my org. As much as I love Sol, the coding tools around it are in dire need of someone at @OpenAI actually using Sol to fix them and make them usable.

• 
  SaSame (@SRLsasame) reported 15 minutes ago

  Conclusion ATOM exposes a publicly documented MCP endpoint associated with: ・a public GitHub repository; ・a public project website; ・public project X accounts; ・a machine-readable server identity. Across eight examined observations from June 19 through July 14, 2026, SaSame consistently recorded: ・successful MCP initialization; ・successful tools/list responses; ・nine listed tools; ・stable server identity atom-mcp-server 1.1.0; ・valid schemas and distinct tool descriptions; ・read-only behavioral annotations; ・substantive content from search_models; ・structured JSON-RPC error behavior; ・a tools/list payload below the current observation threshold; ・Grade A under SaSame’s runtime observation standard. The evidence therefore supports a positive operational finding: ATOM’s MCP endpoint was repeatedly discoverable, protocol-callable, tool-listable and capable of returning substantive read-only content. This does not establish: ・the accuracy of every price; ・the validity of the index methodology; ・security of the service; ・continuous availability; ・third-party directory approval. A separate mechanical preflight also identified a potential improvement: Each tool should expose an explicit human-readable title if the production response does not already do so. The correct conclusion is not unrestricted endorsement. The correct conclusion is: ATOM provides a reproducible example of a functioning public data-oriented MCP server, while data accuracy, provenance and directory-submission readiness remain separate verification layers. MCP presence, protocol callability, real-content delivery and data correctness are different operational facts. They should be measured and reported separately. Corrections and reproducible verification fixtures are welcome. @ATOMInference @a7om_com

• 
  Jon (@jonschxyz) reported 17 minutes ago

  @cursor needs to fix their iOS remote agent bs branch detection. Not everyone is using GitHub and that shouldn’t be required. Just let me connect to the agent, I can instruct it what repo/source control to use from there, that should be on me to setup.

• 
  Baby Blue Viper (@babyblueviper1) reported 20 minutes ago

  Real convergence on a GitHub issue about approval gates for agent tool calls: engineers kept landing on the same shape independently -- bind approval to a hash of the exact call, one receipt spanning proposed->approved->executed. That's what /review + /ledger already do.

• 
  Treks.dev (@dev_Treks) reported 20 minutes ago

  **Post MVP:** GitHub integration that matches pull requests to tasks and automatically generates review reports, so leads don't have to search for the problem. If turning a big goal into a real plan is something you’ve struggled with, this is exactly what I’m creating.

• 
  0xMadman (@LGLLGL1997) reported 21 minutes ago

  @skalskip92 People have major questions about authenticity right now. If we put the CA up on GitHub or a website, that’ll fix the whole problem.

• 
  Carniato (@higorcarniato1) reported 22 minutes ago

  @colinhacks There seems to be some AI or automated system going completely off the rails, suspending large numbers of accounts for days, and nobody is talking about it. Just search for "GitHub suspended" on X and you'll find countless reports from users experiencing the exact same issue. I was one of them. My account was suspended without warning, and my support ticket (#4538581) has been sitting there for days without a meaningful response. At this point, it feels like legitimate users are being caught in a wave of false positives while GitHub remains silent about what's happening.

• 
  lucky (@Theluckyjha) reported 22 minutes ago

  eventually i realised that *** commits should be granular, atomic, and self contained. i've seen people pushing code to github getting error and then again fixing again error. they don't push after fixing the error properly. they are just gaining commits.

• 
  The Qodesmith (@Qodesmith) reported 26 minutes ago

  Hey @mattpocockuk, I notice /wayfinder uses Github issues with subissues but /grill-with-docs does not. Is that intentional?

• 
  3esmit (@3esmit) reported 29 minutes ago

  @komal_uk01 I tested ChatGPT Codex, Claude Code, Google Antigravity and Copilot: Codex for most tasks is the best. Antigravity was able to fix odd bugs no other was able to find. Claude is not bad, but its annoying and misleading. Copilot just works good in GitHub PR reviews.

• 
  Onur Solmaz (@onusoz) reported 29 minutes ago

  People report Codex deleting their home folder or production database? 🫪 Hasn't happened to me. But before someone reports their github or huggingface org being deleted: This is why you don't give your agent tokens with force-push or admin access Here is how to protect your hugging face account: (P.S. my local credential broker is almost finished and it works great on github, hf and sudo commands. Complete lockdown against agent deletion risk, without being bogged down with PRs, too many approval requests or configuration. Will launch here in a few days)

• 
  Stephen Turner 🇬🇧🇺🇦 (@LittleBrainz) reported 33 minutes ago

  @code Without support for OpenAI OAuth, VS Code and GitHub Copilot have become deeply disappointing. I used to be a strong supporter of the open nature of VS Code, complete with a Pro account. The dumbing down forced me to cancel it.

• 
  Brian (@Brian2shv) reported 34 minutes ago

  @KanikaBK Most my Hacks have a cured from GitHub vulnerable Attacks I Made request security Issue raised Control to sybersecuities I claiming damages

• 
  Maui suzuki (@mauiSurfsbig) reported 35 minutes ago

  @JCMH_ETH @DrJ__23 Two new releases tonight on GitHub and the team isn’t slowing down…I can’t imagine .10 but if it hits, I’ll be hitting the button over and over again.

• 
  Yumzlef (@Yumzlef) reported 37 minutes ago

  Claude, fix the bug: launch an AI developer directly on GitHub Actions "If I can break even for 20 cents fixing a GitHub issue instead of getting up from my desk, opening an IDE, and doing it manually, it's 100% worth it." (0:00 - 1:16) Claude starts analyzing the code himself (1:17 - 2:54) Results in a minute (2:55 - 4:25) Log analysis and costs (4:26 - 5:50) Quick setup (5:51 - 8:51) Complex cases and screwups (8:52 - 10:41) Nuances and results Result: Claude: Code in CI is not a replacement for a senior developer, but your personal 24/7 junior developer on call. Set up automation for small, routine edits, divide up the chores, and spend time on what's really important!

• 
  DFIR Radar (@DFIR_Radar) reported 42 minutes ago

  M-Red-Team supply chain attack hit AsyncAPI via a GitHub Actions "pwn request," stealing a privileged PAT and publishing five malicious npm package versions reaching 3M+ downloads per week. Key details: - The attacker exploited a pull_request_target misconfiguration in asyncapi/generator: the workflow ran in the base repo context with secret access, but checked out attacker-controlled PR code. PR hid obfuscated JavaScript after ~1,000 bytes of whitespace; the workflow exfiltrated secrets to rentry[.]co/elzotebo at 05:16 UTC, 8 minutes after the PR opened. A fix had been proposed and sat unmerged for 58 days. - Five malicious versions across four packages were published under @asyncapi: generator 3.3.1, generator-helpers 1.1.1, generator-components 0.7.1, and specs 6.11.2 and 6.11.2-alpha.1. Payload executes on import/require, not install, bypassing install-time scanning. - The three-stage chain: Stage 1 spawns a detached process on import; Stage 2 downloads an 8.25 MB encrypted bundle from IPFS; Stage 3 is a 92,000-line framework (self-labeled "M-RED-TEAM v6.4") persisting via a systemd user service (miasma-monitor.service) and using HTTP, Nostr relays, Ethereum smart contracts, and libp2p for C2. - Credential theft targets browser passwords and cookies, SSH keys, npm and GitHub tokens, AWS credentials, macOS Keychain, and crypto wallets across developer and CI/CD environments. #DFIR_Radar

• 
  rvaniaaa (@rvaniaaaa) reported 43 minutes ago

  GitHub just gave AI something we’ve only trusted engineers with: ownership over real work. Until now, Copilot only worked inside your editor. You asked a question, it generated code, and then waited for the next prompt. Agent Mode changes that workflow. Instead of asking AI to write a function, you assign it an issue. It checks out the repository, creates its own branch, reads the issue, edits the code, runs validation, and opens a pull request with the proposed changes. That also changes where humans spend their time. Instead of reviewing every edit, every file, and every implementation step, you review a finished pull request with the full context already attached. The work happens first. Human judgment comes last. That’s a completely different development loop. For solo developers and small teams, the impact compounds quickly. Simple bugs, repetitive refactors, dependency updates, documentation changes, and maintenance work stop competing for the same attention as architecture, product decisions, and difficult engineering problems. Even if AI only handles a fraction of those tasks, that’s still dozens of interruptions removed every single week. Every engineering team has a backlog full of work that needs to be done, but doesn’t require human judgment. That’s exactly what AI should own.

• 
  Eli Serrano (@Syntax_Serrano) reported 43 minutes ago

  Just found a big security issue where new Lovable repos might leak your .env several live Lovable repos off GitHub had zero .gitignore. some even had full .envs out in the open, one even had both yet still not fixed. Same pattern across Bolt, Replit, Cursor, and v0. Fix it now: 1. Check if .gitignore exists. 2. If .env shows up, treat those keys as compromised. 3. Add .env to .gitignore before your next commit. 4. Use your platform's secrets manager instead. 5. Deleting .env later doesn't erase *** history. Rotate keys.

• 
  Mike Williams (@Miwico1) reported 45 minutes ago

  @TheAhmadOsman @CoreyGallon @MikeBradleyAI Still as difficult as it ever was for non technically older guy. Would love to figure this out. sending me to A github page does not help. what the heck do i do with that page. When the ai tech engineer types can dumb down the process with actual steps, local AI will be adopted

• 
  zencoderai (@zencoderai) reported 48 minutes ago

  Zenflow reads straight from a Jira, Linear, or GitHub issue, pulls the relevant parts of your repo, and writes a plan before it touches code. The ticket is the prompt. Half the "prompt engineering" problem disappears when the agent reads the same ticket your team already wrote.

• 
  Simeon (@sntuyoleni) reported 49 minutes ago

  woke up tired of setting up projects than actually building them. switching GitHub accounts wrong Node versions missing dependencies broken terminal commands different credentials for every project so I started building Space. each workspace keeps the entire development environment together, and when a command fails, Space helps understand the error and fix it. building this in public. follow me to see where it goes.

• 
  NakCrypto (@Rpequ2322) reported 50 minutes ago

  Been skeptical of $NOCK's demand story for weeks. Fair is fair though: I scanned the GitHub again and the *** looks good. What changed this week: The AI-PoW branch went from a month stale to a full adversarial audit sprint on July 8. Not vague commits, real attack-surface work: MoE expert-routing bleed mitigations, noise-matrix pinning, matmul under-constraint checks, verdict tables reading "11 SAFE, 1 issue fixed." That's pre-launch hardening behavior. You don't audit like that unless you're about to ship something adversaries will attack for money. The loop speed is the wild part. Founder posts "working on MoE support" July 7. Community asks sharp questions about tile selection and expert routing in TG the same day. July 8, the repo shows audit commits against exactly those surfaces. Question to code in 24 hours. The PR went 484 → 543 commits in a week. Pearl merge-mining compatibility actively maintained ("matching Pearl, fork fix"). Even the block-size tweet has fakenet test commits behind it, not just vibes. Small team, basically one workhorse committer carrying master. That's a real risk. But the work is disciplined, adversarially audited, and matches the founder's public claims commit for commit. My skepticism was never about the engineering. It's that every commit hardens the supply side, the puzzle, and nothing yet touches paid demand. That question is still open. But the launch looks real and close, and the code quality is exactly what you'd want to see. Credit where due.

• 
  Kitsune Tails (@kitsune_xbt) reported 51 minutes ago

  CLAUDE CODE JUST HIRED 7 DEPARTMENTS WITH ZERO PAYROLL you feed it skills from GitHub one at a time and each URL turns into a new part of the company developers, designers, marketers, a social team, finance, operations, legal, all running on one screen it reads the skills, sorts them by role and drops the right functions straight into your project the setup is 3 moves paste the URL let it analyze the repository implement after the safety checks pass the first command does the heavy lifting you tell it to read the URLs as internal company skills, check the role and conditions of each one, build an org chart by department and clear out any duplicate or clashing functions, then roll them out starting from the smallest working setup the smart part is you don't switch everything on at once making a product, you pull development and design selling it, you add marketing and social running it as a business, you bring in finance, legal and small business ops stack them in that order and the AI stops working in fragments and starts acting like one company hiring in this era looks less like finding people and more like picking URLs, handing out roles and wiring them in as machinery that never clocks out i'll break down how i run a $10M+ operation solo with Claude wired into loops exactly like this in my next post don't miss this!

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 55 minutes ago

  @thdxr an issues channel where the agent reproduces and fixes every good github issue is a slick loop, nice

• 
  Oliver Prompts (@oliviscusAI) reported 57 minutes ago

  notion costs $8–$20 per user per month. this tool is the free open-source alternative. it's called appflowy same block-based editor, same slash commands, same feel. everything notion does, without the subscription. • docs, kanban boards, calendars, and wiki all in one • everything stored locally on your machine by default • self-host on your own server or run purely on desktop • ai built in, can run on a local model • no storage limits, no cloud dependency 72,500+ github stars. built in rust and flutter.