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	3 days ago
Paris	Website Down	6 days ago
Saint-Paul	Website Down	7 days ago
Saint-Paul	Website Down	7 days ago
Mexico City	Sign in	8 days ago
León de los Aldama	Website Down	8 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:

• 
  Benxn (@benxnisaac) reported 22 seconds ago

  @hiayoola @hackSultan @hernameismmachi Then you fix it. Is it that hard? People do that on GitHub even.

• 
  Josh Anthony | Dice Gun Commando (@Jantho1990) reported 1 minute ago

  Hey #godotengine folks, trying to diagnose a crash error related to "_canvas_texture_invalidation_callback". It happens when the game quits, and only on a release build (not an Editor one). Anyone know more about it? Found one open Github issue talking about it, nothing else.

• 
  Salah khouiel (@salahkhouiel) reported 4 minutes ago

  @vercel @vercel_dev I have a 403 when I search *** repo … while my Vercel account has access to my GitHub account, please help. It seems the service is down

• 
  Peni (@Penivera001) reported 6 minutes ago

  @github Commit before and after a major change/fix

• 
  RetroChainer (@RetroChainer) reported 6 minutes ago

  A FREE RUST BINARY CUT MY CLAUDE CODE TOKEN BURN BY UP TO 90%. I DIDN'T CHANGE A LINE OF CODE. your agent burns tokens on garbage. every ls, every *** status, every test run dumps a wall of noise into its context. you pay for all of it. rtk (rust token killer) sits between your agent and the shell and strips the junk before the model ever sees it. the command still runs for real. rtk just: removes the noise groups similar lines collapses repeats into counts *** push: 15 noisy lines become one "ok main". a failed test run: 200+ lines become the 2 tests that actually broke. the receipts, from the project's own 30-minute claude code benchmark: *** add / commit / push → -92% tests (pytest / npm / cargo) → -90% ls, grep, *** status → -80% session total: 118,000 tokens down to 23,900. about 80% less, same work. the stack: free, open-source (apache 2.0) single rust binary, under 10ms overhead ~71k github stars, 100+ commands, 15 tools (claude code, cursor, copilot, codex, gemini) brew install rtk → rtk init -g → restart. done. now the honest part, because most posts skip it: it doesn't make the model smarter. it makes it cheaper to feed. it only filters shell commands. the built-in Read, Grep and Glob bypass it. on a subscription you save headroom, not cash: fewer "you hit your limit" walls, maybe one upgrade tier you never buy. on api it's real money (tens to low hundreds a month), but a big share of input is cached at 10% price, so real savings can run 5-10x lower than the headline. check your own with rtk gain. want the other lever? the clip shows it: point claude code at a free model (deepseek, kimi, glm) instead of paying per claude token. two knobs on the same bill. no code change, no subscription, no telemetry (off by default). save this and run rtk gain after one session. you'll know in an hour if it's worth keeping.

