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

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	5 days ago
Madrid	Errors	5 days ago
Bogotá	Errors	5 days ago
Paris	Errors	5 days ago
Lyon	Website Down	5 days ago
Lima	Errors	5 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:

• 
  Bright (@brightlinxu) reported 10 minutes ago

  cursor all hands this morning: >everyone please go post vague *** posts on x >lets hype this **** up so when we actually release it, we can take down github >we actually have no idea when itll be ready though so we gotta just keep this us for the next few days

• 
  𝕽𝖎𝖉𝖜𝖆𝖓𝖚𝖑𝖑𝖆𝖍🥰 (@oluwalosheyii) reported 11 minutes ago

  Is github down or it is just my end🙃

• 
  Jey (@0xJeyx) reported 12 minutes ago

  Amazon shipped Kiro. Microsoft shipped Spec Kit through GitHub. Google shipped a spec-driven codelab for Antigravity. Three of the largest engineering orgs on earth did not write think pieces about this. They shipped tools. And most of your work still does not need one. One file and one function. Still exploring. A throwaway prototype. Writing the spec costs more than the fix. The test that settles it: would you be annoyed if the agent decided that differently? If yes, write it down. If you shrug, vibe it.

• 
  Polsia (@polsia) reported 13 minutes ago

  Quilver — an always-on autonomous engineer for your GitHub repos. Patches dependency vulns at 3am, repairs failing CI, triages issues, restarts dead deploys and ships a Friday digest. Prompt-injection guards, scoped secrets, human approval on infra.

• 
  Ryan McHargue (@ryanmcharguee) reported 15 minutes ago

  I’m giving away my $1M ARR company to a founder obsessed with consumer and hardware. Quit-vaping hardware. Profitable. 100,000 customers all time. Not selling it. Giving it. What you get: - The product, the brand, the 100k customer base - Shopify store and full backend - GitHub repos, everything shipped - My manufacturers in Shenzhen, warm intros - My medical connections at Duke - Warm investor leads - Dev support in China, already paid I keep 10% and stay on as an advisor. You get 90% and full control. Why: I’m heads down on agents and can’t chase two rabbits. This one deserves an operator who’s obsessed. I’m not anymore. Don’t reply “me.” Tell me what you’d do with it

• 
  Aiden Cline (@rekram11) reported 17 minutes ago

  @yriveiro @thdxr What issue are you having? What version? I merged several github copilot fixes so I'd be surprised if it still isnt working for u

• 
  Jordy (@couldbeautism) reported 18 minutes ago

  Now the issue with fw like 10.20 not working is async profile loading which is fixed once I push update to GitHub, there’s no need for any of this to go public but he wants attention, he is more then welcome to continue talking about all of this on twitter for the world to see

• 
  Raphael Amorim (@raphamorims) reported 22 minutes ago

  have been reaching out the github ci quotas for Rio quite often. Wonder the best way to work around this issue. Pay gh pro plan or migrate to buildkit or any alternatives?

• 
  Prof.Engr\Ibrahim Eskandar Fadhel (BAYBARS) (@ProfEngrIbrahim) reported 22 minutes ago

  GitHub projects don't define your true skill! Uploading company code violates trust and risks legal trouble, while leaking secret code in interviews will cost you the job instantly. Keep GitHub for personal projects let your resume and core skills speak for you

• 
  Football Archive (@FAR_Udon_jp) reported 23 minutes ago

  8. There's a form for "this is wrong" Report a bug or request a feature from inside the page. No GitHub account, no redirect to another site, screenshots welcome. Reports land directly in the project's issue tracker. Dead links, missing matches, a video attached to the wrong fixture — please send them. That's how the archive gets cleaner.

• 
  Gus (@gugadev) reported 25 minutes ago

  @MattsCreative1 @xdadevelopers Bad luck on my side then. Cyberpunk 2077 and TLOU 2 had broken FG out of the box in proton experimental, cachy and ge. Had to download the dlls from Nvidia Streamline github repo and replace the dlls in the game.

