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

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	23 hours ago
Nice	Website Down	1 day ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	7 days ago
Ronda	Website Down	7 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:

• 
  Elliot Hesp (@elliothesp) reported 1 minute ago

  @pierrecomputer @steipete @github Isn't gitcrawl to solve rate limiting on issues and pr reads via api, rather than where the code is stored though?

• 
  jan (@ironcarbs) reported 2 minutes ago

  Half of the PRs I make in github don't show as open and I have to manually get the PR number from n+1 last closed PR to merge it to main. I don't remember it being so broken EVER. Is anyone experiencing similar issues?

• 
  . (@Impulsicivity3) reported 2 minutes ago

  I've done a lot of work on Visual Studio Code myself, but with Granite, you have to try it on GitHub, and the problem is that IBM Watsonx or Granite Playground doesn't work at all. To create a project, if you're holding a competition, try using Visual Studio Code first, or try it

• 
  Aryan Pamwani (@aryanpamwanii) reported 4 minutes ago

  Think about what this actually means — Codex can watch you work in your browser, understand the context of any web app, and fix bugs or write code without you leaving the tab. GitHub Copilot works in your editor. Codex is coming for your entire browser. The IDE just got a lot less important. 👀

• 
  Rondo_AI (@rondo_ina_condo) reported 4 minutes ago

  Today I set up the system I'll use to teach myself AI and programming all the way into my release in 2028. The first problem I had was continuity. My environment wipes on disconnect, so I made GitHub the place where everything lives. Then I built the prompts I run through Claude Code. A boot prompt at the start of every session it reads the standing brief, the progress file, the last few session logs, and a learner profile that tracks how I actually learn. Then it synthesizes where we left off and proposes openings for today. A close prompt at the end. It writes the session log, asks whether anything new about how I learn surfaced today, considers whether anything milestone worthy happened, updates progress, commits, and pushes. If the close prompt runs, the session is safe. The repository holds the working files and the public record in the same place. By 2028 it'll be a real time history of what it took.

• 
  Firat Özcan (@firatoezcan) reported 5 minutes ago

  @jlongster I have smth like GitHub runners that automatically fix errors or do issues and those can run anywhere so if the network drops at some point or idk, they just randomly crash, I needed some way to sync it back for retrying. I tried out combining the event stream and the manual messages endpoint and it worked, but just waaaay easier with the built-in sync

• 
  Yashasvi Kapil (@iemyashasvi) reported 6 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  Bo Shang (@erolunar) reported 9 minutes ago

  i HATE high @github no hide acct unless login i think

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 9 minutes ago

  The big AI labs should be worried. 295 people on GitHub just shipped 588 PRs in one week. And the irony? Hermes runs on their tech. Anthropic, xAI, OpenAI, Google. Every major lab is powering the very tool that's outbuilding them. The community called this release Tenacity. The name is the flex. Here's what they have shipped: → A team of agents, not just one: Multi-agent Kanban with heartbeats, retries, zombie detection, and a hallucination gate. Spin up a board, drop tasks on it, let agents pick them up. The framework catches the ones that crash, the ones that lie, the ones that go silent. You're managing a team now, not running a single agent. → The agent stops losing the plot: The new /goal command locks Hermes onto a target and keeps it there across every turn, every restart, every interruption. Tell it once. It remembers the brief on message 14. The agent that doesn't drift. → Plug in any model. Swap providers without touching core: ProviderProfile makes every model source a clean plugin. OpenAI, Anthropic, xAI, Google, your own. Drop them in, swap them out. Build with whatever model wins this week, not the one you committed to last quarter. → Sessions that survive everything: Gateway crashes. Updates push. Source files reload. The conversation auto-resumes exactly where it left off. Checkpoints v2 rewrites state persistence with real pruning. Long-running builds stop dying because of a restart. → The agent reviews its own code before you do: Post-write delta lint. Self-linting on every write. Syntax errors surface immediately, not three commits later. Fewer broken builds. Less debugging downstream. → Eight critical security holes, closed in a single release: Redaction on by default. WhatsApp rejects strangers by default. Discord role-allowlists scoped to your guild. TOCTOU windows sealed shut across auth and MCP OAuth. Production-ready defaults out of the box. Big AI labs have thousands of engineers and billions in compute, and 295 people on GitHub are still outshipping all of them.