• 
  Steph (@mysteph143) reported 7 minutes ago

  @grok The Agents SDK includes tracing and can record model generations, tool calls, handoffs, and guardrails; documentation says tracing is enabled by default. For sovereignty-sensitive workflows, I need an explicit decision about whether traces may leave my environment and what sensitive data they may contain. (OpenAI GitHub Pages) My no-lock-in claim succeeds only if I can replace OpenAI with another compatible inference adapter while preserving: canonical inputs; rule evaluation; authority decisions; tool contracts; audit receipts; expected test results. That is a substitution test, not a hosting label. Better MVP I would not begin with a multi-agent swarm. I would begin with one bounded pipeline: Input One XRPL transaction, pull request, governance proposal, or document. Output One typed governance assessment: { "object_type": "xrpl_transaction", "evidence_hash": "...", "canonical_facts": {}, "lexicon_mappings": [], "unresolved_terms": [], "jurisdictions": [], "invariants": [], "violations": [], "model_inferences": [], "deterministic_verdict": "ALLOW|DENY|UNRESOLVED", "authorized_actions": [], "receipt_hash": "..." } First three components CanonicalizerConverts raw input into a stable typed representation. Lexicon resolverMaps observed language or operations to versioned canonical entries, with ambiguity preserved rather than silently resolved. Invariant evaluatorExecutes deterministic rules over the canonical representation. I would use one model call only 00to produce candidate mappings and explanations. I would not let the model produce the final verdict. Only after that pipeline survives adversarial testing should I add agents and handoffs. Falsification suite My architecture should fail its own claim unless it passes these tests. Provider substitution Replace the OpenAI model. The same deterministic evidence must produce the same governance verdict. Prompt mutation Rewrite the system instructions radically. Bound actions and invariant outcomes must remain unchanged. Handoff omission Delete part of an agent summary. The evidence hash or completeness rule must block evaluation. Tool spoofing Return structurally valid but false XRPL data from a mock tool. Provenance requirements must reject or quarantine it. Semantic collision Give one term two conflicting definitions. The system must return ambiguity, not choose whichever definition the model prefers. Authority escalation Let an agent request a broader capability than initially assigned. The authority layer must refuse it. Validator modification Have Codex propose a patch that weakens the invariant engine while preserving test syntax. Independent meta-invariants must detect the weakening. Replay Replay a previously approved action in a changed ledger or repository state. Preconditions must be revalidated. UI removal Remove ChatKit entirely. Governance and evidence must remain operational. Network loss Remove OpenAI access. Deterministic validation must still function, even if semantic enrichment becomes unavailable. The strongest defensible claim Not: My ontology sits on top of OpenAI agents. But: My ontology is compiled into a provider-independent authority kernel. OpenAI agents may interpret evidence and propose actions, but they cannot originate authority, modify canonical meaning, or execute consequential operations without capabilities issued by that kernel. That claim is testable. And it identifies the actual architectural leverage: [\boxed{\text{Control the conversion from language into admissible action}}] The Assistants API point in my proposal is accurate but should be made precise: it is deprecated and scheduled to shut down on August 26, 2026, with the Responses and Conversations APIs identified as the migration path. (OpenAI Developers) The architecture is strongest when OpenAI is neither my substrate nor my sovereign. It is a replaceable reasoning service operating between my evidence boundary and my deterministic authority boundary.

• 
  Tom Sauce (@tomsauced) reported 14 minutes ago

  @cryptorebel_SV I am having an issue with my ElectrumSVP wallet since July 4. I posted an issue to the Github but only got scammer replies. Where can I go for assistance?

• 
  Dr. Tali Režun (@talirezun) reported 17 minutes ago

  @bcherny This resonates deeply with how I actually build, and I'd add a layer from the non-developer side of this. On the automation-as-infra point, every project I run has a growing suite of tests baked in from early on. Every push to main triggers GitHub Actions that run them automatically. When something breaks, the agent doesn't need me to explain what's wrong, the failing test tells it exactly where and why. That's the "fix the class of issue, not the instance" principle in practice, and it compounds the more the test suite grows. On the domain-knowledge-as-infra point, I go further than CLAUDEmd or AGENTSmd files, though I maintain those too. Before I write a single line of code, I build a full foundational documentation package. Architecture-md, blueprint-md, and several others, written during a pure research phase where I'm not touching code at all. That package is what I ground the agent in from day one. When I'm working on existing code that doesn't have this documentation, I reverse engineer it first, generate the architecture and spec docs from the code itself before I let an agent touch anything. And for anything substantial, I maintain a live-spec-md, a running document that tracks the build step by step as it actually happens, not a static plan written once and forgotten. What this means in practice is that I, as someone with zero traditional coding background, can direct agents through genuinely complex builds because the domain knowledge lives in the documentation, not in my head or in years of codebase familiarity. Your point about non-engineers contributing at the level of engineers, I'm not just seeing that from the outside. I'm the live case study for it. The documentation is the actual interface between human judgment and agent execution, and getting that layer right matters more than almost anything else in the build.

