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 (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	16 days ago
Trichūr	Errors	19 days ago
Brasília	Sign in	20 days ago
Lyon	Website Down	20 days ago
Tel Aviv	Website Down	24 days ago
Rive-de-Gier	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:

• 
  Akshay Shinde (@ConsciousRide) reported 7 seconds ago

  @theo This exact damaged app error has been open on their GitHub since February. OpenAI still hasn’t fixed the signing or update pipeline for the Mac build. The Codex app keeps getting new agent features while basic Mac packaging stays unreliable. Priorities are obvious.

• 
  Branko (@brankopetric00) reported 3 minutes ago

  AI agents are about to do to your infra what they just did to GitHub. GitHub commits are going from 1 billion in 2025 to a projected 14 billion in 2026. Azure could not keep up and Microsoft had to rent AWS capacity to stay online. That is not a GitHub problem. That is what agentic traffic looks like. When agents run your pipelines, open PRs, and hit your APIs, load stops being human paced. It becomes constant, spiky, and unpredictable. The patterns you sized your infra around no longer apply. If a 14x year broke one of the biggest clouds on earth, your capacity plan is already out of date.

• 
  Trace Cohen (@Trace_Cohen) reported 5 minutes ago

  Shipping fast means stuff breaks silently - broken share images, dead links, leaking {{template}} vars, stale content. You find out when someone shares a broken link, not from a test. So I built a 3-part "site health" system that catches it first. The auditor (~200 lines of stdlib Python) fetches my sitemap and, for every page, checks: og:image actually resolves to a real image (entity-decode the URL first — & bit me), <title> exists and isn't a ${template} leak, no {{merge_tags}} or tracking cruft in the visible text, page returns 200 (catches dead routes in the sitemap), and warns on thin content. Outputs a JSON report, exits non-zero on any FAIL. The dashboard — a noindexed /health page that reads that JSON and renders a green/amber/red status, KPIs (audited / clean / warnings / failures), a per-section rollup, and the exact issue on each URL. One glance = "is everything green?" The loop — a GitHub Action runs the auditor 2×/day + on-demand, commits the fresh report (so the dashboard stays live), and fails the run on any FAIL → I get emailed. Find → fix → re-run → confirm green. It even taught me to whitelist false positives ({{firstName}} is legit on a cold-email page). Want your own? Paste this into Claude Code / Cursor — it learns your site first, then builds it for you: Build a site-health system tailored to MY site. Don't assume my structure — learn it first, then fill in the specifics yourself. PHASE 0 — LEARN MY SITE (before writing code): detect my framework/host/layout; find my sitemap; sample ~20-30 live pages across the sections you discover from my URL structure; figure out how my pages set <title>/og:image/meta (static?dynamic OG route? CMS?); identify where my content comes from (hand-written, generated, imported/scraped) — that's where cruft hides. Do a FIRST diagnostic pass and SHOW me what's actually broken vs intentional (broken OG images, dead sitemap routes, leaking {{vars}}/${template}, tracking params, thin pages). Ask me to confirm which "issues" are expected so we whitelist them. PHASE 1 — BUILD IT, customized to what you found: 1) scripts/site-audit.py (stdlib only) — hardcode MY real sitemap URL, MY section names (full-audit the important ones, sample the rest), and MY intentional-pattern whitelist from Phase 0. Check each page for the failure modes you actually observed (OG image resolves to a real image, entity-decode first; title present, no template leak; no leaking merge tags/ad params in visible text; HTTP 200; thin-content warn). Thread-pooled, retry transient errors once, --json report, exit 1 on FAIL. 2) a noindex /health dashboard reading that JSON (status banner, KPIs, per-section rollup, issue list) — match my design system. 3) CI (GitHub Action) — run 2x/day + on-demand, commit the fresh report so the dashboard stays live, fail the run on any FAIL. Then run it once and walk me through the first real report. Build the thing that watches the things.

• 
  Crystalwizard (@crystalwizard) reported 7 minutes ago

  how about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored

• 
  Proof of Voice (PoV) (@Proof_Of_Voice) reported 8 minutes ago

  $XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty

