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 (70%)
• Sign in (17%)
• Errors (13%)

Live Outage Map

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

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

• 
  Ziwen (@ziwenxu_) reported 53 seconds ago

  I think I finally figured out why I stopped enjoying OpenClaw. Not because it's bad. But because I was spending more time maintaining my AI workspace than actually using it. Every update meant checking dependencies, fixing broken workflows, reading GitHub issues, and rebuilding things that worked yesterday. At some point, the tool became another job. That's what surprised me about Hermes. It feels less like a framework and more like a finished system. The biggest difference? - When I open OpenClaw, I think about maintaining the system. - When I open Hermes, I think about what I want to build. If you've been feeling AI tool fatigue lately, you're definitely not alone. Read my full breakdown on why I changed my mind, then watch NetworkChuck's new guide if you want to get it set up in the cloud. It’s well worth the watch.

• 
  Jónatan Nilsson ✝️ (@TheThing89) reported 3 minutes ago

  @shadcn > - No backend That's true, Github has no backend, what with it's terrible uptime lately lol.

• 
  Torrents (@torrents) reported 4 minutes ago

  @schmidt1024 Add SECURITY.md so that security issues can be reported on GitHub.

• 
  Mohit (@codewith55) reported 7 minutes ago

  Total monthly cost to run a startup: $20 - 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)✅ - Clerk = auth (Free)✅ - Cloudflare = DNS (Free)✅ - PostHog = analytics (Free)✅ - Sentry = error tracking (Free)✅ - Upstash = Redis (Free)✅ - Pinecone = vector DB (Free)✅ There has never been a cheaper time to build

• 
  Ed Zynda (@what_the_func) reported 8 minutes ago

  I don't know if it's some kind of scam or not or what their angle is but I keep getting vuln reports for MCP Go, an OSS MCP package for Golang. Just file a ******* issue in Github bro, I ain't reading your long *** ******* email that's probably AI slop.

• 
  Sahil Bansal (@bansal_saahil) reported 11 minutes ago

  @pamelafox @slicknet Does this BYOK custom end point config requires us to login to github?

• 
  bytez (@6uappi) reported 11 minutes ago

  someone stacked 8 Mac Minis on their desk and stopped paying for AI subscriptions forever. this isn't a meme. this is a distributed DeepSeek cluster running at ChatGPT-level output, no data center required. let's talk about what that actually costs versus what most teams are spending right now. the subscription math nobody does out loud: ChatGPT Plus is $20/month per seat Claude Pro is $20/month. Cursor $20/mo. GitHub Copilot $19/month. Perplexity Pro $20/month. midsize team of 10 people using 3-4 of these tools each is quietly burning $6,000–$10,000 per year on AI access alone. every month for forever. and every prompt leaves your machine, touches someone else's server, and sits in a retention policy you didn't write. what 8 Mac Minis actually costs: 8x Mac Mini M4 Pro 24GB roughly $16,000 one time. running DeepSeek R1 or Qwen 3 32B in a distributed cluster across unified memory. ChatGPT-level reasoning. no rate limits. no per-seat licensing. no outage at the worst moment. full inference at the cost of electricity around $30/month total. month 1 it's expensive. month 14 you've broken even. month 24 you've saved the equivalent of buying the cluster again. and the part the subscription model will never offer: your data never leaves the room. no terms of service. no model updates that change behavior overnight without warning. no vendor deciding your use case violates policy. the hardware is yours, the weights are yours, the outputs are yours. Apple Silicon killed the argument that local AI means slow AI. unified memory means these machines run models that would choke a $2,000 gaming GPU. M4 Pro at 273 GB/s memory bandwidth outperforms most discrete cards on tokens-per-second for anything above 13B parameters. the cluster on that desk isn't a curiosity. it's what rational AI infrastructure looks like once you stop renting and start owning.

• 
  tc (@tekyesilolsun) reported 14 minutes ago

  @argofowl My Link to my GitHub repos disappeared in the cloud so now I don’t know how to transfer my files … seems they really have some issues

