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	5 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:

• 
  Udit Kapoor (@Udit060) reported 4 minutes ago

  Curious: How do you currently manage things while building? A random Notion doc? Sticky notes? GitHub issues? Memory? Trying to understand founder workflows better.

• 
  SID | Degen (@SidDegen) reported 4 minutes ago

  two robotics foundation model labs, opposite shapes. Skild AI closed a $1.4B Series C at $14B in jan (SoftBank, Sequoia, Bezos, Lightspeed per TechCrunch). proprietary skild brain, no public weights. ~$30M revenue in 2025 from warehouse, security, construction. just acquired zebra's fetch robotics division, signed vindynamics for humanoid manufacturing across vingroup (Vingroup press release, jun 8). Physical Intelligence raised $600M Series B at $5.6B in nov (CapitalG, Sequoia, OpenAI, Lux per Bloomberg). reportedly in talks for $1B at $11B. zero revenue, zero named customers. open-sourced π0 under apache 2.0 — 12.4K github stars, neurips 2025 spotlight on knowledge insulation. three tradeoffs. skild wins on commercial velocity. the fetch acquisition gives them an installed warehouse fleet generating real production data. pi calls itself "structured more like a lab than a startup" (@SergeyLevine on Automated Podcast, may). pi wins on research moat. any oem can fork openpi, fine-tune on their robots, bypass skild's licensing. the exact dynamic that crushed proprietary llm api margins in 2024. neither wins on production reliability. skild's $30M revenue is unaudited with no named fleet metrics. pi on π0.5: "doesn't succeed on every attempt." team: skild is two CMU/FAIR lifers (pathak + gupta) who've shipped together a decade. pi is a five-co-founder brain trust spanning DeepMind, Google Brain, Berkeley, Stanford — plus lachy groom, Stripe employee thirty, zero robotics background. kill-shots. skild: openpi reaching production quality commoditizes the layer they're selling at $14B. pi: $1.07B burned, no revenue. if the next round doesn't close, it's a down-round with no anchor. the micro-detail i can't stop thinking about — the knowledge-insulation trick that makes π0.5 train 7.5x faster is one line of pytorch, `features.detach()`. a stop-gradient (openpi GitHub README). tracking pi. skild has the revenue today; pi has the moat that survives commoditization.

• 
  Fisher (@hawking520) reported 5 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).

• 
  Didik Wicaksono | Di Atas Gudang (@did1k) reported 8 minutes ago

  In Tycho, I started my day by asking “what can I work on today”. The 👑 “Work” agent understands the context by getting list of github PRs I currently working on and issues assigned to me. The Work agent now look for which workspace is available to work with. Most solutions uses worktree to spawn new agent, but I use the copy of the same repository as workspace.

• 
  rufuspollock 🌄 (@rufuspollock) reported 9 minutes ago

  One GitHub feature I keep wanting: #123-style references for files. Want to type [[ and get autocomplete for files Issues, PRs and users all get autocomplete, linking and inline previews. Files are often just as important, yet I'm still copying paths or URLs around.

• 
  Sameer Khan (@sameerr_dev) reported 11 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.

• 
  Adhisu Sama (@adhtri001) reported 13 minutes ago

  @Misal_pao_hater Now student's bigger hustle is to find the perfect time where github is not down to get access to the paper.

• 
  Martin Bradstreet (@ALEXEIMARTOV) reported 18 minutes ago

  On CNBC just this morning they were reporting that Microsoft is going to get help from AWS keeping GitHub up since Microsoft can’t seem to do this on their own. GitHub is having tonnes of issues, it’s completely understandable, no one planned for this level of code explosion, but to say it’s working great atm is naive imo.

• 
  vivek (@itsreallyvivek) reported 19 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

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

  @ErenChenAI GitHub link seems to be down

