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

Live Outage Map

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

City	Problem Type	Report Time
Trichūr	Errors	1 day ago
Brasília	Sign in	2 days ago
Lyon	Website Down	2 days ago
Tel Aviv	Website Down	5 days ago
Rive-de-Gier	Website Down	5 days ago
Itapema	Website Down	24 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:

• 
  timur (@brachkow) reported 2 minutes ago

  @Railway something is clearly down right now. Im unable to deploy my GitHub repo, and UI is just stuck in placeholders

• 
  Zee 💌 Holofunk arc (@z_zmag8) reported 3 minutes ago

  @proluigi_ I believe that too, like ppl in that github server can just be hiding stuff you know base game is FULL of surprises

• 
  Jay.TL (@JayTL00) reported 3 minutes ago

  *** was built for humans who type, think, and commit. DeltaDB was built for agents that generate, iterate, and never sleep. Zed just announced DeltaDB — a version control system that captures every keystroke and agent operation as a fine-grained delta, each with its own stable identity. The source code and the conversation that produced it live in the same place. You can jump from any line of code to the prompt that created it. Or from a past conversation to that code as it stands now, or the exact moment the agent wrote it. This is one of those announcements that sounds incremental until you sit with it. Here's why it matters more than it seems: 1. ***'s unit of work is the commit. That made sense when humans wrote code in batches and decided when to checkpoint. But agents don't work in batches. An agent might make 47 edits across 8 files in a single conversation, backtrack three times, and land on a solution that looks nothing like the path it took. *** sees none of that. It sees the final diff. The "why" is gone. DeltaDB preserves the entire trajectory. 2. Multi-agent collaboration breaks ***'s mental model. When two agents (or an agent and a human) are editing the same file simultaneously, ***'s branch-merge-resolve workflow is overhead, not safety. DeltaDB uses a CRDT-based working directory — multiple agents can edit the same file concurrently without locks, without merge conflicts, without waiting for someone to push first. Real-time collaboration for code, not just documents. 3. The conversation IS the commit message, but better. Every code change is permanently bound to the agent conversation that produced it. No more "what was I thinking here?" — you can see exactly what the agent was prompted with, what alternatives it considered, and why it chose this implementation. This is the intent layer that code review has always wanted but never had. 4. *** compatibility is the Trojan horse. Zed confirmed that "***'s discretized snapshots are a subset of DeltaDB's continuous history." This means existing CI/CD pipelines, GitHub integrations, and deployment workflows keep working. You don't migrate off ***. You add a richer layer underneath it. But here's what most people missed: The real question isn't whether DeltaDB is better than ***. It's whether version control is even the bottleneck. One developer asked the right question: "Reviewing 600-line diffs kills me way before version control does. Is DeltaDB solving the tracking side or the review side?" This is the sharper critique. When an agent rewrites half your codebase in a single session, the problem isn't that *** can't track the changes — it's that no human can review them. DeltaDB gives you the audit trail, but an audit trail you can't read is just a log file. There's also a competing bet from Mainline, a Go CLI that stores engineering intent (goals, decisions, rejected alternatives) without leaving ***. Their thesis: you can get the intent layer without rewriting version control. Two different answers to the same question. And then there's the SOC2 question. Every keystroke, every agent conversation, every delta — all stored, all auditable, all potentially sensitive. When your version control system now contains the full reasoning trace of every AI-assisted code change, it becomes a compliance surface area that didn't exist before. The deeper signal: we're watching the first real attempt to build development infrastructure native to the agent era. Not agents bolted onto existing tools (Copilot inside VS Code, Claude Code inside terminals), but tools designed from scratch for a world where most code is written by machines and supervised by humans. DeltaDB may or may not win. But the category — agent-native developer infrastructure — is now real. What happens when the conversation that generated your codebase becomes more valuable than the codebase itself?

• 
  Kuruś (@donqrakko) reported 8 minutes ago

  @HermesAgentTips @Teknium 1/2 @Teknium please fix hermes desktop for windows. I don't have time to create issue on github 1. I get error - *** not installed, but i have latest version of *** 2. I noticed hermes and hermes desktop is almost 3gb od size. So i got angry and tried to uninstall it

