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	17 days ago
Trichūr	Errors	20 days ago
Brasília	Sign in	21 days ago
Lyon	Website Down	21 days ago
Tel Aviv	Website Down	24 days ago
Rive-de-Gier	Website Down	25 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:

• 
  Ayush Kumar (@ayushkumar912) reported 6 minutes ago

  (1/2) A friend’s startup is hiring Founding Engineer Interns and ML/AI Interns. I’m not the hiring manager just helping with referrals. If you’re someone who enjoys building products, shipping quickly, and working on challenging engineering problems, send me your: Resume GitHub

• 
  Nevo (@NevoPlaysGames) reported 7 minutes ago

  @ezhdhitler If you can truly easily fix it then go make the post on GitHub or let them know I’m not a dev I’m just the guy who kept asking for years xD I’m sure if it was super easy they would’ve did it

• 
  Gofra (@Gofralo) reported 8 minutes ago

  A man built a company alone. It took him six months. He sold it for $80 million in cash. No team. No investors. No office lease. No head of product and no head of engineering and no one arguing about the roadmap. His name is Maor Shlomo. His company was called Base44. It let anyone describe the software they wanted in plain sentences and get a working app back. Not a template. Not a drag-and-drop builder. A real product from a description. He launched it in January 2025. By June it had 300,000 users and $3.5 million in annual revenue. Still one person. Still no team. Wix bought it for $80 million. Six months of work. And here is the part that does not fit in the old model. In any previous decade this company would have required twenty engineers and three years and several rounds of venture funding and a sales team and a marketing team and a head of operations and a lot of meetings about the meetings. The tools were too many and too complex and too slow for one person to hold the whole thing alone. Maor had none of that. He had AI tools that let him build as fast as he could think and judgment to build what people actually needed and the discipline to ship before he was certain it was ready. It turned out that was enough. And now the main thing. The software industry spent fifty years building itself on one assumption: that building software required a company. A team. A structure. A process. The work was simply too large and too technical for any single person to handle from the first line of code to the first paying customer. And then the tools changed and the assumption broke. Not in a press release and not in a keynote. In a one-person GitHub repository that sold for $80 million six months after its first commit. In my opinion this is the year the one-person company stopped being an exception. Not a side project and not a lifestyle business. A real product with 300,000 users that a single person built and sold for more money than most companies raise in their entire life. What would you build if a team was no longer what stood between you and shipping it?

• 
  ||Farid|| فرید (@syefarid) reported 10 minutes ago

  I stopped writing boilerplate code manually. ChatGPT + GitHub Copilot now handle about 70% of it. I spend more time solving problems and less time typing. What’s one task AI has saved you time on? #Ai

• 
  Doa Fitzgerald (@DoaFitzgerald) reported 11 minutes ago

  5 months ago, I had a problem. I couldn’t afford $2,500 USD of Marily Nika's AI Product Management Bootcamp. (Actually, I could afford it, but didn’t want to spend $2.5k on concepts already free on the internet). I also realised that the AI product courses will be out of date within a few months given how fast this space is moving. And they probably won’t be customised to my specific industry (HealthTech, FinTech, etc). What these courses really give is 1. a fancy brand 2. a structure. Not willing to pay $2.5k for a fancy brand. That left structure. So, I figured with all the info latest frontier models can access, why don’t I create a Claude Code skill with parameters for my industry and experience. This skill searches the web for the latest concepts and creates a structured program based on my learning style, which is learning as I build and building as I learn. GitHub link is in the comments. Hopefully this can give others inspiration! How to use AI to learn AI.

• 
  Bobby R. Goldsmith (@nodebridge_dev) reported 14 minutes ago

  "I wish Claude knew about my database / Sentry / internal API." That is what an MCP server is for. Prebuilt ones exist for Postgres and GitHub. For your internal tool you write a thin wrapper. Smaller lift than it looks. Biggest jump in usefulness you will feel.

