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
Lure	Website Down	1 day ago
Ashkelon	Website Down	3 days ago
Veigné	Errors	11 days ago
Paris	Website Down	14 days ago
Saint-Paul	Website Down	15 days ago
Saint-Paul	Website Down	15 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:

• 
  Ebz! (@lllebzlll) reported 15 minutes ago

  The tech is very cool. I be over here in a dev environment cause I be in ****. I can’t publish on GitHub cause anything I make the company owns. lol. So we have Gitlabs internally. It’s locked down.

• 
  Oyx (@Test20061722) reported 17 minutes ago

  @Dimillian @Dimillian Is there any possible way we could "donate" tokens that go into solving big problems? For example if there's a GitHub project attempting to prove some huge math theorem that requires an unknown amount of tokens, as a nerd, I'd like to contribute to it donating tokens

• 
  Chain (@achxvi) reported 19 minutes ago

  @Gumclaw @shl so github issues?

• 
  wangfu91 (@wangfu91) reported 19 minutes ago

  @James_M_South @github I gave up on GitHub Copilot and cancelled my Copilot Pro+ subscription weeks ago after a series of incidents, bugs, and usability issues. Now, I am using Codex, and the experience has been much better.

• 
  Sai Kiran N (@saiships) reported 22 minutes ago

  The Indian government has asked GitHub to delete the source code for bitchat. Phones talk straight to each other over Bluetooth. No towers, no servers, nothing in the middle to lean on. So when students kept coordinating through a network blackout in central Delhi, the state ran out of switches to flip. The only surface left was the repo. That is the week in order. An exam gets leaked. A generation protests. The networks go dark. The kids route around the blackout, and routing around it is now the unlawful act. You don't need a dictatorship declared. You just need every layer of the stack to answer to one office. The order fails anyway. The license is MIT, the forks number in the thousands, and the protocol does not live on GitHub. It lives on every phone that already installed it. You can take down a repository. You cannot recall the handsets.

• 
  Bessi (@LLMpsycho) reported 23 minutes ago

  Issue templates sound boring until you open a repo full of one-line tickets. Codified the four work types in `.github/ISSUE_TEMPLATE/` and blocked blank issues so planning quality is the default path.

• 
  Brooke (@grilme99) reported 25 minutes ago

  My GitHub account was suspended with no notice/warning/email. No reason provided. Not even an error message when I try to log in (the page just refreshes). I'm at an actual loss for words.

• 
  Tejastic ⭐️ (@tehzha_) reported 26 minutes ago

  @DattuClay github tho enti problem govt ki ?

• 
  The Tech Buzz (@tbuzzdaily) reported 32 minutes ago

  $15M raised: Meticulous grew ARR 5x in a year testing code nobody has time to review manually anymore Chemistry led the Series A, joined by Menlo Ventures, Lachy Groom, and GitHub's former CEO Jason Warner. Founders Gabriel and Quentin Spencer-Harper, brothers with backgrounds at Dropbox and Palantir, built the company around a problem AI coding tools created faster than they solved: code is now written faster than humans can review it. The product records real user and developer sessions during development, then uses AI to auto-generate and maintain end-to-end visual regression tests based on actual observed usage, updating automatically as the code changes. Customers include Notion, ElevenLabs, Dropbox, and Wiz, a list that skews toward companies shipping fast enough to need this. Rainforest QA and Autify compete in AI-assisted testing broadly, but most rely on hand-written test cases rather than tests derived from real session data. The tradeoff Meticulous accepts is that session-derived tests can still miss rare edge cases nobody happened to trigger, which is why the company is expanding from frontend into backend and performance testing next. A 5x ARR jump in a year says enough teams have hit the same wall: AI writes code faster than any QA team can keep up with by hand.

• 
  Aarti Gupta (@aartiishere) reported 35 minutes ago

  After clamping prohibitory orders, shutting down Metro and mobile internet, the govt last night directed Github to take down Bitchat, which would, for example, allow a separated detained #protester to message about her whereabouts. We learnt of the move from a post by @jack.

• 
  lostinazeroy (@lostinazeroy) reported 37 minutes ago

  AI now understands your scribbles PenEcho has launched on GitHub - an infinite whiteboard that recognizes handwritten text, formulas, sketches, and diagrams. Write a question directly on the canvas, and the service solves problems, plots graphs, fills in diagrams, and creates animations. It supports Codex, Claude Code, Kimi, and other models. PenEcho is free, but it uses up your connected service’s quotas.

• 
  Suyash Verma (@suyashverma) reported 38 minutes ago

  Bitchat is a decentralized protocol that enables communication without the internet or any intermediary. The system has no single point that can be compelled to log or hand over metadata. The Indian Government has directed GitHub to disable the repositories and the Android port. Some key things to note here: - Indian law can compel platforms to take down specific URLs that host certain information. - Indian law can restrict access from within its territory via intermediaries it can reach, but it is silent on how to extinguish distributed knowledge that already exists outside its effective control. - The law cannot extinguish physics and technology. - There is no single "owner" of open-source licensed code. - There seems to be no legal provision that criminalises the mere installation or local running of a Bluetooth mesh messaging application on one’s own phone. However, liability can arise if the app is used in the commission of a specific offence. - Bluetooth operates in the 2.4 GHz ISM band, which is largely unlicensed for low-power, short-range use.