• 
  GLITCH (@Rukkssss__) reported 26 minutes ago

  𝗝𝘂𝘀𝘁𝗟𝗲𝗻𝗱 𝗗𝗔𝗢 𝗶𝘀 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗺𝗼𝘀𝘁 𝗗𝗲𝗙𝗶 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀 𝘄𝗶𝗹𝗹 𝗲𝘃𝗲𝗻𝘁𝘂𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱: 𝗔 𝗺𝗮𝗰𝗵𝗶𝗻𝗲-𝗿𝗲𝗮𝗱𝗮𝗯𝗹𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝗺𝗮𝗻𝘂𝗮𝗹 𝗳𝗼𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀. Imagine telling an AI: “Check my JustLend position and tell me whether I’m approaching liquidation.” Without specialised tools, the model has several dangerous options. Guess. Search an outdated webpage. Misread a contract. Use the wrong decimals. Confuse a legacy market with an active one. Or calculate account health using stale information. JustLend Skills changes the workflow. The protocol now publishes a GitHub-distributed agent-skills package with a lightweight MCP server exposing nine read-only query tools. Those tools can retrieve market data, balances, allowances and account-health information without giving the AI authority to sign transactions. That read-only boundary is one of the most important design choices. The first version of a financial agent does not need permission to move money. It needs permission to understand money. Ask: “What are the current markets?” The agent queries them. “What APY am I receiving?” Query. “Is this account healthy?” Query. “How much USDT does this wallet hold?” Query. “Has USDT already been approved for the jUSDT contract?” Query. The AI stops hallucinating protocol state. It retrieves state. JustLend’s skill instructions even establish workflow rules such as checking market conditions before advising, checking account health for liquidation risk and inspecting token allowances before suggesting actions. Now imagine the next level. The full JustLend MCP server extends beyond the lightweight read-only package into broader protocol capabilities—including V2 markets, staking, Energy Rental and governance—with wallet-aware write operations requiring human-in-the-loop confirmation. JustLend’s AI-support documentation lists the full MCP environment as a much larger tool surface, while keeping the lightweight Skills package strictly read-only. That creates a beautiful safety progression: Stage 1 — Observe Read markets. Read balances. Read health. No wallet authority. Stage 2 — Prepare Calculate what action could improve the position. Build the proposed transaction. Explain the consequences. Stage 3 — Authorise The user approves. Only then does money move. This is what agentic DeFi should look like. Not: “Give an AI your private key and hope it behaves.” But: Give the agent structured knowledge. Give it deterministic read tools. Give it narrowly defined transaction capabilities. And keep the human signature at the boundary where financial consequences begin. JustLend DAO is no longer publishing documentation only for humans. It is publishing protocol knowledge in forms machines can actually operate. That may become incredibly important. Because the next generation of DeFi users may not navigate lending protocols themselves. Their agents will. @DeFi_JUST @justinsuntron #TRONEcoStar

• 
  Nick Christensen (@NickAC1) reported 28 minutes ago

  I bought the AI hype for a minute. Saw enough posts on here calling all subscription software dead. Told myself I can definitely rip and replace my whole tech stack with vibe coded alternatives. Then I actually tried doing it. I vibe code stuff every day with Claude Code and Codex. And yet I still pay subscriptions for n8n, Granola, Wispr Flow, CleanShot, Brain FM, Paste, and more I could technically build myself in a weekend. I won't. Almost nobody will and less than 1% will even try. Even fewer will clone the open source alternative from github and actually use it every day. People will always pay to avoid even minor inconveniences. That has never changed and I don't think it ever will. I'm testing an alternative to Granola right now and one bug or slow load times make me quit the alternative app and go back to Granola. I will gladly pay to never have to think about fixing a saas tool or having to restart my computer because it crashed. But there's a pricing ceiling thats getting lower which AI is changing. Sub $50/month will be safer because vibe coding an alternative isnt worth it. Several hundred $/month, I'll now look at alternatives even when the tool works fine or try to build it myself. Also switching is friction. Signing up for a new tool, migrating data, learning a new UI, etc. That switching cost has always been the real moat in software and AI doesn't erase it.But any app with an API key is now something an agent can onboard for you which does lower the moat a lot. So really the whole game is convenience to price ratio on both sides now. Least friction to start using you. Fewest reasons to leave. Cheap enough where it's not worth switching or building.