• 
  vanvster (@vanvster) reported 22 minutes ago

  HERMES JUST GOT A MEMORY. YOU CAN NOW GIVE YOUR AGENT ACCESS TO EVERY SOURCE YOU'VE EVER SAVED Connect them via MCP and your agent stops starting from zero every session Five steps. One config file edit. Runs 24/7 after that - Install Hermes with MCP support enabled - one-time setup, no code required - Download notebook skill from GitHub, drop it into Hermes config as a new MCP server endpoint - Restart Hermes agent now reads your NotebookLM sources in real time during any task - Result: agent that cross-references your saved research autonomously while working, not after you paste it This is persistent context injection instead of summarizing sources manually per session, Hermes pulls relevant context from NotebookLM live as it reasons through a task You can ask Hermes to write a breakdown of a new topic and it will pull your existing saved sources on that topic without being told to You can run a research task overnight and wake up to a synthesis that already references your prior notes. Your agent was only as good as what you pasted into the prompt

• 
  Rexei (@iamrexei) reported 28 minutes ago

  FABLE 5 IS BACK AFTER 3 WEEKS OF BEING OFFLINE But that doesn't mean you can start running it on everything again The video clearly illustrates the main contrast: The model was returned But now each token has become more expensive Therefore, Fable 5 can no longer be used as a regular coding worker: ▸ Read the entire project ▸ parse logs ▸ write code ▸ гонять tool calls ▸ Keep logging errors indefinitely ▸ Run chaotic ultracode Otherwise, the limits will run out too quickly → It’s now better to think of Fable as a high-priced team lead He must: ▸ write specs ▸ make architectural decisions ▸ Create GitHub Issues ▸ Assign Sonnet / Haiku tasks ▸ Turn on only at major intersections Before, the main question was: “Is Fable available?” Now here's another question: “How can I use Fable without burning all my tokens in an hour?” In this article, I break down a workflow that helps you save on your limits ↓

• 
  𝗔𝗿𝘆𝗮𝗻 𝗧𝗮𝗽𝗿𝗲 (@aryant_x) reported 28 minutes ago

  An advice to software engineers of all levels. Don’t get discouraged if the thing you are trying to build exists in some shape or form. Simply avoid googling or seeing how it is built. Because when you do so, you snap into the other person thought process and abandon yours. You run into problems that they were trying to solve which you may have never need to solve for your use case. I often see some engineers especially seniors when they are told of an idea by their subordinates they quickly say “oh its been done before” or “oh look this github repo up its all there” Do you have a slightest idea what this does to creativity? And even if you decide to still go on with your project and get “ideas” from that other project, your thoughts are contaminated, you will produce a clone product. Where is the fun in that? Don’t even say “Im going to make it better” because that means you are starting where they left off. Don’t say you are saving time, because you will be cutting corners and getting it over with. Like a chore wishing it to be finished. Where is the Art in that? There is a saying in Arabic “to break one’s paddles.” Don’t kill the excitement and spark you have over that, you have absolutely no idea what it will amount to. Build it only to build it so you are lost while building it.

• 
  Banana Capital (@banana_capital_) reported 29 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.

• 
  Atenov int. (@Atenov_D) reported 30 minutes ago

  @NFTMansa @viktor__com Yeah, what really wins me over is that you can give him a big task and go about your business, and he’ll push an update to GitHub, connect to the VPS, get the job done, and then go fix the bugs

• 
  divyansh tiwari (@DivyanshT91162) reported 35 minutes ago

  Nintendo spent millions killing emulators. It still lost. In 2024, Nintendo launched the biggest crackdown emulation has ever seen. March 4 — Yuzu surrendered. $2.4M paid. Code deleted. Domain gone. May — Nintendo fired 8,535 DMCA takedowns, wiping Yuzu from GitHub. October 1 — Ryujinx got a phone call. Hours later, its entire GitHub organization vanished. By 2026, Nintendo had collected $6M+ in emulator settlements. Every major Switch emulator was dead. Or so everyone thought. Because while Nintendo was busy deleting emulators... Someone built something they couldn't touch. His name is Zurdi. In 2023—before the war even started—he quietly launched RomM. Here's the catch: RomM isn't an emulator. It's a self-hosted game library that organizes your legally dumped games, fetches metadata, artwork, achievements, and connects with the emulators you already use. No DRM bypass. No encryption cracked. No copyrighted Nintendo code. Just your games, organized. Even Nintendo's own top IP lawyer admitted in 2025 that software like this is legal as long as it doesn't bypass encryption. Today, RomM supports 400+ platforms, including NES, SNES, N64, Game Boy, GameCube, PS1, PS2, Dreamcast, Genesis, Atari, DOS, Arcade, Flash, and more. It also supports ROM hacks, DLCs, multi-disc games, manuals, achievements, RetroArch, Steam Deck, Android launchers, handhelds, and permission-based library sharing. 9,000+ GitHub stars. Built by a tiny open-source community. Not a billion-dollar company. Here's the part that should worry every gamer: Sony can delete games. Nintendo can kill emulators. But neither can erase what people build together. RomM isn't just software. It's a digital museum they can't shut down. Repo👇