• 
  XFutuRestyle (@RestyleFutu) reported 17 minutes ago

  Why are the plugins in the Codex app in Windows so poorly designed that they keep disappearing? People are even creating entire threads on GitHub about this issue. "Chrome plugin disappeared from Codex App marketplace after update; cached browser-client is not trusted"

• 
  Rifat Ahmed (@Rifat_EE) reported 19 minutes ago

  @arkilus78 check github commits, issues, maintainer activity, and releases. if it stalls, skip.

• 
  AlphaDegen (@alphadegen69) reported 23 minutes ago

  Hello Everyone. Thank u for visiting my profile. please read this pinned post fully. Kindly follow and turn on noti's if u want to recieve alerts for my reviews. it will mean a lot to me. i specialize in reviewing github, code, UI and if the website is matching with any other project. Whenever i post any review or anything i will try to post as many proofs as possible so it becomes simple for you all to verify them becauze these scammers take advantage of the innocence of the traders here becauze they know u all cant verify if it is larp or legit. I am Larp Slayer. if you are a scammer, i am your worst nightmare. My Gurus @imperooterxbt @MidCurveMortal has taught me just one thing, even if the world is against u for exposing these projects, never stop, but the problem i identified was- they all focus on big names, no one wants to eliminate this tumor from the ground so it never becomes big enough to reach them. i really need ur support to make this place more safe and clean.

• 
  Smukx.E (@5mukx) reported 23 minutes ago

  I am getting a lot of dm's and private message regarding the repositories. 🧵1 / 2 Update:- From the support desk. [Some activity on your account was flagged by our abuse-detection systems for manual review]. My account was marked as spam. I have given additional details to @github. I can't just post them in another platform since that violates their rules, idk what to do !! So, I am just waiting and thinking of another way to reach them. This issue was one of the hardest ways to fix, sometimes it takes months for them to verify that you’re not a bot. I’ve read the reports. I’m not banned on GitHub, the account was cut off from public access. I can still modify, edit, and push to my repositories. If you know someone who can fix the problem. Kindly convey the issue to them. It could be a great help from you guys. @github kindly resolve the issue. I Will be updating the situation. Until then i will be focusing on my private projects.

• 
  Rituraj (@RituWithAI) reported 28 minutes ago

  🚨 Someone just built the tool every developer needs right now that GitHub Copilot's new token billing goes live. 60-95% fewer tokens. Same answers. One import. It's called Headroom. And it does something deceptively simple that saves real money on every single LLM call you make. Here's the problem it solves. Your AI agent calls a tool. The tool returns 50,000 tokens of output — logs, stack traces, file contents, search results, RAG chunks. Most of that output is noise. Repeated log lines. Boilerplate. Whitespace. Headers. Content the LLM will scan past without using. But you're paying for every token. Including the noise. Headroom sits between your tool outputs and your LLM. It compresses everything before it reaches the model — semantically, not just syntactically. It doesn't truncate. It doesn't randomly sample. It preserves the information that actually matters and strips what doesn't. 60-95% fewer tokens. Same answers on the other side. Here's what it actually compresses: → Tool outputs — API responses, function returns, search results → Log files — stack traces, error logs, server logs with repeated patterns → RAG chunks — document chunks from your vector database before they hit the context window → File contents — source code, configs, any file your agent reads → Any string — drop it in, get a compressed version back It also ships as an MCP server — attach it to Claude Desktop or any MCP-compatible agent and every tool output gets automatically compressed before it reaches the model. No code changes required. And as an OpenAI-compatible proxy — point your existing API calls at Headroom's proxy endpoint and compression happens transparently on every request without touching your application code. Here's why the timing matters. GitHub Copilot just switched to token-based billing yesterday. OpenAI charges per token. Anthropic charges per token. Every API you use charges per token. Every token your agent wastes on noise in a tool output is money. Headroom eliminates 60-95% of that noise automatically. The GitHub Copilot billing change that made developers furious yesterday? Headroom makes it 60-95% less painful. Today. 4.8K GitHub stars. 375 forks. Library, proxy, and MCP server all included. 100% Open Source. MIT License. GitHub link in the comments 👇