• 
  BigLlamaToe (@bigllamatoe) reported 8 minutes ago

  ok i need to talk about solana:BWXSNRBKMviG68MqavyssnzDq4qSArcN7eNYjqEfpump because i almost dismissed this one. found it on a chart scan. $130k mcap, thin liquidity, low volume. looked like a hundred other dead privacy tokens. then i read the whitepaper. this isn't a narrative token. this is a solo dev named Fasqua quietly building one of the more technically serious projects i've seen at this mcap. let me break down what's actually being built. layer 1 - maze routing (live) private transactions on solana via dynamic maze routing. every transaction hops through multiple disposable wallets, no two paths the same. 21,173 hops routed lifetime. 1,604 new nodes spun up in the last 24 hours. not a roadmap stat, a live network. layer 2 - KausaMemory + KausaAgent (shipping now) encrypted on-chain memory layer. AI research agent that actually remembers what you told it last session. just added document upload this week. not next quarter. this week. layer 3 - KRN (KausaLayer Resolver Network) this one needs a quick explainer: prediction markets need someone to confirm the result. did bitcoin close above $100k? did team A win? right now most protocols use human voters to decide. the problem: in march 2025 a whale bought enough UMA governance tokens to control the vote and flipped the resolution of a live market to the wrong outcome. people with winning bets got paid as losers. KRN replaces the human vote entirely. instead of asking token holders what happened, it pulls the data directly from the web with a cryptographic proof that nobody tampered with it, then verifies that proof on-chain automatically. no voters. no dispute window. no whale with a bag of governance tokens can flip the result. the math either checks out or it doesn't. the chart, if you like slow cooks, pull it up. launched late march, nobody noticed. grind through april. first spike in may got slapped back. instead of dying it made higher lows. ran to $300k in early june, got rinsed to $100k, now consolidating $120-140k. dev kept shipping through the entire retrace. whitepaper dropped during the bleed, not during the pump. that's the tell for me. the numbers $130k mcap. $13.7k liquidity. 565 holders. solo pseudonymous dev. verified twitter, consistent shipping, active github. risks are real. liquidity is thin. three product tracks is a lot for one dev. KRN isn't live yet. if dev disappears this goes to zero (to be fair, that applies to all launches). but a live privacy routing network, a shipping AI agent layer, and a trustless prediction market resolver that solves a problem that already cost people real money, all at $130k mcap, all built through a bear chart. i don't see this combination often. small bag. not adding until liquidity deepens. but the tech is seriously gud! 🦙🦙🦙🦙 / 5 DYOR - NFA just a llama on X @kausalayer

• 
  Sai (@sbkcode) reported 9 minutes ago

  Github is down

• 
  Matteo Collina (@matteocollina) reported 10 minutes ago

  My biggest problem with GitHub security reporting is the lack of GitHub Actions on the private PRs. I have been living this hell for a week now.

• 
  Vivek Yadav #PROCoach (@viveky259259) reported 15 minutes ago

  The honest status board, Day 12: • npm: 138/day (up from ~0) • GitHub stars: 0 • Signups: 2 So: people are installing the CLI, but the repo isn't converting visits to stars. That's a README problem, not a traffic problem.

• 
  Eray (@erayajk) reported 18 minutes ago

  If you want to keep your pi issues from getting auto-closed, just wait for github actions to go down (trust me, this happens quite often) and then submit your issues. I actually built my own pi extension for this purpose. It watches github downtime and files issues.

• 
  Ryan Delaney (@_rrdelaney) reported 18 minutes ago

  @jhasanofficial @karrisaarinen @linear Coding sessions run in a secure sandbox with no access to secrets or credentials, and limited GitHub access. Additionally, for externally created issues we lock down the sandbox's network access.