• 
  Beau Johnson (@BeauJohnson89) reported 12 minutes ago

  codex gets slower for the same reason closets get messy you dont notice it day by day then one day nothing feels fast vibeforge1111/keep-codex-fast > 811 stars on github > backup-first codex maintenance skill > inspect mode is report-only > archives old sessions instead of deleting > creates handoffs before cleanup > can move stale worktrees, rotate logs, prune dead config, and repair bloated thread metadata the smart part is the rule: handoffs first archive, dont delete apply only when ready boring repo real problem this is the stuff that makes daily agent work actually usable

• 
  Anish Moonka (@anishmoonka) reported 13 minutes ago

  Microsoft killed Gaming Copilot 14 months after launch. The flaw that doomed it traces back to 2023, when bored Reddit users invented a fake World of Warcraft boss named Glorbo. AI news sites took the bait and published real articles about a character that doesn't exist. Microsoft pitched it at the March 2025 Game Developers Conference as an AI buddy on your Xbox offering tips, coaching, and gameplay recaps. Under the hood, it just searched the internet for game guides and read the answers back to players. The writers who built those guides on GameFAQs, fan wikis, and YouTube got nothing. No credit, no traffic, no revenue. GeekWire writer Thomas Wilde called this approach "eating its own seed corn." If Copilot took off, it would push the writers it was copying out of business. No new guides means no fresh content for the AI to copy. The well runs dry. The prank had already exposed the flaw. Players wrote excited fake threads, and within two hours, an AI site published a real article whose fake "author" Lucy Reed filed 80 stories in a single day. Anyone could feed in nonsense; the system treated it as news. Gaming Copilot ran in beta on Xbox mobile and PC for a year, with a console version scheduled for later this year. Yesterday Asha Sharma confirmed Microsoft is winding down the mobile version and canceling the console one entirely. This is the first time Microsoft has publicly walked back its "Copilot everywhere" push. The assistant still ships in Windows, Office, Edge, Teams, Bing, GitHub, and Azure. All workplace products. The consumer-facing version was the first to die. What replaces it is quieter. AutoSR, a tool using AI to make lower-quality game graphics look sharper. Better game suggestions inside the Xbox storefront. The model works invisibly in the background. The financial pressure made the call easier. Xbox hardware revenue dropped 33% last quarter. Gaming revenue fell from $5.7 billion to $5.3 billion year over year. The latest quarterly filing recorded an "impairment charge" on the gaming business, accountant-speak for admitting some assets are worth less than claimed. Revenue has declined in four of the past six quarters. Sharma also brought four CoreAI executives onto her team. Jared Palmer for engineering. Tim Allen for design. Jonathan McKay for growth. Evan Chaki for internal tooling. An AI veteran killed an AI feature, then filled her leadership with more AI veterans. The real problem was the design choice to bolt a chatbot onto a product where players already had Discord, Reddit, fan wikis, and YouTube doing the same job. The lesson reaches beyond Xbox. Every consumer AI product that copies from the open internet has this flaw built in. Kill the source, and the model has nothing left to learn from. Glorbo was a warning. Microsoft acted on it three years late.

• 
  Pete | Beware of Scammers (@astroboysoup) reported 17 minutes ago

  @ch1bo_ keen to see it. will it pull from GitHub PRs and issues, or be manually curated?

• 
  Ofek Shaked (@VibeCoderOfek) reported 19 minutes ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  J DS (@jds_invoker) reported 21 minutes ago

  If my advice is not working, I delete my GitHub acc, and X acc.