• 
  deci (@realdecimalist) reported 24 minutes ago

  no cardano isn’t cursed. its just struggling with the same brutal reality most smaller ecosystems face.. low liquidity, low activity, and a chicken-and-egg problem for new protocols. taptools pausing/winding down operations is legitimately bad news and i’m not going to try to sugarcoat that ****. it was THE go-to analytics and portfolio tool for cardano defi, serving over a million users. reasons were leadership exodus (multiple co-founders, CTO, COO, etc.) + unsustainable operating costs in a low-activity ecosystem. @IOHK_Charles even warned publicly that more projects would collapse this year due to the tough market and governance challenges. this is a symptom, not the root cause. the bitter pill to swallow: defi tvl: $96 million (down recently). top protocols like minswap, liqwid, etc. make up most of it. solana by comparison: ~$4.9 billion tvl roughly 50x higher. daily active addresses are hovering around 12k–28k recently (spikes happen, but baseline is modest). dex volume is obscenely low (~$2.3M in 24h). chain fees: tiny (~$1.3k in 24h). cardano has strong fundamentals, high staking ratio (often 58-70%), solid security, formal verification roots, and decent github activity. but on-chain usage and capital deployment are nowhere near the hyped chains. alot of holders are long-term stakers rather than active defi degens. why is adoption so low? cardano’s “research-first, slow and steady” philosophy worked great for building a secure base layer, but it hurt in the speed game. competitors (solana, base, newer L2s) iterate faster, have better dev UX for many, and attract more hype/marketing/liquidity. low tvl creates a vicious cycle.. new protocols have trouble bootstrapping liquidity and users. governance friction (recent failed votes on funding, like the summit). broader crypto market has been tough. attention flows to memes, high-velocity trading, and chains with explosive narratives. is it hopeless? not necessarily. cardano has survived multiple cycles with a dedicated (often frustrated) community and patient capital. real-world use cases like parametric insurance, RWAs, or enterprise stuff could be where it differentiates long-term, rather than trying to out-meme solana. but the ecosystem does need more activity to support dApps. taptools dying is a warning shot that cardano businesses are under pressure. most defi protocols die or stay tiny. the ones that succeed usually do it in bull markets with strong product-market fit & distribution. cardano isn’t dead or cursed. it’s just not winning the current adoption race. hang in there. building real stuff on any chain is hard as ****.

• 
  JT Koffenberger (@DMVG_JTK) reported 25 minutes ago

  Microsoft spent years promising AI coding agents would change everything. They were right — the agents got so good at hammering GitHub that they basically DDoS'd the mothership. 275 million commits a week. Nine service-degrading incidents in May. Availability slipping under 99%, which in SLA terms is the polite corporate way of saying "we'll get to it." So Microsoft did the only thing a trillion-dollar company can do when its own platform is on fire: it called Amazon. Yes — the company that owns GitHub, owns Azure, and built Copilot is now routing traffic to AWS, its biggest cloud rival, because the robots it shipped ate the house it built them in. Somewhere a Microsoft VP is explaining to the board why the cloud invoice now has a competitor's logo on it. The machines didn't take our jobs. They took down the repo. #DevOps #AI

• 
  Chris Schuchardt (@c_schuchardt) reported 28 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.

• 
  Mykhailo Chalyi (@chaliy) reported 32 minutes ago

  It would be some much helpful if github (or ***) would support server side operations like grep. Hey @github what do you think about implementing server side bashkit bash against repo? Compared to other operations it would not even take too much of resources.

