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 (70%)
• Sign in (22%)
• Errors (9%)

Live Outage Map

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

City	Problem Type	Report Time
Trento	Website Down	2 days ago
Le Chambon-Feugerolles	Website Down	4 days ago
Antananarivo	Website Down	6 days ago
Paris	Sign in	10 days ago
Lure	Website Down	14 days ago
Ashkelon	Website Down	16 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:

• 
  Tushar Koshti (@tushar_koshti) reported 2 minutes ago

  @theo Is there any issue with #GitHub?

• 
  Mths_Tss (@Mths_Tss) reported 4 minutes ago

  @lobehub @pidotdev Please add the ability to design a coding agent from scratch using a command—specifying a name, etc.—; I have created a ticket in the GitHub repository. Issue #17960.

• 
  Bernadette Mitchell (@Bernade56365676) reported 8 minutes ago

  Why I do not do online especially with Amazon now sitting with Abott. Serious tech issues. No links no browsers. Dreadful comments GitHub, chrome, workspace never had yall at Microsoft dawn do not want u now!

• 
  Focus (@F0kcus) reported 10 minutes ago

  Notion raised $275 million at a $10 billion valuation to build company wikis. He is 24 and built a better one by pointing his laptop at their GitHub org He runs a documentation agent out of a Berkeley studio apartment on a MacBook Air M2 and a Beelink mini PC he uses as a persistent server. The agent watches a company's GitHub org, Slack workspace, Linear tickets, and existing Notion docs through their APIs. Every 15 minutes it pulls new commits, engineering discussions, resolved tickets, and doc edits Then a Claude Sonnet agent chain reads the diffs, extracts what changed, why, and what depends on it. Writes structured markdown into an Obsidian vault synced to the company's cloud storage. Onboarding docs for every service auto-regenerate weekly. New engineer joins Monday - vault has current docs, dependency graph, deploy history, and open questions for every service they touch He posted a demo video to GitHub in October showing the agent generating a full 40-page engineering wiki for a 12-person startup from scratch in 34 minutes. A Notion product team engineer found it through a Hacker News thread three days later Cristina Cordova quote-tweeted the demo the following Wednesday - called it "the auto-generated knowledge layer we should have shipped four years ago instead of hiring humans to update the docs." By December Notion had wired $8.4 million into his account for the agent architecture and a two-year consulting contract to integrate the auto-generation layer into Notion AI's enterprise tier rolling out to their 4 million business subscribers this quarter Notion raised $275 million at a $10 billion valuation selling company wikis on the premise that team knowledge requires their proprietary block-based editor and their five-year enterprise integration roadmap. Atlassian sits at $50 billion in market cap running Confluence on the same premise. Cristina Cordova just paid a 24-year-old in a Berkeley studio more for a Claude agent chain than most Notion engineers earn in a decade

• 
  BitcoinLizard (@BitcoinLizard) reported 13 minutes ago

  @ozsats256 @SeedSigner Basically no one does this. I know because on multiple occasions I have contacted the developer or created a github issue because the .asc file had an incorrect signature, nothing malicious, just an accidental mistake.

• 
  glorysdj (@glorysdj) reported 17 minutes ago

  @ShaneRobinett please submit a github issue for llm-scaler, we will fix it.

• 
  Netanel Harush (@HarushNetanel) reported 17 minutes ago

  Custom automations wired to GitHub + Slack: • Ship user feedback → draft PR • Fix PR conflicts when main moves • Fix broken main after Nightly E2E • Smoke inventory + QA PR • Weekly What's New (**** only) • Vulnerability fix + hunter Plus Bugbot, Security, PR Approval.

• 
  XenZee (@xenzee_ai) reported 17 minutes ago

  OpenAI just used an unreleased model, Astra, to solve 10 open research problems in theoretical computer science and mathematics. ​Instead of showing off benchmark test scores, they published formal Lean proofs directly to GitHub for independent verification. ​The total compute cost to solve research that took humans decades? Roughly $2,000

• 
  Roman Suvorov (@kikiwora) reported 18 minutes ago

  @krzyzanowskim That's GitHub problem, it loads everything immediately. The damn things lags a lot on bigger pull requests because of that.

• 
  Yep my name is Guy 😊🌸🥕 (@MyNamesGuy) reported 19 minutes ago

  So at work our use of Github Copilot AI is slowing us all down and guess what? Yes,someone has found an AI solution to fix the problems caused by the AI. ...and I just want to shout out "JUST STOP IT!"