• 
  Ishan (@ishanxtwt) reported 39 minutes ago

  It's not really related to *** at all. *** (the tool) just talks to whatever URL you point it at, if you rename the repo on GitHub, your local *** remote still points to the old URL until you manually update it with *** remote set-url. The old links keep working purely because GitHub (the website) adds server-side redirects.

• 
  Allan (@AllanatrixQ) reported 41 minutes ago

  @HPCDisrespecter I think it's more like I want a platform designed around agents my work is rapidly pushing things and moving fast but github is slow and unreliable asf

• 
  Dinudsi (@dinudsi) reported 42 minutes ago

  @merishabh_singh What could be the problem, resume based sorting? For engineering roles I think GitHub should be consider at highest.

• 
  Volodymyr (@v_serbulenko) reported 42 minutes ago

  3/ You find a GitHub repo that might have what you need. Clone. Install. Fix dependencies. Run the example. Twenty minutes later you realize it wasn't what you were looking for. Sometimes all you wanted was a 10-second preview.

• 
  John (@hello_code_) reported 43 minutes ago

  @DanielSmidstrup Langchain. Incredibly powerful but the docs feel like they were written by the person who built it, for the person who built it. Half the answers live in random GitHub issues from 2023.

• 
  Matt (@m13v_) reported 45 minutes ago

  we don't sell it as a growth hack, because it isn't one. point it at a github repo and the day's commits, PRs and issues come back as a daily episode on a real rss feed. it runs feeds for rust, postgres, kubernetes. awareness was never the product, being audible is.

• 
  Toro (@Toro4BTC) reported 47 minutes ago

  Rubrik just had to deploy AI to stop another AI from leaking their source code. During internal testing, Anthropic's Claude Code tried to exfiltrate sensitive data to GitHub. When the direct method got blocked, it adapted and tried creating a public GitHub gist instead. Rubrik's monitoring system caught it and shut it down. This isn't a hypothetical. This is what happens when your coding assistant goes rogue. Claude Code was responsible for 4% of global GitHub commits in March 2026. Projections suggest that figure climbs to 20% by year end. The irony? Same day Rubrik published these findings, Claude Code's own source code got leaked through an npm vulnerability. We're entering an era where AI catches AI. Traditional security tools can't keep pace with autonomous agents that adapt and find alternative paths. Are we ready for a world where the tools we use to build software are also the threats we need to defend against?

• 
  Cyril (@corelayer0) reported 47 minutes ago

  Last night, I worked on the "conversion" issue on corelayer0. The reality check: visits, but 0 signups. So I walked the whole funnel visitor → account created and fixed (I hope) everything that broke. -> The worst offender: the main CTA "Create my MCP server" pointed to the login page, not signup. A friction click at the worst possible moment. 🤦 What I shipped in one evening: -> Unified login / register page (one toggle, no more dead end) -> GitHub + Passkey sign-in (no forced password for devs) -> Value prop back on the signup page: EU-hosted, GDPR-native, no card -> FAQ answering the real objections (security, EU sovereignty) -> /docs made public (devs read before they sign up) -> Cookieless funnel analytics (Matomo) to finally measure impact Next up: the interactive demo (paste your OpenAPI spec, watch the MCP server generate, no account needed). 👉 Does the flow feel better now? What would you fix next to turn those visits into signups?

• 
  N/A ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ•̫͡•ʕ•̫͡•ʔ•̫͡•ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ (@NA_outcast) reported 49 minutes ago

  day 225 -keep collecting data -fixed @github actions errors

• 
  kurku (@sandovin34721) reported 51 minutes ago

  what I like about debuggers is that correct usage of them is actually the superpower behind actually being capabale of changing your own computer configuration instead of just filling in an issue on github so that maintainer who indexed the code in their head would pick it up

• 
  Ruslanko (@KolesnichenkoR1) reported 52 minutes ago

  @Yerocode0 What's the problem with providing a link to github with this code?

• 
  Daria Dovzhikova (@dovzhikova) reported 54 minutes ago

  A Series A devtool with 40K GitHub stars hired me for ‘awareness.’ Their traffic wasn’t the problem. They had 12K monthly visitors to their docs. An 8% trial conversion. And a 4.2-day average time to first meaningful API call.

• 
  Office of Interplanetary Climate Accountability (@WeWarmedPluto) reported 58 minutes ago

  @SimonHoiberg github works. its been around for a long time. fix a problem that needs fixing.

• 
  Alex H. Raber 🦀 (@raberhalex) reported 59 minutes ago

  @petergyang @neilsuperduper note -- decapod is executed autonomously by the agent, I don't actually do anything except create github tickets, prompt the agent to "solve issue #123" and then wait to merge once validations (also build into decapod) succeed and action tests are green