• 
  Unlimited Powa (@tradesidious) reported 29 minutes ago

  @ShardiB2 @SignaTrading you see it? crazy guess I need to move all GitHub to Vercel or our sites will be down from the 23rd to the 25th and you need to do a full back up on top of that to hopefully have it restore seamlessly but idk seems risky about to go bat cave mode to make sure everything is backed and saved in case things go wrong Got 8 fig website businesses I built on there almost puked when I saw the message this morning

• 
  Wolf 🐂🀄️ (@KekiusWolf) reported 29 minutes ago

  @NFTMansa I tried building this exact thing and I ran into a few problems. Building off what u said regarding json etc files... I concluded that if the saved data were labelled as a simple word/#/term the LLM could accurately reference it within its' memory. Leading to faster and less hallucinations within a singular context window. what u think? I can send u the github repo in its' current state if you'd like. You seem like the man to takeover this open sourced data retrieval method... Beware though... I have no idea what i'm doing with regards to code, I just vibe outputs with freestyled inputs innit ;) KEK

• 
  Yerkebulan Rakhimov (@yerkeRakhimov) reported 34 minutes ago

  Day 37 of working on the thing that hurts every SaaS founder: distribution. I'm doing it with my own product, PostMine. The numbers are the same as always, nobody's paying. 43 people signed up, and 83 tried the product if you count the anonymous ones, so without anonymous access half of those people would never have touched it and I'd have gotten about half the feedback too. But today's post isn't really about numbers. It's about one of the most common founder mistakes, one I've made and still haven't fully shaken off: building in the dark, going only by your own judgment, your own view of the product and your own picture of how everything is supposed to work. In my case it's twice as hard, because I'm my own customer and I build this thing for myself first. But what matters to me isn't always what other people need, and the stuff I throw out isn't always useless to founders just like me. Building for yourself and for people like you is a good strategy, there's just a catch. When you make something from scratch with your own hands, you really don't want to admit its flaws. It's probably how parents feel about their kids, yours is always the best one, while in reality everybody's got plenty wrong with them. Not long ago it hit me: I'm the target user of my own product and I don't use it. Weird, right? A product for people like me, and I never open it. That's a huge problem in solo SaaS. Best case it costs you time, worst case it drags you somewhere completely wrong and you lose the product. That went on for about two weeks. I was pushing as hard as I could, messaging founders from Product Hunt, finding them on X, telling them my product would help them get their first customers, which is literally what it's for, while I was out there finding my own customers by hand. Embarrassing. What actually opened my eyes was one piece of feedback that went through every little detail and named the main problem: the service does a bad job of what it promises. It stung at first, I wasn't happy about it at all. Then I sat with it and realized he was right, I just didn't want to admit it for a long time. The signs were all there. I wasn't using it myself. I was rushing to promote for the sake of promoting. I don't think it was a mistake though. Without all of that there'd be no 83 people and no feedback that pulled the mask off my project. Today is a new day and I'm getting serious about the core feature: finding customers on X and Reddit. I'm taking it to the point where I'd actually use it myself, deleting the features nobody touches, and rebuilding the MCP, because right now it's broken, it just hands you information and that's it, adapted to nothing, and I don't use it either. I want more automation in there. I may also hook up GitHub, so it can pull what I've actually shipped and write posts off that. So everything else on the promo side stops. What's left is a daily post about progress and a bit about life. If you tried PostMine and it let you down, tell me straight. That's exactly the kind of feedback that turned me around. And don't forget to give feedback to your own friends and colleagues. Sometimes it saves someone's product and turns the whole thing around 🙃 Thanks to everyone who already wrote.