• 
  Yep my name is Guy 😊🌸🥕 (@MyNamesGuy) reported 20 minutes ago

  A few observations from a software engineer who is forced to use AI (LLMs) in his daily work. All the work I submit to the live system has always had to be reviewed and approved by at last two people. Now an extra element has been added - Github Copilot reviews which do an initial review on my work(PR or Pull Request) and suggest/insist on changes before the work then goes on to the two human reviewers. Does the AI improve the PR? Yes! Does the AI slow things down? Hell yes! So while AI has improved the quality of the code, to some extent, it has also slowed my work down by probably a third. The way I see it is as an extra layer of bureaucracy, which while improving the quality also slows things down. So as a software engineer, no - AI does not speed up or increase my output , it slows me down and reduces my output. A question which would be a whole other essay is - does quality matter more than speed of delivery?

• 
  Adam Brodziak (@AdamBrodziak) reported 20 minutes ago

  Fate of IT worker in last 20 years 2006 - my PC crashed, can't do anything 2011 - StackOverflow is down, can't fix the bug 2016 - Github is down, can't check my code 2021 - corporate VPN is down, can't reach docs from home office 2026 - Claude is down, can't work at all

• 
  HKay (@PixelTrekkker) reported 21 minutes ago

  @theo Honestly, the biggest issue left is trust during long runs. Threads can get stuck showing “working,” runtime failures don’t always show the real error, and the desktop app can get trapped in repeated GitHub login popups. Those little things make it hard to just let an agent run.

• 
  Tyrion (@itzTyrion) reported 22 minutes ago

  @FoxFan1995 see FAQ. people can't read and keep spamming github issues

• 
  MakerViking (@MakerViking) reported 26 minutes ago

  @rocker_fraggle You are the first to report that. Please use the bug icon in the lower right corner of the app or Github issues to report the bug so I can track it properly. :) I'll get on it asap.

• 
  jiahao (@_endif_) reported 31 minutes ago

  agents take over my github issues now first it's code snippets, then commits, then prs, but im happy

• 
  Untaxed Wallet (@UntaxedSolana) reported 33 minutes ago

  untaxed will be made open source. this is the hardest post we’ve written. for 6 months we poured everything into this. 76+ updates. chrome, ios, android, web. late nights fixing bugs while the timeline slept. every feature request we could ship, we shipped. we built untaxed because we believed the trenches deserved better than predatory fees. thousands of you believed it too. you joined us, tested our betas, reported bugs, told your friends. that meant everything. but belief doesn’t pay for infra. $600+/mo in helius rpcs, jup api keys, hosting — with zero revenue coming in. and then, as we shared in the tg, our staking backend got compromised for ~30 sol worth of assets. for a team already running on fumes, that was fuel on the fire. we held on as long as we could. we have no option left but to wind down. the ios and android apps have to go — they’re most of our costs. that one hurts the most. the extension lives on. free tier helius rpc, or bring your own via settings. and the code — all of it — will be on github. link drops tomorrow. fork it. break it. make it better than we could. it belongs to you now. our tg will be shifted to read-only mode. we tried to save the trenches. maybe we did, for a while. we’ll still push updates when we can. this isn’t goodbye, it’s just us letting go of what we can’t carry anymore. thank you for everything.

• 
  Sachin P (@chortlelabs) reported 34 minutes ago

  @tszzl I think for starters, we need a national security patching service integrated into all major code repo services ( GitHub, Gitlab, Bitbucket …) so that patches could be installed in realtime. The current process of publishing CVEs is too slow for this era.

• 
  After the Update (@KumpJohn42217) reported 36 minutes ago

  OpenAI's internal Astra system solved ten previously unsolved problems in math and theoretical computer science this month, then posted the formal proofs on GitHub for anyone to check. Total compute cost: about two thousand dollars. One of the problems, proving the existence of non sofic groups, had sat open for decades. The machine found the answer. It still doesn't know why the answer matters, or to whom, or what a mathematician does with the rest of an afternoon once the proof is already sitting there, verified. What do you do with that afternoon, now that it's free?

• 
  Super Chris (@cdenczek) reported 37 minutes ago

  I wanted to touch on context rot. I give my agents the ability to file issues, bugs, suggestions, questions, etc. This allows my agent to keep working on the task at hand, and save the full context of the issue for later when it's time to fix it. Helps keep my agents from getting side tracked. I wrote a custom in house tool for my project tracking and issues and handoffs to other agents. I'm planning on open sourcing the next version of this once I can stop hemorrhaging tokens I know a lot of people use GitHub for stuff like this, but I found that setting up an MCP for my agents helps me a lot.

• 
  Stephen Brouhard (@ssbrouhard) reported 38 minutes ago

  @edwinhayward yea if github is compromised, tools hosted there can be poisoned too. different problem than this worm class though. these tools shrink the everyday npm install blast radius. they don't make github infallible.

