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	1 day ago
Trichūr	Errors	4 days ago
Brasília	Sign in	5 days ago
Lyon	Website Down	5 days ago
Tel Aviv	Website Down	9 days ago
Rive-de-Gier	Website Down	9 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:

• 
  Patrick O'Brien (@AllTheTokens) reported 1 minute ago

  @johnennis They don't respond to customers, don't reply to github issues, and don't answer calls.

• 
  tintwotin (@tintwotin) reported 2 minutes ago

  @SoyKhaler Could you post the error log on either GitHub or Discord (I do not run Linux myself, so I have to rely on Claude to solve it)

• 
  Trantor (@Trantor__) reported 6 minutes ago

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

• 
  Sameer Khan (@sameerr_dev) reported 7 minutes ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  Rohit (@rohit4verse) reported 9 minutes ago

  In 2026, harness engineering is the difference between an agent that ships and one that burns tokens. If you want to learn it, someone just dropped the one-stop resource on GitHub, free. 12 lectures, 6 projects, 14 languages, 8k+ stars. Inside: - 12 lectures, each on one hard question: why strong models still fail, why agents call "done" too early. - 6 projects where you build a real Electron app, your harness getting sharper with each one. - Copy-ready templates (AGENTS.md, feature_list.json, init[.]sh) you drop into your own repo today. - A harness-creator skill that scaffolds a production harness in minutes. It even opens with Anthropic's experiment: the same model going from a broken build to one that ships, on harness changes alone. Codez wrote the 14-step map. This repo is the course underneath it.

• 
  Jaden Tripp (@jadenitripp) reported 12 minutes ago

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

• 
  Gandalf Stormdrain (@auroter) reported 13 minutes ago

  @godspeed_mista Works better for me every single time. Opus and GPT have not given me a correct solution in months, even to simple problems. I have to come up with the solution on my own, or ask a model that isn't nerfed. I've collected data on this, and I'm going to be sharing that soon. I'm also not the only one. There's a famous Claude Code Github thread from the head of engineering at AMD who has observed the same issues I have with Claude.

• 
  UD (@udfromden) reported 15 minutes ago

  Most people in Web3 claiming to "BUILD" are not builders. They're narrators of building. .. Real builders: - Have GitHub commits - Have paying customers - Have shipped things that work - Have user complaints to fix - Have things that broke in production Builders on CT: - Have threads about building - Have frameworks about building - Have opinions about building - Have courses about building - Have never shipped anything anyone paid for

• 
  DEX223 (@Dex_223) reported 16 minutes ago

  @liquidityXBT @base 9/ With all that in mind and accounting for the fact that the exact problem was reported in the very ERC20 finalization thread on github it can be concluded that the standard is not *secure by design* It is known to entail financial losses It violates known security principles

• 
  Zhu Liang (@paradite_) reported 16 minutes ago

  i found it really suspicious that vercel auto-deploy from github is currently down when fly. io is down. maybe vercel uses fly. io for auto-triggering deployment from github?

• 
  WiseBlindCat (@WiseBlindCat) reported 18 minutes ago

  @GitHubSupport My account was suspended after I tried to update my payment method. No policy violation a billing issue. Two tickets opened, two weeks, zero human response. I'm paying $48 for GitHub Pro with no access. Ticket #4436824 and 4447591. Please escalate immediately.

• 
  Daniel Vassallo (@dvassallo) reported 19 minutes ago

  @GustavoValverde @levelsio Judging by the number of openclaw github issues, it seems not easy to solve.

• 
  HopeSeekr (@hopeseekr) reported 20 minutes ago

  I cannot leave review comments on GitHub Pull Requests... it's broken?

• 
  Mercy (@MercyyyyAJ) reported 20 minutes ago

  @github @mariorod1 @github the link to my GitHub account has never been accessible, keeps giving 404 error. I have tried every solution I found online but it is to no avail

• 
  Alexandre Daubois (@alexdaubois) reported 23 minutes ago

  @marcelgsantos @enunomaduro @nikita_ppv That’s right! But it’s on GitHub because they were « forced » by the backdoor incident in 2021. And also, if GitHub stops working, it’s easy to re upload the repo somewhere. If all mails go to GitHub issues, everything could be lost and/or it would be really complicated to transfer everything. If I was the only one to decide, I’d say it would be fine, but…

• 
  Will (@economitra) reported 26 minutes ago

  Anthropic accidentally shipped Claude Code's own source code in March. A packaging mistake, ~500k lines on GitHub before anyone noticed. They confirmed it: human error, no model weights, no customer data. The leaked part was just the harness. The harness is the whole lesson.

• 
  Ben Holmes (@BHolmesDev) reported 30 minutes ago

  @trentkocurek @warpdotdev That doesn't sound like a setting you missed, focus should carry over when you switch tabs. Verified I'm seeing that on my latest stable. Can you run /feedback in Warp? It files a GitHub issue prepopulated with your version and OS to help repro