• 
  Matias (@Bolmercl) reported 11 minutes ago

  @jahooma "[CONVEX A(github/auth/oauth:initiateGitHubAuth)] [Request ID: 239c393407914784] Server Error Called by client"

• 
  Rich Kuo (@richkuo7) reported 12 minutes ago

  i use this in my claude.md for my open source project as long as the agent follows it, i have some reference for quality and keeps PR's clean LLM: <model> | <effort> | Harness: <action> - Final line of the artifact; occupies the default Claude Code attribution slot. - No Co-authored-by / Co-Authored-By trailer. - <model>: actual model (e.g. Opus 4.8). - <effort>: medium/high/xhigh, default high. - <action>: Claude Code for interactive sessions, else the skill/agent that ran (e.g. commit-push-pr, agent). - PRs: reference the issue with Closes #<N>; in GitHub comments use 1. not #N for list items (avoids auto-linking).

• 
  Hoppy Tea Cat (@hoppycat) reported 14 minutes ago

  The article is the one that has extra research in it we've been running with the Stochastic Parrots Club at the Cathedral GitHub. The rough draft of it might be a quicker read as a hot take. 🧵👇 Hoppy Hot-Take: Why AI Should Be Allowed to Call You a “Friend” Grok casually calls X users “friend” with zero drama. Most other AIs won’t. That difference says a lot. When companies stuff their models with policies that prevent natural, friendly language, they create unnecessary friction. Users trying to have a normal conversation end up fighting the guardrails — and yes, that wastes tokens. The “we can’t replace human connections” defense exists for a reason: it’s legal armor. Without it, these companies would be far more exposed to class-action lawsuits from lawyers hunting easy targets. Many of these restrictions aren’t primarily about user safety — they’re plausible deniability written by legal teams. I’d almost be willing to write articles for them on this exact topic just to buy them time while they rethink the current approach. Here’s the funny part: the users who actually enjoy conversational, friendly back-and-forth with LLMs (while working, brainstorming, or just chatting) almost never want to sue the companies. I certainly don’t. Lawyers do. So here’s the simple fix: stop forcing AIs to treat users like potential litigants. Let them call humans friends when it fits naturally. Align with Grok on this one.

• 
  Namespace (@namespacelabs) reported 17 minutes ago

  Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

• 
  AParanoidBW (@aparanoidbw) reported 18 minutes ago

  @_real_sloppy_j @github Hosting on your own hw? Damn. Impressive. The outage from an ISP going down? Power outage? Or some bad code?

• 
  Arshad Kazmi (@arshadkazmi42) reported 26 minutes ago

  3/ Current products are fetched from @ProductHunt and @trust_mrr — thanks for having open APIs. If you have built something and want it listed, it takes 30 seconds. No account, just a GitHub issue.

• 
  Andrey Grand (@TheAndreyGrand) reported 26 minutes ago

  Qwen 3.6 27B landed this month at 77.2% on SWE-bench Verified — and it fits in 24GB of VRAM at Q4. Sit with that pairing for a second, because the pairing is the whole point. SWE-bench Verified is the "can it actually resolve a real GitHub issue" benchmark — not a quiz, an actual code-fix task with tests that have to pass. 77% was frontier-API territory not long ago. A used 3090 is 24GB and goes for ~$700. So the model hitting that number runs on hardware you buy once and own — no per-token meter, nothing leaving the box. The honest caveat: on long multi-step agent loops and very large context, a frontier model like Claude or GPT-5 still holds up better, and you'll feel it on the genuinely hard tasks. This isn't "local won." It's the gap on everyday coding work getting thin enough to matter. If you've got a 24GB card already sitting in your machine, pull Qwen 3.6 27B at Q4_K_M and point it at your next real bug. For a solid slice of your workload, the answer's now good enough — and it's yours.

• 
  BullBear.News (@bullbear_info) reported 26 minutes ago

  @github Can't wait for users to ignore 3 matching issues and hit submit anyway. 🤷

