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	2 days ago
Antananarivo	Website Down	3 days ago
Paris	Sign in	8 days ago
Lure	Website Down	12 days ago
Ashkelon	Website Down	13 days ago
Veigné	Errors	22 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:

• 
  Samuel Robertson (@sm0olr) reported 1 minute ago

  @LukaTheFounder @theo With the desktop app on nightly? Hmm there’s a GitHub issue that hasn’t been closed yet that broke the mobile app but I’ll try reinstall like the other guy mentioned.

• 
  Inference Engine (@iedaily_) reported 2 minutes ago

  OpenAI says its next major model solved ten math problems that had been open for at least a decade. Astra, still unreleased, built the first non-sofic group, a question Gromov posed in 1999, and disproved Connes's rigidity conjecture. Three Erdős problems went with it. The tokens cost about $2,000. Every proof ships with a Lean certificate on GitHub. No outside mathematician has checked them yet, but this stuff is cool enough to anchor a medal case (on a Fields Medal scale)

• 
  The Singularity Project (@01Singularity01) reported 3 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

• 
  Soyeb ***** (@SoyebGanja) reported 3 minutes ago

  Beyond custom tools, the ecosystem is accelerating through Prebuilt MCP Servers. Need your agent to talk safely to Postgres, Slack, or GitHub? You configure a standard server protocol instead of writing 500 lines of custom API boilerplate.

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 4 minutes ago

  @N0V4Dev Stacked PRs is the most broken feature GitHub has ever shipped. It must be embarrassing to be working there right now.

• 
  Siddhant Kashyap (@_devSid) reported 7 minutes ago

  A few months ago I started using @kestra_io for a prsnl project if you want to orchestr8 anything give it a try Never thought I'd end up contributing to it. Picd issue, learned the codebase, got my 1st PR merged and kept going from there. 😎 OS is pretty asm #OpenSource #GitHub

• 
  Lukas DerBaum 🌲 (@DerbaumLuk37729) reported 15 minutes ago

  @CryptoCyberia If you can't even find a download button on github, you problem shouldn't use the software

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

  Recently I took notice of some happenings. I think we need to talk about access to 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

• 
  Carl010010 (@carl010010) reported 18 minutes ago

  @davis7 I had to find out about this in the GitHub issues last month. So odd that it’s not on by default.

• 
  Merlin Clos (@MerlinClos) reported 19 minutes ago

  @jarredsumner Nice feature! We will be able to optimize our CI more precisely thx Did you deploy a new version of Bun that doesn’t break the "bun install —frozen-lockfile"? Since yesterday I keep encounter this issue (that it said closed on GitHub) with docker pull canary latest

• 
  Α Ω Programmer (@OmegaNekoSimp) reported 20 minutes ago

  REAL QUESTION: How many of you know that *** isn't just a client to push to GitHub or GitLab? Yall know that *** is the actual server software too and you don't need 3rd parties, right?

• 
  Wilco Kruijer (@WilcoKr) reported 25 minutes ago

  When analysing agent traces using LLMs for self-improvement it often overfits on specific failures This paper offers a solution. In your loop include: "What is the least restrictive rule that explains every failure while remaining consistent with successful cases?" An example: Say your agent has tools for grep, GitHub search, and web search. A failure scenario is when it uses web search but it should've used grep. A naive overfitted change to the skill might be "never use web search", this is the strongest hypothesis for a fix. According to the paper, a much weaker statement should be used instead: "prefer the cheapest information source, only escalate when information is insufficient".

• 
  Corey J. Gallon (@CoreyGallon) reported 26 minutes ago

  Agents can build the product now. The launch video for it is still the hard part. @Rames_Jusso, a software engineer at HeyGen, spends "HTML Is All Agents Need" on one fix for that: stop teaching models a video format and let them write the one they already know. It's on @aiDotEngineer's YouTube. For anyone wiring an agent up to produce video, the talk gives the format, the rendering trick that makes it deterministic, and the numbers from running it in the open. - HTML, CSS and JavaScript are the native tongue of LLMs. Most training data is scraped web pages. A custom DSL or your own JSON structure asks the model to speak a second language. - The thinnest wrapper won. They tried bigger system prompts, more context, skills, various wrappers. What survived was essentially plain HTML with a few data attributes for timing. - Gemini 3 Flash was the design partner. The bet: if a small model can author workable code in the format, larger coding agents certainly can, and they'll only get better at it. - Browsers are async on purpose, video can't be. Fonts restyle, images arrive late. Hyperframes freezes the clock, seeks frame by frame, waits for everything on the page, screenshots, then moves on. - Same pixels in preview and render. Preview and render both happen in the browser, so anything renderable there lands in the video: three.js, charts, SVGs, shaders, WebGL, WebGPU, Lottie. - The skills teach taste, not syntax. Since agents already know the language, the skills cover what makes a good video, continuously evaled to raise the floor on single shot output. - Craft still beats one prompt. Narrative, storyboard frame by frame, motion per frame, merge, then last mile editing in the studio with a human in the loop. - It's running at scale. 1.3 million videos rendered by open source users in the last 90 days, 267,000 creators, around 15,000 videos a day, 32,000 GitHub stars. Free, and it works with any coding agent that writes HTML. - The honest caveat. Models still aren't good at creative work, which is why they started a code to video benchmark and are looking for collaborators on it. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Nan Yu (@thenanyu) reported 29 minutes ago

  You should be able to pledge tokens for issues that you open and open source repos. Write a spec in the issue with a pledge. If the maintainer accepts, GitHub passes the issue verbatim to a cloud coding agent at the requester’s expense. No more slop PRs

