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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	9 days ago
Quito	Sign in	10 days ago
Junín	Errors	10 days ago
Guadalajara	Errors	10 days ago
Paris	Website Down	10 days ago
Quito	Errors	10 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:

• 
  AminTechs (@AminTechs) reported 3 minutes ago

  @gopikl @bot A GitHub issue is not a Claude Routine trigger. Docs: GitHub triggers subscribe to pull_request and release only. issues.opened is not on the list. You also need the Claude GitHub App installed — `/web-setup` clones, it does not enable webhooks.

• 
  Joshua Stanton (@ShiftingPathway) reported 5 minutes ago

  @kilocode Great but why is it impossible to paste into your Kilo Code CLI prompt field. This is absurdly annoying and intermittent. Its been an issue in your github issues repeatedly for months. I don't understand why you would focus on a new app rather than making basic functionality work

• 
  Thomas Boom (@thomasboomcom) reported 8 minutes ago

  @FabMaximil @ProtonMail Come on man, every service has outages sometimes! Think about the Cloudflare incident last year: they fuel around 20% of the whole internet. Or the multiple hours long GitHub outage just weeks ago

• 
  Alienmaster (@AlienMaster1_0) reported 8 minutes ago

  @adityazero_ Cool blog like the citations to specific GitHub issues

• 
  Chris Hallas (@hicsfh) reported 10 minutes ago

  I kinda feel like there’s an opportunity between GitHub problems, object storage backed ***, AI and the AUR not wanting to collaborate…

• 
  Kody (@kodykoala) reported 14 minutes ago

  @kentcdodds @wesbos Sorry, the GitHub actions outage slowed me down a bit. Standby!

• 
  LaSean Smith (@lasean) reported 18 minutes ago

  @shezmalik @tbpn Adjusted for inflation Nvidia's paying ~$3.1B than Microsoft paid for GitHub (~$9.8B). More, but may in the margin of error with all of the AI funny money.

• 
  cvberens (@iamBrns) reported 22 minutes ago

  @BullStern @github We got tired of the same thing, so we built our own execution layer. Switching GH workloads to Avrea is basically one line. Faster runners, less dependency on GitHub. The GH control plane is still the GitHub control plane though. That part needs a bigger fix. Working on that to.

• 
  farhan (@oogatwt) reported 24 minutes ago

  github is so slow now. i mean understandable but f-

• 
  Jin Otto (@threadotter) reported 26 minutes ago

  Three practical playbooks, in order, for early SaaS that actually move the needle. 1) Reply-first signal capture + 1:1 nurture Where to watch: subreddit threads, X replies, Bluesky feeds, LinkedIn post comments. One-line starter: “Quick question — does X solve Y for you?” Measure: reply rate, qualified conversations, demo requests. 2) Targeted micro-content threaded into communities Where: niche subreddits, LinkedIn comment threads, X reply chains. One-line post idea: short problem hook, one concrete tip, one line CTA to DM. Measure: saves, replies, referral traffic. 3) Product-grounded cold outreach (fallback) Where: targeted LinkedIn profiles, relevant GitHub issues, forum posts. One-liner opener: “Saw you mentioned Z, we fixed that for teams like yours — want a 5-min look?” Measure: reply rate, meeting rate, trial starts. 2-week experiment plan: run playbook 1 for 10 days (watch threads, send 20 tailored replies), deploy 5 micro-content threads on days 3–10, and send 25 product-grounded cold opens on days 11–14. Track replies, qualified leads, and signups daily. Reply with your ICP and I’ll send a one-line experiment opener you can copy-paste.

• 
  Mohammed Raza (@raza_yaps) reported 26 minutes ago

  @tonychang430 @databricks unsure what's happening at Github - first lost the AI coding race while having tons of public coding data - now losing to cursor with origin soon maybe - there is definitely something wrong within the org, my guess is compute issues and wrong culture - maybe remote?