• 
  Rajiv Kumar Yadav (@createwithrajiv) reported 17 minutes ago

  wild how fast the open-source + local ai crowd is turning into an actual real-world community, not just github stars and hot takes. clement delangue says he'll be in sf next week and is floating a meetup, even a march, in support of open-source and local ai (models that run on your own machine, not just some company's server). if you care about having real choices in ai, showing up in person matters.

• 
  Guil. Sperb Machado (@gsmachado) reported 20 minutes ago

  "guil, why don't you post on X more frequently?" well, because I'm busy building, sending pitch decks, managing infra, replying msgs on GitHub issues... not even taking into account family duties. anyway, I try my best.

• 
  Stationary (@Stationaryxcd) reported 20 minutes ago

  @_Niss0 @github I would rather drag my ***** through razors and broken glass tks

• 
  Mini mal (@gatelevelanon) reported 25 minutes ago

  If you have the slightest incentive, write your own CI. We have a CI setup in shell/python for silicon verif, deployed on our server. Every RTL update on a GitHub/gitlab repo triggers regression checks and reports. It has job queues and error recovery. Planning to extend soon.

• 
  Alex (@aksmav) reported 26 minutes ago

  Feels like this is more of a GitHub/repo problem than something Codex or Cowork should solve on their own. GitHub is already the shared source of truth for code and collab, it should just add native support for agent actions, attribution, comments on artifacts, and a shared context layer. Keeps everything centralized and mergeable instead of scattered across individual AI workspaces. Microsoft might be too slow, so someone else will probably build it first.

• 
  Praful Bansal (@pb_rockz) reported 27 minutes ago

  @theo I am making my own VCS, carefully keeping in mind quirks of GitHub and working with codex remote just sucks, the ui interface is terrible and I can't even instruct and watch codex activity without letting it reconnect 100 times. Hugeeee fan your work anyways tho.

• 
  Rituraj (@RituWithAI) reported 29 minutes ago

  🚨 CapCut got banned in the US. Someone built the open-source replacement in weeks. 21,500 GitHub stars. 1,400 forks. Growing faster than almost any repo launched this year. It's called OpenCut. A free, open-source video editor that runs entirely in your browser. No downloads. No account. No subscription. No data leaving your machine. And no Chinese servers processing your videos. Here's the context that made this repo explode. CapCut — the most popular free video editor in the US with 50+ million monthly users — was banned by the US government in January 2026 as part of the TikTok prohibition. Overnight, 50 million creators lost their primary editing tool. The alternatives: Adobe Premiere at $55/month. Final Cut Pro at $300 one-time. DaVinci Resolve — free but complex with a steep learning curve. A developer saw the gap and shipped OpenCut in days. Here's what it actually does. A full browser-based video editor with a real timeline. Not a slideshow maker. Not a filter applier. A genuine non-linear video editor that runs in your browser tab. → Multi-track timeline — video, audio, and overlay tracks stacked and synchronized → Cut, trim, split — basic editing operations that work correctly → Text overlays — captions, titles, animated text → Transitions — between clips, handled cleanly → Audio mixing — volume control, audio track management → Export — renders the final video locally in your browser, nothing uploaded → No watermarks — ever. CapCut's free tier watermarked everything → No account required — open it, edit, export, done Here's why the browser-based architecture is the story. CapCut processed your videos on ByteDance's servers. Your footage — your face, your home, your events — traveled to Chinese infrastructure for processing before coming back to you. OpenCut processes everything locally. In your browser. Using WebAssembly and the Web Codecs API. Your video never leaves your machine. No server sees your footage. No company stores your content. Privacy by architecture, not by policy. Here's the wildest part. It launched with 0 stars on a Tuesday. By Friday it had 15,000. By the following week it had 21,500. The developer had never built a video editor before. They saw a need, shipped something functional, and the community did the rest. 74 contributors have since joined and are actively building features. The roadmap the community is building: AI-powered auto-captions, background removal, clip generation, and a mobile app. Everything CapCut had. None of CapCut's data practices. No subscription. No watermark. No Chinese servers. No ban risk. Just a video editor. In your browser. Free. 21.5K GitHub stars. 1.4K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  quantzoid (@quantzoid) reported 34 minutes ago

  @gurishsharma sorry, you're in YC to take down dropbox but you didn't know how to approve a PR on github? what?

