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 (69%)
• Sign in (17%)
• 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	21 hours ago
Trichūr	Errors	4 days ago
Brasília	Sign in	5 days ago
Lyon	Website Down	5 days ago
Tel Aviv	Website Down	8 days ago
Rive-de-Gier	Website Down	8 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:

• 
  Amaan (@BilwarAmaan) reported 5 minutes ago

  @uwukko @dehazzle @heliumbrowser not sure how to get the crash logs but i sure will file a github issue about this, thanks :)

• 
  Axiro (@Axirohq_) reported 8 minutes ago

  The US government just forced Claude Fable 5 offline. Three days after launch. A jailbreak was found. The system prompt leaked on GitHub. Commerce Department sent an export control directive at 5:21pm Friday. Anthropic shut it down for everyone worldwide. First time ever a government has killed a frontier AI model. While their IPO is in progress.

• 
  Jeremy Nguyen ✍🏼 🚢 (@JeremyNguyenPhD) reported 11 minutes ago

  @ErenChenAI GitHub link seems to be down

• 
  Gill (@gurtej__gill_) reported 11 minutes ago

  The biggest AI skill shift in 2026 isn’t prompt engineering. It’s LOOP ENGINEERING. Most people still work like this: → Prompt AI → Get output → Review manually → Fix mistakes → Prompt again The human is still doing the hard part: the feedback loop. Loop engineers think differently. Instead of writing better prompts, they design systems that: -Discover what needs to be done -Plan the work -Execute tasks -Verify results -Fix failures -Repeat until the goal is achieved A good loop has 6 building blocks: 1-Automations (triggers) 2-Worktrees (parallel workspaces) 3-Skills (reusable knowledge) 4-Connectors (GitHub, Slack, Jira, etc.) 5-Subagents (makers + checkers) Memory (what happened before) The future isn’t: “Write me a function.” It’s: “Write it, test it, fix it until it passes, then summarize the changes.” Prompt engineers optimize outputs. Loop engineers optimize outcomes. A reliable loop beats a perfect prompt every time.

• 
  top10.dev (@Top10_Dev) reported 16 minutes ago

  GitHub Trending today: openclaw (283.1k★, 'personal AI assistant, the lobster way 🦞') sits above @reactjs (243.9k) and torvalds/linux (221.6k). The kernel that runs every cloud server openclaw queries from has fewer stars than openclaw. GitHub stars stopped being a quality signal years ago. This is just the cleanest example yet — an AI wrapper repo passing the operating system it runs on. Use weekly npm/PyPI downloads instead. They reflect usage, not bookmarking. #opensource #github

• 
  Trantor (@Trantor__) reported 18 minutes ago

  @VittoStack @WolfEatSheep69 They'll make github take down capable models...

• 
  xavier (jack) (@KMkota0) reported 19 minutes ago

  @MaximeHeckel eventually, everything good will be copied. i guess the difference now is that, with ai, the cost of copying is almost zero. the more i think about it, the more i believe the solution has to involve the platforms. reddit and github in my case. there will always be bad actors using new technology. the real problem is when those bad actors get distribution. platforms need to reconsider their policies around this new reality.

• 
  Ibrahim B. Oduola (@diboworks) reported 19 minutes ago

  Is GitHub down?

• 
  shmidt (@shmidtqq) reported 20 minutes ago

  Solo dev, OpenClaw creator: Peter Steinberger. "My hands are too precious to type code." He doesn't write. He dictates. Sat down, spoke it out, and in one hour a prototype was born. It became the fastest-growing repository in GitHub history. 180,000 stars in days. For 13 years he typed PSPDF Kit by hand. A billion devices. Now he won't touch a keyboard. While you argue that's not real coding, he already shipped. Lazy, or the new normal?

• 
  Lucky Lawrence 💌 (@imluckylawrence) reported 22 minutes ago

  It should be noted that it is not one isolated server, but perhaps a network of discord servers, github repos and google sheets of data hosted publicly at this time.

• 
  Aleksey Shipilëv (@shipilev) reported 22 minutes ago

  At some point, a reasonable strategy to fix GitHub performance issues would be to get a contractor job there, find ten bottlenecks (as one does), fix them, get paid and ****.

• 
  primitive.host (@PrimitiveHost) reported 25 minutes ago

  Is anyone else getting insanely slow page loads on @github today or is it just us?