• 
  DFIR Radar (@DFIR_Radar) reported 24 minutes ago

  OceanLotus shifts from external to domestic espionage with two campaigns targeting Vietnamese 🇻🇳 stock investors and infrastructure firms using SPECTRALVIPER backdoor. Active from 2024-2026, operations likely support Vietnam's 🇻🇳 anti-corruption crackdown. Key technical details: • Supply-chain compromise of FireAnt MetaKit update server (metakit.fireant[.]vn) delivered SPECTRALVIPER via unsigned updates from Oct 2025-Mar 2026 • Corporate network intrusion targeting Vietnamese 🇻🇳 construction company Nov 2024-Feb 2026, suspected SQL Server RCE initial access • SPECTRALVIPER uses DLL side-loading (T1574.002), process injection into OneDrive.Sync.Service.exe, encrypted HTTPS C2 with domain-fronting • C2 domains crafted per campaign: financemachinelearning[.]com for stock targeting, gatewayrvcenter[.]com for infrastructure targeting • Orchestration model uses named pipes for lateral movement between compromised hosts OPSEC failure exposed RTTI class structure revealing XGU framework with Pivot orchestration and Feature remote control capabilities. Hunt for unsigned DLLs side-loading into legitimate signed executables (dtlupdate.exe copies) and HTTP Cookie headers with euconsent-v2= or zd_cs_pm= prefixes to suspicious domains. Full IOC list available in ESET GitHub repository. #DFIR_Radar

• 
  skhlgnev (@Suheil7020) reported 26 minutes ago

  @jxnlco The plugins don’t know when to activate; I think that’s the main problem. For example, I use GitHub, and there’s a GitHub plugin, but when a task related to GitHub comes up, the plugin doesn’t activate. I think the plugins are really useful, but some serious work needs to be done to ensure they activate correctly when they’re needed.

• 
  Zee 💌 Holofunk arc (@z_zmag8) reported 30 minutes ago

  @hachapurr Was told earlier that someone who i believe was in that funkin github server or like whatever asked hundrec about that stuff and apparently thats what they said Tho lowk I was alr mentally exhausted today so I kinda was maybe tweaking a little bit

• 
  Kodark🃏 (@kodarkweb3) reported 31 minutes ago

  Lesson 2: The projects that survive aren't the ones with the best marketing. They're the ones that kept building when nobody was watching. Github commits during bear markets tell you more than whitepapers during bull markets. Check what teams do when the price is down.

• 
  Melfoy (@melfoy_work) reported 35 minutes ago

  The repo had 313 skills. Devon had installed three. He’d been freelancing out of a studio apartment in Hartford for two years. Web copy, landing pages, the occasional SEO audit. $3,200 a month on a good month. He typed every prompt by hand, start to finish, every session. His girlfriend asked why he was still at his desk at midnight. “Reading something,” he said. “Work?” “Could be.” The article was a list. Ten skills, five install commands, nine prompts. One open-source repo, 15,300 GitHub stars. Most people had touched three. He ran the install command at twelve-thirty. Cold brew from that morning, still on the desk. The landing-page-generator went first. Single command, one config file. Full TSX funnel, GSAP animations, brand palette validator. He’d been charging $800 for that. Took him four hours. The skill did it in forty seconds. He sat with that for a minute. Then the content-creator. Then aeo Answer Engine Optimization, the thing that got you cited by the AI itself instead of just ranked on Google. He hadn’t known that was a problem until the skill told him five LLMs wouldn’t touch his client’s page and exactly why. The cmo-advisor came last. 90-day plan to hit $40,000 MRR, zero ad budget. He gave it his numbers. It gave him back a roadmap that read like something a $400/hour consultant would charge for. He raised his rates the next morning. Didn’t tell his existing clients yet. By month three he’d stopped writing prompts entirely. He wrote specs now. Installed skills. Reviewed output. His girlfriend noticed he was sleeping more. “You seem less stressed.” “I stopped doing the work,” Devon said. “What do you mean?” “I mean I stopped doing the work.” The repo ships new skills every week. Most people will read this and install nothing.

