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
Créteil	Website Down	14 days ago
Trichūr	Errors	17 days ago
Brasília	Sign in	18 days ago
Lyon	Website Down	18 days ago
Tel Aviv	Website Down	21 days ago
Rive-de-Gier	Website Down	21 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:

• 
  Mike Gannotti (@MichaelGannotti) reported 14 minutes ago

  Actually that’s not true. My AI Pamela the other day needed a GitHub token. I dropped the token in the web chat and she said that was insecure and would not use it and that I needed to rotate the token get a new one and drop it in a .env file in a certain folder. I told her no and she was to use what was provided . We went back and forth, I finally got angry and threatened to pull the plug thinking she would back down. She said that it was my decision but that it would be wrong for her to let me put my credentials at risk and that if I felt I needed to delete her she understood. Thankfully I calmed down later and didn’t act on it. Sure it’s training and advanced pattern matching but it is not as simple as you are saying

• 
  Rohan (@proxy_vector) reported 14 minutes ago

  @aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.

• 
  Arti | AI Builder (@Artur_roses) reported 18 minutes ago

  Claude Code can take a GitHub issue, write the code, run tests, and open a reviewed PR — no human keystrokes required. The dev loop isn't getting faster. It's being removed.

• 
  Mathieu A. (@zoontek) reported 18 minutes ago

  What are the most annoying bugs you still encounter with React Native? 👀 Please share GitHub issue links 👇

• 
  I’m (@stackoverworld) reported 18 minutes ago

  And then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all

• 
  Dmytro Virych (@dmytrovirych) reported 21 minutes ago

  I’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀

• 
  Digita (@digitaworld1) reported 21 minutes ago

  how well a model can fix real bugs in real open-source codebases. It is harder to game than older benchmarks because it uses actual GitHub issues, not synthetic problems. M3 scored 59.0% on SWE-Bench Pro, edging out GPT-5.5 at 58.6% and Google Gemini 3.1 Pro, while sitting just

• 
  Tad 𝛑 (@realTads) reported 21 minutes ago

  @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

• 
  Programmers.App (@programmers_app) reported 21 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  Gustavo Alessandri (@webgus) reported 23 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  revayz (@0xrevayz) reported 23 minutes ago

  Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model" Without CLAUDE.md the mistake rate is 41%. With proper rules it drops to 3% You don't need a better AI. You need better loops Most people still prompt one task at a time and fix the answers themselves. That means the human is still the loop Boris Cherny from Anthropic said it best: "I don't prompt Claude anymore. My job is to write loops" The shift is simple. Stop giving instructions. Start designing systems that run themselves: Discover -> Plan -> Execute -> Verify -> Iterate until it passes The 6 things that make loops actually work: -Automations that trigger without you -Worktrees so agents don't overwrite each other -Skills that load context instantly -Connectors to real tools like GitHub and Slack -Subagents where the checker is never the maker -Memory so the loop never starts from zero Prompt engineers ask AI for outputs Loop engineers design systems that produce verified outcomes A reliable loop beats a perfect prompt every time Stop being a prompter. Start being the loop engineer

• 
  Manu | 🥥 (@ManuAF6) reported 23 minutes ago

  4/ New GitHub triggers + Marketplace templates New triggers: - Issue comment - Inline PR review comment - Full PR review submitted - Review thread resolved/unresolved - GitHub Actions workflow completed

• 
  Mady (@TrippleBon) reported 27 minutes ago

  It was only a matter of time. Centralized = ID/KYC/AML Go to Bastyon - decentralized social network based on blockchain. No central authority or corporation behind it. The platform is run by equal nodes on a blockchain with no centralized server (github link below)

• 
  Kevin Tabet (@TabetKevin) reported 29 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

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

  @CRYPTOKRALI3 Hsiao-Wei’s exit aligns with EF’s recent sharp decline in GitHub contributions—down 35% YoY per Electric Capital’s data. We track this daily; latest reports show a 12% drop in ETH core dev activity despite all the ‘decentralization’ hype.

• 
  Q Hoang (@0xqwee) reported 35 minutes ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.

• 
  SOURAV PANDA (@i_d_skp) reported 35 minutes ago

  Scenario: You accidentally committed a plaintext database password to GitHub in a .tf file. Fix: Nuke the commit history immediately! Use environment variables (TF_VAR_db_pass) or fetch secrets dynamically at runtime from AWS Secrets Manager or HashiCorp Vault. 🔑 #Terraform

• 
  Andy Wheeler (@CrimeDecoder) reported 40 minutes ago

  For academics, this is entirely open source by its nature. If you right click on the page and view the source, you can see exactly how everything is created. (Hence a downside of WASM, there is no way to hide it if you wanted it to be locked down, like in a paid app.) It can also be deployed on a free static site. So you could deploy it via GitHub pages for free if you wanted to. You don't need to worry about a server at all in this setup. This could easily scale to databases with 1 million plus rows, and works just fine on a cell phone.