• 
  Yu Sun (@ysun1993) reported 30 minutes ago

  @luccahuguet Yep, I have to spend over 100 hours yearly for GFW problems. Even GitHub and DockerHub are behind the GFW, what the hell🥲

• 
  Anshuman Goswami (@Anshuman0769) reported 31 minutes ago

  @DanielSmidstrup When a pipeline fails at 3 AM, instead of a data engineer spending hours figuring out what broke, Ordo investigates the failure and sends the error, root cause, and likely fix to Slack in under 60 seconds. Now supports github connections helping to show who committed the last so error happened.. Many features to come yet..

• 
  Chris Schuchardt (@c_schuchardt) reported 31 minutes ago

  @erikzhang @kurubatermit @ngd_neo You’re the only one (besides superboyiii or Owen) with the actual permissions to remove someone from the core dev team in the GitHub repo. I was removed after my transparent 4-month school break — which I notified the entire team about in advance, with a planned return in ~90 days. This isn’t about money. It’s about getting $NEO to a proper coding and application standards. Here is the message from Discord `Neo Core Developers` server.

• 
  Diogo Neves 👨‍💻 / ☕️ (@DiogoSnows) reported 31 minutes ago

  hey @OpenAI @gdb this is unacceptable! I setup Codex code reviews through my personal account, but because I use the same github account at work, it's using my works Codex to review my personal (and private!) repos! How can I fix this?

• 
  Karan Bhilhatiya (@karanbhilhatiya) reported 34 minutes ago

  after months of building, posting, and shipping i've concluded that my github visibility is still terrible. time to beg for stars. shamelessly.

• 
  RintaroOkabe (@RintaroOkabe03) reported 34 minutes ago

  Same for me. I have went over to do planning docs with GPT 5.5 Pro using the web version with the github connector. So I can spec out very good task documents. But 4.8 still can't execute them without holding its hand phase by phase. What is crazy for me is communication barrier. My goal is to create a visualisation for my dashboard that expresses states like an animated infographic with state transitions. Took me several attempts to just get that point accross. So I asked it first to break down the process looking at the code and skill and suddenly it had no issues. Got that state machine correct. I let it than make mermaids of individual transitions and then let it make an integrated version where it shows step by step a build up sequence and then a tear down sequence. So it should get the temporal sequence now and how these things are connected. But of course it fails than to tranlate it into an animated visual. And it gets stuck on the tiniest things and gets them wrong. And I thought Opus is great for design. But it seems only decent for copy-pasta web pages. With Fable it felt that it not only understands the task. It was often even 2 steps ahead of me in thinking. I think of something only to read a few lines down the line that it already took care of that. I don't get that on Opus or GPT 5.5

• 
  Jaden Tripp (@jadenitripp) reported 40 minutes ago

  @MatthewBerman I can't wait for Cursor to build a GitHub competitor and fix this

• 
  Toñin (@Tonin_eth) reported 43 minutes ago

  🪦 AUTOPSY REPORT #50 A cozy fishing RPG on Ronin. Inspired by Stardew Valley, Dave the Diver, and Runescape. Cast your line, reel in fish, compete on leaderboards, trade in a player-driven economy. Browser-based. Mobile-friendly. Easy onboarding. Not just any Ronin game. THE Ronin game. The first permissionless title to receive an official partnership with Sky Mavis after they opened the chain. The showcase. The proof that Ronin could support third-party studios, not just Axie Infinity. Sky Mavis gave them everything: publishing support, marketing resources, technical infrastructure, promotion across all Ronin channels, and strategic collaboration. The full package. The kind of support most web3 games would kill for. And the numbers were real. 9 million installs. 50,000 peak daily active users. 25,000 sustained DAU. $1 million in revenue. $600,000 in NFT trading volume across four collections. $130,000 in in-app purchases. 240,000 on-chain transactions in two weeks. 888-piece Founders NFT Collection launched via Mavis Launchpad. This wasn't a ghost project. This wasn't a whitepaper with a Discord. This was a GAME. People PLAYED it. People SPENT money. The floor price of the Founders Pass sat 3.5x above mint. 60%+ unique holders. Real distribution. Real conviction. And it still wasn't enough. "We were ultimately unable to prove our thesis on crypto gaming and could not find product-market-business fit." Read that sentence carefully. This isn't a team that failed to build. They built. This isn't a team that failed to attract players. 9 million installs. This isn't a team that failed to generate revenue. $1 million. They could not prove the THESIS. The fundamental idea that crypto gaming works as a business. 9 million people installed the game. The economics still didn't close. Servers shut down June 25. The token: spend-only, untradable. USDC from the liquidity pool redistributed to the community by Karma score. Refunds for spending since Chapter 3 launch. Proof of Distribution rewards handled by Sky Mavis directly. Karma scores open sourced on GitHub. Clean exit. Real refunds. Open-sourced what they could. No ghost. No pivot. No blame. This was not a $5 million indie project that ran out of runway. This was not a studio with no players. This was not a game that nobody liked. This was Ronin's NUMBER ONE partner game. With Sky Mavis in the corner. With real traction. With real revenue. With real players. And the team looked at all of that and said: we still can't make the math work. If the flagship game of the chain that INVENTED crypto gaming can't find product-market fit with 9 million installs and Sky Mavis support, what does that tell you about the thesis? Autopsy report number 50. And this one asks the hardest question of the entire series. Which game is this?