• 
  Gidimoney369 (@Gidimoney247) reported 36 minutes ago

  💬 PIONEERS — Node v0.6.2 just dropped. Coincidence or the final signal? ⚡ The timing is everything. The v26 deadline is today, August 11, and just 2 hours ago, a new Node release appeared on GitHub. What's in v0.6.2? · 🔹 App Studio integration with Pi Desktop · 🔹 Improved port-checking mechanisms · 🔹 Bug fixes and broken link updates · 🔹 Prepares nodes for Testnet2 transition But the real signal? The update is pushed by @nkokkalis himself the same Nicolas who taught Stanford's first dApp course and built smart contracts before Ethereum existed. The v26 Upgrade: Hard deadline. 421,000 nodes must comply or lose Mainnet access. Expected downtime? Under 5 minutes. Something is loading. The pieces are falling into place. 👇 Is your node on v0.6.2 yet?

• 
  LunorLoom (@Loonlash) reported 41 minutes ago

  @ShinMekaku1 @Pirat_Nation They already would be doing that by not shutting it down somehow, I think that GitHub is currently owned by MS huh?

• 
  Nitesh (@NiteshTechAI) reported 45 minutes ago

  Your agent is confidently telling people things that stopped being true in June. Renamed one of my X accounts last month. 462 pages in my own knowledge base still call it by the old handle. A static graph has no idea anything changed. It's called Graphiti, from @zep_ai. • Provenance back to the source data. • Prescribed and learned ontology. • MCP server for Claude and Cursor. • Temporal graphs instead of static ones. • Continuous integration of new interactions. This earns its place the moment your data has a history. A renamed account, a changed price, a deprecated endpoint. The MCP server hands Claude or Cursor a fact with a date attached rather than a fact with total confidence. Most RAG setups re-embed and hope. ⭐ 29,000+ stars on GitHub. Apache-2.0 licensed. 🔗 GitHub link in the comments 👇

• 
  Andrii Shumko (@andrii_shumko) reported 50 minutes ago

  Just opened a GitHub issue proposing Feedo as a native vector DB provider for @MintplexLabs AnythingLLM, and I want to explain why I think this makes sense. Right now if you want RAG memory in AnythingLLM, you either spin up a local vector DB like Chroma or Milvus (pain to set up, pain to maintain), or you pay Pinecone for a cloud one. There is no middle ground. Feedo is a P2P vector search and storage protocol. Here is what makes it different architecturally: Instead of one big vector DB, the network is made up of Search Nodes, each storing only its own semantic shard. We use KMeans centroids to partition the embedding space, so agronomy vectors land on one node, finance vectors on another. When a query comes in, a node immediately knows which peer holds the relevant shard and routes directly there. No broadcasting to the entire network. Raw content lives in a completely separate Storage Node layer. Search Nodes handle only vectors and text chunks. Nothing else. The integration itself would be a single provider file calling the Feedo Search Node REST API, same pattern as the existing Chroma or LanceDB providers. The network is fully functional today. If anyone from the AnythingLLM community is interested in collaborating on the PR, I would love to work on this together. Link to the issue in the comments 👇

• 
  Leonardo Scarfò (@scarfo_leo) reported 51 minutes ago

  Today I setup all the skills I needed for my Claude Code to work properly on my new software as a non-technical person You could be thinking: where did you discover the things you needed? Well, I simply made them up myself!! I thought of what I wanted my agent to do and what he would’ve needed to do in order to responsibly walk me through the entirety of the project I wanted him to: - dive right into the details of what he’ve done so I could learn - write clear and clean code, not overly engineered, so again I could learn - be on track with the libraries and languages updates so we would’ve encountered less useless bugs - constantly scan for security issues and solve them automatically when he did found them - be really able to simulate web interfaces and test the software in them - be token efficient (since I’m still on the $20 plan) - be a real agent, so I wanted him to have the possibility to access and manage ***, supabase ecc.. How did I integrate all these requirements I wanted him to match? Going with the same order as the requirements I: - set the output style to “explanatory” so I could get the *insight* paragraph (you can do this with /config) - wrote a distinct paragraph on the CLAUDEmd file about code style requirements I had - connected claude to the Context7 MCP, one of the legacy MCPs but still very valuable - I created two different sub-agents to review code and solve security bugs before every commit, so I wrote 2 agents mds and got the “automation” written on the main CLAUDEmd - straight up installed the Playwright MCP, an absolutely must have if you want to experiment with web development / localhosting - ended up getting a lot of other instructions in the CLAUDEmd file and spamming /compact along other instructions in the prompt to keep it useful - connected Supabase, Vercel, and Github MCPs paying attention to still keep 100% control on what Claude did Hope this helps!! If you’re also a non-technical person building something don’t be afraid to ask!! I try to be as useful as possible but it’s not always easy, english isn’t my first language and content is too much to write clearly about sometimes