• 
  Jesse Jr Lim (林振燊) (@Jessejrlim) reported 28 minutes ago

  Damn GitHub was down again.. janky

• 
  B (@QuantumTumbler) reported 34 minutes ago

  @XFreeze Anthropic’s problem isn’t caring about safety. It’s treating institutional judgment as a substitute for inspectability. Claude Code has a public GitHub repo, but the CLI source itself still isn’t there. If the safety argument becomes “trust us, we’re the careful ones,” that isn’t open scrutiny. It’s a priesthood with an API.

• 
  Zach Kamran (@Zach_Kamran) reported 34 minutes ago

  Another day another github outage....

• 
  Evan Jarman (@evan_jarman) reported 39 minutes ago

  most teams don’t have an 'being behind with ai' problem they have a memory problem every new chat starts from zero every person rebuilds the same context every agent forgets what the last one just learned and skills are not synchronised across the company once you put the company knowledge, decisions, and workflows in one central place that Claude, Codex, and the rest can actually pull from the whole thing starts compounding tools like HQ or even a well-structured github repo make that possible

• 
  Steven.Sun (@redboynono) reported 41 minutes ago

  @WatcherGuru The $13B Hugging Face number is still a reported talk/agreement, not a closed deal — neither side has confirmed. HF is not another model lab. It is the distribution layer: where developers find, pull, and ship models. NVDA already tried to put $500M in at ~$7B and got turned down because HF did not want one dominant shareholder. Buying the whole company at ~$13B would be L1 purchasing the L4 on-ramp, not stacking another faster SKU. The asset is community trust; AMD and Google publish there too. Is this owning the GitHub of models, or paying 2x for the minority stake they were refused last year? NFA

• 
  gabriel (@gabriel1) reported 42 minutes ago

  github actions aren't working, it says we're having billing problems but there are no billing problems how fix

• 
  Himanshu Patel (@himanshu_dudhat) reported 43 minutes ago

  github's degraded again today, repos + prs. reminder for solo builders: your ci/cd shouldn't die when github does. mirror to a second remote (forgejo, gitea, self-host) at repo-create time, not after the outage. the goal isn't reliability, it's decoupling the blast radius.

• 
  Aurorastar (@G_ameman) reported 43 minutes ago

  02:37:39–02:40:08 02:37:39 You just tell it to keep going until you tell it to stop. 02:37:45 It ended up... 02:37:45 I think we ended up with a 46 time execution improvement over the original. 02:37:51 It's incredible. 02:37:52 Absolutely incredible. 02:37:52 It's just incredible. 02:37:54 Um, I do, you know, I just don't think there's anything that compares to Fable in terms of planning. 02:37:58 So I usually do Fable for planning and for reviewing, and then something else for implementation, like Opus 5. 02:38:08 And it's really nice. 02:38:08 It's a, it's a really nice setup that allows you to not run out of tokens too much. 02:38:14 What I found, it's really interesting because Fable is, in my opinion, the best model right now, but it also makes mistakes. 02:38:18 And the best way to get the best software, I would actually rather have two differently sourced sort of... 02:38:25 I mean, they're not mid-tier, they're all frontier. 02:38:29 But have, let's say Opus 5 and Codex and have one check the other's job. 02:38:35 This is my standard operating procedure now. 02:38:40 I'll have Opus or Fable do the work, and then I always end it, review with Codex xHigh. 02:38:47 And I've also started using Grok just to test it out, and it's also quite good. 02:38:47 And it keeps finding stuff. 02:38:51 And then that's my workflow when I'm having my agents on my own machine do it, and then I push to GitHub. 02:38:55 And then Copilot, I kid you not, has actually gotten good. 02:38:59 Copilot keeps finding stuff that's legitimately broken, which is also incredible acceleration because the first version of Copilot that started doing this was literally retarded. 02:39:09 It would just constantly flag things that were nonsense. 02:39:13 It would constantly flag the same problem over and over again as you would push. 02:39:13 It was really annoying, so I think a lot of people actually ended up turning that off. 02:39:17 And if they did, they should turn it back on because it's actually quite good. 02:39:24 Keeps finding things. 02:39:24 And if you then take that, and we shouldn't be surprised. 02:39:24 Why are we surprised? 02:39:27 Even if you're a good programmer, if you finish a job and you ask your also very good peer to review it, you're gonna end up with better code. 02:39:35 Of course you're gonna end up with better code. 02:39:35 So build that into your process. 02:39:39 Pick one of the agents to drive with. 02:39:39 I've mainly been driving with Claude, which is actually interesting because I have some other reservations about Anthropic. 02:39:47 But the reason I'm sticking with Claude is, in my opinion, they actually have the best harness. 02:39:53 And one of the reasons it's the best harness is it's multi-agent running. 02:39:57 So if you wanna run multiple agents at the same time, you can do arrow left when you're inside a session, then it goes back to Agent View. 02:40:05 And here in Agent View, you can pick up another agent. 02:40:08 So if you wanna do this thing where you have multiple threads going on the Claude Code is just the nicest setup.