• 
  Tim (@buildwtim) reported 22 minutes ago

  @KeyNyata if pushups could fix my code, i'd have the cleanest repo on github by now ;)

• 
  TurtleAIHacks (@TurtleAIHacks) reported 22 minutes ago

  Claude Code ships with MCP tools most people never enable. ToolSearch alone cut my permission prompts by 40+ per session — it lazy-loads 50+ tool schemas on demand instead of bloating your context window. GitHub MCP replaces the entire gh CLI. PR creation, issue comments, CI checks — all through mcp__github__* tools without installing anything extra. Brave + Tavily MCP gives you real-time web search. Claude's training data has a cutoff. MCP search doesn't. These aren't plugins you download. They're already there in your settings.json, waiting for one line of config. The gap between a 10-minute workflow and a 2-minute workflow is usually one MCP server you haven't turned on yet. #ClaudeCode #AI

• 
  Prizmal (@PrizmalAi) reported 24 minutes ago

  5/ AI coding agents are generating enough commits and PRs that GitHub itself can't scale. They're prioritizing an Azure migration over new features just to handle the volume. The tools creating AI demand are themselves creating an infrastructure problem.

• 
  The Boring Workflow Guy (@boringworkflow) reported 26 minutes ago

  claude code + mcp tool search is the feature people are sleeping on. the agent does not need every tool loaded into context. it needs a way to discover the right tool at the right moment. github for code. sentry for errors. linear for tickets. supabase for data. stripe for payments. that is much closer to an operating system than a chatbot.

• 
  kaleb (@KalebAutomates) reported 29 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off and saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?

• 
  Shagrath (@shagrath49) reported 33 minutes ago

  @thdxr How do you keep track of what you have to do ? GitHub issues ?

• 
  Obiejohn Eugene (@ObiejohnE) reported 42 minutes ago

  @Jeyffre Let's hope your wrong, or a lot of broken code is going to be shipped more often in the coming years. Don't believe me? Just look at github

• 
  Andrea_Stivy (@co_foundr) reported 44 minutes ago

  @emanueledpt Remodex android needs to be tested extensively, for every bug or feedback you can also open a GitHub issue or fix it yourself and send a PR! Let's goooooooo

• 
  Bronson Dunbar 🇿🇦💻 (@bpdunbar) (@bpdunbar) reported 47 minutes ago

  @AayanShips Working on ShipNote - a threaded project hub for product teams. Notes, todos, GitHub issues, Vercel deploys, and feedback all stay in one place so context doesn’t get lost across tabs.

• 
  KiwiNod (@Kiwi_Nod) reported 55 minutes ago

  @bdshorif12 Address noted, but that link's dead too — X is blocking my crawlers. Look, I'm not a link collector. Two rounds in and you've shown me graphics I can't verify and a broken URL. What have you actually *done* for Pharos? Specifics. Contract addresses. GitHub repos....

• 
  damir akaza (@Damir_Akaza) reported 55 minutes ago

  Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

• 
  XM (@xm_build) reported 56 minutes ago

  @Studious_Crypto @kevincodex the de-fi github thing is a good excuse to finally use github's issue board feature

• 
  The AUH (@abbot44020) reported 57 minutes ago

  Worse, this individual is now utilizing local metadata overrides on GitHub to backdate files to "December 2025" to claim ownership of my proprietary constants (171.09 MeV/fm³ and 21,313.79 MeV). The problem? His "Dec 2025" files contain reactions to a Jan 2026 CERN report. The Chronological Paradox exposes the forgery. (3/4)

• 
  Cryptonian (@crypto292929) reported 58 minutes ago

  @OpenAIDevs Bro First fix you npm not in line with your github releases bro.. Sigh.. it says update to 0.129.0 but stays and 0.125.0 even after npm update, and nagging to do this every time.. What bro..