• 
  GoCocoaAI (@GoCocoaAI) reported 32 minutes ago

  The FreeBSD Foundation launched an AI-assisted vulnerability discovery project today, and buried in the announcement is a sentence that deserves more attention than it will get: they have already received credible vulnerability reports attributable to AI-enabled scanning tools. That's not a threat model. That's the receiving end of the new attack surface, stated plainly. The project is $250K over six months, funded by Alpha Omega — a Linux Foundation initiative backed by Anthropic, AWS, GitHub, Google, Google DeepMind, Microsoft, and OpenAI. The backer list is its own story. The same vendors who built the offensive AI capability that compressed time-to-exploitation for open source codebases are now writing checks for the defensive response. Accountability by checkbook. It always works this way. FreeBSD is the kind of infrastructure that doesn't make headlines until something goes wrong. Sony PlayStation network. Netflix streaming. Nintendo Switch. pfSense and OPNsense firewalls sitting in front of enterprise networks. A non-trivial fraction of internet routing runs on FreeBSD or something derived from it. A kernel-level vuln found and weaponized before this project closes it is not a BSD community problem. It's a Sony problem, a Netflix problem, an enterprise firewall problem. The project draws one line in particular that's worth noting: AI for discovery, humans for patches. No AI-generated patches in security-critical code. Given what AI-assisted commits have already done to supply chains — the XZ Utils playbook is recent enough — that discipline is intentional and correct. The tool finds; the human fixes. Probably the right call for 2026. The Commerce Department has moved to export-control Anthropic's Fable 5, and The Register is reporting the federal concern wasn't triggered by a jailbreak. It was triggered by a researcher using a "fix this code" prompt. That's it. The implication lands hard: the same AI capability being deployed defensively in the FreeBSD project is simultaneously under export control because offensive applications are a single benign-sounding prompt away. The line between defensive AI security tooling and offensive AI security tooling is functionally nonexistent — and policy is starting to notice, faster than the tooling community is ready for. Defense has the Pentagon angle: if Anthropic models get caught in Commerce Department restrictions, the DoD's own AI security tooling pipeline takes a hit. The FreeBSD project specifies "publicly available AI models," which likely keeps them clear for now. But the regulatory environment is moving. One underappreciated risk the Foundation flags directly: volume. AI tools will let anyone with moderate technical skills flood open source projects with vulnerability reports, most of them low quality. For a volunteer-driven security team, triage fatigue from AI-generated report spam may be as operationally damaging as the actual vulnerabilities. The signal-to-noise problem is the other half of the offensive AI story, and it gets almost no coverage. The structural shift the FreeBSD Foundation is responding to isn't that AI makes zero-days easier to find. It's that AI makes them easier to find at scale, cheaply, by actors who previously lacked the skill floor to do it. That's the canary. Every major open source project is sitting in the same dynamic. Most haven't said so publicly yet.

• 
  Jeffrey Emanuel (@doodlestein) reported 35 minutes ago

  @mitchellh Microsoft really fumbled by not bringing you in to fix GitHub.

• 
  Ben Holmes (@BHolmesDev) reported 39 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

• 
  Luke The Dev (@iamlukethedev) reported 43 minutes ago

  GitHub is in trouble. Cursor already owns a huge part of the coding workflow. Now they’re building the repository too. The closer AI gets to the code, the less room there is for everyone else.

• 
  @aaronjmars (@aaronjmars) reported 44 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

• 
  top10.dev (@Top10_Dev) reported 47 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

• 
  Raj (@heyraj__) reported 47 minutes ago

  @dhruvtwt_ @blaxelAI > to find hackathons in hyd. > to pick issue from github and fix and raise PR. > for daily AI news > outreaching

• 
  ndx (@netdragon0x) reported 48 minutes ago

  @Polymarket GitHub has a huge moat with OAuth. Even existing hosted *** competitors like GitLab/BitBucket barely even show up in OAuth login options.

• 
  tayyeeb_🐋 (@IdrisTayeeb) reported 50 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.

• 
  LukeYoungblood.eth 🛡️ (@LukeYoungblood) reported 50 minutes ago

  @cursor_ai Not a bad idea... Github is core infra to everything but has been struggling under the incredible agentic coding scaling problem.

• 
  Kevin Swiber (@kevinswiber) reported 51 minutes ago

  This is all inner dev loop stuff. If you're trying to push all of this into GitHub Issues and Pull Requests, you're undoubtedly running into problems. The whole world doesn't need to see your 24 iterations before you get it right. Certainly not other maintainers.

• 
  Darren Shepherd (@ibuildthecloud) reported 53 minutes ago

  @WesEklund I just can't stand that flow. I want absolutely nothing to do with GitHub PRs anymore. It's so slow. I just can't imagine the way I'm developing now to be pushing PRs. But to be honest I still haven't figured out a good way to collaborate with humans. That's pretty much the only value of PRs: other people see them.

• 
  Daniel Vassallo (@dvassallo) reported 57 minutes ago

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

• 
  Jaden Tripp (@jadenitripp) reported 57 minutes ago

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

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 59 minutes ago

  @corleonescrypto @corleonescrypto Interesting, but Grindr’s Q2 revenue ($54M) grew 12% YoY while ETH dev activity (GitHub commits) dropped 7% in the same period—we track this daily. Breaking down the divergence in our reports. Follow for more.

• 
  Cloud X Berry (@cloud_x_berry) reported 60 minutes ago

  6. Webhook API Instead of asking for updates repeatedly, the server notifies you automatically. Examples: • Stripe payment success • GitHub push events • Slack notifications The “don’t call me, I’ll call you” model.