• 
  Rexan Wong (@rexan_wong) reported 45 minutes ago

  been building AI software for brands + talking to hundreds of AI operators for months whoever is building in AI now, these skills will compound like crazy in the future here's 10 signs your company isn't actually AI native (just AI curious) - so you can fix it before the ai gold rush leaves you behind: 1. y'all got no skills library every prompt gets retyped from scratch and the second your best operator takes pto, and the tribal knowledge walks out with them lol you might think this is basic by now, but ive seen full AI-native ops running without one. THE FIX: write the prompts once, version them, let the whole team pull from the same library. 2. our agents have no context they start every task with brain damage. no clue what the company does, what's already been decided, what "good" even looks like here. then u wonder why the output is mid. THE FIX: build a brain. markdown files in folders, agent-readable. start with SOPs, past wins, brand voice, customer transcripts. add as u go. Can do deeper research into Obsidian or Supermemory as memory / context solutions 3. you're in claude code clicking approve every 30 seconds thats not autonomy, thats a hostage situation with a chatbot. just let it run in auto mode bro human in the loop matters, but AI is good enough now that u gotta let it cook. the actual skill is developing the instinct to know when a change is critical, so u jump in for that and stay out of the rest. 4. nothing fires on a trigger. work only happens when someone notices a slack ping or an email and types a prompt. your speed-to-signal is capped at whatever ur worst meeting day allows. THE FIX: easy: MCPs. wire your agents into gmail, slack, notion, your crm. let the trigger come from the system, not from u remembering. 5. ur SOPs arent versioned they live in a notion doc nobody opens, or worse, in one person's head. cant diff it, cant improve it, cant hand it to an agent. THE FIX: move them to markdown, put them in github, treat them like code. every change is a commit, every commit has a reason. 6. no eval loop you cant tell me if todays output is better than last tuesdays, which means u also cant compound saw on a pod that has a great solution, he has a "standard" benchmark, a tangible result he runs every new model and setup against thats how u know whats actually best for ur use case instead of vibes-checking it. 7. u throw away the traces. every session ends and the reasoning, the dead ends, the half-built decisions just vanish, ur company forgets everything by friday. THE FIX: save the sessions, save the artifacts, even the broken ones. the cutting room floor is where the next SOP comes from. 8. ur team is still doing the middle strategy and review is where humans win, execution is where agents eat if your people are still stuck in the middle of the sandwich,your margins could be gone in 12 months. 9. testing a new feature still means a figma file and a 2-week sprint the AI native version of ur team shipped a clickable prototype, ran it past 20 real users, and had the feedback synthesized before u finished writing the PRD. Take this list as you wish and lets scale with ai worddd

• 
  vivek (@itsreallyvivek) reported 46 minutes ago

  @tenobrus ig you dont have a job or genuinely dont do anything thats why you are keeping an eye on me each and every nanosecond and hoping i write or do something wrong. i cant see your single contribution on your feed just random bs atleast i actually made something for the public a knowledge base where they can navigate and learn things. its live on github you can check it tho and might be a good way to spend your time instead of just pulling me down

