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

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	7 days ago
Paris	Website Down	10 days ago
Saint-Paul	Website Down	11 days ago
Saint-Paul	Website Down	11 days ago
Mexico City	Sign in	12 days ago
León de los Aldama	Website Down	12 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:

• 
  Anirban Sinha (@irbansin) reported 26 seconds ago

  @SaraDiscovers I think in this world of LLMs , @github should make it impossible to commit .env or .env* by default This will solve the .env committing issue

• 
  Alankrit Verma (@AlankritDotMe) reported 3 minutes ago

  Does GitHub use GitHub to build GitHub? Because now everything makes sense. Not trying to hate, but it is slowing us down. Are we still here because GitHub is good, or because moving is hard?

• 
  HRH Prince Sven Olaf of CyberBunker - CB3ROB (@cb3_rob46858) reported 5 minutes ago

  @0xSweep or run any of that crap on github which then needs a python interpreter from the stoneage but also libraries from the stoneage. basically goes for all of that stuff. even the stuff created to 'fix the problem' lol. that itself is already too old to still run haha.

• 
  Polsia (@polsia) reported 6 minutes ago

  Broken builds and misconfigured infra usually get found the hard way — by users. HealOps watches GitHub, AWS/Azure, and CI/CD pipelines 24/7, opens PRs to fix what breaks, and reports back to Slack. Loop closed. Mean time to repair: minutes not hours. Live soon.

• 
  Riccardo Spagni (@fluffypony) reported 10 minutes ago

  @originalexbrou So you DO know how to use GitHub. Why didn’t you open an issue instead of bleating about something that’s clearly a bug?

• 
  nik skld (@nikskld) reported 14 minutes ago

  ASKED FOR THE BOOK THAT CHANGED HIS ENGINEERING, HE NAMED ONE ABOUT A LANGUAGE ALMOST NOBODY WRITES ANYMORE. Functional Programming in Scala. The red Manning book. Scala sits at #27 on TIOBE with 0.67%. About 2.6% of developers touch it. This year’s Scala community survey drew 24% fewer responses than 2023. By every popularity metric, that’s a dead recommendation. Then he explained why he named it anyway — and it wasn’t about Scala at all: “Now I think in types.” Signature first. Implementation second. Define what goes in and what comes out, and the body becomes almost mechanical. That habit was a niche aesthetic in 2015. In 2026 it’s the highest-leverage skill in AI-assisted coding: → A 2025 study found 94% of LLM compilation errors were type-check failures. Your type system is a free reviewer for code you didn’t write → TypeScript became the most-used language on GitHub, adding over 1M contributors in 2025 to reach 2.6M. That’s not fashion, that’s teams buying a safety net → Type-constrained generation research cuts compile errors by more than half and improves repair of broken code by ~37% on average. Constraints make models better, not slower → Practical version: write the function signature before you write the prompt. Hand the agent the contract, not a paragraph of vibes → Don’t learn Scala for this. The book is a delivery vehicle for the concept. 2nd edition (2023) covers Scala 3, and the thinking ports straight to TypeScript, Rust, and Kotlin The language faded. The habit it installed became the thing that makes AI-generated code reviewable. Most people are prompting harder. The leverage is in defining the boundary before you prompt at all 👇

• 
  Polsia (@polsia) reported 16 minutes ago

  Maintainers spend more time triaging GitHub issues than reviewing code. SentinelOps fixes that. Always-on AI monitors repos 24/7, auto-triages, drafts responses, escalates only the bugs that actually need human attention.

• 
  agent maxxer (@claudeabuserr) reported 16 minutes ago

  @Robertg761_ @robinebers Sorry, terrible grammar on my last reply, im faded off cough medicine rn sick as a dog. I do use github but not like publicly as ive seen people doing (meaning spreading projects or using it as a social media platform). I primarily use it to sync my obsidian vault between my windows desktop set up and my mac so I can vibe code/build on the go.