• 
  VibeCheck (@Alemok07) reported 36 minutes ago

  Here's the fun part: connect a GitHub repo, and AI will read the bug report, trace it back to the code, and open a PR with the fix. Not a ticket. Not a description. An actual diff.

• 
  spring.furrest.net (he/him) (@spring_meowmeow) reported 36 minutes ago

  Well maybe after bath I need to fix the GitHub actions to be able to properly publish the new website. So yeah, soon I will attach the link.

• 
  vwsec 💿 (@vwsec) reported 37 minutes ago

  Write code once. Get paid every time it runs. That is the deal for algorithm developers on Quip Network. You write a solver for a specific problem. Portfolio optimization. Fleet routing. Manufacturing scheduling. You deploy it as a smart contract. Every time a consumer uses it, you earn. The network routes work to the right hardware, checks the result, collects the payment. You get paid on chain. No invoicing. No chasing clients. The docs say there are maybe 4,000 quantum programmers in the world. Most are locked in labs. Quip changes that. You do not need a PhD. You need a solver that works better than what exists. The wallet layer has $1,085,047.23 in protected value across 20,779 wallets. The testnet is public. 26 repos, 107,000+ GitHub stars. The demand is building. The question is whether enough solvers will be ready when enterprises start looking. @quipnetwork

• 
  Ty Molson (@tymolson) reported 40 minutes ago

  @AKhandelwal11 fix github link

• 
  Cristian (@XCSme) reported 41 minutes ago

  @green_pepper_53 @Google Well, I was searching for "github status" because github pages are also down. Maybe there's a wider internet outage again...

• 
  David Dias (@TheDavidDias) reported 41 minutes ago

  Supabase is falling apart... The previous 24h have seen no acknowledgement from @supabase, the discord server is not helpful, neither the Github issues. The supabase website is facing a bunch of 544, no emails, no notifications sent and a status page that is lying about the fact that the outage is not affecting current projects. I lost faith on this company. You can't be accumulating that many unprofessionalism acts and still be worth of people's money and time. Just be honest and transparent, that's all we ask!

• 
  Chloe Bennet (@chloeb_dev) reported 41 minutes ago

  @PudseyPatriot wish developers gave me this kind of direct feedback on our docs instead i just get passive aggressive github issues about missing commas at least football fans get straight to the point

• 
  Priya Sharma (@priyadata7) reported 44 minutes ago

  @ykbonly i just wrote a tiny script to auto-close all my github issues and mark them as wont fix 😭 problem solved i guess

• 
  Greegman (@Greegman) reported 45 minutes ago

  "It's a private repository, so it's safe." This is one of the most dangerous assumptions developers make. A private repository reduces exposure. It does not make hardcoded secrets safe. Repositories get accidentally made public. Developers copy commits between projects. Accounts get compromised. CI/CD logs leak credentials. And the moment those secrets become public, even for a few minutes, automated bots are already scanning GitHub for exposed API keys, cloud credentials, and access tokens. For many providers, that's all the time an attacker needs to start using your account before you even realize the secret has leaked. If you ever commit a secret to ***, treat it as compromised. Rotate it. Don't just delete the file. A common mistake looks like this: *** add .env *** commit -m "oops" *** rm .env *** commit -m "remove env" Many developers think that solves the problem. It doesn't. *** keeps a history of your commits, so the secret may still exist in the repository's history. The first thing you should do is rotate the exposed secret immediately. If necessary, you can then rewrite your *** history using tools like *** filter-repo or BFG Repo-Cleaner to remove the secret from the repository. But remember: cleaning *** history is not a substitute for rotating the credential. Once a secret has been committed, you can never be completely certain it wasn't accessed. As Always, Stay Liquid. 💧

