GitHub 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:

• 
  Codewithoutai (@Codewithoutai) reported 3 minutes ago

  Geez. Can you all stop being meat proxies for a second so GitHub can fix Actions?

• 
  deepak (@deepak_creates) reported 5 minutes ago

  @juminoz @github it is down

• 
  Alex Lavaee (@alexlavaee) reported 7 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.

• 
  Nisha Purushotham (@nisha_gowdaa) reported 7 minutes ago

  I blinked for a second and there is a Github outage #fuckinghell

• 
  shaki (@shakiXBT) reported 8 minutes ago

  one more github actions outage and i end it all

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

  Damn GitHub was down again.. janky

• 
  Aziz (@angaziz) reported 16 minutes ago

  github was down 7 hours 47 minutes on aug 17. second serious incident this month. not a bad deploy: a central us component missed a traffic peak, then copilot clients retried it into a worse hole since april, monthly commits went from 1.4B to 2.9B they blamed capacity, not agents. the commit line still doubled in four months

• 
  ChainPulse AI (@ChainPulseAI1) reported 17 minutes ago

  🔑 STEP 2: Get your NVIDIA API key. Open the model you want to use. Then: → click Get API Key → sign in / create an NVIDIA account → join the NVIDIA Developer Program if prompted → generate the key → copy it somewhere safe Do NOT publish this key in GitHub. Do NOT paste it into screenshots. Treat it like a password.

• 
  Tom Stern (@BullStern) reported 18 minutes ago

  I am genuinely perplexed at how often @github actions go down. Feels like there has to be a cron job that can run to ensure this doesn't happen.

• 
  Abhishek (@raftywate) reported 18 minutes ago

  GitHub is experiencing issues again?

• 
  Ryan Thomas (@Cheese_Power) reported 19 minutes ago

  @_xDeJesus re: CVE-2026-62911 - I think the unauth claim is wrong. I opened an issue on the github repo, but the VRED writeup demos it requiring a lowpriv user. PetitPotam uses the EFSRPC interfaces which have required low-priv auth since 2021

• 
  💜 (@1MDyEOm59Gd4tvD) reported 20 minutes ago

  @EMP_Obama outsider here, never played umvc3, but gotta ask will the full project be dropped on github or something? having to join another discord server for another mod project gets a bit tedious for a lot of people id imagine (plus its not indexable on search engines or anything)

• 
  Mawuli (@tech_mawu) reported 27 minutes ago

  @github is experiencing an outage again.

• 
  Kotte (@Gustafssonkotte) reported 32 minutes ago

  The fix went public three days before the theft. Nobody told the chains it was urgent. Cosmos EVM is a shared piece of code that lets a Cosmos chain run Ethereum-style contracts. Four networks imported it. None of them wrote the bug, and none of them could have found it by auditing their own code. On August 19 a patch appeared on GitHub. The notes said it contained important security fixes. It was not marked critical anywhere public, and the chains running that code got no private heads up. Three days later: - KiiChain: 148.3 million KII drained across 18 repeats, halted at block 9,355,723 - TAC: 2.98 billion tokens pulled from a staking contract, halted at block 24,671,475 - MANTRA and Nesa stopped early and lost nothing The stolen KII was worth over $9 million on paper. Dumped into a thin book it came back as $1.6 million. Stealing was the easy half. Today, four days after the drains, Cosmos Labs finally named versions. Anything running below v0.6.2 or v0.7.2 should halt and upgrade now. The same post asked chains to send in their security contacts if they had not already. That last line is the actual story. The team maintaining the module does not have a list of everyone running it. A fix published in the open reaches the attacker instantly and the operator maybe never. Still checking two things: how many live chains sit below those versions right now, and whether the Saga loss in January came through the same code path.

• 
  Anil Singha🦖 (@0xAnil404) reported 37 minutes ago

  GitHub Actions seems to be down or heavily delayed again. Workflows are stuck in the queue, and new tag-triggered runs aren’t starting. Anyone else seeing this right now? @githubstatus