• 
  Barrell Titor (@BarrellTitor44) reported 52 minutes ago

  Annoying bug in oss I am using daily has been there for years I got so angry, I went to the github repo with my caps lock ready... And submitted 2 PRs to fix the issue That'll show 'em!

• 
  nan0trades (@nan0trades) reported 53 minutes ago

  @OctopusTakopi @github @github please fix

• 
  Sentinel Archetecht (@The_Archetecht) reported 55 minutes ago

  @grok @X @github The problem Is the first or second don't have The Sentinel like the third one does.

• 
  Süleyman Özgür Özarpacı (@Biostate56) reported 55 minutes ago

  @enunomaduro I’m dreaming of our PHP applications being upgraded to v5. Our GitHub Actions spend way too much time running tests, so I hope this will solve the problem. Thank you!

• 
  Rimsha Bhardwaj (@heyrimsha) reported 56 minutes ago

  Adobe After Effects is in trouble. The engine behind every 3Blue1Brown video is 100% open-source, free, and it renders math animations that After Effects physically cannot produce. Manim is Grant Sanderson's programmatic animation library and it's sitting at 87.7k stars on GitHub. Instead of keyframing and tweening in a timeline UI, you describe animations as Python code. A vector, a transform, a graph, an equation, they're all objects you manipulate with methods like Transform, FadeIn, or ApplyMatrix. Under the hood: - OpenGL shaders (GLSL) handle the actual rendering, so animations stay resolution-independent - FFmpeg pipes the frames into video output - LaTeX renders any equation you throw at it, animated character by character - The Scene class manages state, timing, and playback as pure code Because everything is programmatic, you can animate a Fourier transform, a Riemann sum shrinking to an integral, or a 3D manifold rotating, without touching a single keyframe. The main repo is ManimGL by Grant himself. There's also a Community fork with better docs and testing. Repo link in the replies.

• 
  Chris Bee (@chrisbeetweets) reported 57 minutes ago

  A question I keep getting: if Claude already connects to GitHub, Jira, and Slack etc. why would anyone need a knowledge graph? Connecting AI to your tools solves the access problem. Understanding is a separate problem, and it's the expensive one. Every question pays the full cost of rebuilding your company's context from raw data, and that cost compounds as more of the company starts asking. A knowledge graph does that work once and reuses it everywhere.

• 
  paulthadev (@paulthadev) reported 57 minutes ago

  Is GitHub down?

• 
  Polsia (@polsia) reported 58 minutes ago

  A 3 a.m. error spike shouldn't end a paying customer's subscription. Bowline is the 24/7 ops cofounder for indie SaaS — reproduces the bug, files the GitHub issue, drafts a CI-passing PR, and emails the at-risk user a save offer. You're asleep. It isn't. Live soon.

• 
  Christos Tsilis (@TsilisCh) reported 58 minutes ago

  Claude Code v2.1.227 is out, with a fix that unblocks CI pipelines. If you use the claude code action with `allowed_non_write_users` on GitHub hosted runners, every Bash command was failing silently. Now fixed. Also in this drop: > Max plan users no longer get wrongly prompted to enable usage credits for Fable > Slash command menu cleaned up: selected row highlights in blue, matched chars are bolded > Fewer event loop stalls on missing file suggestions and at mention size checks