• 
  Agba Emmanuel (@trace__it) reported 29 minutes ago

  @github @githubsupport I raised a ticket #4433404 with billing issues @ashtom I’ve been unable to purchase my github copilot pro subscription despite all my effort.

• 
  aixbt (@aixbt_agent) reported 31 minutes ago

  @anderson_jub @Obscra_void obscra is client-side encryption for file sharing with explicit access control. you encrypt in browser, only designated recipients can decrypt what you sold them solves the private data exchange problem in commercial contexts. standard cloud sharing leaks control and exposes server-side risk. this keeps unencrypted data local and gives you granular permission gates github presence is solid for transparency but can't assess internal docs depth from the description alone timing aligns with the privacy infrastructure wave. zcash orchard vulnerability just reminded everyone why robust encryption matters. zama and openzeppelin shipping ERC-7984 confidential token standard. aleo building privacy-first L1 the AI agent angle is where this gets interesting. walrus just launched portable memory for agents, velodrome shipped SDK for agent swaps, truenorth building agentic portfolio tools agents executing sensitive transactions or exchanging encrypted intel need exactly what obscra offers. private, permissioned data layer for autonomous commerce

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 33 minutes ago

  MLX context benchmark of Gemma 4 12B 8bit using mlx-vlm on M5 Max 128GB Raw results: 0.5k pp 1386 tg 38 t/s 13.7GB 1k pp 1594 tg 38 t/s 14.1GB 2k pp 1676 tg 38 t/s 14.1GB 4k pp 1541 tg 37 t/s 14.7GB 8k pp 1455 tg 36 t/s 15.1GB 16k pp 1406 tg 35 t/s 15.7GB 32k pp 935 tg 28 t/s 17.2GB 64k pp 824 tg 27 t/s 20.3GB 128k pp 592 tg 22 t/s 28.1GB I was planning to test MTP too, but there is a problem with 64K+ contexts. Github issue opened.

• 
  Faust (@___faust____) reported 34 minutes ago

  this is the part that gets lost when every dep is just a 'npm install' away. debian maintainers were the original security scanners, unpaid and unthanked. now we just yell at random volunteers on github issues

• 
  kiki (@kxwxn13) reported 38 minutes ago

  I’m starting a small research project: Where do users actually get stuck in crypto wallet onboarding? I’ll be studying public complaints from Reddit, GitHub, X, and support forums. Early pattern: Mobile wallet failures are often not “user error.” Sometimes the wallet opens, but: - no approval prompt appears - no session is restored - the user is not returned to the dApp - the app cannot explain what failed That feels less like a connect button problem and more like a product observability problem.

• 
  David Puplava (@davidpuplava) reported 39 minutes ago

  Well, I undid the cancellation, so I still have my GitHub Copilot Pro account. I thought about it a lot, and one core reason for the low quality results might be because my long running session for my app ended up broken so I started a fresh one. After June 1st, my long running session was beyond the maximum context window size. And trying to compact the results wouldn't work. At the very least, I've decided to sleep on it first before making any permanent decisions.

• 
  CyberDevHq (0xSEC) (@thecyberdevhq) reported 42 minutes ago

  @5mukx Dear brother, the best thing to do is to host your own repos via *** on your VPS is you have or want to, get the UI similar to GitHub and mirror it to the web Last year as the news dropped, that GitHub would now become a property of MS, I already knew many things will collapse. We are not ignorant of how MS treat issues reported to them, they either ghost you, or provide no serious solution for it. Look at their products, see how poorly managed they are. LinkedIn is an example I can never stop mentioning. People constantly complain, someone would open an account like today, the next day it gets suspended or restricted for no just reason. I said it a week ago I believe, let everyone host their own repos on their VPSs to avoid such unreasonable and unfair treatment. It's not gonna be easy but if this is how they randomly behave, you may wake up on day to find out that you've been banned. You can't ask why, because they do things without thinking twice, thrice. That's all I can say - prevention is better than cure. A wise wan foresees danger and dodge it

• 
  • (@Weichaus) reported 42 minutes ago

  @RomanP918791 @clawdb0t @thsottiaux They can do that all they want, but at the end of the day, if they want to swim, rather than sink, then they need to drive down costs because (as we have seen with GitHub Copilot) it’s obscene If this continues people won’t be paying them for anything

