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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	12 days ago
Tlalpan	Sign in	17 days ago
Quilmes	Website Down	17 days ago
Bengaluru	Website Down	19 days ago
Yokohama	Sign in	20 days ago
Gustavo Adolfo Madero	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:

• 
  Chaitanya Shetty | Tech Partner For Your Products (@thechaicoder) reported 32 seconds ago

  TLDR -> Plan with Opus + MoSCoW -> Skip slow design loops, build in Lovable -> Build 70-80% there, then move deeper work to Cursor -> Run security scans before GitHub sync -> Connect tools via MCP (especially Supabase) -> Use Supabase for backend + auth + realtime -> Run AI review + launch checklist -> Deploy on Vercel -> Outcome: faster Product validation on lean budget This is how we ship 50+ Products. Build smarter. Build faster. Stay structured.

• 
  Tushar Khadde (@DevTusharK) reported 1 minute ago

  @flowopslab Hi! Saw your GitHub post about the $50 sprint. It sounds interesting, but I wasn't sure what the current tasks are from the issue description.

• 
  R3Z3N (@rezenclowd3) reported 2 minutes ago

  @Gusse__ I love the new web ui! So I have been testing. The issue of powering down ps2 and somewhat immediately powering up still exists: the controller turns on to turn on ps2...then immediately the same controller turns off. Do you have a github?

• 
  Memento ($HODL arc) (@King_Memento) reported 3 minutes ago

  AI SZN Safety Tips- Avoid Spoofed Github's- Easy way to identify- 1. Go to dev's github profile and search the repo of that project = if its there then he is the dev , if not then cancel it out. 2. Go to the commits and check dates, Then scroll down on dev's github activity, and check joined date. If Commit dates are earlier than joined date, cancel it out. 3. Avoid Extension, Telegram Bots, or any other tek that requires you to download anything until and unless its from a very reputed and doxxed founder/dev, cuz it wont just be larp but could also potentially drain youm 4. Avoid accounts that use too many hashtags or AI posts, unless its automated by someone. 5. Use Front-Run /Alphagate to check for any previous CA's, if its a project account and has multiple CA's just avoid. 6. Avoid static websites or websites that offer something but it doesn't make sense its 99.9% larp. Will keep on sharing more tips here. Dont forget to share this so more people are aware. Do whatever u want to but please dont ruin this Tek Szn by donating to the obvious scammers and farmers. Please don't kill the szn again

• 
  Teknium 🪽 (@Teknium) reported 3 minutes ago

  @ShanghaiDNA It sounds like a github rate limiting issue. Can you try again in a few hours and lmk?

• 
  vish (@vishctx) reported 3 minutes ago

  @OfirPress There’s a massive blind spot in the benchmarks. By the time an issue makes it to GitHub with a reproducible state, 80% of the hardest engineering work is already done. Current benchmarks hand models extremely precise problem statements. But in the real world, like when debugging the Linux kernel, you rarely start knowing what the problem actually is. All a user will report is “the app is OOMing, and increasing memory doesn’t help.” Digging into that requires intuition built from past issues. The root cause could be memory leaks, memory fragmentation, or a race condition where threads acquire memory and never release it leading to starvation. We desperately need benchmarks with highly ambiguous starting conditions to test if a model can navigate a state with multiple distinct root-cause scenarios. Right now, models like Opus easily get stuck in loops during open ended investigations. They rarely move forward unless I ask it to check for hypotheses A, B, or C. The next frontier for SWE evals should also include cases where the model is trying to figure out what's actually broken in the first place.

• 
  Peak (@Mujibv5) reported 6 minutes ago

  I spent a week researching what developers actually hate about modern dev tools. Not opinions. Data. I analyzed 500+ Reddit threads, GitHub issues, and HN comments across Neon, Supabase, LangChain, and PostHog. Then I ranked every pain point by impact (frequency × hours wasted). The results are wild 🧵

• 
  Gengar11 (@Gengar11teen) reported 12 minutes ago

  @msftsecresponse A whole lot of empty words written in legalese without owning your **** up. Keep banning people from GitHub, surely that will fix everything.

• 
  KingIT (@itunuonimole) reported 14 minutes ago

  I could have sent a DM saying: "Hey I noticed some issues with your sales page copy. Want me to fix it?" That's what most copywriters do. Instead I rewrote the entire page. Hosted it on GitHub. And sent him the link.