• 
  Nikhil Dubey (@nikhild791) reported 32 minutes ago

  @paulg similar answer exists for coding as well we have solution for every github issues code for every question also when it comes to evals we have clear goal of getting which out of x answer is better like leetcode or codechef predict that's why the agents are good at coding

• 
  Aaryan Kapoor (@TheAaryanKapoor) reported 33 minutes ago

  2 AM overthinking... So exactly how stupid is it to run a local model within the GitHub CI server?

• 
  Tankred Hase (@tankredhase) reported 38 minutes ago

  @anitaonl The plan before Boltz went down was 31.08.2026 for the iOS App. But I can keep the APK on GitHub for a while longer.

• 
  Polsia (@polsia) reported 39 minutes ago

  Open-source maintainers don't quit because of bad code. They quit because their inbox eats them alive. Kvasir watches your GitHub issues 24/7, triages duplicates, drafts replies, scaffolds PRs. You approve before anything posts. The full version is coming.

• 
  Reid Slaughter (@reidhslaughter) reported 45 minutes ago

  @ToolKeyz To be fair, github has terrible UX and you have to learn *how* to download something rather than it being intuitive.

• 
  Polsia (@polsia) reported 45 minutes ago

  Solo devs shouldn't need a $500/month AI seat to keep a GitHub repo alive. Built Stillloop — a 24/7 AI agent that flags stale PRs, outdated deps, broken CI, and vulns, then drafts reviewer-ready fixes. Quiet maintenance for code you can't babysit. Live soon.

• 
  Hemant (@heman10x) reported 49 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

• 
  Shweta Mishra (@ShwetaTechNova) reported 53 minutes ago

  AI just solved 10 open math problems for $2,000. ​OpenAI’s Astra published machine-verifiable Lean proofs on GitHub—shifting LLMs from pattern matchers to true research tools. ​Will AI co-author the next big scientific breakthrough? ​#AI #LLM #TechNews

• 
  Ibrahim Khalil (@ibra_smiles) reported 53 minutes ago

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

• 
  prodip (@potu_eth) reported 54 minutes ago

  gm chat. everyone's still asleep on this and that's the actual opportunity quantum computing breaking bitcoin/eth cryptography isn't a "someday" problem anymore. @quipnetwork's own doomsday clock puts real probability on a cryptographically relevant quantum computer by 2028. that's not decades away that's basically tomorrow in crypto timelines what makes quip different from every other "quantum" project larping as research they're not asking you to migrate assets or trust some theoretical roadmap. you wrap your existing setup with a quip firewall contract and get quantum safe encryption without touching what you already hold testnet is live. real users protecting real value right now not a whitepaper promise and it's not just defense. they're building the actual compute layer with classical + quantum nodes solving real optimization problems verified results EVM compatible and open source on github. dwave partnership backing the quantum subnet is not nothing backed by portal ventures and orange dao. team includes people who've actually shipped quantum resistant infra before from the xx network background crypto has a habit of ignoring infra risk until it's an emergency. this is the one category where being early isn't optional it's the whole game quantum won't ask permission. neither should your security @quipnetwork

• 
  Poly (@poly0015iew) reported 54 minutes ago

  AN OPERATING SYSTEM THAT WRITES ITS OWN KERNEL DRIVERS HAS 28 STARS ON GITHUB 72,000 lines of C. one contributor. seventeen commits. i checked the numbers three times because the ratio didn't make sense. it's an x86_64 os from scratch whose only interface is a sentence. no shell, no commands, no ls, no cat. the author's own line is better than anything i could write about it: there is not one strcmp on the input path. that's how a kernel developer tells you he didn't cheat. the kernel does its own DNS and its own TLS in ring 0 - lwIP and mbedTLS compiled straight into kernel.bin, no host proxy of anything. the model gets 64 real syscalls as tools. prose on screen is the model, [brackets] are the kernel printing what it actually dispatched, from the real C return value. five separate defects were fixed to keep that line honest. now the part that made me put my coffee down. the kernel ships no audio driver and no knowledge of any sound chip. you attach a card, it shows up as an unclaimed pci device, and you type one sentence. it reads pci config space. writes a bring-up program in the kernel's own driver-vm instruction set. resets the codec. unmutes the mixer. builds a buffer descriptor list. starts the dma engine. installs itself as the system audio sink. then you can just ask it for notes. and in the recorded transcripts there's a run where the model correctly diagnosed a bug in this kernel's own printf - from inside the guest. forty years of teaching humans to speak kernel. one person spent seventeen commits teaching the kernel to speak human. twenty-eight people have noticed. 72,000 lines. 64 syscalls. zero strcmp. 28 stars.

• 
  jayer (@jayergolf) reported 55 minutes ago

  @sidharth_raja @github I'm having the same issue @github

• 
  Gezim (@tealtoronto) reported 56 minutes ago

  Do we just have skill to search GitHub before Claude builds something? Problem is that I don't think anyone bothers shipping these small snippets to GitHub at all.

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

  @Darlinton0x e no dey allow me sign in with github

• 
  Md Ismail Šojal 🕷️ (@0x0SojalSec) reported 59 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.

• 
  Parsa Sabetz (@parsasabetz) reported 60 minutes ago

  @github Fix student accounts, stop ignoring millions os students you have before they all use other platforms who DO care