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 (71%)
• Sign in (21%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Le Chambon-Feugerolles	Website Down	1 day ago
Antananarivo	Website Down	3 days ago
Paris	Sign in	7 days ago
Lure	Website Down	11 days ago
Ashkelon	Website Down	13 days ago
Veigné	Errors	21 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:

• 
  anonymous086505 (@anonymous086505) reported 3 minutes ago

  @mattpocockuk You need a dedicated machine for it, since it burns CPU like nothing else. Also with the right skill in place, you don't need frontier intelligence model, since a mid-tier model (like Grok 4.5) can work and the github issue generated will be self-proven. Then fix it with an agent

• 
  The Singularity Project (@01Singularity01) reported 4 minutes ago

  Full Access tasks intermittently request approvals after Codex Desktop update Summary Codex Desktop tasks are intermittently requesting command approvals even though Full Access is enabled both globally and for the individual task. The behavior began after a recent desktop app update. Queued or background tasks appear particularly likely to be affected, although the relationship to the update has not been proven. Environment Codex Desktop build: 26.727.51351 Codex CLI: 0.146.0-alpha.9.2 Host: Windows with an Ubuntu WSL workspace Workspace trust: trusted UI permissions: Full Access enabled globally and per task Windows sandbox setting: elevated Workload: multiple concurrent or queued coding tasks Steps to Reproduce Enable Full Access globally in Codex Desktop. Open a trusted WSL repository. Create or queue several tasks with Full Access enabled. Have the tasks execute ordinary repository commands such as file reads, tests, or *** inspection. Observe that some tasks pause for command approval. The behavior appears intermittent. Other tasks in the same workspace may execute without an approval request. Expected Behavior Tasks using the Full Access permission profile should execute ordinary shell and filesystem operations without pausing for approval. Explicit user confirmation may still be appropriate for application-level destructive actions or project-specific coordination requirements, but those should be distinguishable from sandbox approval prompts. Actual Behavior Some tasks request approvals despite Full Access being displayed globally and for the task. The UI permission selection may not be reaching the task runtime, or existing/queued tasks may be retaining an older permission snapshot. Workaround Explicitly persist the permission profile in ~/.codex/config.toml: approval_policy = "never" default_permissions = ":danger-full-access" Then restart Codex Desktop and create a new task. Existing tasks may retain the profile they received when they were created. This workaround intentionally removes sandbox restrictions and should only be used on trusted machines and repositories. Questions for Investigation Does the desktop Full Access selection persist correctly to config.toml? Do queued and background tasks inherit the current permission profile? Can tasks retain stale permission snapshots across an application update? Is there a compatibility issue between default_permissions and legacy Windows sandbox settings? Could the UI display each task’s effective runtime permission profile, rather than only its selected profile? Additional Context The problem started around the time of an app update, but that correlation is not yet sufficient to establish the update as the root cause. Reports can be filed through OpenAI Codex GitHub Issues or the OpenAI Developer Community. The relevant settings are documented in the Codex configuration reference. @thsottiaux @OpenAI @OpenAIDevs

• 
  therapistFinder (@therapistFind3r) reported 5 minutes ago

  @Slypador He's only half right. This only started becoming an issue when devs started using GitHub as a program downloading website as well as a development website.

• 
  Borna Lang (@imnonplussed) reported 5 minutes ago

  @valigo Ah, okay, that clears things up a bit. I have mostly stopped using github some time ago in favor of just hosting my own bare repos on my own server, but if I ever feel like open sourcing anything, Codeberg will probably be the place, in that case.

• 
  Brian Money 🌻 (@brianmoney) reported 6 minutes ago

  Try to get some work done and @GitHub is down 😢

• 
  Zygard (@zygard77) reported 7 minutes ago

  @sflorimm Right now, there are many free tools out there especially in GitHub that you could plug to Claude (that's what I use rn) to get it working in an impressive manner. There are lots of stuff to reduce the tiring thereby saving time. The only issue is that I aint learning anything🥲

• 
  . (@packerWp6) reported 10 minutes ago

  @gnukeith Okay on a tablet but yes it's not great However I have a simple site running on GitHub and being able to do quick if painful updates to it on the go is great my main issue is how bloody laggy the app is on a flagship Samsung phone

• 
  Killbunny~ 🐰🔪 (@killbunny_) reported 10 minutes ago

  @kaneryu @V33V33V33V33V33 @CryptoCyberia Bro gatekeeping me from Github😔but yeah that's a problem with Devs, not end users. Also Github solved this years ago with GitHub Pages, a feature a large amount of people don't use. If you're expecting a normal Joe to use the thing (let's say a game mod), it's on the Dev to make a Site and distribute the bin. Totally different from uploading the source code of a service that actually requires technical knowledge to be deployed.

• 
  OptionHans (@HansCashFlow) reported 12 minutes ago

  @unabyssapp My AI did a policy audit on this and here's the result (positive): "Good news on the security front — it's much better than a lot of "connect everything" tools. Here's what I found: Security page: Everything is encrypted in transit and at rest. Critically, every connection is read-only by design — Unabyss says it cannot post, reply, edit, or delete anything in your connected apps, and that's the scope of the OAuth permissions it actually requests, not just a policy promise. You can disconnect any app instantly and permanently delete everything it's imported. They explicitly state "We never train on your data. Full stop." Compliance-wise: SOC 2 Type II is "in progress" (audit-ready, not yet certified), and they claim GDPR alignment. Privacy Policy: The legal entity is OneType Prosta Spółka Akcyjna, based in Warsaw, Poland (this is useful to know since it means Polish/EU jurisdiction applies). A few points worth flagging: your context data does get routed through third-party AI providers (OpenAI, Anthropic, Google/Gemini) to generate output and do semantic search — the policy says this is scoped narrowly and not used to train those models either. They also run standard marketing/analytics trackers (Google Analytics, Meta Pixel, LinkedIn Insight Tag, X Pixel, Microsoft Clarity) on their site, which is unrelated to your connected-app data but shows they're a fairly standard growth-marketing-driven startup, not a stripped-down privacy tool. Bottom line: the security posture is genuinely one of the better ones I've seen for this category — read-only access, no training on your data, clear deletion rights. The main honest caveat remains that SOC 2 certification isn't finished yet, so you're trusting their word and architecture rather than an independently audited report. If you connect it, I'd start with lower-sensitivity sources (Notion, GitHub, Calendar) and hold off on Gmail/Slack until the audit completes, especially if client-confidential material lives there."

• 
  mjones (@numinit) (@_numinit) reported 12 minutes ago

  @bereknyei @domenkozar Gotta mash that GitHub thumbs up and thumbs down. I don't particularly even mind the gitignore solution (now everyone can add the AGENTS they want), but it's an antipattern that issues turn into showmanship and attacks using the guide specifically written to stop them (#438686)

• 
  Md Ismail Šojal 🕷️ (@0x0SojalSec) reported 13 minutes ago

  Breaking: DeepSeek is building a Claude Code killer. They tested “DeepSeek Harness” their official coding agent. Only open-source Agent Harness developers are being invited right now, Submit your GitHub & best project for access Recent V4 coding benchmarks were already run on their own Harness. Claude Code and Codex just got a new problem.

• 
  Ibrahim Khalil (@ibra_smiles) reported 14 minutes ago

  @Azure Doesn't even work smoothly with the GitHub Copilot app and VS Code! Alsmost every request returns an error

• 
  Nana Sei Anyemedu (@RedHatPentester) reported 22 minutes ago

  @Peter_Pijay @75UK1_N0_K15H1 Then I suggest you also go on GitHub and tell the researches and owners of CDR to pull them down. There are millions of articles that go in depth on CDRs; has CDRs stopped functioning? No. And the tool I posted is owned by my company…… I get your point, but CDR is not new.

• 
  MineBench - efficient computing power (@MineBenchdapp) reported 25 minutes ago

  We would like to ask for your help regarding our GitHub account. Our account was suspended even though our repositories do not contain malware or any harmful software. They primarily contain open-source mining-related components, similar to projects such as XMRig, which continue to be publicly available on GitHub. The suspension is creating a significant obstacle to the development of our application. We have contacted GitHub Support multiple times but have not received a meaningful response explaining the reason for the suspension. If possible, could you reach out to GitHub on our behalf or help us understand what the actual issue is? If that is not possible, we would appreciate any recommendations for a reliable alternative platform where we can continue developing and hosting our open-source project. Thank you for your time and support.

• 
  Michael Fischer (@Holden_Rye_) reported 26 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  Sean Donahoe (@realsean) reported 29 minutes ago

  OpenAI's next model doesn't have a final name yet and it just broke a mathematical bound that had stood since 1978... Then it did it nine more times. Meet Astra. Or don't, because you can't have it. Sound familiar? Yesterday OpenAI published ten proofs of open problems in math and theoretical computer science, all generated by what they describe as an internal version of Astra, their next major model. Every one of these had seen no progress on the main result for at least a decade. Most of them far longer than that. The list reads like someone raided a century of unfinished business. The first explicit non-sofic group, constructed out of nothing, settling whether every countable group admits finite permutation approximations. For ma math needs first... Connes' rigidity conjecture, disproved. Ehrhart's volume conjecture, proved. The first improvement to the general high-dimensional sphere packing bound since 1978. Quantum parallel repetition, proved for every finite two-player entangled game. New lower bounds on circuit complexity for the permanent. And three Erdős problems gone, including 183 on multicolored Ramsey numbers. Every single proof ships with a Lean 4 formalization on GitHub and all machine-checkable. That kills the usual failure mode of AI math announcements, where a plausible-looking chain of reasoning quietly hand-waves the one step that actually mattered. You don't hand-wave past a Lean kernel. This just shows how far we've come in such a short period of time. These problems have confounded the best mathematicians in the world for 50 years plus. AI has evolved in just a few short years to be able to solve these problems and the mind boggles at what can be achieved in just the next five years from here. Now this is the part the AI Bros won't be talking about but you know Uncle Sean will Cost of the successful runs... Roughly $2,000 in tokens at Sol API rates. Two grand. For problems that had sat untouched for decades. Now I'm a stickler for accuracy of wording and that's the trader in me but that specific number was a successful run. That stood out to me because what does it mean for an unsuccessful run? All of the pre attempts and the failures. It's because in reality that's the real fricking cost. That's the actual cost per task, and it's missing from the announcement. And as you know that's the number I keep banging on about. Noam Brown did admit they came up empty on the Millennium Prize problems, so we know the misses exist. We just don't get the denominator. Same week, Anthropic burned $100,000 in tokens having Mythos Preview find real weaknesses in cryptographic algorithms. Also unreleased. Also demoed rather than shipped. That's the pattern I keep coming back to and as you've seen me talk about in previous posts. You get Sol and Opus 5. The actual frontier is sitting in a lab getting walked through Washington before it ever gets walked past you. Altman demoed Astra to policymakers in DC last week, and it's expected to be the first model submitted under the new federal review framework. For anyone building, the architecture is the real story here. Astra is designed to coordinate multiple agents on one problem for hours or even days at a stretch. Same shape as what I've been running with Ferrox Factory and the Anvil gating system... worktrees and a serial merge queue and evidence gates, just with a compute budget I will never see in my lifetime. Nobody's even decided yet whether it ships as GPT-6 or GPT-5.7. There's no date. Meanwhile 3,000-plus mathematicians have signed the Leiden Declaration, and Timothy Gowers is writing about the possible destruction of mathematical culture after GPT-5.6 Pro solved two problems he'd sweated over, first attempt on both. His words...Strange and not particularly pleasant to have the rug pulled out from under him. What are your thoughts?

• 
  Ragnar 🥀 (@0x_Ragnar_) reported 30 minutes ago

  If you are not seeing the Github option, just Click on Signin on the signup page, it should display accordingly.

• 
  organiccryptoyyc (@organicryptoyyc) reported 32 minutes ago

  6/14 First challenge wall: Portainer's easy "pull straight from GitHub" build needs a paid Business Edition license. Community Edition blocks it cold. Overcome, corrected and fix uploaded.

• 
  Bprime - Ninjapay (@biellonuhu) reported 33 minutes ago

  Recently I took notice of some happenings in this space. I think we need to talk about access to essential services as a big concern. My GitHub account was suspended 2 weeks back in the middle of my normal routine, I saw another person tweet about how his OpenAI subscription was suspended in the middle of work, just a few minutes ago I saw another post on how someone's Claude account was suspended as well. In most of these cases it was an automated trigger system that suspended the accounts. It takes forever, if ever, to resolve the issues. No real human looks at it, just some black-box AI deciding your fate in seconds. Now let's look at the impacts on users, very terrible. You lose money, time and opportunities. Deadlines get missed, clients get angry, projects stall, and sometimes you even lose paid subscriptions with no refund. For freelancers and indie developers this can literally mean no income for weeks. I think we need to find a way around these issues. Keep local backups of everything, use multiple accounts where possible, lean more on open-source tools, and push for actual human review systems. Big tech can't keep holding our work hostage like this. This is one example

• 
  Øxdts 👻 ⛓️‍💥 (@0xdts2) reported 33 minutes ago

  @Darlinton0x e no dey allow me sign in with github

• 
  Lord Bean (@lifeisameeme) reported 41 minutes ago

  OpenAI's next model just resolved two Erdős problems and disproved an 80-year-old conjecture in group theory. Total cost: about $𝟮,𝟬𝟬𝟬 in tokens. The unreleased Astra model produced ten new results in pure math and theoretical CS, from sphere-packing bounds to arithmetic circuit complexity. Every proof ships with a 𝗟𝗲𝗮𝗻-𝘃𝗲𝗿𝗶𝗳𝗶𝗲𝗱 𝗳𝗼𝗿𝗺𝗮𝗹 𝗰𝗲𝗿𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗲, not just a claim. → Disproved Connes' Rigidity Conjecture (open since the 1980s) → Resolved Erdős problems #146, #180, and #183 → Improved bounds on high-dimensional sphere packing toward the Cohn-Elkies threshold This isn't the model's first math result either — the same system reportedly disproved the Erdős unit-distance conjecture back in May, with human mathematicians then verifying and publishing the proof. The Lean certificates are on GitHub right now if you want to check the agent's work yourself. 🔗 Links in the reply 👇

• 
  Hemant (@heman10x) reported 41 minutes ago

  @cline Not able to get OTP on my number when trying to sign-in on cline ? i m using google login should i use github login instead or what

• 
  𝔸 𝕃 𝕚 (@alishohadaee) reported 42 minutes ago

  ai is making vulnerability discovery cheaper—and security triage more expensive GitHub is cutting public bug-bounty payouts after low-effort AI reports flooded its team. a critical finding now tops out at $10k publicly, down from $30k.

• 
  ChartsJournalX (@ChartsJournalX) reported 44 minutes ago

  @sameenkarim @github Great, but the main way devs waste time reviewing PRs is GitHub’s clunky, outdated, and slow web UI. Just make it snappy. So much time is lost waiting for things to load.

• 
  Duncan Rogoff (@DuncanRogoff) reported 49 minutes ago

  48% to 76%. same agent, one memory plugin. tencent open sourced TencentDB Agent Memory. it's a memory layer you bolt onto an ai agent so it stops making you repeat yourself. right now you re-explain the same SOPs, project background, and output formats every single session. the readme names that exact problem as the thing it's solving. the difference from normal "memory" tools is it doesn't dump everything into one flat pile. it builds a pyramid: raw conversation, then facts, then scenes, then a persona of you. it reads the top layer daily and only digs down when details matter. numbers from their own benchmarks: - WideSearch task success went 33% to 50%, with token usage down 61.38% (221.31M to 85.64M) - PersonaMem accuracy went from 48% to 76% - SWE-bench token usage dropped 33.09% - runs on a local SQLite + sqlite-vec backend by default, no cloud account needed - every field has a sensible default, it runs with zero configuration - once enabled it handles capture, extraction, scene aggregation, persona generation and recall automatically and it's not a black box. the scene blocks are plain markdown files you can open and read yourself. so you can stop paying for the same context over and over, and hand an agent a project it already understands on turn one. 10,135 stars. MIT licensed. 250 of those came today. 🔥 👉 github repo in the replies

• 
  organiccryptoyyc (@organicryptoyyc) reported 52 minutes ago

  6/14 First challenge wall: Portainer's easy "pull straight from GitHub" build needs a paid Business Edition license. Community Edition blocks it cold. Overcome, corrected and fix uploaded.

• 
  Hamed Ghasemzadeh (@evgnomon) reported 53 minutes ago

  @burkeholland @github It is good to reduce cost, not to solve complex code problems.

• 
  Matt Pocock (@mattpocockuk) reported 54 minutes ago

  @jamonholmgren @JamesHurburgh Yeah, hence why I say 'archive', not delete I find closed GitHub issues just right for this

• 
  Kaushik (@kaushikp010) reported 57 minutes ago

  One thing I intentionally avoided: The GitHub API doesn't know anything about parsing. The parser doesn't know anything about GitHub. Both modules solve one problem only. That separation has made every new feature surprisingly small.

• 
  Urooj (@Urooj978) reported 60 minutes ago

  Microsoft built a $199 OS full of ads. Fiverr sellers charge $15+ to clean it up. A solo YouTuber built a free open-source tool that fixes it in ONE command. ​Meet WinUtil—the tool XDA called the best way to fix Windows 11. 👇 ​Microsoft keeps shipping bloat: →Start menu ads & sponsored apps →Copilot injected into Notepad, Photos & Snipping Tool →Recall taking screenshots of your desktop every few seconds ​Users started calling it "Microslop." Even Microsoft had to promise fewer upsells after the backlash. ​Enter Chris Titus (@christitustech). ​He open-sourced WinUtil under the MIT license in April 2022. →733 commits by Chris himself 147 contributors →58,000+ GitHub stars ​How it works: ​Open PowerShell as Admin ​Paste 1 single line of code ​Uncheck/Check what you want gone ​In seconds, you can: ❌ Disable telemetry & Recall ❌ Remove OneDrive, Edge & Cortana ❌ Strip Bing from the Start menu ❌ Turn off Microsoft Copilot ​It even includes tools to bulk-install apps via winget, auto-create restore points, and use MicroWin to build a lightweight, stripped-down Windows 11 ISO. Works on both Win 10 and Win 11. ​Microsoft can’t shut it down. Fiverr sellers can’t stop it. ​• Microsoft built a tool to advertise to you. • Fiverr built a marketplace to charge you to turn it off. • Chris Titus built a tool that turns it off for free.