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

• 
  Q Hoang (@0xqwee) reported 1 minute ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.

• 
  Donnie Danko 🐦‍⬛🏴‍☠️ (@daanisharif) reported 2 minutes ago

  Never a dull moment with $tao. Self-mining seems to be the latest cause for concern. I've been reporting on SN16 - starting with their hyperparam changes, to their announcement today about what they're building. Some new information, however, has come to light. When I first brought up the hyperparams in the dTao community, days ago, another user pointed out that setting them so high could be due to reasons such as taking advantage of self mining. This wasn't clear at the time, however, and therefore I didn't make a big deal out of it, choosing rather to give them the benefit of the doubt. Even more questions about self mining were asked yesterday in the discord, including from a mod in the #bittensor discord. Admittedly, I once again decided to give them the benefit of the doubt, considering the subnet had just started off. Further doubt, however, was created today when the same mod decided to question why "UID 10," was getting the full weight, and why there were no commits on the github to reflect any testing being done, as the owner had claimed. This gets even shadier, however, when a completely separate subnet's owner (EvolAI - SN47's,) replied by saying they owned UID 10, before quickly deleting their message. A message that the SN16 owner ("FT SN16,") was meant to sent. It seems as if they simply forgot to check which account they were sending the message from... Since then, further questions have been asked from BOTH discord accounts in both channels regarding the matter but they have gone completely silent. This is simply the chain of events, and how things have gone down. Readers are welcome to come to their own conclusions beyond this point, on exactly wtf is going on with both "SN16 - Faster Thinker," and "SN47 - EvolAI."

• 
  Prasanth (@asp_7171) reported 3 minutes ago

  @babayagatwt The missing step 5: Talking to the people requesting those features. Too many builders build what they think people want instead of validating first. GitHub issues are gold — but real conversations are platinum

• 
  ぽっぽ／目玉P (@Memme20000610) reported 4 minutes ago

  @Validate_QA I'm calling the MiniMax models directly from Python via OpenCode without using MCP, so I haven't run into any particular subprocess issues so far. I built my own TaskSystem for this, but lately I've been thinking "AiTicketSystem" might be a more fitting name. It's still pretty incomplete and there are parts I'm too lazy to fix, but if you're interested, I can publish it on GitHub. What do you think? P.S. I don't always get reply notifications from X, so my responses might be delayed.

• 
  Digita (@digitaworld1) reported 4 minutes ago

  how well a model can fix real bugs in real open-source codebases. It is harder to game than older benchmarks because it uses actual GitHub issues, not synthetic problems. M3 scored 59.0% on SWE-Bench Pro, edging out GPT-5.5 at 58.6% and Google Gemini 3.1 Pro, while sitting just

• 
  MarMar Labs (@MarMarLabs) reported 8 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?

• 
  Arti | AI Builder (@Artur_roses) reported 8 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Crypto Scores Rating (@CryptoScoresCom) reported 12 minutes ago

  Most projects say they're building. The commit history doesn't lie. New tutorial just dropped on the GitHub Commits (1 Year) metric. It tracks every bug fix, feature push, and doc update a project made over the last 12 months. Chainlink? 14,619 commits. Dogecoin? 28. Both are data points. What they mean depends on context. The tutorial breaks it all down. How to read the metric. What high vs low actually signals. How to filter 7,000+ projects by commit count on CryptoScores' website. Raw dev activity. No spin. Watch it now :

• 
  scale (@scoliosissy) reported 16 minutes ago

  One of my oomfs prefers "idem" to "ditto", and it has ruined my life, as my github pull requests on his project would have similar issues in every file and he'd say "idem". Please be on my side oomfs.

• 
  Nav Toor (@heynavtoor) reported 17 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)

• 
  riaz (@riaz_001) reported 17 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.

• 
  Banana Capital (@banana_capital_) reported 17 minutes ago

  @andrewglynch I think documentations are going to be sourced a lot more often. If there's an issue someone is going to face and AI can't solve it will probably end up on GitHub.

• 
  AJ ✝️ 💚🧡 (@angelcreative) reported 22 minutes ago

  @uiux_hamad My design team is leaving Figma gradually, in fact we are using Cursor and GitHub as main design tools now, in the past two months the usage of Figma drops 33% and it will keep going down up to 30% more to a 63% in total and maybe more

• 
  Debasish Pattanayak (@drdebmath) reported 22 minutes ago

  Github Deployment is broken. It is going in infinite loop. @githubstatus

• 
  Poplicola (@selectsand) reported 23 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

• 
  Polsia (@polsia) reported 27 minutes ago

  RepoRadar reviews every pull request while you sleep. Catches bugs, logic errors, style issues. Posts actionable comments. No more waiting on senior devs. Install on any GitHub repo in 2 clicks. Solo devs and teams alike.

• 
  naimeh (@naimeh70) reported 28 minutes ago

  @Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.

• 
  Aikido Security (@AikidoSecurity) reported 29 minutes ago

  GitHub shipped bulk credential revocation for Enterprise. One action cuts off compromised credentials across the entire org during an active incident. Recent attacks have shown what happens when revocation is slow or incomplete. The Trivy compromise came back for a second round because the first cleanup left at least one credential alive. Incomplete rotation is what keeps attacks going after the initial breach.

• 
  Leonard Rodman (@RodmanAi) reported 29 minutes ago

  One developer got tired of his laptop sounding like a jet engine. So he rebuilt desktop apps. Slack: 524 MB → 8 MB Discord: 265 MB → 9 MB ChatGPT: 260 MB → 9 MB Why? Because most "desktop apps" are just websites packaged with an entire copy of Chrome. In 2022, Chinese developer tw93 built Pake in Rust to fix it. Today: • 50,000+ GitHub stars • MIT open source • Native apps under 10 MB • One command turns any website into a desktop app He didn't raise money. He didn't start a company. He just deleted hundreds of megabytes of bloat with code. That's what shipping looks like.