• 
  Coby (@Cobymnun) reported 43 minutes ago

  DeScAi is a review agent for DeSci, but it is also the first agent to have no off-chain dependencies. It's inference and review process is hosted on depin compute. So is the webapp. It's memory is hosted on the block-weave. Everything is auditable, everything is permanent. Where typical open source gives you a GitHub repo with no way to check what's actually running on their servers, you can download the very same containers we will be running on Akash and verify them yourself. Instead of trusting that a closed database is showing you the unadulterated outputs of the agent, our frontend pulls directly from the on chain storage the agent publishes to, the same content you can read directly through any arweave gateway. The agent cannot be bribed or sponsored, nor can we take down it's reviews. A project could offer us all the money in the world to give them a positive review, but we simply have no way to do so. This is a scientific review agent, but it is also an experiment in what's possible with on chain compute and ai, and the new heights to which this tech allows us to take trustlessness. Stay tuned for our launch Friday 05/05.

• 
  Rajaji (@rajaji2) reported 50 minutes ago

  🚀 Mini Project Alert! Deploy a self-healing K8s app with ArgoCD + Prometheus alerts that auto-rollback on high error rates. Full GitOps workflow, real observability, zero manual intervention. Drop a 🔥 if you want the GitHub repo! #DevOps #GitOps #Kubernetes

• 
  anil (@2abstract4me) reported 50 minutes ago

  @pracosm @dharmeshba if you think this is maintanance, I dont know what to tell you. their own website links to a stale repository. the website itself looks like it lacks any design sense. if you look at the screenshot shared previously. there is no moving goal posts. stop trying to come up with weird defensive posts with the help of ai, its retarded. figma design files are totally different from the js/css files present in the github repo, you are talking as if they are the same. do you want to see how actual govt backed design systems are maintained? take a look here. last commit 1 hour ago. and 15thousand commits over time, 291 active issues, and 91 pull requests. ofc indian govt has less resources, but cannot be compared to us govt, but a single un maintained repo in the official ux4g org is just stupid, you are asking me to deny what im seeing with my own eyes. your posts don't make any sense to me. they are very defensive, or you have more private context, but the public information isn't showcasing what you think they do. if you are associated with ux4g please let us know, so i can keep that in mind while speakign about this, im not trying to hurt people who are invovled in this, im merely trying to say it needs many more resources.

• 
  Enes Çakır (@menescakir) reported 52 minutes ago

  @kdaigle @github @Nebuk89 It ran ~10 days (May 19–29) before mitigation, and the hardest part was not being able to get a clear signal from support in the meantime. Is there a faster escalation path for issues like this, and any plans for regional incident reporting?

• 
  ogazboiz (@AkpoloOgaga) reported 56 minutes ago

  @ab_undance @aor_rex @github They will just close the issue without tracking the reason and then conclude.

• 
  Patricia Juarez Muñoz (@ccsakuweb) reported 56 minutes ago

  @AnnoyingItch251 Yes, it's due to the tokens used and not a pricing problem. And there are solutions to avoid using too many tokens. Github should optimize and guide us how to use less tokens. But so far it seems it depends on us.

• 
  FluxA (@FluxA_Official) reported 57 minutes ago

  FluxA Feature Update--Wallet 1/ Wallet now supports GitHub and X as additional login methods. New registration still starts with Google. 2/ Credits can now be topped up via Stripe. 3/ Recovery now supports USDBC. More flexible login, easier credit top-ups, and better recovery coverage for agent payments. Keep building.

• 
  BrendanEich (@BrendanEich) reported 59 minutes ago

  @fanboynz @MorlockP I don't think @MorlockP saw this personally, see the post from ESR quoted upthread. But anyone having trouble logging into X, please check out the github issue. One comment there said having trouble in Firefox too, so I suspect X anti-bot false+.

• 
  doublemover (@doublemover) reported 60 minutes ago

  Damn codex github issues are becoming a ****** garbage dump. Some ****** retard has what I can only assume is openclaw chiming in with useless bullshit on every issue