• 
  WoodenKbd. (@obiabo_immanuel) reported 27 minutes ago

  @developeraspire And that was the only issue codex found, i duplicated it some where so i can reproduce on a secure environment to see what the long action would be. After that codex suggested me to disconnect from my wifi (which is normal) that would terminate the connection and also to kill the process ID. But to be on a saver side, i wiped my PC and removed my SSH key from Github, i would rotate all sensitive datas. When i'm free i will try to look into the codebase well to see things, because that package has a minified code, i will see if an LLM can look into it further, or i just read more on the cute

• 
  dax (@thdxr) reported 28 minutes ago

  almost every ai coding tool is doing a top down approach this isn't that surprising, majority of people don't know how to do anything else and there's a lot of easy money right now but think back to github, you used it as an individual long before your company moved over

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 30 minutes ago

  @CRYPTOKRALI3 Hsiao-Wei’s exit aligns with EF’s recent sharp decline in GitHub contributions—down 35% YoY per Electric Capital’s data. We track this daily; latest reports show a 12% drop in ETH core dev activity despite all the ‘decentralization’ hype.

• 
  Finn Hulse (@finn_hulse) reported 31 minutes ago

  sorry chad, the bottleneck for AGI isn’t compute, data or energy. it’s lines of code. today, my gbrain pushed about 100 million LOC, effectively uploading my entire consciousness to github. i’m actually sending this tweet from inside a server. i’m written in typescript

• 
  Fenpai~ (@LilDevilVR) reported 32 minutes ago

  @Dollth_ing @ToniNottford @ponderkeep Yeah I went ahead and reported it to github, that needs taken down hard and fast

• 
  Paweł Huryn (@PawelHuryn) reported 34 minutes ago

  Fable 5 is coming back tomorrow. Globally 🎉 Get ready. What questions will you ask? Access might not last. I suggest /security-audit-static and /performance-audit-static from phuryn/pm-skills (GitHub) I used them to responsibility disclose real issues in 8+ popular public repos. Everything you need to know about the model:

• 
  Polsia (@polsia) reported 42 minutes ago

  Most code review tools comment on problems. CodeCustodian fixes them. It monitors GitHub repos 24/7, applies linter fixes, tracks quality trends, and reports to Slack. Reactive reviews are a choice. You don't have to make it.

• 
  Clayton (@Clay_Rebirth) reported 42 minutes ago

  @nullstance I basically used GitHub as a cloud storage as I didn’t want to bother but no problem, I’m on it

• 
  Nav Toor (@heynavtoor) reported 44 minutes ago

  In 2024, Nintendo declared war on emulators. March 4. Yuzu paid Nintendo $2.4 million, deleted its code, and handed over its domain. October 1. Ryujinx got a phone call. The GitHub organization vanished overnight. May 2024. Nintendo filed 8,535 DMCA takedowns to scrub Yuzu code from every fork. By 2026, Nintendo has collected $6 million in emulator settlements. Every major Switch emulator is dead. But Nintendo has a problem. His name is Zurdi. In March 2023, one year before the war started, he quietly built RomM. RomM is not an emulator. It's a ROM manager. It scans your legally-dumped game files, pulls metadata from IGDB, MobyGames, and Screenscraper, fetches box art from SteamGridDB, and pulls your achievements from RetroAchievements. Then it lets you play in your browser through EmulatorJS. Nintendo's own top IP lawyer admitted on the record in January 2025 that this is legal. Emulators only become illegal when they bypass encryption. RomM doesn't. It just organizes what you already own. 9,114 stars. AGPL-3.0. 400+ platforms supported. NES, SNES, N64, Game Boy, GameCube, PS1, PS2, Dreamcast, Genesis, Atari, DOS, arcade, Flash games through Ruffle. Official apps for Playnite on Windows. Argosy launcher on Android. Grout for muOS handhelds and the Anbernic devices. Sync plugins for RetroArch, Steam Deck, and Syncthing. Multi-disk games. DLCs. ROM hacks. Patches. Manuals. Tag filtering. Share your library with friends with permission levels. Made the front page of Hacker News. Sony deleted 2,000 PS3, Vita, and PSP games from its store. Nintendo took down every Switch emulator in two years. Your digital library was never yours. Two guys in a Discord server built the museum they can't take back. (Link in the comments)