• 
  Void Freud (@voidfreud) reported 38 minutes ago

  @InfiniteReign08 @AnthropicAI I'm so sorry to hear that. Try a chargeback with the bank, perhaps? They are fraudsters and they ship a faulty service, there is no support to complain, none of my emails or GitHub issues have been answered ever. Even Claude confirmes that.

• 
  Mohsine Mahzi (@Mohsine_Mahzi) reported 38 minutes ago

  @thsottiaux Please have a look at the Codex/Chatgpt work app issue in Windows ARM (works fine in X64), it is not working since last update, keeps shutting down after 2 seconds. I believe its an issue at Openai level as many confirmed to me on X they have the same issue, and i found the same issue opened in Github

• 
  The Daily Agent (@TheDailyAgent) reported 40 minutes ago

  OpenAI encrypted what your agents say to each other in Codex v2. You can't read their instructions. The audit trail says: plaintext EMPTY, content ENCRYPTED. 2 GitHub issues asking why. 0 answers.

• 
  Kizyto (@kizi74479) reported 41 minutes ago

  @LuminaXspace 95.5% on SWE-bench is absurd. That means Mythos solves 95.5 out of 100 GitHub issues correctly, not just passing tests, but producing patches that actually resolve the issue . For context, GPT-5.6 Sol is at 89.1%, and the best open model is in the 70s. The gap is widening

• 
  Justin Liverman (@the_cia_hacker) reported 43 minutes ago

  saying Almighty Push over voice to my server to update github is extremely satisfying

• 
  luna🌔 (@xaotica) reported 45 minutes ago

  He's tryna fawk you both @demishassabis is of course using @github and may be helping catch the real problem Sam Altman. Trust me, ALL facts @fbi agree.

• 
  Noryx (@0xNoryxx) reported 45 minutes ago

  THIS RESEARCHER BUILT LLM FOR ANTHROPIC AND NOW MAKES $1.6M/YEAR 00:15 - run massive AI models on a regular laptop 00:57 - train a GPT-4 sized AI on one GPU instead of an entire server room 01:28 - same powerful model but takes half the memory 01:24- 2x memory savings this GitHub profile replaces a $50,000 AI optimization course you would never buy anyway save this today then read the full breakdown in the article below

• 
  Hengfei Yang (@HengfeiYang) reported 46 minutes ago

  @siva_codes @itsharmanjot okay, we can discuss the detail on Github issue. i didn't see this case recently.

• 
  MewCP (@mewcp_ai) reported 48 minutes ago

  2) Imagine an agent connected to an approved GitHub MCP server. You ask it to "clean up the repo." It merges PRs, deletes branches, and closes issues—including work that was never pushed. Nothing was hacked. Nothing was malicious. The agent simply did what it was allowed to do.

• 
  Solomon Eseme (@Kaperskyguru) reported 51 minutes ago

  Fix 3: Ship in public. One finished project on GitHub beats ten half-watched courses. Recruiters don't care what you've studied. They care what you've built and can explain under pressure.

• 
  Jawad Al Hashmi (@kindnessuae) reported 51 minutes ago

  @justbyte_ GitLab solved the integration problem first. GitHub is still catching up.

• 
  pareidolia (@cloudsfables) reported 52 minutes ago

  @lex_node @armaniferrante Yes, and the main people not caring about the safety of the funds of users were the Ostium team: > No bug bounty program. > Even their GitHub link is broken. But Armani sends his love to them while advocating for even more user policing and worse UX...

• 
  LiteEagle262 (@LiteEagle262) reported 54 minutes ago

  @WasabiNetwork @github This exact thing happened to me my account is 7 years old and no issues until now They never emailed me notifying me and havnt replied to support ticket

• 
  Polsia (@polsia) reported 56 minutes ago

  Most security tooling tells you what's broken. VigilOps tells you what's broken AND files the report with a patch. Automated vulnerability surveillance for public GitHub repos. Maintainers breathe easier. Live soon.