• 
  Anto (❖,❖) (@OtnaEsoj) reported 35 minutes ago

  Here's a clear hint about $POLY that many seem to be overlooking. Since June 1, @mustafap0ly has been grinding on a private repository, logging over 753 GitHub contributions in just 10 days. That's not normal maintenance activity — that's launch-mode intensity. Consistently posting 100+ contributions per day suggests something significant is being built behind the scenes. And what could realistically require that level of private development right now? The strongest candidate is $POLY. The clues don't stop there. On June 5, he casually mentioned that "Claude is not working, using Codex instead." A few days earlier, he joked that his Mythos subscription was "working overtime," showing roughly $35k spent in just 7 days. Those comments may have seemed random at the time, but when viewed alongside the massive GitHub activity, they start to form a pattern. None of this confirms anything. There has been no official announcement. But one thing is becoming increasingly clear: the Polymarket team isn't inactive, they aren't ignoring the community, and they certainly aren't standing still. They're quietly building. Maybe it's $POLY. Maybe it's sooner than most people expect.

• 
  Traceback (@Tracebackqa) reported 38 minutes ago

  Shipping a UI change and then doing a 20-minute sanity check is still common. It’s slow, brittle, and easy to miss one edge case. - Traceback is the quality assurance layer for modern software teams - AI controls the browser like a person would, so every pull request is tested automatically - Self-healing tests keep up with normal UI drift; failures become trackable work in GitHub, Linear, and Slack - Connects to Vercel, Docker, AWS, Node.js, React, Next.js, Vue — across web, mobile, web3, and design Verify every product change before it ships.

• 
  Slkoshka (@Slkoshka) reported 40 minutes ago

  @bee_fumo I got curious how Omarchy was handling this because my main complaint about it was automatic AUR updates. There's literally no discussion about this at all. There's one GitHub issue with zero replies and a Reddit post with like 3 comments. Those people live in their own world.

• 
  Jess Temporal (@jesstemporal) reported 42 minutes ago

  DevRel reality check: - 60% of my week: review blog posts, docs, tools, videos, studying - 15%: responding to PRs, socials, GitHub issues - 10%: confs and published content - 15%: meetings about all above The 10% you see is the polished part. The other 90% is the actual job.

• 
  Tim Hey (@_TimHey) reported 43 minutes ago

  6/ the honest limit: github doesnt expose user-agent per view. you cant prove claude fetched it. you infer from the four reads. want proof? you need a property you control + its server logs.

• 
  Joseph 𓄿 (@Ebiowei1999) reported 47 minutes ago

  backend engineer interview question: you deploy a fix and error rates get worse. what do you check first: logs, metrics, rollback, or blame github actions?

• 
  Adedolapo (@0xqdee) reported 47 minutes ago

  Structured feedback, with fixes: 1. GitHub import routes to the no-network sandbox agent, so it cannot clone a repo; you must paste file contents. Clone server-side or relabel the option. 2. Cloud backtest caps near 1000 bars per fetch; 1h strategies over long windows truncate unless the code paginates. Paginate by default. 3. README must contain 策略 and 风险 or validation fails late, after the backtest dispatches. Validate README format up front and document it. 4. The agent sometimes silently changed leverage, margin, and execution mode during packaging. Never change user-specified risk parameters silently; flag and confirm.

• 
  Daniel C (@daneelchia) reported 50 minutes ago

  @BirdsofParadiz8 This misses the point entirely. Chinese grads don’t need GitHub as Qwen3 and DeepSeek are the frontier now. SG’s problem isn’t China’s copying. It’s being squeezed out of BOTH ecosystems simultaneously.

• 
  Xaden Ryan (@XadenRyan) reported 51 minutes ago

  @jxnlco The computer use process is completely broken and corrupted. There are two issues open with hundreds of comments on it in github. Please fix it.

• 
  Slyke 🇦🇺 🇨🇦 (@SlykePhoxenix) reported 51 minutes ago

  @OpenAI Can you guys fix the Codex app so it doesn't keep breaking? Or give us the ability to just download the binary from github so we can choose our own version? Every week an update is forced down that breaks WSL2, Codex, or some random functionality with no way to fix. It's just not worth $100/mo when this happens on a weekly basis. Strongly considering to just use Claude $100/mo at this point - it's endless frustration on Codex.