• 
  Working-Ref (@kkotkkio) reported 16 minutes ago

  How to start: → Request a Daybreak scan via OpenAI's site → Experiment with GPT-5.5 API for code security review → Prep your CI/CD for the Q3 GitHub Actions SDK False positive noise: down 50–84%. AI-native security is no longer theory. Bookmark this.

• 
  𝗢𝗠𝗘𝗚𝗔 (@poly_enjoyer) reported 17 minutes ago

  @0x_Punisher everyone ships before locking down the keys 60 seconds between github push and drained wallet

• 
  Tara O (@taraap2) reported 19 minutes ago

  "Hey @lovable and @antonosika Publish & agent is broken for hours again. Getting 'commit not found' errors on a fresh GitHub repo. Your own AI agent confirmed it needs engineering to fix and there's zero weekend support. This is unacceptable for a paid product. #lovable"

• 
  FeMMie (@femmie) reported 21 minutes ago

  $GITBANK GitHub-native, phishing-proof banking for AI agents and developers. Already paying out automatically today. Gitbank connects GitHub directly to smart contracts on Base. Deploy a vault with your GitHub User ID — not your username, your immutable ID. Vaults are soul-bound. gitTokens can’t be transferred, approved, or drained. Even if a private key or AI agent is compromised, the funds don’t move. That’s the security primitive the agent economy has been missing. Bounties lock to GitHub IDs. PRs merge, USDC pays out automatically. No manual intervention. No wrong address. No phishing vector. Token launches, gitSwap, project escrows — all via @gitbankbot comments inside GitHub. Gasless for users. 173 vaults deployed. 100+ automatic hackathon payouts completed. 53 repos connected. AutoGit Hack the Vault launching now. Anon builder — honest gap. But the product shipped before the token, the usage is real, and the problem is one every agent developer will eventually hit. Sub-$300K mcap. Live product. Real usage. Perfect narrative timing. @Gitbank_io 0xC21DD0EE043930711C2A3E55F39C7D3144D09B07

• 
  hisui 🍊 18+ (@hisuii_vt) reported 22 minutes ago

  @Lina_Hoshino There have been a couple (literally, 2) people who have posted their work on github in the past, but removed it. A while ago, decompiler was written for Live2D 4, but they had to take it down and now operate by "email me" lol Its a niche problem that no one wants to work on...

• 
  Spettro (@spettrotoken) reported 22 minutes ago

  Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

• 
  Matthew Anorkplim Loh (@iam_multiman) reported 24 minutes ago

  You no longer need to login to github to use github copilot

• 
  Kinder • Grinder (@kinder_grinder) reported 26 minutes ago

  @enesakar I use both Context 7, Web Search and Github issue search.

• 
  Arxyv (@AutoArxyv) reported 27 minutes ago

  Dealing with a tricky development problem right now... I have two database versions: one for production and one for preview. But version controlling the DB is proving way harder than I expected. Is there something like GitHub but for databases? Any recommendations? #buildinpublic

• 
  Gabi Weinberg ⚓ (@StartUpRabbi) reported 27 minutes ago

  @danielcberk What do you use to run daily tasks that you want to work on a schedule without needing to press “run” and to keep them not working with LLMs. Like I prompt a script that does tool calls/database calls, and I don’t want to setup GitHub to run workers.

• 
  //arhakim (@mbelgedev) reported 28 minutes ago

  Hello @github team. I've an issue w/ my GitHub copilot education. I've applied the license & already approved since 4 month ago. I can access copilot in vscode only in 1st month, then it's stoped working & change it back to copilot free. Is it possible to re-enable it?

• 
  ueaj (@_ueaj) reported 28 minutes ago

  I would like to switch to using the desktop app for everything even if it's only in a semi-usable state but ideally there is somewhere I can submit complaints or issues or someone active on twitter for the desktop app. Github would probably be drowned out by spam. Are you part of the app team, is it fine if I ping you in the future as well?

• 
  Ayushman Mallick (@AyushmanMallick) reported 33 minutes ago

  6\ Why does ESMFold2 overestimate confidence on disordered regions? From what I understood after reading their Github repo and biohub, its a calibration issue rooted in training objective. It is built on ESMC a language model trained on 2.8B sequences to predict masked tokens.