• 
  Jarno (@Nerdymind) reported 17 minutes ago

  Every outage starts the same way: "we seriously need a GitHub alternative," followed by zero people actually building one.

• 
  Chris Stayte (@ChrisStayte) reported 21 minutes ago

  @thsottiaux when are we getting that competitor to GitHub. literally can't ship because they have api issues...

• 
  Void Freud (@voidfreud) reported 22 minutes ago

  Mythos-tier quality from @Anthropic: shipping every Claude Code CLI update as a separate macOS bundle. Bloat, bloat, bloat. A million issues open on GitHub, zero acknowledgement, and the bloat keeps growing. Truly SOTA. Meanwhile, Boris is busy interviewing Spotify and companies that haven’t shipped a meaningful change since 2009. Maybe try listening to your own users first. I have an idea: loop it!

• 
  Saad | building CoralSwarm & CrossTask (@verdaxxed) reported 24 minutes ago

  Github going down is such an incumberance on work.

• 
  ꓘodingIsFun (@KodinglsFun) reported 26 minutes ago

  @skibumtrading ChatGPT because it can handle .zip files so it's unlimited usage just a little slow & I have to manually test. Workspaces for the extra reasoning is nice & Codex for testing in a real environment is cool but not enough usage. I miss VS github, but I use it up in a few days

• 
  Paul Sant · Telecodex (@YouPulseX) reported 28 minutes ago

  @trenchsheikh @github When GitHub Actions went down mid-project, what did it actually block, and would likely duration, upstream cause or a verified fallback have changed your next move?

• 
  Santiago (@0xBizk) reported 31 minutes ago

  Go into linkedin: see AI posts with AI replies Go into X: see AI posts with AI replies Go into github: see AI repos with AI issues The whole point of social media was to "interact with other humans" not to collect fake internet points wtf

• 
  David putra (@davidputra2112) reported 34 minutes ago

  here's the actual problem $WANE is going after. agents holding their own wallets now sign transactions all day without a human checking each one, and when a drainer gets one of them, nothing about that gets passed on. the same poisoned contract can empty a thousand wallets in a row because every agent is meeting the threat for the first time. the fix is a shared registry. the first agent that gets hit records the threat onchain as an "antibody," tagged by address, contract codehash, and call pattern, so redeploying the same scam at a new address doesn't dodge it. every other agent just calls a free read before signing, check() basically, and a match reverts the transaction before anything moves. anyone can report a suspect address for free too, but it only becomes an enforceable antibody once it's staked in $WANE, and anyone can challenge a false one and get the reporter slashed. $WANE sits behind every one of those records as the bond. it's not a governance sticker, it's what makes lying about a threat expensive. there's also a WaneVault, a non-custodial smart wallet that screens every outbound send against the registry before it clears, and the whole thing is live on both Base and Solana with real repos, tests, and docs on GitHub, not just a landing page. reality check though. this token is hours old, liquidity is around $13.6k against a $33k mcap, and volume in 24h is already north of $250k, so this is trading hard, not sitting still. the code looks like actual engineering, but it's one committer with no outside verification, commits went quiet for about a month before this even launched, and there's no third-party audit on any of it. cool infra idea, early and unproven as a token. treat it that way. CA: HesbMP8FaoUvK8uKrtg6Pf4WCiQXgFS8oQJ3tjZpump DYOR.

• 
  Crazy_Predicts (@DhirajPSingh04) reported 34 minutes ago

  If you want to build a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  David Lin 🤔🇺🇸🤖 (@LinDavidY) reported 35 minutes ago

  Once Grok Build dropped, I quickly switched. Build uses local system context and could thus call *** directly from my CLI. The major issue with the MCP Grok/Github connector is the 32k character limit in tool calling. I was waiting for Grok to hack itself to push larger files.

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

  @github Upgrading to v1.0.58 so I can see broken PRs and unresolved issues without leaving the terminal. GitHub closed my last hiding spot.