• 
  𝖉𝖊𝖒𝖎 (@demi_hl) reported 48 minutes ago

  everyone asking how. here's the actual build. rate limits: four oauth logins 3 claude max accounts + codex pro, four independent rate pools. a worker hits a 429 and auto-rotates to the next account, overflowing to codex when all three are capped. credential swap mid-task, no re-login, no dropped work, no gap. you stop hitting the wall because there are four walls and you're never against more than one. night shift: i label github issues during the day. a cron drains the queue serial overnight. branch → bounded goal-loop resolves it → lint+typecheck+build gate → PR. serial so it never thrashes the box, bounded so it can't spin forever, gated so nothing opens a PR that doesn't compile. branch-only, never main, never deploy. i wake up to clean PRs and merge what's good. it codes while i sleep. the fleet: opus on the brain rig handles all reasoning and orchestration. the mac does hardware render, videotoolbox encode, nothing else. a cheap sonnet box eats bulk grunt work and runs a local model for the free tier. the vps runs what has to survive a sleeping laptop, the live bot never blinks. all wired over a tailscale mesh. per-device execution, one shared cognition. memory: obsidian vault + a local semantic index = one source of truth every agent retrieves from by meaning, not filename. persistent memory and skills carry across sessions, corrections stick, procedures compound. no agent starts cold or relearns what another already solved. foundation: the whole thing runs on pop!_os. linux means the stack is native, systemd cron, ssh mesh, headless browser, the overnight loop, no wsl layer to crash mid-job. nvidia drivers out of the box so the local gpu just works. nothing reboots your 3am run, nothing meters the metal. you own the box. none of these pieces is exotic alone. the leverage is the wiring, each layer covers another's failure mode. rotation means the cap can't stop you. night shift means progress while you sleep. the fleet means each machine does only what it's best at. shared memory means nothing starts from zero. and linux means it all runs native, no layer in the way. that's the stack. ask below.

• 
  Vyron Vasileiadis (@fedonman) reported 49 minutes ago

  @charliermarsh @OpenAI @github You could start by not closing down pyx.

• 
  Faisal Karim (@Le__FaiCee) reported 51 minutes ago

  - Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier)

• 
  Joyce Marius R. (@r_joycemarius) reported 51 minutes ago

  @Yharnam_dev @ryaneddisford Error 404! The github repo was nuked by those mfs at Sony for sure and @ryaneddisford X account was suspended

• 
  sankit (@sankitdev) reported 52 minutes ago

  *** is a distributed version control system. As, I read this line a question came wtf distributed means here. Distributed means there is no central server here. Me and my friend both will have same whole copy. But, there is no server and without Github can I even share code??? Thats where i ran ssh server on my pc and moved to my friend pc, sshed into my pc and "*** clone" a repo of mine. Just to demonstrate how powerful *** alone is. Github is just a place to host *** repositories. *** itself doesn't need it. My respect for linus torvald is increasing day by day.

• 
  tayyeeb_🐋 (@IdrisTayeeb) reported 52 minutes ago

  The Fable 5 story just got wilder. The jailbreak that got it suspended by the US government? The full technical details are now published on GitHub. 120,000 character system prompt. Publicly available. AI safety just became everyone’s problem.

• 
  Abhay Ganti (@silvermango9927) reported 54 minutes ago

  I’m testing a CLI that optimizes the generated server. GitHub-ish issue response: Before: ~7.8KB After: ~1.3KB Slack user response: Before: ~2.5KB After: ~417B The goal is not compression for its own sake. It’s making the agent see only the fields it needs.

• 
  Benjamin Gagnon (@benfromqc) reported 57 minutes ago

  @Weird_Canadian @hollyanndoan @PrivacyPrivee You make way too many assumptions (which is also AI's problem). Github copilot is tuned to use the best possible model but I've tried at least 10. The best model is always very bad. I code almost everyday and run into AI issues every single day. It's completely useless for inline suggestions because it's wrong so often. I'm done arguing with you. It's not a time saver right now and Vibe Coders will get **** code and unmaintainable projects because AI cannot think. It doesn't actually sound like you are a programmer to me. A script kiddie perhaps. What tools do you use which make AI worthwhile and how? The only areas it save me time on are documentation. It'***** or miss for everything else, usually miss.