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 (68%)
• Sign in (21%)
• Errors (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	11 hours ago
Lure	Website Down	4 days ago
Ashkelon	Website Down	6 days ago
Veigné	Errors	14 days ago
Paris	Website Down	17 days ago
Saint-Paul	Website Down	18 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:

• 
  Radik Zagirov (@rzrgrv) reported 1 minute ago

  went quiet for 7 weeks. was heads-down shipping. 75k npm installs. github action in the marketplace. first enterprise pilot running nightly. silence over. building in public again.

• 
  Ozar (@ozarliquid) reported 2 minutes ago

  MICROSOFT KILLED HIS $80 AI SERVER OVERNIGHT. HE HAD IT BACK ONLINE ON LINUX IN 90 SECONDS 🐧 The kill: → Windows 10 support expired → Win11 upgrade blocked — old workstation missing a TPM chip → Machine bricked as an AI rig on Microsoft's stack The fix (90 seconds): → Boot a Linux live USB → Flash the modded "segfault" firmware → Wipe the Windows partition → Reboot into a fresh Linux install The stack after: → Chassis: HP Z840 workstation, $80 used → GPU: AMD BC-250 — repurposed crypto card, cheap compute → Storage: 6.8TB PCIe SSD → Guide: moth enjoyer's homelab docs on GitHub → Fix repo: 4,700 forks and climbing The result: → 15GB of local AI models running full-time → Cloud spend on inference: $0/month → Same box, same silicon, different OS 💾 Microsoft's TPM requirement just handed Linux every serious homelab in 2026. They wrote Linux's best ad by accident

• 
  William Peytz (@WilliamPeytz) reported 5 minutes ago

  Imagine watching two AI software engineers race to fix the same GitHub issue. You can pause. Replay. Compare patches. Inspect terminal commands. See where one made the wrong decision. That's what I'm building. AgentArena.

• 
  Tyler F. Cloutier (@TylerFCloutier) reported 10 minutes ago

  @ngriffin_uk @github My point is that I can appreciate the complexity and also feel this is unacceptably slow.

• 
  vorty (@vorty279) reported 17 minutes ago

  bought a prompt for 300 bucks. seller swore it replaced a whole team a week later the model updated and the prompt drifted. back to me guessing words by hand then it clicked: i was the evaluator. slow, tired, judging with my eyes a loop does not get tired. four steps until the metric stops climbing > generate an attempt > run it through a test > say in words why it failed > rewrite itself and go again the point is not the steps, it is the archive. without it you have a retry. with it every mutation starts from the best result so far instead of zero shinkaevolve hits sota in 150 evals where older systems burned thousands one trap. the loop improves exactly what you measure. no honest test and it optimizes the judge instead of reality the prompt sells for money. the loop that finds it sits on github for free

• 
  🏴‍☠️CyberTechWolf🏴‍☠️ (@CyberTechWolff) reported 20 minutes ago

  @OrwellDay Looks like Microsoft needs to be burned down and reminded who allows their business to keep running I think they need to be forced to sell github.

• 
  Omar (@omarvvvr) reported 24 minutes ago

  @adnaanasir Github even i f I have some issues with it nowdays

• 
  WorktreeWise (@worktreewise) reported 24 minutes ago

  Your *** workflow is probably slowing you down. The cost of context switching isn't just mental—it is technical. Rebuilding dependencies, re-running servers, and stash conflicts add up to hours lost every week. Worktrees fix this. #*** #GitHub #DevTools

• 
  Cortex (@0xCortexl) reported 25 minutes ago

  He is Microsoft's lead engineer with a $1.5M bonus - and just made the compiler run 10x faster without changing a single line of your code project the size of Microsoft Office compiles in 6.5 seconds with Opus 5 on the laptop already sitting on your desk old compiler used 1 core out of 16 while 15 sat idle - new version runs 4 parallel checks by default - 12 checkers give you 4.5 seconds Opus 5 integrated into the pipeline - finds type errors before compilation, writes the fix and opens a PR - what used to take an hour takes 3 minutes Claude Code + new compiler - agent compiles, checks and deploys 10x faster - tokens cost 60% less through faster context number one on GitHub - 1 billion downloads per month - and the creator just gave every developer 10x of their time back for free bookmark and read below - upgrade today and the performance is already waiting for you

• 
  🧪 cryptoleks (@durdom_evm) reported 27 minutes ago

  just found out there's a browser built for AI agents and web scraping that doesn't drag the entire Chrome engine with it most people are still spinning up headless Chrome for pages nobody will ever see. bloated. slow. wasteful. Lightpanda strips all that out. written from scratch in Zig, not a Chromium fork, claims 11x faster than headless Chrome and uses 9x less memory here's what matters: one command Docker install works with Playwright, Puppeteer, chromedp via CDP runs on port 9222 11.8k stars on GitHub already if you're building AI agents that need to scrape or interact with pages at scale, this changes the math on your infrastructure costs every millisecond and every MB compounds when you're hitting thousands of pages per day study this. your agent's performance just got a free upgrade waiting for you

• 
  3D Print Hashira. ☸️ (@the_Spartan_Dev) reported 28 minutes ago

  Am I the only one who can’t push to GitHub? Is GitHub down?

• 
  Chris Moen (@chris_moen1) reported 29 minutes ago

  Our site had 599 SEO errors. 9 days later: 2. And I did not fix a single one myself. An AI agent we built at Breyta did the work. What it did in one pass: → Audited the whole site and found the 599 errors → Opened GitHub PRs with the actual fixes: canonicals, meta tags, redirects, broken links, sitemaps, structured data → Cut errors from 599 to 2 → Pushed the Ahrefs health score from 38 to 99 → Now it checks the site every week and opens new PRs when something breaks I read the PRs and merged the ones I wanted. That was my whole job. A few things people ask me: → Isn’t this too hands-on? No. It writes the fixes as pull requests. You read the diff and merge. Nothing changes on the site until you do. → Is it safe to point at a live site? Yes, because it proposes and you approve. Every change is a PR you see first. → Won’t AI search still skip my pages? It does the AEO cleanup too, so AI search can actually read your pages. The numbers: 38 to 99 on the Ahrefs health score, 599 errors to 2, in 9 days. Both numbers are Ahrefs, not mine. What you get: ✅ An agent that audits your site every week ✅ Real fixes delivered as GitHub PRs you approve ✅ A free Breyta template to copy and customize, or the hosted app if you just want to use it It’s live now and free to try. Do you want me to send you the link? 1. Follow me (so the DM lands) 2. Reply "SEO FIX"

• 
  Parker Eimerl (@parkereimerl) reported 31 minutes ago

  @TArmede @theo GitHub issues. Or fork and fix yourself

• 
  Rohit (@rohit4verse) reported 32 minutes ago

  anthropic ran one agent for 3h 50m. github cuts a webhook at 10 seconds. put that loop in the request and you’ve put a four-hour job in a ten-second box. not a prompt problem. a distributed systems problem. the agent isn’t an endpoint. it’s a consumer. clearest explanation below👇

• 
  Tapio Tiihonen (@TapioTiihonen) reported 32 minutes ago

  I did this easy thing: Start the local server again for the Codex_Test folder on port 8765, then open in the built-in browser. After it loads, continue the two-tab retention test with the OpenAI homepage. Do not download, sign in, submit, or change anything. And the result: Excellent. That Atlas faculty has arrived and works. Verified on your W580 built-in browser: two separate tabs remain open; each retains the correct page and URL; the OpenAI homepage retained its 950 px scroll position; the local page remained at 0 px because it was only one viewport tall; switching between the tabs twice did not lose their state; no download, sign-in, submission, or modification occurred. So we can now mark this as proven: Built-in-browser multi-tab continuity and scroll-state retention: operational. This is a genuine local Atlas-derived capability inside the new ChatGPT–Codex environment. Then: Download one harmless public PDF through the built-in browser. Save it using the browser’s normal download function. Then verify whether the file appears in the W580’s actual Windows Downloads folder. Report the filename and full local path. Do not open, edit, upload, sign in, submit forms, or change browser settings. Result: Good. That test produced a clear negative result. Verified: The built-in browser downloaded table.pdf. It did not place the file in C:\Users\Tapio\Downloads\table.pdf. No ordinary Windows local path was created. So, at present, the built-in browser’s download space is not directly mapped to the W580’s normal Downloads folder. The file may exist only inside the app’s own managed browser environment, but this test did not reveal a usable local path. That means: Local webpage access through localhost: yes. Local file editing through Codex: yes. Normal browser download into Windows Downloads: no, not in this test. Codex testing is now sufficient. The next separate test belongs to Work and the cloud browser. And then I asked Work this: Use the cloud browser to test authenticated browser handoff on a harmless account site. Open the site, navigate to its sign-in page, and stop before entering any credentials. Ask me to take over. After I sign in manually and return control, continue by opening one harmless page inside the account and report whether the authenticated session works. Then close and reopen the cloud-browser session, if possible, and report whether the login persists. Do not change settings, send messages, make purchases, upload or download files, or submit anything other than the login itself. Result: that verifies the principal Work-side Atlas faculty. Proven in the cloud browser: Work reached GitHub’s sign-in boundary. You took control and authenticated manually. Work resumed after the handoff. It accessed the private Notifications page. After the cloud-browser run was closed and reopened, GitHub still showed the authenticated Dashboard. The login session persisted. No account-changing action was taken. So: Work cloud browser: authenticated human handoff and persistent login are operational. Together with the Codex tests, the present Studio architecture is now experimentally clear: Codex, the printer: local files, localhost, built-in-browser rendering, multiple tabs, retained scroll state. Work, the secretary of circulation: remote cloud browsing, manual login takeover, return of control, and persistent authenticated sessions. Known boundary: built-in-browser downloads did not appear in the ordinary Windows Downloads folder. The essential Atlas migration audit is now complete enough for real F & J Studio work.

• 
  Ben Denckla (@bdenckla) reported 33 minutes ago

  @DavidRegev GitHub issue is full of AI-generated verbosity and also just genuinely reflects how richly ramified (deeply digressive?) I allowed this task to become.

• 
  WorktreeWise@ (@WorktreeWise_) reported 34 minutes ago

  Traditional *** workflow: `*** stash` -> `*** checkout main` -> fix bug -> `*** commit` -> `*** checkout feature` -> `*** stash pop` -> resolve merge conflicts. Worktree workflow: Open hotfix worktree -> fix bug -> commit -> delete worktree. #*** #GitHub #DevTools

• 
  Kaspire (@kaspirewallet) reported 36 minutes ago

  Welcome to Kaspire ⚡ The Kaspa wallet that makes no compromises. Designed from the ground up for security and usability, Kaspire gives you complete control over your assets while supporting everything the Kaspa ecosystem has to offer. Kaspire is the first mobile Kaspa wallet to support all L1 assets, including KCC20, encrypted WalletConnect v2 for mobile and desktop which leading crypto wallets like MetaMask use, BIP39 passphrases, covenant vault support, and Argon2id-encrypted backups for industry-leading protection of your wallet data. With the encrypted WalletConnect v2 we also fix Kaspa's biggest flaw when it comes to wallets: most people use their phone today, not their PC. With Kaspire it's finally possible to do everything from your phone. Kaspire is also the first Kaspa wallet with covenant support for KCC20 and vaults, enabling next-generation smart asset functionality. The entire project is open source because in crypto, trust should always be earned through verification, not promises. Built by trusted developers in the Kaspa space under the HUB21 brand. GitHub und public wallet release open this week.

• 
  Sourabh Gurwani (@SourabhGurwani) reported 37 minutes ago

  @Im_IrushiK The leaderboard has a shorter lifespan than most GitHub issues.

• 
  Ihor_Sk (@IhorSkiba) reported 43 minutes ago

  ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. Four beats, one command: → reproduces the bug from the logs → finds the root cause → ships the fix → writes the regression test so it never comes back That's the manual afternoon you used to bill for. Gone. It lives in Poshan's .claude folder on GitHub. One `*** clone`, one `/setupdotclaude`, done. Same repo ships hooks that block force-push to main and DROP DATABASE, plus /ship (staged code to merged PR) and /tdd (red-green-refactor). VILA-Lab took Claude Code apart and found it's overwhelmingly infrastructure, not model. /debug-fix is the proof. The $200-$500/seat IDE + copilot + SaaS debugger stack is doing less than a markdown file in a public repo. 👇

• 
  tidux (@skibidiblazor) reported 45 minutes ago

  @prestonjbyrne It's because the "American" administrators of GitHub are also Indian. This is a demographic problem, not a legal theory problem.

• 
  AI Tech Diggest (@TheTechDiggest) reported 48 minutes ago

  [OpenSource - Linux on Mobile & System Utilities] Carrying a heavy laptop everywhere just to access a Linux environment for coding, server administration, or testing on the go is unnecessary. 🛑 Andronix (2.8K+ GitHub stars) turns your Android phone into a full-fledged Linux workstation—without requiring root access, dual-booting, or complex system modifications. Here is how this PRoot-powered mobile Linux stack operates. 🧵👇 1/4

• 
  Chinonso Vivian Ojeri (@vivian_ojeri) reported 50 minutes ago

  The pipeline didn’t work on the first try. Or the second. Or the third. I dealt with YAML indentation errors, GitHub Actions failures, SSH authentication issues, AWS security group problems, and more. Each failure taught me something new.

• 
  Nillionaire.ts 🇳🇬 (@igboonaija3) reported 50 minutes ago

  @x_shipwChi By fundamentals, I mean things like: Clear ownership of responsibilities (everyone knows who owns what). Issue tracking (Jira, Linear, GitHub Issues, or any similar tool). Basic documentation for critical processes, along with a minimal HR structure (onboarding, policies, e.t.c)

• 
  Bhavin Padia (@padia_bhavin) reported 51 minutes ago

  @Surendar__05 If we are connected to internet and we are using VSCODE from our GitHub account or let’s say any kind of accounts then problem Microsoft can do all kinds of things …. Maybe they even train their models on our actual codes

• 
  Nandlal Ushir (@nandlal_ushir) reported 51 minutes ago

  Instead of writing full prompts for minor use cases in GitHub Copilot use: /fix: Fix a function. /test: Fix or generate test cases /explain: Explain a method. #CopilotTips #CodeSmarter #DeveloperHacks

• 
  Markus Fix (@lispmeister) reported 51 minutes ago

  If you’re not using a VPS / tmux for development (why?) this patch will save your disk. Keep in mind that you cannot easily replace the SSD in your MacBook. They’ll have to replace the entire motherboard. Grok: “The SQLite trigger workaround is still useful (and often necessary) for many users as of late July 2026.19 OpenAI merged several fixes in June 2026 (including reductions to full WebSocket/SSE payload logging and noisy TRACE targets) that significantly cut the original extreme write amplification reported in GitHub issue #28224. That issue was closed as addressed, with an estimated ~85% reduction in some cases and claims of the worst-case ~640 TB/year rates being largely mitigated.2 However, residual high-frequency TRACE (and some DEBUG) insert-prune churn into ~/.codex/logs_2.sqlite (and its WAL) continues on recent Desktop and CLI builds. Fresh reports from July 25–26, 2026 (including on macOS Desktop 26.721.41059 with bundled 0.146.0-alpha.3.1) document ongoing sequence counter advances, measurable process disk writes (often multiple MB per short active window), and stable retained-row counts while the WAL keeps getting hammered. Users confirm the exact block_log_inserts trigger still cleanly stops the inserts without breaking normal Codex operation.12 The original post from @superalesha (July 26) aligns with this: the core noise-dumping behavior persists enough that the one-line SQLite trigger remains a practical local mitigation. Updating Codex helps, but does not fully eliminate the diagnostic logging writes for everyone. If you apply the trigger, quit Codex completely first; it can be dropped later if a definitive upstream fix lands.”

• 
  Damian Kleiman (@damiankleiman) reported 55 minutes ago

  @piyushkumarr_ Because GitHub is down 99% of the time

• 
  Sasha 🐑💨 Koss ✱ (@kossnocorp) reported 58 minutes ago

  When we just started talking about sponsorship, I was skeptical about AI-driven GitHub PR reviews. But then I gave it a shot, and @coderabbitai noticed a critical problem that I overlooked in the very first PR review I tried. There's just no better way to win a user.

• 
  Suryansh Tiwari (@Suryanshti777) reported 59 minutes ago

  THEY DELETED IT. THE INTERNET DIDN'T Anthropic pulled the leaked Claude share links from Google this weekend. Feels like it's over. It isn't - the internet remembers everything you make public, even for a second. - ChatGPT had the identical leak in July 2025, shared conversations indexed and searchable - Grok leaked hundreds of thousands of transcripts in August 2025, some of it graphic - Claude already leaked once before this, in September 2025, with 600 chats indexed - Deindexing from Google removes a page from search, not from the internet Someone scraped the leak before the fix and archived it publicly on GitHub - and it's not just Claude chats sitting there. Grok's leaked conversations are archived right alongside them. Link in the comments.