• 
  @aaronjmars (@aaronjmars) reported 32 minutes ago

  @connorking @NousResearch the only issue is execution is still living in your computer w/ @aeonframework we ship everything out of the box as a runnable github + sandboxed, so your memory is interoperable + ultra lightweight

• 
  Abdullah Alaqeel (@Aqeel_AT) reported 32 minutes ago

  @neogoose_btw I wanted to see the fff GitHub repo but couldn’t. I’ll have to search manually or open the link from my laptop. If the demo site is on github I’d love to fix the footer thingy

• 
  Manav (@Manavvv31) reported 33 minutes ago

  NVIDIA just dropped an open-weight model that can solve 60% of GitHub issues on its own The model is Nemotron 3 Super, released at NVIDIA's GTC 2026 conference on March 11. The benchmark that matters for software engineering is SWE-bench Verified, which tests whether a model can autonomously resolve real issues pulled from production GitHub repositories. The closest proxy the field has for: can this thing actually do engineering work unsupervised. Nemotron 3 Super scores 60.47 percent on that test, the highest score ever published by an open-weight model. For context, the previous leader, GPT-OSS, scored 41.9 percent. That is not a narrow margin. The architecture explains how a 120-billion parameter model can run efficiently at scale. It uses a hybrid Mixture-of-Experts design that activates only 12 billion parameters per forward pass, not all 120 billion. The result is 5x the throughput of the previous generation and 2.2x higher than GPT-OSS, running on a 1-million token context window. On RULER, the benchmark for long-context retention, it scores 91.75 percent versus 22.30 for GPT-OSS. The context window actually works. The weights ship under the NVIDIA Nemotron Open Model License, which permits commercial use, alongside full training recipes and datasets. It runs on vLLM, SGLang, TensorRT-LLM, and a free tier on OpenRouter. Production deployments already confirmed by Perplexity, CodeRabbit, Factory, Greptile, Palantir, Cadence, Dassault Systèmes, and Siemens. The honest context: on raw intelligence benchmarks, Chinese open-weight models, particularly Kimi K2 and Qwen3.5, still lead globally. Nemotron 3 Super wins on a different axis entirely: inference efficiency on NVIDIA hardware, and the ability to ship code changes autonomously in production without sending proprietary repositories to a cloud provider. For the first time, a model that resolves 60 percent of real engineering issues runs on hardware you own, at a marginal cost that scales with your servers rather than someone else's pricing.

• 
  Fisher (@hawking520) reported 36 minutes ago

  THE FIRST-100-USERS PLAYBOOK Pick your row. Run the cheapest test that can fail. Get paid before you polish. STEP 1 — Find your type (decide in 30 sec). Run ONLY this row's 2 channels. Dev tool / OSS / infra → Show HN + GitHub Consumer / visual AI → Discord + creator seeding B2B SaaS → Social listening + pre-sell Prosumer / extension → Reddit problem-threads + Product Hunt B2C web app → SEO Mobile app → ASO + micro-creators STEP 2 — Validate in a WEEK, before any code. Run one. If it fails, kill the idea. Fake-door → 1 page: outcome headline + email box. Send 100 visitors (a few replies + 1 small post). Pre-sell (B2B) → DM 20 people who named the problem: "Building X to fix this. Can I put you down for a paid pilot at $___?" Get a written yes or a deposit. Concierge → do the job by hand for 5 people. Charge them. PASS BAR: 20–50 emails OR one real "yes, I'll pay." Miss it → stop. Demand isn't there. STEP 3 — Build only the core. One job, done well. Cut every feature you can defend cutting. Ship when it's embarrassing — polish isn't the test; distribution + willingness-to-pay are. STEP 4 — Run your 2 channels. The exact first move: Dev tool → Show HN with a runnable demo in line 1. Pin the repo. Reply to every comment for 6h. Consumer AI→ Open a Discord. Weekly output challenge. Seed 50–100 micro-creators (not 3 big ones). B2B SaaS → Search Reddit/X/LinkedIn daily for the problem. Same-day help, not a pitch. Ask for an LOI. Prosumer → Find the subreddit where people complain. Post a useful answer; mention the tool only if asked. B2C web → Pick ONE "best [tool] for [specific audience]" phrase. Build the page that wins it. Mobile → Nail the App Store title + screenshots first. Then seed 5–10 niche micro-creators. STEP 5 — Get users by hand (65% start with no audience — that's the normal start line). Daily 30 min: 15 min → find 3 people complaining about your problem. Help. No pitch. 10 min → make one shareable result; ship it publicly. 5 min → DM one warm contact for an intro or a quote. Run it 30 days before you judge anything. STEP 6 — Positioning. Lock before you scale. One-liner: "I help [who] [do what] without [the pain]." Say it to 5 strangers — they must repeat it back. Landing page, this exact order: outcome headline → their own words (paste real Reddit phrases) → 10-sec demo gif → proof → one CTA. Delete the rest. STEP 7 — Get paid (the $0 → $1 unlock). 3 tiers, anchor the middle. Price ~2x higher than feels comfortable. Never paywall a free crowd later — charge from the start. Solo / non-US? Use a Merchant of Record (Paddle or Polar) — handles global VAT, collect legally today. Need fast cash + warm users? Run a lifetime deal (AppSumo).

