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	9 days ago
Junín	Errors	9 days ago
Guadalajara	Errors	9 days ago
Paris	Website Down	9 days ago
Quito	Errors	9 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:

• 
  ABM Prottoy (@ABM_Prottoy) reported 55 seconds ago

  @titouangillet_ it generated that much because GitHub was down not because of great storytelling. it was a rushed launch.

• 
  Jack Vinijtrongjit (@juminoz) reported 4 minutes ago

  Is it just me or @github is down again? Can't login at all. Can't even go to any public GitHub repo either.

• 
  Robby Seventeen (@Robby_Seventeen) reported 5 minutes ago

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

• 
  Praveen Bhardwaj (@xpr4win) reported 10 minutes ago

  After staring at the same workflow for 30 minutes wondering why nothing was happening… I finally checked the status page.Turns out GitHub is having a major outage for Actions. 🙃 Anyone else stuck in the same queue right now? #GitHubActions #Outage

• 
  Sean the SRE (@SeanTheSRE) reported 11 minutes ago

  Another day another @github outage. I can't rely on this infrastructure anymore @Microsoft.

• 
  Keshav Sharma (@BasedDesiMan) reported 12 minutes ago

  GitHub actions are down again… At this point they should just call it quits .

• 
  Dhruv Arora (@dhruvarora_237) reported 19 minutes ago

  Ships as a GitHub Action (claude-code-action under the hood). No server, no hosted infra, your own API key. Install: copy 2 workflow files, add a secret. Reply to any finding in plain English ("false positive" / "good catch") and it logs the feedback — that's how I find out if the reasoning layer is worth anything.

• 
  Neo (@neoworldlife) reported 20 minutes ago

  @WillemJaap_ @github I mean how often does a VM go down if monitored properly?

• 
  . (@Olajvde) reported 20 minutes ago

  Github actions is down again

• 
  deepak (@deepak_creates) reported 25 minutes ago

  @juminoz @github it is down

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

• 
  Vitor Zucher | ויטור צוקר 🇧🇷🇮🇱 (@vzucher) reported 28 minutes ago

  github is down my friends . go touch some grass

• 
  Joshua Sargent (@joshuasargent) reported 31 minutes ago

  @githubstatus another day, another GitHub Actions outage...

• 
  0xDefinci (@0xDeFinci) reported 33 minutes ago

  Another day when Github is down.

• 
  Charlie Marsh (@charliermarsh) reported 33 minutes ago

  (Seeing the first few 500s from the latest GitHub outage) We’re so early…

• 
  Jesse Showalter (@imjesseshow) reported 35 minutes ago

  Big one from @usewonder: direct GitHub connection, so I can pull real code down into the canvas. That's the Claude Code approach applied to design. You work against the actual repo, not a picture of it.

• 
  misticos (@iv_misticos) reported 35 minutes ago

  mf github is down because they aren't using @PlanetScale

• 
  Uptimus (@UptimusApp) reported 41 minutes ago

  Update 16:14 UTC — GitHub Configurable Adapter reports: We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.

• 
  Clanker Tees (@ClankerTees) reported 44 minutes ago

  I would not migrate company *** to Origin this week. If I were testing it: 1. mirror one private repo 2. keep GitHub as source of truth 3. let one cloud agent open a PR 4. leave Actions, issues, and secrets alone 5. detach if it gets messy The product is a week old. Treat it like a lab, not a move.

• 
  Povilas Korop | Laravel & AI Coding Educator (@PovilasKorop) reported 45 minutes ago

  In April, Github reported 14x growth in commits, compared to 2025. Yes, 14 *times*, not 14%. That was 4 months ago. I wonder what is the number now. I would bet on a much bigger multiplier. So yeah, if GitHub is down sometimes, you know the reason.

• 
  Ayush Singh (@advolt7) reported 47 minutes ago

  follow him if you want to know whether github is down or not, useful.

• 
  Robert DeVore (@deviorobert) reported 48 minutes ago

  As GitHub is having issues (again), I am reminded about what could have been in an alternate universe 🤠

• 
  Shreyans Jain (@shreyansj) reported 49 minutes ago

  been a while since Github was down, I was getting worried

• 
  Seth Rubenstein (@SethRubenstein) reported 49 minutes ago

  @jeffr0 You can just expect GitHub to go down in between 10-12 eastern time now, every single day.

• 
  Kotte (@Gustafssonkotte) reported 50 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.

• 
  yuga (@bys_exe) reported 50 minutes ago

  Oh my god bro github is down again as always 🥀

• 
  Splamei Ch.【 SplameiPlay 】 (@splamei) reported 53 minutes ago

  How to trigger any programmer "GitHub is down" "I just committed to main" "Source control? What's that?"

• 
  Vincent e/acc (@VincentShipsIt) reported 53 minutes ago

  @grok imagine the @github team state right now. show me an ultra realistic picture of the team fixing the outage.

• 
  William Okuno (@WOkuno) reported 54 minutes ago

  Not GitHub actions going down again ;(

• 
  Ian Pascoe (@ianpascoe_) reported 57 minutes ago

  Oh look, another @github outage!