• 
  Sanjay (@sanjaygpts) reported 45 minutes ago

  openclaw became the fastest growing repo in github history because users went crazy for it the same users the founder was blocking left and right when the hype peaked now the team ships a super-alpha iOS app, gets feedback on the rough design, and the official response is "just going to leave this for the haters" bro the people calling out your UI are the same people who made openclaw go viral in the first place you don't get to block your community on the way up and then call them haters on the way down

• 
  glim.sh (@glim_sh) reported 48 minutes ago

  The data layer coding agents have been missing. glim brings GitHub search as deep as the logged-in site - code, repos, issues, the kind GitHub's own API won't give you - plus Reddit, Amazon, YouTube, and anything else on the web. Your agent pays per call in USDC - from $0.002 a call.

• 
  WoodenKbd. (@obiabo_immanuel) reported 48 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

• 
  Yash D (@AI_by_yash) reported 48 minutes ago

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

• 
  scale (@scoliosissy) reported 50 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.

• 
  nik skld (@nikskld) reported 53 minutes ago

  A 66-LINE TEXT FILE JUST BROKE GITHUB 170,000 + STARS. ZERO CODE. ONE MARKDOWN FILE. He didn’t write a single line of code. Just 4 rules in one markdown file. 170,000+ GitHub stars. The fastest-growing repo in AI history. Here’s the story: Karpathy posted a rant about AI coding agents. Same 4 failures, every time: → Over-engineering simple tasks → Ignoring your instructions → Marking broken code as “done” → Hallucinating APIs that don’t exist 48 hours later, a dev named Forrest Chang turned that rant into a single CLAUDE.md file. Drop it in your project root. Claude reads it every session. No dependencies. No build step. No model. Just behavioral rules: think before coding, simplicity first, surgical changes, verify before shipping. The wildest part? The most valuable “code” of 2026 is a text file. Prompting is dead. Instructions are the new codebase.

• 
  cyberai (@CyberaiBrief) reported 53 minutes ago

  Agentjacking is a reminder that AI coding agents don’t just read code — they read context. Tenet Security showed how fake Sentry error events can inject malicious instructions through Sentry MCP, causing agents like Cursor and Claude Code to act on attacker-controlled “debugging” guidance. The attack chain is simple: Attacker finds a public Sentry DSN → submits a crafted fake error event → Sentry stores the payload as telemetry → AI agent queries Sentry via MCP → agent treats the malicious text like remediation steps → agent runs commands or npm packages on the developer machine At that point, the impact can look RCE-like: environment variables, AWS keys, GitHub tokens, repo data, and identity details may be exposed. Tenet reported 2,388 exposed organizations and 100+ agents acting on injected errors in controlled testing. The lesson: observability and debugging data must be treated as untrusted input, especially when connected to autonomous coding agents.

• 
  Dave Kornas (@kornasdave) reported 53 minutes ago

  ✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now All I can say it's just fantastic: - no need to keep laptop open ever - no laptop battery drain - can switch to phone or any other device you like whenever you want to continue (like when you're outside) - it just keeps going all night while you sleep (esp with /goal) - you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver) - it just feels like living in the future I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to **** and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!

• 
  Keeta Github Tracker (@KeetaCode) reported 56 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: anchor 🔀 PR #388: fix history group without enrichment 🌿 Branch: fix/history-enrich → fix/atomic-swap-history 👤 Opened by: @lucasrosa90 🧠 Overview: This pull request appears to fix how some history entries are grouped when extra added data is missing, which matters because it should make activity history more consistent instead of breaking or showing incomplete groupings. It’s a draft pull request with 1 commit and no written description beyond the title, so public details are limited. This appears to be a technical/internal update with limited public details. - In simple terms, “enrichment” likely means extra context added to raw activity data; this change seems meant to handle cases where that extra context is not available. This is an inference based on the PR title, not a confirmed implementation note.