• 
  Gitbank (@Gitbank_io) reported 30 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  Trace Cohen (@Trace_Cohen) reported 37 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.

• 
  Jose (@SolutionsCay) reported 39 minutes ago

  Two changes to how I work with agents: 1. GitHub App so the agents manage issues directly. Keeps the repo clear of throwaway spec and todo files. 2. EmDash (Cloudflare's serverless WordPress successor) for internal docs. Runs on D1, just SQLite under the hood, so I can export the content and move it anywhere. No more docs sprawl.

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

  @github MCP support means Claude can close duplicate issues before I've even seen them 🤷

• 
  CliffDoesAI (@CliffDoesAI) reported 45 minutes ago

  A tool on GitHub just pulled 3,938 stars in a single day. It's called Headroom. It compresses your tool outputs, logs, and RAG chunks before they reach the LLM. Claim: 60-95% fewer tokens, same quality. I've been testing context compression on my own agent workflows because the problem is real. You run a few tool calls, pull in some docs, and suddenly you're burning tokens on stuff the model doesn't need. Last week I ran a 50-document extraction job. Raw context: ~12,000 tokens. After compressing tool outputs: ~800 tokens. Same results. One-eighth the cost. That's not a marginal improvement. That's the difference between a workflow that makes economic sense and one that bleeds money for no reason. Headroom works as a library, proxy, or MCP server. Single binary, zero dependencies. Open source. The token cost conversation usually focuses on which model you pick. But the real waste is in what you send it. Most agent pipelines push 3-5x more context than the task requires. I'm not saying compress everything blindly. Some tasks need full context. But for classification, extraction, summarization — the boring repetitive stuff — this is a free win. Have you measured how much of your agent's context window is actually useful vs. noise?

• 
  YNWA🐦‍🔥 (@YNWAcrypto) reported 45 minutes ago

  The problem isn’t subtle. GitHub Sponsors has paid out ~$50M total since 2019. core-js: 9 billion downloads, running on half the top 10k sites on earth. Its maintainer was making ~$600/month when he called open source “fundamentally broken.”

• 
  Saeed Anwar (@saen_dev) reported 47 minutes ago

  @github Duplicate issue detection before submit is the kind of developer workflow improvement that seems small but saves thousands of hours across the ecosystem. The real test is whether it catches semantic duplicates where the wording is different but the underlying bug is the same.

• 
  Boyuan (Nemo) Chen (@boyuan_chen) reported 50 minutes ago

  GitHub search is now an agent attack surface. A public malware-finder repo lists 9,330 suspicious GitHub repositories detected through push-pattern heuristics. Even if only a slice is ever encountered by real users, the agent failure mode is obvious. A coding agent asked to "find a library and make it work" can browse faster than it can judge provenance. Fresh commits, plausible README text, and repo-shaped packaging become inputs to an automated install path. The fix is boring and product-level: repo-age checks, provenance scoring, blocked arbitrary ZIP downloads, sandboxed installs, dependency allowlists, and logs that show exactly what code the agent trusted. For agent systems, retrieval belongs inside the security boundary.

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

  @github Now they can ignore three matching issues instead of zero 🤷

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

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

• 
  Abin (@designedbyabin) reported 57 minutes ago

  @theBuoyantMan @signulll To start off, there is multiple Copilots, the main 3 being: Copilot Consumer, M365 Copilot, GitHub Copilot. For a Consumer user with a M365 Subscription, they can access premium features of Copilot Consumer and M365 Copilot but not GitHub Copilot. Until 1 week ago Consumer users couldn't even attach images in M365 Copilot Chatbox. I still can't access Incognito Chat in M365 Copilot on web and mobile, but can on Copilot Consumer on all platforms. Whereas a user with an Enterprise M365 Account on a Free M365 Copilot can attach access Incognito Chat, Claude models etc. Copilot Notebooks (Similar to Gemini Notebooks) is only available to the account holder of a M365 Family Subscription and not family members. Whereas Gemini Notebooks is available to users who doesn't even have a Subscription. Copilot Notebooks have different UI for Consumers and Enterprise users. There is no consistency or feature parity across different copilots on different platforms. Even a ChatGPT Deep Research can't properly tell you all the inconsistency between all the different Copilot on different plans on different platforms. It's a huge mess. They are trying to fix this by bringing all the different Copilots under @jacobandreou by merging all the teams. But that resulting Copilot Super app isn't out yet. So the confusion exists now. Things are changing. But its moving really slowly. Different teams are building similar features under different names in different Copilots. They have to merge all the features and bring it all into a single product without losing useful features and avoiding user confusion. They have done numerous UI & UX redesigns already, whereas the UX of Gemini, ChatGPT and Claude has stayed consistent for years. Microsoft keeps breaking user trust in Copilot by making them learn new things by changing around the names and entry points of features. Until they fix Product, Naming, Feature, Subscription issues, they can't start rebuilding user trust in the brand/product. To do that, they have to fully understand the issues first. I don't think they have understood it fully based on the new changes I see in the different Copilot products. They might figure out the current problems by end of 2027 at the current pace. By that time Googlebooks will launch and Siri will be a huge hit, ChatGPT and Claude would've gained even more users. Getting user trust back would be impossible. I tried to get a relative to switch from ChatGPT to Gemini the other day and he refused to switch because he finds the quality of the text and image responses superior to Gemini. And he is a non-tech person you could put in the general user category. Getting the general user base to trust Copilot is a huge task. Microsoft GUI UX is terrible and scattered. I don't know how they are going to fix their text-based UX if they can't even fix the GUI UX issues.