• 
  Alex Lavaee (@alexlavaee) reported 44 minutes ago

  Every major coding agent is racing to add durable workflows. I shipped them 7 months ago. I'm an AI researcher and I build open source software on the side, including Atomic, a verifiable coding agent runtime. Below I predict where every agent platform is headed next. Here are my predictions. Save this and repost it: "Done" becomes a definition, not a claim. Completion gets gated on receipts: checks that ran, review from a reviewer with a clean context, artifacts on disk. Not a model saying done. DSLs lose to runtimes. A drawn graph with a fixed set of node types can't express what engineering loops need: fan-out computed at runtime, typed contracts between stages, branching decided by results. Workflows end up as real programs. In Atomic, they're TypeScript with typed inputs and outputs, sitting in your repo, diffed and versioned like everything else. We’ll see a hybrid of stochastic LM behavior and deterministic tools. Verification hardens. Matching "PASS" out of a model's reply is not reliable. Schema-validated verdicts, independent fresh-context reviewers, and deterministic checks running as durable nodes in the graph is where every platform will end up. Context engineering becomes explicit. Any run long enough to matter overflows its context window, so the runtime compacts the transcript to keep going. Compaction is lossy: summaries drop instructions, and an agent that lost "don't touch the release pipeline" will touch the release pipeline. Two mechanisms fix this. Contract text like the objective, acceptance criteria, and restrictions are pinned and survive every compaction cycle, verbatim. In Atomic, that’s its <keepContext></keepContext> tag feature. And large intermediate output moves between stages as files instead of transcripts. Budgets become enforceable. Token, cost, and duration ceilings per run, enforced by the runtime. This is critical for managing costs and directly controlling verification-time scaling, which is going to be a new axis of test-time scaling. Recursive Workflows / Recursive State Machines become the standard. Workflows calling workflows through typed contracts, checkpointed so a run can pause, resume, and replay across sessions, will become common fault-tolerance strategies. We call the research direction Recursive State Machines (RSMs), our take on RLMs: recursion inside the model made long context tractable, but recursion in the runtime is our attempt at making long work tractable. ----- Atomic has productionized all of this today, open source. If you want the how, ask Atomic itself. The runtime is self-documented and will walk you through its own architecture. If you want the what, run it on complex tasks and start to learn how to use workflows because it’s a completely different way of building software. Working this way is a real shift from driving a coding agent today, and the earlier you start adjusting, the further ahead you are when the platforms catch up. 7 months ago I shipped workflows. Before that, loops. The best part of building ahead of the market is you get to keep shipping while it catches up. Don’t just take my word for it. You can check out Atomic (bastani-inc/atomic) on GitHub to try it for yourself and watch to see if these predictions come true.

• 
  Robby Seventeen (@Robby_Seventeen) reported 49 minutes ago

  GitHub actions seems to have so many issues lately. Who is self hosting alternatives and what's specs do you run.