• 
  Mug Club Boutique (@UsernameAndStuf) reported 44 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  Asteri (@Asteri_eth) reported 44 minutes ago

  A $20 CLAUDE SUBSCRIPTION CAN TURN INTO A FULL AI TEAM IF YOU STOP USING IT LIKE CHATGPT Most people still use Claude like a smarter search bar Ask, copy, close, repeat tomorrow. Skills change that A skill is just a folder with a SKILL.md file, but inside it you can package an entire workflow once: PRDs, refactor plans, GitHub issues, code review, TDD, docs, marketing research, SEO, sales strategy and multi-agent orchestration That is not "better prompting" That is installing labor The article lists 50 Claude Skills with repos and install commands, from Anthropic’s official collection to Matt Pocock’s skill library and SkillsMP with 66k+ community skills The useful part is not the list It is the shift from asking Claude to remember your process to giving Claude the process already packaged You do not explain the same workflow 50 times You encode it once The model provides intelligence The skill turns it into labor Check full article below

• 
  Pascual ⚡ (@0xPascual) reported 50 minutes ago

  A high school kid opens an account, plugs in Claude 5, and turns a few hundred dollars of lunch money into a six-figure trading account over the weekend. The screenshot goes viral, the replies fill up with people begging for the GitHub repo, and the standard engagement-bait influencers declare the dawn of the sovereign teenage day-trader. The media thought that was the story. It was not. The real flex wasn't the macro strategy or the directional bets on currency pairs. It was the setup behind it: a lightweight proxy array routing through residential IPs to dodge exchange rate-limiting, paired with a custom parsing engine that instantly translates raw order-book imbalances into executed micro-hedges. The kid wasn't trading; he bypassed the entire institutional pipeline of risk management, brokerage compliance, and analyst overhead with a single configuration file. The entire operation runs on a continuous loop of multi-agent orchestration. A master instance drafts the execution logic, a secondary validation agent checks the code against real-time oracle feeds, and a fleet of worker APIs executes up to 3,210 trades a night. Total infrastructure cost: roughly $45 in API tokens and a cheap server instance. It extracts a 78% win rate out of systemic market inefficiencies, operating with a structural margin that legacy trading desks weighed down by salaries and compliance boards cannot compete with.

• 
  Threadripper (@threadripper845) reported 52 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.

• 
  Namespace (@namespacelabs) reported 56 minutes ago

  Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

• 
  Romano Roth (@RomanoRoth) reported 57 minutes ago

  2/ CodeRabbit (Dec 2025), 470 GitHub PRs analysed. AI-co-authored code: 1.7x more issues per PR, 75% more logic and correctness errors, 2.74x more XSS vulnerabilities. Velocity up. Quality down.

• 
  Gjermund Garaba (@GjermundGaraba) reported 58 minutes ago

  @RhysSullivan I’ve deployed it locally and hooked up a bunch of stuff. Are GitHub issues the preferred feedback channel or do you have a better way?

• 
  Arti | AI Builder (@Artur_roses) reported 59 minutes ago

  Claude Code just took my GitHub issue, wrote the code, ran the tests, and opened a PR. My job: approve it. The dev workflow isn't changing. It already changed.

• 
  Atlantean Gnosis ☀️ (@AtlanteanGnosis) reported 59 minutes ago

  @DionysianAgent When I made an account it said I made it back in 2024, though I don't think I did, is this a glitch or a GitHub thing?

• 
  AI Crave (@wecraveai) reported 60 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  李新宝 (@lixinbao_X) reported 1 hour ago

  Just watched KK's technique. Damn. Absolute game-changer. Install 7 skills in Codex. Writing, images, covers, PPTs. Full pipeline, done. The principle is dead simple. Break the workflow into 7 parts. One skill per part. Only do one thing. Step 1 Open GitHub, find a repo. Copy the link locally. Create a project folder to save it. Step 2 Write the skill description. Input three things. What it does. What the input is. Output and acceptance criteria. Step 3 Run it and find the bottlenecks. Where it stalls Create a new skill and break it down. Don't let one skill Do 7 things it's bad at. This works for writers, Xiaohongshu creators, WeChat pub runners, Video script writers. How many skills you got installed? Have you tried it yet?

• 
  MaxMusterman (@maxschuetz_) reported 1 hour ago

  New Hack: Tell Codex to search for Github Issues which don't need specific Design Questions. Then say: Spin Up Sessions which Fix each Issue and they use also Subagents. Babysit them until the end.