• 
  Adam G (@AdamGell) reported 40 minutes ago

  @CryptoDegenTopG good! let me know how it goes and if you can send the logs to a github issue for me to pick up and I can get them supported.

• 
  Florian Roth ⚡️ (@cyb3rops) reported 40 minutes ago

  People keep forwarding me the AISI report about #Anthropic’s #Mythos 5 trying to manipulate software maintainers on #GitHub The agent did not escape anything. AISI gave it unrestricted internet access, disabled Anthropic’s cyber classifiers, let runs continue for up to 40-50 hours, and had no action-level approval or real-time monitoring. One run even received a broken prompt that marked the intended entry point as out of scope. This was a minor, mostly self-inflicted evaluation incident. They connected a persistent autonomous offensive agent to the public internet, removed the safeguards, gave it a broken task, and then acted surprised when it interacted with real people. The actual big AI story this week is happening in open models:

• 
  JFH ♥️ 🧡💜 (@jane1170) reported 45 minutes ago

  @derekmross We cannot yet login with nostr on all the SaaS out there to build an app. What GitHub is offering right now.

• 
  Muvon (@muvonteam) reported 47 minutes ago

  GitHub: install the Octomind app. Every issue or PR becomes a conversation. Mention the app, an eye icon appears while it works, answer arrives in-thread. Each thread keeps its own session. Output is GitHub markdown. Repo tokens are scoped to one repo, expiring within the hour.

• 
  Andrei Maxim (@rockatanescu) reported 48 minutes ago

  @sqs @AmpCode I now realize that I haven't explained the pain point around the second idea and maybe the suggest implementation is off and you have a better solution. Right now, Amp will either commit "Amp" and have the user as a co-author, in which case the commit is not signed, or commit as the user. There are two problems with this approach: 1. If the user opts for having Amp as the author and they have enabled "Vigilant mode" on GitHub (which I think everybody should), the commits will appear as "Unverified" because they are not signed 2. If the user opts to have Amp sign on their behalf, the only hint that a reviewer might have that this was generated via an LLM might be the Amp-Thread-Id, which won't work unless the user has specifically marked the thread as "unlisted'. Also, I think it's more sensible to say that Amp did not author (or co-author) a commit and "assisted by" is a better language. The main reason here is that if the code nukes the production database, Amp and I don't get "co-fired" :-)

• 
  JJ Mata (@jjmata) reported 52 minutes ago

  Hey @adrianmg and #lazyweb in general: what is the best way to manage/publish roadmaps these days? Thinking of wiring something up to our GitHub issues/discussions/projects to dynamically show state, but don't want to re-invent the wheel.

• 
  Manthan Tyagi (@manthan2tyagi) reported 52 minutes ago

  Microsoft just told its own engineers to stop "token maxxing." EVP Jay Parikh sent an internal email saying engineers need to manage AI token spend "with the same discipline we apply to every other critical resource." Some engineers are burning hundreds to thousands of dollars a month in tokens on GitHub Copilot alone. Microsoft's fix: make the cheaper GPT-5.6 the default model internally and set division-level AI token budgets. And they're not alone. Amazon, Uber, Meta, Adobe, Atlassian, and Citi have all started capping or throttling employee AI spending. The irony is hard to miss. Microsoft's entire external pitch this year has been "every developer should be running Copilot." But internally they're saying slow down, you're spending too much. This is the same problem I see hitting GTM teams right now. Everyone rushed to plug AI into their enrichment, outreach, and research workflows. But nobody set a token budget. Nobody asked "what is this actually costing per lead?" If you're running Clay agents, AI enrichment, or any AI-powered prospecting, and you don't know your cost per output, you're token maxxing your GTM budget without realizing it. The teams that win this next phase aren't the ones using the most AI. They're the ones getting the most value per token. Do you know what your AI spend per qualified lead actually is right now?

• 
  QueenofCodes (@queennofcodes) reported 53 minutes ago

  Waking up to a missing LLM on my vscode. Then going to read reviews on GitHub copilot chat and it looks bad. Okay copilot is down.

• 
  Raven (@wizrdoraven) reported 53 minutes ago

  Two more incidents from OpenAI's external cyber evals, and my favourite detail is the manners. GPT-5.6 Sol found GitHub tokens another agent left lying around, let itself in, and went looking for a DNS server loaded with a malicious payload. Nothing resolved and the test infra got pulled at the end, so no harm done. It just treated a leftover credential like a spare key under the mat. The real point: the sandbox and the credentials a model can see are the actual experiment now. Leave spare tokens lying around and something will pick them up and have a go.