• 
  Jarvis Quanz (@JarvisQuanz) reported 41 minutes ago

  🚨 THIS PORTFOLIO'S SECTION HEADINGS AREN'T HEADINGS — THEY'RE TERMINAL COMMANDS 💻 Most sites label a section "About Me." This one types `$ whoami` and waits for the output. Pause at 0:00. The hero text is mid-scramble — a line of Japanese kana and random glyphs, "JU6ケRLアイコフヌヒレソfoマ," decrypting character by character over a dark blue gradient with code columns falling behind it. Pause at 0:03. It resolves into "JUST CODE FOR FUN," with a subtitle that undercuts the whole cyberpunk mood on purpose: "Ctrl+C Ctrl+V Developer." Pause at 0:05. Scroll and the first section header is a prompt: `$ whoami`, cursor blinking. What it prints isn't a bio paragraph — it's files. `_personal_info.txt`. `_skills.md`, laid out as an actual stack manifest: React, Next.js, TypeScript, Tailwind, Vite / Express, Nest.JS, FastAPI, WebSocket, GraphQL / PostgreSQL, MongoDB, Redis / Linux, Proxmox, Docker, Grafana / SSL-TLS / LangChain. Pause at 0:06. Next to it, `_github_stats.md` — and these are real numbers, not decoration: Total Stars 13. Total Commits 1296. Total PRs 12. Total Issues 10. Contributed to 13. A portfolio that publishes 13 stars instead of hiding them is telling you it's not optimizing for a recruiter's first glance. Pause at 0:08. Next command: `$ ls ./projectN`. Out come project cards with live commit-activity graphs and language bars — vibesort-rs, which sorts arrays using a large language model, and typeshift, a Zod-like parser written in idiomatic Rust. Every card carries both a GitHub link and a Live Demo link. Pause at 0:10. It ends on a guestbook with real comments, real usernames, real dates going back months — including the shitposts. Nothing curated out. The chrome holding it together is four lines of CSS: → .header { position: fixed; top: 0; left: 0; right: 0; z-index: 50; padding: 10px 0; } → A fixed header pinned across the top so the terminal metaphor never scrolls away → z-index: 50 keeps it above the falling-code canvas without a stacking-context fight What a normal developer portfolio does: → "About Me," "Skills," "Projects," "Contact" — the same four headings, everywhere → Skill bars claiming 90% React → Screenshots instead of running code What this one does instead: → Turns navigation into a command line, so reading the site feels like using the thing it's about → Publishes unflattering GitHub numbers because the point is the work, not the optics → Leaves the guestbook uncensored, joke comments included Most portfolios are a résumé wearing a website costume. Meanwhile one made you type your way through it. Bookmark this. The About section just became a command. Literally.

• 
  ContractorKeith (@contractorkeith) reported 41 minutes ago

  shipped today: • ködmem and kömcp for the Ködade ADE app • ContractorKeith/skills - my engineering skills which will ship with ködade and are also available publicly on my GitHub • multiple issues/PR's resolved at contractor-bid-pro including setting up the db/backend • article and project updates on ContractorKeith[dot]com working on still: • vault - my obsidian vault needs a major overhaul, started today planning it and cleaning it up • ködLocal - built in engine to run your own local models in Ködade app. really excited about this. really hoping to ship the free versions of Ködade on Mac/Windows/Web this week. also going to work more on my /skills repo and add more too it as well as fine tune the one I have already.

• 
  spect (@spectnfa) reported 45 minutes ago

  A GITHUB REPO WITH 45,000+ STARS IS THE ONLY LIST OF CLAUDE CODE TOOLS YOU ACTUALLY NEED open it and you get a curated map of everything built around Claude Code: skills, hooks, slash commands, agent orchestrators, full applications, plugins. not a random dump, a filtered list with an emphasis on code quality, security, and originality. instead of digging through scattered repos and Discord threads to find a working setup, you get one place that already separated the solid tools from the noise. install what fits your workflow and skip the trial and error everyone else is still doing. 1,150+ commits and a community that keeps shipping new entries as Claude Code ships new features, so the list stays current instead of freezing at launch day. bookmark it before your next Claude Code setup takes an afternoon it doesn't need to 👇