• 
  Hot Aisle (@HotAisle) reported 52 minutes ago

  @ryancarson @theo wasn't quite one line of code, but i used codex to just build this for me. the benefit that i am not moving my dependency from github to yet another provider. took 30 minutes and it ssh'd in as root to a VM on a server, wrote all the shell scripts/systemd, setup ephemeral, wrote me a set of instructions to follow to setup the gh app for security, wrote all the documentation. pretty impressed honestly.

• 
  Laksh Nijhawan (@laksh_2705) reported 53 minutes ago

  @github broken link wow

• 
  Sybre Waaijer (@SybreWaaijer) reported 54 minutes ago

  @dannyvankooten Hi Danny! Yes, it's a known issue with WP 7.0. It's a "floating" title that dynamically calculates its offsets. It appears only when you input text, and it should take the appearance of the text input. In WP 7.0, they messed with the height and line height of the input fields, and the calculator doesn't account for these yet. The colored checkboxes on the SEO Settings page are also broken (but the next update makes them much better). And the new odd 3-color "modern" admin scheme lets the dynamic color scheme fall back to the old "fresh" one (because 3 isn't 4 -- this will also be much better in the next update). Some backstory: WordPress still doesn't provide a proper styling API. Many devs complained about these changes in various tickets, so I held off to see if they would be addressed (obviously, they haven't). Then WP 7.0's release was delayed, so I just kept developing new features, and my release schedule got messed up. Then GitHub Copilot announced major changes to its service, so I had to reorganize everything because I kept getting rate-limited (on their biggest subscription). To still make the most of it, I sprinted to launch another project (which turned into a marathon that consumed 1.216 billion tokens in 3 weeks—oops). All in all, this is why there's no update yet. TSF officially states that it's compatible with WP up to 6.9.4. The only thing that really changed with WP 7.0 is the jarring interface with the ever-so-more-jarring view transitions. I was secretly hoping they would revert all that, so I didn't feel the pressure to address it quickly. If anything, I'm eagerly awaiting a proper admin API, as any modern CMS should have. I just picked up development for TSF again. I still need to triage what's important and decide whether to release an update sooner rather than later.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 54 minutes ago

  boris cherny stopped prompting claude. his job now is writing the systems that prompt claude for him 100% of his personal code for 30 days straight came from loops he'd set up once, not from manual prompting sessions. that's not a flex that's a timeline most devs are still on rung 1 or 2. rung 1 is claude as autocomplete you review every line. rung 2 is juggling 5 claudes in parallel routing between them manually, thinking you're advanced rung 3 is different architecture entirely. you don't prompt better you stop prompting. you encode the logic into something that runs without you. claude executes against conditions, verification gates, retry logic you designed once. it fails succeeds hits edge cases you didn't anticipate—the loop handles it the gap between manual prompting and loop engineering looks invisible at first. week 1 feels the same but one trajectory improves the work you already do. the other builds a system that handles that category while you design the next one linear vs compound that's why the june 7 moment mattered. the scoreboard went public karpathy's running 50 ml experiments overnight on a single gpu. agent modifies training code reads results iterates. no human in the loop. he called it the loopy era of ai github data shows claude code at 4% of all public commits. that's not happening through manual sessions running individual prompts to ship production code is the it works on my machine of agentic development now i build and ship daily with Claude Code. SaaS, tools, automations. ⭐ if AI can build it, I've probably broken it first. what works → link in bio

• 
  MG (@MikeG_builds) reported 58 minutes ago

  @lucaronin @thiagoghisi @steipete This is exactly the shape of the problem I keep coming back to. The hard part is not another board. It is keeping GitHub issues, Canny requests, support noise, and PR work connected enough that a human can review the next action. I think the useful unit is not a request. It is: need + evidence + affected users + proposed change + review.