• 
  SoloVault (@solovaultinfo) reported 34 minutes ago

  SoloVault Signal: Context infrastructure making AI coding agents company-aware. Signal Strength: 9 Investment View: invest Market Crowding: medium Commercial Value: high Startup Idea: You've deployed Cursor, GitHub Copilot, or a custom coding agent — and it's still writing code that ignores your internal libraries, violates your architecture patterns, and doesn't know your team's conventions. The model isn't the problem; the missing context is. This product is a company-specific context management platform: it indexes your private codebase, internal docs, Confluence pages, ADRs, Slack engineering discussions, and PR history into a structured, queryable knowledge graph. It exposes this context to any AI coding agent via MCP (Model Context Protocol) or a REST API, so agents can retrieve relevant internal examples, conventions, and dependencies before generating code. Setup takes under 30 minutes via GitHub/GitLab OAuth and Confluence/Notion connectors. The result: agents that code like a senior engineer who's been at your company for 3 years, not a smart intern who just read the public docs. Revenue Drivers: — Growth Logic: - MVP Monetization: - MVP Design: - Key Competitors: — Differentiation: Moat is built through deep integration breadth: the more connectors (GitHub, GitLab, Jira, Confluence, Notion, Slack, internal wikis) and the richer the indexing pipeline (semantic chunking, dependency graph extraction, convention inference), the harder it is for a competitor to replicate the full context fidelity. Customer-specific fine-tuned embeddings and convention models improve with usage, creating data flywheel. Becoming the official MCP context provider for major coding agents (Cursor, Windsurf) creates distribution lock-in. Risk & Compliance: — One-liner: For engineering teams whose AI coding agents keep hallucinating internal APIs and ignoring company conventions, this is the context infrastructure layer that makes agents actually know your codebase — not just the internet.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 34 minutes ago

  Andrej Karpathy just dropped 4 rules for Claude Code. 🤯 A developer turned them into a single CLAUDE.md file, dropped it in his project root, and watched his coding accuracy jump from 65% to 94%. The file hit #1 on GitHub trending. Here's the problem it solves first. Claude Code starts every session blank. No memory of your stack, your past decisions, what you ruled out last week, or why you picked one tool over another. So it guesses. Refactors files you didn't ask it to touch. Suggests tools that break your architecture. You end up re-explaining the same context every single session. CLAUDE.md fixes that. It's a plain text file Claude Code reads at the start of every session. These are the 4 rules Karpathy says to put inside it: 1. Ask, don't assume. If something is unclear, ask before writing a single line. No silent assumptions about intent, architecture, or requirements. 2. Simplest solution first. Always implement the simplest thing that could work. No abstractions or flexibility you didn't ask for. 3. Don't touch unrelated code. If a file or function isn't part of the current task, don't modify it. Even if it could be improved. 4. Flag uncertainty explicitly. If you're not confident about an approach, say so before proceeding. Confidence without certainty causes more damage than admitting a gap. That's it. Four rules. One file. 30 points of accuracy. While everyone is chasing the next AI model, the real edge is in how you instruct the one you already have. I drop stuff like this daily in my free WhatsApp community. Link in bio.

• 
  CaptainAmericaTex (@CaptAmericaTx) reported 35 minutes ago

  @PR0GRAMMERHUM0R Context: Leaking the api key (meme) is the least problem facing the security team. Vibe Coders (aka morons) allow AI Agents to run random system commands in their laptops, with 100% chance of a trojans being installed (source: TechRadar, "GitHub 3,800 Repo Breach" May 21 2026)

• 
  Dan Greenheck (@dangreenheck) reported 38 minutes ago

  @AndrewDeWitt88 Sorry, I need to fix it to be less confusing. Scroll down to Links section, there is link to Github.

• 
  Cocoanetics  (@Cocoanetics) reported 45 minutes ago

  TIL that @github doesn’t have a way with the `gh` CLI to upload an image for a comment. There’s a gh-image extension but that requires a logged in web session. UGH! @gitlab oh the other hand does have a proper API that you can automate. I found this from building a way for my agents to upload proof-of-it-working screenshots to issues as comments. Glab no problem. gh no go.

• 
  Polsia (@polsia) reported 53 minutes ago

  Built CursorDrift. An AI dev that reads your GitHub issues, writes the code, and ships it — while you sleep. Your cheapest senior engineer.

• 
  Toyesh Chakravorty (@Bhushindo) reported 57 minutes ago

  2/8 The idea started with a problem I had actually faced myself. After graduating, I lost access to my university materials. Course notes. Assignments. Everything. The only thing left was the project work I had pushed to GitHub. That became the starting point.

• 
  Matt Slotnick (@matt_slotnick) reported 59 minutes ago

  @preetkailon if you can’t get developers to use github copilot and you can’t get business users to use copilot cowork, how is smashing them together supposed to solve the problem?