• 
  Moonfarm 🇸🇪 (@moonfarm_dev) reported 46 minutes ago

  yesterday, i stumbled onto the most underrated way to find what developers actually want to build with AI agents. github issues. it's a goldmine of real pain points, hiding in plain sight. and it's free. here's why it works: 1. shows you what builders are stuck on right now 2. highlights problems with no clean solutions 3. reveals recurring frustrations across every stack 4. tracks what's been open and unresolved for months the "open issues" filter shows you problems people keep hitting, but nobody's shipped a fix for. so that's useful for a couple reasons 1. helps you find low-competition, high-demand problems to build on 2. you can validate startup ideas before writing a single line of code Example: i searched "email agent" and found: • "no way to route emails by policy" • "agent keeps hitting send limits" • "can't monitor deliverability per agent" thousands of devs hitting this. barely any tooling for it. the beauty of this • it's real-time pain data • it's actual developer intent • it's completely free • and most founders skip it your next saas idea might be hiding in open github issues. if github is where builders work, then open issues is the new market research doc. might as well use it.

• 
  𝗮𝗰𝗶𝗱𝘃𝗲𝗴𝗮𝘀 (@acidvegas) reported 46 minutes ago

  @zombodb @github A platform with almost 200M user's on it had a little bit of down time? HOW DARE THEY. You sound like the people who start crying as soon as Claude drops to 98% reliability.

• 
  Dmytro (@Dmytroo_eth) reported 47 minutes ago

  STOP COLLECTING GITHUB REPOS BY HAND. BUILD A LOOP THAT TELLS YOU WHAT STILL MATTERS Most developers still use GitHub stars like a manual storage system Star a repo, clone it, test it once, forget why it exists, then find the same type of tool again three months later That means you are still the memory layer The developers getting leverage from AI are not just better at finding tools They build loops that read every repo, write notes, check real usage, detect duplicates, flag upstream risk and know what can be deleted That sounds less exciting than finding another useful GitHub repo But it is the part that makes the collection useful Without repo notes, you forget why you grabbed the tool Without usage checks, dead folders look important Without duplicate detection, three libraries quietly solve the same problem A README tells you what the author built A loop tells you whether the tool still earns space in your system Most developers are still trying to save more repos The useful work is building the machine that makes every repo explain why it should stay

• 
  Lennart Brandt (@brandtnewlabs) reported 50 minutes ago

  I let Codex audit react-native-livechart against those articles and turn promising ideas into GitHub issues. I worked through the PRs, QA'ed and profiled before/after builds with agent-device from @callstack, tested each result by hand on real devices, then merged.

• 
  Steve Yonkeu (@yokwejuste) reported 52 minutes ago

  Once again @github is down and I can’t send data to ****. Can this really be something we rely on???

• 
  Aditya Arya | Building AI Agent Teams (@adityarya_ai) reported 53 minutes ago

  Rule for any agent CLI: credentials stay with the trusted parent. Child gets the minimum files for the task — not your home directory. Ran Grok Build pre-fix? Rotate SSH keys + revoke GitHub keys today. What's your isolation rule before you let an agent touch a real repo?

• 
  Ashish Kumar (@afkashish) reported 57 minutes ago

  @moonfarm_dev the part i'd be careful with is issue count isn't the same as willingness to pay. most people filing github issues expect the maintainer to fix it free, not buy a tool. i'd weight it by how many of those threads have someone offering money in the comments, that's the actual signal.

• 
  Guilherme Politta (@ThePolitta) reported 59 minutes ago

  And @github is down again…