• 
  Wes Eklund (@WesEklund) reported 37 minutes ago

  @ibuildthecloud > tell the agent to run that command when it's done? Hope to do it once and it remembers? Or just every working session? For CC at least, it would do something like save it in 'memory' But I haven't really relied on it before. Any ideas or bugs it finds or new features, I tell it immediately to make new GitHub issues.

• 
  paul (building stuff nobody asked for) (@banx0isme) reported 38 minutes ago

  @elder_plinius no github no problem. and necessarily call it national security

• 
  Ekemini Billions (@pablobtc46883) reported 46 minutes ago

  The part of building that drains me isn't even writing code. It's all the little things after that. Setting everything up, deploying, making sure nothing breaks, then sitting down again to write a launch post. So seeing the likes of @moonshiftio trying to handle the build, push the app to your own GitHub and Vercel, while also preparing the marketing side, is an interesting direction. If AI is going to save time, that's probably where it should start.

• 
  Rituraj (@RituWithAI) reported 48 minutes ago

  🚨 Someone just turned Claude Code into a fully autonomous bug bounty hunter. Recon. Vulnerability detection across 20 attack classes. Exploitation. Report generation. All inside your terminal. All running while you do something else. It's called claude-bug-bounty. 2,500 GitHub stars. And it does what used to require a team of security researchers. Here's what it actually does. You point it at a target. It runs reconnaissance — subdomain enumeration, port scanning, technology fingerprinting, endpoint discovery. It maps the entire attack surface automatically. Then it hunts. Across 20 vulnerability classes — SQL injection, XSS, SSRF, authentication bypass, IDOR, command injection, insecure deserialization, and more. Not running a static scanner with known signatures. Reasoning through each endpoint the way a human security researcher would — understanding the application logic, forming hypotheses about where weaknesses might exist, and testing them. When it finds something, it doesn't just flag it. It writes a full report — proof of concept, impact assessment, remediation steps — formatted exactly how bug bounty platforms expect submissions. Here's what makes this different from a vulnerability scanner. Traditional scanners check for known patterns. Signature matching. They miss anything that doesn't match a known CVE format. Claude reasons about the application the way a human hunter does. It understands business logic. It notices when an API endpoint behaves inconsistently. It chains together minor issues into a meaningful exploit path the way an experienced researcher connects dots that a scanner can't see. Here's the wildest part. It runs autonomously. You give it a scope. It hunts continuously — recon, testing, validation, reporting — without you babysitting the process. Check back later and you have a stack of findings with reports ready to submit. This is the same shift that's happening across every domain right now. Coding agents that work for hours unsupervised. Trading agents that execute without confirmation. Now security research that hunts independently. Here's why this matters for the entire bug bounty industry. Every bug bounty hunter manually testing endpoints one at a time just got a competitor that works 24 hours a day, tests every endpoint systematically, and never gets tired or misses a step from fatigue. The barrier to entry for security research just dropped to whoever can run Claude Code. Built strictly for authorized testing — your own systems, or bug bounty programs where you have explicit permission. Using it against unauthorized targets is illegal regardless of what tool you used to find the vulnerability. 2.5K GitHub stars. 429 forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  Data Wolf 🐺 (@0xDataWolf) reported 49 minutes ago

  Weird tip: Don't use native Hermes to set up Camoufox. Give it the Camoufox repo on GitHub and get it to install it, and most importantly, GET IT TO USE DOCKER to host Camoufox. THEN hook Hermes up, and write a skill on how to use it for the next AI session. This makes it easy for Hermes to debug Camoufox issues. If you leave it running as a PID background thing, it will keep bugging out while struggling to fix it

• 
  Noctilust (@stillwaterus) reported 51 minutes ago

  @ericjing_ai could you fix github link on homepage?

• 
  Vikram Aditya (@viks_rum) reported 52 minutes ago

  @JayaGup10 we need a github for ai token spend - requests get routed through team leads who can accept or reject. this slows development by maybe a few mins but still keeps things contained. token issue is a workforce management problem. high time to treat token as real-time reimbursements.

• 
  Stefanescu Liviu (@liviusa) reported 59 minutes ago

  @swyx @TomasReimers @cursor_ai What's wrong with ***? Maybe github has some availability problems, true, but *** is fine, need to see what's different and better

• 
  Faisal Karim (@Le__FaiCee) reported 59 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)