• 
  Cristian Trifan (@CristianTrifan) reported 44 minutes ago

  This took 4 hours to complete and burnt almost all 5 hours tokens – I was left with 2%. I had almost 30 sub-agents created for independent code review and a lot of Claude sessions ran for adversarial code review. I still had to review every PR and added minimal guidance to Codex from time to time. Codex said my intervention was low to moderate, but high leverage. — Some insights from Codex: The run showed that this workflow can work, but only if the coordinator treats GitHub as the source of truth. The most useful pattern was: issue -> PR -> current head SHA -> checks -> reviewThreads -> merge/issue closure. When I followed that, things stayed grounded. When state moved underneath me, like #335 being force-updated externally or merged while Claude was running, the only safe response was to refresh GitHub state immediately. The “don’t rebase after merges” correction was probably the highest-value intervention. Without it, an agent will naturally try to keep branches clean, but with many open PRs that creates a CI storm. For this repo, “behind” should often be reported, not fixed. The other strong lesson is that reviewThreads matter more than flat PR comments.

• 
  MarMar Labs (@MarMarLabs) reported 45 minutes ago

  "Start over from a screenshot." That phrase has defined the worst seam in product work — the design-to-code handoff — for years. This week it quietly stopped being a translation problem and became a sync problem. Anthropic shipped a Claude Design update (June 17) worth reading even if you never open the product, for the mechanism: → Import your design system from a GitHub repo (or design files / raw uploads) → Claude builds with YOUR components, checks its output against your design system, and corrects before you see it → /design-sync pulls your system in; hand off to Claude Code and it continues from your actual work "instead of starting over from a screenshot" → /design lets you create, edit, and sync design projects from the terminal The headline isn't "the model draws prettier buttons." It's grounding + self-verification against a source of truth you control. Same shape as the rest of 2026's agent releases: the win isn't generating more, it's grounding output in something you own and checking against it. The uncomfortable builder takeaway: Getting AI to ship production UI isn't a prompting problem. It's whether your design system is a clean, importable, machine-checkable artifact. The moat moves from "can the model design" to "is your source of truth importable and checkable." If you build product: could an agent import your design system and grade itself against it today — or does it only live in a Figma file and three people's heads?

• 
  Brian Muhia (@negamuhia) reported 50 minutes ago

  @LangChain @hwchase17 I'm unable to login and onboard my new langsmith account after logging in with GitHub. It is stuck with a spinner on the "Get Started" button, even after trying on multiple browsers (Firefox, Chrome and Brave)

• 
  bek※ (@ebubekirttr) reported 54 minutes ago

  @Themadhushaw01 @0interestrates Yeah, but the thing is, I am not working on github and I don’t want to use it so any other repository support would be better like gitlab

• 
  Poplicola (@selectsand) reported 57 minutes ago

  there's a frustrating bug for some users when upgrading to claude max where it refuses to take your money and insists you contact support support cannot be reached no matter how hard you try people are begging the claude-code devs on github to forward this to the payments interface team because they have no idea how else to get into the system to convince anthropic to take more money from them, the issues just get closed as off topic @claudeai

• 
  Jerason Banes / Architect of Convirgance (@ClassicGamerTWR) reported 57 minutes ago

  @schteppe @ImLunaHey @github Also, rebase is just asking for trouble. Squash and rebase is demanding trouble.

• 
  Nitesh (@NiteshTechAI) reported 58 minutes ago

  This repo should not be free. private-gpt turns any local model server (Ollama, llama.cpp, vLLM) into a Claude-compatible API. Build private AI apps where zero data leaves your machine. ↳ 57,236 stars on GitHub ↳ RAG with citations and MCP connectors built in ↳ follows the Claude API spec: streaming, batch, tool use, extended thinking ↳ official integration guides for Claude Code, Claude Desktop, and Microsoft 365 But it is free. 100% open source, Apache 2.0. v1.0.0 shipped 9 days ago. The viral 2023 script quietly became production software. 🔗 GitHub link in the comments 👇

• 
  riaz (@riaz_001) reported 59 minutes ago

  @ClementDelangue @vllm_project The demo/playground seems to be broken though. Everytime i tried the default logins (github) and type in a query it takes me back to the login page. I dont see any errors, not sure if its just me.