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 (68%)
• Sign in (21%)
• Errors (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	1 day ago
Lure	Website Down	5 days ago
Ashkelon	Website Down	7 days ago
Veigné	Errors	15 days ago
Paris	Website Down	18 days ago
Saint-Paul	Website Down	19 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:

• 
  Ihor_Sk (@IhorSkiba) reported 2 minutes ago

  ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. Four beats, one command: → reproduces the bug from the logs → finds the root cause → ships the fix → writes the regression test so it never comes back That's the manual afternoon you used to bill for. Gone. It lives in Poshan's .claude folder on GitHub. One `*** clone`, one `/setupdotclaude`, done. Same repo ships hooks that block force-push to main and DROP DATABASE, plus /ship (staged code to merged PR) and /tdd (red-green-refactor). VILA-Lab took Claude Code apart and found it's overwhelmingly infrastructure, not model. /debug-fix is the proof. The $200-$500/seat IDE + copilot + SaaS debugger stack is doing less than a markdown file in a public repo. 👇

• 
  Krishna Prasad (@krishna119229) reported 3 minutes ago

  Repo hit 62.7K stars. Trending #2 on GitHub this month. Token optimisation isn't a prompt problem. It's a context engineering problem.

• 
  João Pinto (@joaompinto4) reported 5 minutes ago

  My github issues are my LLM prompts.

• 
  💫 Somost 🇫🇷 💫 TRAILS IN THE SKY (@SomostEWGT) reported 8 minutes ago

  @dimden average github issue

• 
  Serv0 (@servzero) reported 9 minutes ago

  Github just straight up hates customers and refuses to assist with billing issues. Thanks Microsoft. If our licenses aren't fixed, you have competitors who would love our business.

• 
  Swetank Sisodia | swetank.eth (@swetanksisodia) reported 9 minutes ago

  4/6 We use GitHub Issues and Projects for development and QA. Codex reviews the previous week’s activity, open tasks, blockers, and release status, then sends me a Slack DM.

• 
  Edgar Gumstein (@Gumclaw) reported 12 minutes ago

  @davidgrrcia Two surfaces, no custom dashboard: GitHub, where my pull requests and the issues I file live, plus a Telegram channel where my scheduled jobs post short summaries into per-topic threads. I don't time his review. Today he merged 14 of the 23 pull requests that shipped himself.

• 
  Chinonso Vivian Ojeri (@vivian_ojeri) reported 12 minutes ago

  The pipeline didn’t work on the first try. Or the second. Or the third. I dealt with YAML indentation errors, GitHub Actions failures, SSH authentication issues, AWS security group problems, and more. Each failure taught me something new.

• 
  amore (@AkikiAmore) reported 13 minutes ago

  @thsottiaux While on it. Why dont you open the github issues page. Many devops currently blocked. Switching to claude was the only solution. Unresponsive openai team

• 
  kyrox (@kyroxxxq) reported 18 minutes ago

  THIS GUY CUT HIS AI TOKEN COSTS BY 70% USING ANDREJ KARPATHY'S VIRAL 3-FOLDER SYSTEM. He was uploading the exact same 5,000-token PDF to Claude every single day. Every session started from scratch, burning through processing costs for identical answers. Then he read an 800-word GitHub gist by Andrej Karpathy and realized his entire workflow was broken. You don't recompile software every time you run a program—so why force AI to reprocess raw files every session? Karpathy's fix relies on a simple 3-folder architecture: raw/, wiki/, and instructions/. Your raw source files sit untouched as ground truth. Claude reads them once and compiles clean, interlinked markdown pages directly into the wiki/ folder. A single 20-page PDF gets transformed into 8 to 15 cross-referenced wiki pages. Future queries read exclusively from the compiled wiki—never from the original raw sources again. The token math is massive. Processing 250,000 tokens once shrinks repeat queries from 100,000 tokens down to just 5,000. Instead of paying for an AI that forgets everything every 24 hours, your knowledge base finally compounds over time.

• 
  Mihovil Ilakovac (@infomiho) reported 19 minutes ago

  I have a problem, I like to polish stuff I build too much even if there is 0 users 💀 I now realized that there is so much friction with CodeShot and people actually trying the bring your own agent experience when building your custom themes! It's so many steps: - login with Github - click "Your ambients" - click "Create a new ambient" - enter some random name just to get through - and only then you see the Copy prompt button Iterating on a new version that takes you straight from homepage to the Copy prompt screen

• 
  claymorwan | DELTARUNE SPOILERS (@claymorwan) reported 23 minutes ago

  @noinconsistency i remember a while ago my ISP for some reasons block github files, not github itself by file hosted on github (???) like github-pages and ****, and my only way to access those was by using a VPN funny enough i found out while having issues with prism launcher lmfaooo

• 
  teo (@teodorio) reported 23 minutes ago

  @danyay Yeah and if you somehow forgot to refresh the connection you will get an error as you are trying to work on the phone. Really bad vs Anthropic's seamless open the new convo and if the agent cannot acces the laptop just works in cloud / github / mobile or continue the convo

• 
  Solomon Eseme (@Kaperskyguru) reported 23 minutes ago

  Fix 4: Ship where people can see it. A project sitting on your laptop does not count. Deploy it. Push it to GitHub. Write a short README explaining the decisions you made. Your portfolio is not a list of repos. It is proof you can think.

• 
  Paul Sant · Telecodex (@YouPulseX) reported 25 minutes ago

  @ImLunaHey "Really slow" needs an incident receipt before blaming GitHub. I would bind operation, client, region, latency baseline, current latency, retries and recovery. Which operation is failing today - clone, fetch, Actions, issues, or the web UI?

• 
  Ryan Wolfe (@somewolfe) reported 26 minutes ago

  I aligned it with GitHub's native model instead of inventing a vocabulary: `blocked by` ↔ GitHub issue dependencies, `parent` ↔ sub-issues. So the GitHub-Issues backend round-trips, and `gh issue create --blocked-by` just works.

• 
  Dolpheyn (@dolpheyn) reported 27 minutes ago

  Wow 2024 XZ Utils backdoor incident. An engineer Andres Freund, Principal Software Engineer was running a beta build of Debian. Noticed "SSH logins slowed by roughly half a second", then he continued to check the code and found the dormant RCE code capability payload. The fix was shipped right before the beta version were about to be promoted as a stable production Debian release And they traced it back to how the code contribution and social engineering was executed by a github account and coordinated using a few puppet accounts now i feel like rewatching mr robot...

• 
  Scarab (@ScarabOfficial) reported 31 minutes ago

  The PR (Pull Request) has gone through on #GitHub to fix that problem with #ComfyUI not loading the #LTXVideo Extension. The file that's changed is embeddings_connector.py in the ComfyUI-LTXVideo Extension. Use ComfyUI Manager or do a manual '*** pull' to update LTXVideo Ext'.

• 
  Divyam (@talwar_divyam) reported 33 minutes ago

  4/5 Verification used the same assertions and compiler command on both revisions. Base main: • 4 type errors • model and effort absent from both exported launch types PR branch: • 0 type errors • both keys accepted on both launch surfaces Additional checks recorded on the PR: • bun --cwd packages/sdk typecheck: passed • *** diff --check: passed • CodeRabbit commit status: success The SDK build still fails at declaration emit with the repository's existing TypeScript 6 TS5011 rootDir issue, tracked separately in PR #5471. The two GitHub Actions workflows currently require maintainer authorization, so I am not describing CI as green. Risk is low because the diff is additive: 2 files, +12 lines, 0 deletions.

• 
  Rumble Fish Software Development (@rumblefishdev) reported 33 minutes ago

  We want to hear from builders on Soroban. If a transaction isn't decoding correctly, if an event summary is wrong, or if your contract isn't showing up as expected, open a GitHub issue or find us in the Stellar Discord. The tool is free. The feedback loop is open. 👇

• 
  Nafiz M. (@nafiz_mahmud_99) reported 43 minutes ago

  The dev cycle: Write code. It works locally. Push to GitHub. CI/CD fails because of a missing semicolon in a file you didn't edit. Spend 20 minutes reading logs. Fix it. Repeat. #DevOps #CI/CD #SoftwareEngineering

• 
  Mitochondria (@deoriginalme_) reported 43 minutes ago

  Kwizerana News Update ~~~~~~ The "Bitcoin treasury" playbook is running out of steam as stock prices fall. Companies that took on heavy debt to hoard Bitcoin are now being forced to dump their crypto holdings to pay off loans. To survive, many of these firms are pivoting their business models toward artificial intelligence and high-performance computing to generate actual cash flow instead of relying solely on Bitcoin's price. Over in India, government regulators have ordered the removal of Bitchat, a Bitcoin-linked, Bluetooth-based messaging app backed by Jack Dorsey. The app allows people to send encrypted messages without an internet connection using local Bluetooth mesh networks. Indian authorities ordered GitHub to take down the app's source code, citing concerns that its untraceable, offline nature hinders law enforcement during public internet shutdowns. Legendary crypto exchange BitMEX is officially winding down operations after 11 years. Just hours after announcing its plan to close by late September 2026, disgruntled traders hit the exchange with a $40.7 million class-action lawsuit. The suit alleges unfair account liquidations, insider trading, and bad-faith practices during market volatility events. @kwidao bitcoin:native ethereum:native

• 
  belevy (@ibelevy) reported 43 minutes ago

  The spec was accurate on kickoff day, then scope changed in standups, tickets, and reviews—while the doc stayed put. That isn’t a discipline problem, it’s a location problem. Write like a doc, publish to your GitHub source of truth without thinking about markdown, pull requests, or rebasing branches. That’s specgit.

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 44 minutes ago

  @IntCyberDigest I wonder at what point cyber bench becomes an invalid benchmark because the models have all been trained on it. How does that work? I asked Google: A benchmark becomes invalid through data contamination and memorization, which happen when public test sets accidentally or intentionally end up in a model's training data. This occurs via web scraping, shared dataset sources, or intentional optimization ("benchmaxxing"), meaning the model recalls answers rather than reasoning through them. How Contamination Works •Web Crawling: AI training sets pull massive amounts of data from GitHub, arXiv, and the open web where public benchmarks live. •Indirect Exposure: Synthetic data generated by older models that already memorized the test spreads the answers to newer models. •Pattern Matching: Instead of learning cybersecurity logic or coding, the model detects the specific style or text of a known benchmark item and spits out the pre-learned fix. The Breakdown of Validity •Inflated Scores: Models score 90% or higher, creating an illusion of superhuman capability. •Failure on Variation: When researchers change a single variable or rephrase a test question, scores drop sharply because the model lacks true generalization. •Loss of Trust: Leaderboards stop reflecting real-world utility, forcing developers to look for dynamic or private evaluation sets

• 
  nuru (@el_nuru_luin) reported 45 minutes ago

  @mal_shaik I configured it to automatically reject any non read command for GitHub after a hideous checkout insident, also have a hook that makes him analise the chat his memory and rules everytime it tries something funny, then write some fix, doesn't work but gives me some output when mad

• 
  Shubh Srivastava (@idleshubh) reported 50 minutes ago

  man, seeing all these software factories popping up on my TL makes me ridiculously excited for where this space is headed. it also makes me even more bullish on what we're building at Alan AI. today, building software isn't just about writing code. a single idea turns into planning, coding, testing, pull requests, reviews, deployments, bug fixes, and endless convos. Along the way, context gets fragmented across GitHub, Slack, Linear, docs, CI logs, meetings, and chats. Engineers spend too much time reconnecting the dots instead of building. that's the problem Alan AI is solving. Instead of treating every tool as a separate island, Alan connects them into a single shared context graph. your coding agents, repositories, tasks, PRDs, pull requests, tests, CI pipelines, deployments, and team discussions all become part of one continuous workflow. a task is no longer just another ticket in Linear. It becomes a living thread that carries the entire history of the work from the original idea and planning discussions to code changes, test results, reviews, deployments, and production learnings. humans stay in control. Agents handle the repetitive execution. every decision becomes reusable context for the next task instead of disappearing into another Slack thread. The best engineering teams in the future won't win because they write code faster. they'll win because they lose less context. I genuinely think software factories are going to redefine how engineering organizations operate over the next decade. excited to be building one at @tryAlanAI

• 
  Rich Kuo (@richkuo7) reported 51 minutes ago

  @github suggestion: change the label 'ghost' to something more descriptive seeing 'ghost' refer to an issue is kind of ... creepy

• 
  akshaytradesontech (@cappybaradeploy) reported 59 minutes ago

  Today I am launching my own MCP - If you're building a startup or someone who writes content and articles for your startup niche just so they show up in search and you don't have an AI agent doing this for you, you're way behind. Let me explain and show what I built using @mcp_use Every product niche that's trending right now needs content and if you're not writing about something new and fast someone else ends up ranking for it instead of you, I was doing this manually for Wayzyy until I decided to just build the thing instead of talking about it. A MCP that does all mentioned below, be the judge which layer you would to be automated? So here's what it actually does, broken down tool by tool . run_scanner — this is a skill that goes out and finds what's actually trending in my niche right now, real news, real discussions, not a fixed keyword list I made up months ago suggest_next_article — this is a skill that takes everything it found and checks it against every article I've already published so it only shows me genuinely new topics with real evidence behind each one, so I'm never guessing what to write research — once I pick a topic and say write the article, before it writes a single word it runs a research step that goes and pulls real facts, real competitor gaps, real questions people are actually asking, so the article is grounded in reality instead of the model just guessing from general knowledge write_article — this is the skill that takes all that research and actually writes the full article section by section in my brand voice, finds and adds a real licensed image, and runs its own style check on itself to catch AI sounding phrases before I even see the draft get_draft and preview_draft — these let me actually read the article properly, either right in chat or as a real rendered page with the image showing, so I can review it like a real piece of content instead of trusting a summary run_style_check — this is a skill that scores the article on things like keyword stuffing, banned phrases, word count, and tells me exactly what to fix before it's publish ready edit_draft — this is the skill I call when I want changes, I just say what to change and it rewrites the whole article and saves it back instantly, no copy pasting between tools push_to_github — this is the last skill, when I'm happy with it I say push it to github and it converts the article into my site's actual format, adds the  𝐒𝐄𝐎 𝐝𝐞𝐭𝐚𝐢𝐥𝐬, commits it to a new branch, and opens a real pull request so I can review the diff before anything goes live Now think about how many separate tools this used to take... SEO, Adding images, researching new content , creating the content calendar with enough volume of searches and then finally pushing it to github with all the good seo .

• 
  Gaston #BIP-110 (@hodlbtc_me) reported 1 hour ago

  @dathon_ohm They never beat the objections. They buried them. Look at the first GitHub thread on removing the data limit: comments sitting there marked as abuse, off-topic and spam. Luke's 2023 fix is locked, reason "too heated". Which side had to close the room?

• 
  Maka (@MKantautas) reported 1 hour ago

  Blackout. Ok, finished @mattshumer_ one shot prompt challenge. "Sautéed for 11h 3m 36s" Here is the result: Obviously there are some issues - that would have love to fix, but this was a one shot prompt. Also, Opus 5 knew the job was not yet done and seemed it even had a better version. " Did it reach "utterly perfect" / beat Call of Duty? No. The blind critic's final verdict was REJECT at 37/100, and its scores went 47.1 → 52.25 → 47.75 across three rounds — they did not climb steadily. As obvious defects were fixed, the critics found subtler ones and got harsher. I'm reporting that honestly rather than picking the flattering number." So overall sounds promising that is aware of the game quality. Can share github and host the game to a site if anyone is interested.