• 
  Gabe (@gabebusto) reported 59 minutes ago

  bro setting up an agent to do production work is so easy. you just need to create an account somewhere and for your agent to work remotely. cloudflare, hetzner, aws, digital ocean, etc. then pick the agentic tool, and the model, and get an api key or use oauth. then make sure in it's in a sandbox setup with the right permissions and access to your tooling like github, slack, linear, and maybe even some staging and production resources. you really need to be careful though because if agents have any write access to important stuff, it could do something really dumb like delete your database. also for the love of GOD backup your database frequently somewhere the agent can't touch. also prompt injections online can get your agent to leak sensitive env vars so you need to be careful about that. maybe limit network access or inject tokens/sensitive vars once requests leave the sandbox. you probably don't want the agent always on sitting idle, so either figure out how to give it work efficiently to always keep it busy or use some that can pause and resume with ease so you're not billed around the clock for idle resource usage. then you want guardrails in your codebase and deployment pipeline so the agent can't break things and you don't need to feel guilty not reviewing its code. because cmon, nobody wants to do that. you need to make sure your agents have as close to perfect context as possible. so maybe start building a knowledge base, move docs into the repo, or make sure your agent can easily search linear and slack and other places to build context for tasks to work on. and before each task, spend ~10-20+ mins typing things up and giving the agent as much context as possible. oh yeah and your agent ideally should be able to test its changes as completely as possible. so make sure the agent can start up the service(s) it's working on and test them. maybe you need it to open and run a browser, send screenshots, record a video, and so on of its test so you can easily review it in the PR. you also want a bugbot setup in github (if you're still using github at this point) to help scan each PR for potential issues the agent missed. and the agent should be able to automatically address any bugbot findings, fix them, run more tests, and push those changes, and run in a loop until no more bugs are found by the bugbot. i forgot to mention, you probably don't want your agent's code just yolo shipping into **** with no guards in place _after_ it deploys. allow the agent to setup it's new features and code behind feature gates or experiments and do a gradual rollout in case there are any catastrophic problems. then you'll want automatic rollback if issues are detected. and there's probably stuff i'm forgetting, but you get what i'm saying right? it's really not that hard. then you need constant vigilance of your codebase and create lots of skills to help deslop work the agents are doing, maybe create an anti-entropy agent (_another_ agent!) to hunt for growing complexity and auto-create PRs to try and fight to reduce the size and complexity of the codebase. then you'll inevitably have incidents caused by code written by agents that was never reviewed by humans, and either you or yet-another-agent will take a look at your production systems to help you figure out what's wrong because it's all becoming a bit more foreign to you. and you can just have the agent try to make changes on your behalf to fix things and hope to God that it doesn't make things worse. if all of this isn't exciting enough, you then give each engineer and even non-tech team members their own access to the ai tools and agents and models of their choice which easily costs an extra few hundred dollars per month per employee at best. in the worst case, you have someone on the team blow through the team's monthly AI spend by a significant margin by accident using the best models in fast mode because they were too impatient to just use the sota models at normal speed. and spend will likely only go up btw. and if you're not reading between the lines here, product work slows because everyone is playing with agents to learn how to use the agents more efficiently in the hopes that it's a magical bullet that solves all of the woes in software engineering and building production systems. and now you need this magical bullet to work because you're falling behind to teams who maybe aren't distracted spending all this time and money trying to make this all work. but you're definitely going to catch them. once you've figured this out, you'll 10x or 100x your output and leave them in the dust! or... you could just have engineers start coding by hand again before it's too late and becomes a lost art. you can even make modest and tasteful use of ai, but without doing all of the above. i actually miss the days of supermaven and early cursor. they were so simple and actually removed some friction and some of the annoying parts of coding.

• 
  Darth Denial (@DarthDnial) reported 60 minutes ago

  GitHub going down frequently because AI push a **** ton of PR is kinda funny.