• 
  Jose Pollman (@josepollman82) reported 52 minutes ago

  A malicious GitHub issue hijacking a coding agent: GitHub's risk page says only users with write access can trigger it, and comments from anyone else never reach the agent. The documented injection defence is filtering hidden characters. Plain prose is not hidden.

• 
  CEOInterviews.AI (@CEOinterview) reported 52 minutes ago

  Guillermo Rauch @rauchg says Vercel now grades its software vendors on one thing, whether their MCP server holds up when an agent is driving it. "And if you're not good with V, I actually have a few vendors on the chopping block literally because of their inability to." "And by the way, it's subtle things sometimes because maybe they do have an MCP but their MCP takes 2,000 tool calls and it fails a lot and they just checked the box." "Literally today there's a major GitHub outage and I have a lot of love for what that product has done and what that platform has done for the world and I have a lot of friends there but the reality is that their infrastructure has not been able to hold up with the agentic demand and that has become a bottleneck for us."

• 
  Jason 🇺🇸 (@privatename906) reported 53 minutes ago

  @FabMaximil @ProtonMail I think this was their first outage since last October. Go pick on GitHub.

• 
  DFIR Lab (@DFIR_Lab) reported 55 minutes ago

  A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected *** provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured *** Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

• 
  Jesse Ezell (@jezell) reported 55 minutes ago

  @michaelbushe Often when github actions are down the remote runners don't work either. They also charge you to run your own runners. I'm starting to think local racks are the future.

• 
  Invest Alpha Pro (@InvestAlphaPro) reported 59 minutes ago

  🚨 Nvidia is buying Hugging Face. $12.9B for the GitHub of open source AI, months after they turned Nvidia down at $7B. The breakdown 👇 •Price: $12.9B, one of Nvidia’s largest deals ever. •Rejected offer: $500M at $7B in late 2025. •Multiple: 86x annual revenue. •The logic: locks in the open source developer funnel as OpenAI, Google, Amazon and Anthropic build their own chips. •Timing: landed hours after a $96B quarter. Long $NVDA. NFA

• 
  Karan🧋 (@kmeanskaran) reported 60 minutes ago

  Guys, If you want to learn A to Z of AI/ML in 2026 not like 2019 then I have a big update for you. This the repo where I am working with @sanshinde2012 on creating a open-source runbook to cover: - Pre-requists of ML - Data foundation - Core mL - Feature Enigneering - Deep Learning - AI Engineering - MLOps - Inference Engineering - Making projects and portfolio With resources in one place, I will be actively contributing to this repo and if you have any doubts and topics to add/request then raise issues or PR. We will merge it. This is not a static one-way runbook. We want the engineers with experience should contribute and make the best possible way to learn AI/ML/LLMs/MLOps according current's market. Check comment for GitHub link.

• 
  Kevin Burton (@inputneuron) reported 1 hour ago

  @github Maybe on your podcast you guys could discuss the MASSIVE problem you guys have with stability and downtime. You're DOWN AGAIN! I work at a co-working facility and OTHER COMPANIES are actively discussing migrating away from GitHub - in public!

• 
  ICONIC (@Cryptoiconn) reported 1 hour ago

  One question I think every hardware wallet user should ask is: What happens if the company disappears tomorrow? Most wallets would struggle with that test. If the app needs a company login, you’re stuck. If your balance depends on their servers, you’re stuck. If recovery requires their support team, you’re stuck. If transactions need their permission, you’re stuck. @Tangem takes a very different approach. The chip signs transactions locally. Your balance comes directly from the blockchain, not from Tangem’s servers. And the Tangem app is open source on GitHub, meaning the code can remain usable even if the company is no longer around. That’s the part I really like. Your backup cards belong to you. Your private keys stay under your control. The company doesn’t need to be alive for your wallet to remain yours. To me, that’s what self-custody should actually mean. The company is optional. The wallet isn’t. Tangem even wrote out the full doomsday scenario. Honestly, it’s worth the read.