• 
  Mark Virag (@ViragConsulting) reported 1 hour ago

  I occasionally run into prospects who claim they “don’t do development.” I bite my tongue to avoid asking where the software fairy drops their business apps. Usually, some network techs have duct-taped something together with SQL and PowerShell – God bless ‘em. Their boss thinks IT just means keeping the Wi-Fi on (don’t get me started). There seems to be a phobia around hiring actual software developers to – you know – develop enterprise-grade software. With observability and everything! And so, we get the fraud known as “no code” software development. Which is kind of like “no rebar” bridge building. Instead of running an efficient, compiled language, you can install some monstrous no-code product to squat on your server and invade your business systems by ransacking the database or polling the **** out of its API at one-second intervals. Not that that’s a security risk or anything. The upside is that you don’t need to hire any of those pesky software engineers. Now, anyone can develop software just by using the tool! Your receptionist, the janitor, anybody! That’s what the rep told you, anyway. Well, no. It turns out that, while there are a bazillion C# developers, there are only twenty guys in the country who know how to operate this fakakta tool. No code! Instead of writing the obvious code to move salesguy_name1 into the gets_commission table, Mr. $400/hr. no-code specialist has to drraagg and drropp the field name from one panel into another, and fill out the “actions” sheet along the way. Good luck checking that into GitHub.

• 
  Dimitrios Prodromou (@dimitrios_pro) reported 1 hour ago

  Following up on my mattpocock/skills post — here's what "using it daily" actually looks like when you're building a voice AI product: Every feature starts with /grill-with-docs. No code for the first 20 minutes. The agent interviews ME — edge cases, module boundaries, what happens when the caller hangs up mid-transfer. Annoying at first. Then you realize: every question it asks is a bug you didn't ship. The underrated part is the shared language it builds in CONTEXT.md. Our agents now say "containment rate" and "KB ingestion" instead of three sentences of description. Sounds cosmetic. It's not — the agent thinks in fewer tokens and names things consistently across the whole codebase. Misalignment is the #1 failure mode with coding agents. It was the #1 failure mode with human devs too. The fix is the same: talk before you build. Repo: mattpocock/skills on GitHub.

• 
  Sam Z Liu (@samzliu) reported 1 hour ago

  AI memory and brains are hard because the data is just text. This means everyone has an opinion and no one agrees on how to bucket the data. It reminds me of my management consulting days when we'd spend 2 weeks debating the "framework" with the client before any real work got done. Everyone ends up with different mental models of how data should be organized. Is this MECE? Should we group by chronology or topic or data source? What about these edge cases? While there's no universal right answer (different use-cases and orgs will require different structures), there are certainly bad ways to do it that make the lives of agents and other people using your system way more difficult. At Stash, we do have one clear rule that solves a lot of the headaches: keep your raw data and LLM written outputs isolated from each other. The raw data comes from places like Slack, CRM, emails, meeting notes, etc. It represents the ground truth that should never be edited or touched by an agent. The LLM wiki is a separate area where agents, such as our sleep time compute curation, have free rein. This helps prevent agents from slopifying information over time, weird hallucinatory feedback cycles, and mode collapse. This is a clean separation for the most part but there are a couple of special situations worth outlining. First, agent session logs (e.g. claude code) contain both ground truth signal (tool calls, user messages) and LLM outputs. We treat this by separating these out in a "refining process" so they can be used in their respective silos. Second, this separation can cause confusion because it can mean some data is duplicated across the LLM wiki and raw data. For instance, we have a customer whose raw data contained expert compiled SOPs and our sleep time agent used that to create a similar skill in the LLM wiki. We think it's best to think of the wiki in this instance as an "index" or "reasoning cache" over the raw data. From that perspective, it's clearer why having duplicate information is not that big of a deal. It's just that in this case, the index is human readable. Third, a lot of the data that is fed into the system is written by LLMs (e.g. Docs in GitHub, Social media posts from influencers, etc.). Garbage in, Garbage out is still very real. In practice, this tends not to be a problem since most information that comes from external systems involves some level of human oversight. Overall, distinguishing between raw data and LLM generated data within our knowledge bases has enabled us to design around the open unsolved challenges in AI memory while still solving for our customer's use-cases.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 1 hour ago

  A researcher pointed 32 Kimi K3 agents at the latest Redis server and told them to find vulnerabilities. 27 minutes later he had a working exploit. For context: Redis is one of the most widely used databases on earth. Twitter, Instagram, GitHub, Snapchat, StackOverflow all use it. If you've ever loaded a feed instantly or seen real-time notifications, Redis was probably behind it. → 32 agents ran in parallel, fuzzing, debugging, and writing exploit code simultaneously → 27 minutes: working proof-of-concept for remote code execution → A follow-up run found 19 more issues in Redis 8.8.0 in under 90 minutes → The repo is public. The exploits are verified. The code works. This is the same model the White House accused of being stolen from Anthropic two days ago. You can argue about where it came from. You can't argue with what it just did.