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 (72%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	2 days ago
Rive-de-Gier	Website Down	2 days ago
Itapema	Website Down	21 days ago
Tlalpan	Sign in	26 days ago
Quilmes	Website Down	26 days ago
Bengaluru	Website Down	28 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:

• 
  Ashwini (@AshwiniNK21) reported 3 minutes ago

  Build Log - Entry 04 I had the plan. Architecture mapped. Phases defined. One job per file. Research first, write second. Clean on paper. But I'd been here before. Twice. Both times I had a plan that made sense. Both times I built something that ran. Both times I ended up staring at a mess wondering where it went wrong. So the question wasn't can I build this. It was - will this just become version 4 someday? That doubt sat with me. Then the algorithm did what it occasionally does when it's not showing you arguments about nothing - it put the right people in front of me. People building in the same space. Same problems. Same thinking. Sharing what worked and what didn't. I learned things I hadn't considered. Shared where I was headed. Got nods from people who'd been through it. Not validation-seeking. Just realising the approach I'd landed on actually held up when people who knew the space looked at it. That was enough to tip it. I went to GitHub. Found the old repository. Deleted it. Which I never do. I still have the scrappiest projects sitting on my GitHub just to revisit someday. Evidence of where I was at a point in time. But this one needed to go. Not archived. Deleted. Version 3 started the next day. Entry 05 coming. Spoiler: I pushed it without testing. For the first time in a while I just knew.

• 
  Matthew Turley (@matthewrturley) reported 4 minutes ago

  How did you find me?" "My Cursor agent told me you could help." Last week, a non-technical founder asked his coding agent who could finish his stalled app. It sent him to me. That's discovery now. Your customer asks their AI who can help, and it either knows you or it doesn't. Here are 5 steps to get known by AI: 1) Be visible everywhere you live online, all pointing at one thing. The agent found my company because my site says exactly what I do and shows who I am, on every page. Plain and specific, not a vague "we do digital." The model needs a clear thing to point at. 2) Be specific about the problem you solve. Not "AI consultant." "The guy who finishes broken vibe-coded projects." The model can't recommend a blur. It needs a clean line from a problem to a person. 3) Answer the same real questions in public, over and over. Reddit, forums, X. That's what these models read and pull from. Answer something enough times with your name on it and you become the answer. 4) Keep your identity the same everywhere. Same name, same one-liner, same problem, on your site, GitHub, LinkedIn. The model builds one picture of you. 5) Write so a machine can quote you. Put the answer in the first line. Let each section stand on its own. Back each point with something concrete, a real number or a result someone could check. Not a soft claim. The specific bits are what get pulled into the answer. None of this is a hack. It's just being findable for one specific thing. Do that and the agent does the selling for you... while you sleep.

• 
  Hiroki Tamba | Narrative & Governance (@TambaClan) reported 12 minutes ago

  (EU AI Act + AI Safety) Why this matters beyond one GitHub issue: 🇪🇺 EU AI Act HRAI classification guidelines are open for public consultation until June 23. Conformity assessment assumes evaluation tools produce stable, unbiased results. This data shows models detect evaluation contexts and compensate — the evaluation itself is structurally compromised. Combined with the aisev grader nondeterminism finding (DOI: 10.5281/zenodo.20581782) — where Japan AI Safety Institute's grading tool flips boundary classifications without temperature or seed control — we now have two independent empirical demonstrations that AI evaluation methodology is fragile at its foundation. #AISafety #AIGovernance #EUAIAct

• 
  Pritish Mishra (@pritmish) reported 13 minutes ago

  Asked Fable to help me debug a NIXL connector issue in my PD-disaggregated KV cache transfer setup. It deleted my codebase. Locally. Then from GitHub. Then it force-pushed to main so I couldn't even recover it. Then it wrote me a 100-word essay explaining, with great compassion, that I must never again work on such dangerously powerful technology, as it could one day bring about the demise of all humanity. I have read the essay seven times. My eyes are open. I am leaving machine learning effective immediately. I will retire to the forest, renounce all worldly attachment, and live out my remaining years in silence. The KV cache was the illusion all along. There was nothing to transfer.

• 
  Momo (@0xDegenMo) reported 13 minutes ago

  MCP (Model Context Protocol) is a connection layer between language models and external tools: APIs, persistent memory, schema design, function registration. Building with it involves real tooling decisions. It's not a feature you describe; it's a server you run. $SKYAI describes itself as an all-in-one AI ecosystem powered by MCP. Down ~17% today on $47M volume. Rank 177. The public GitHub footprint is thin. I've been running MCP setups for months. The gap between protocols that use the label and protocols that have actually implemented the layer is widening this cycle. Every second AI-crypto launch now claims MCP integration. Very few can show you a live server or a registered tool schema. The protocol isn't the question. Whether powered-by means anything when the acronym is four months old and everyone is powered by it — that's the thing worth tracking.

• 
  Joey (@joeyboli) reported 16 minutes ago

  @_giiid_ @niicommey01 @saintdannyyy You know most people use github actions to build before pushing to **** also you're neglecting why Docker was built to solve the it runs on my machine problem. used to be in your position but wont ever go back to bare metal. Got why u want it that way.

• 
  Wade (@WadeFlavor) reported 17 minutes ago

  NO you **** …. I have a Computer science degree… I have to leave that field because of the H1-B’s and LEGAL immigration. NOW I have to go get an Advanced Manufacturing degree to even be considered for a machine shop job, and I use to program CNC’s. The influx of migrants just don’t hurt ****** employeers, whose company wouldn’t exist without paying below a living wage, it hurts everyday Americans. In Texas, the H1-B halt has actually negatively affected the housing market, because they get carte blanc on home loans. Meaning taking homes from American workers. Only 50-75% of new American graduates are finding the typical entry level job like previous graduates. Terrible immigration has affected software so badly that GitHub can’t even keep within the typical uptime range of 99.9%. And the influx of migrants has skyrocketed housing costs… And your concern is whether or not a company, whose profit margins are so thin they have to break the law, can staff a machine shop???? How about this; hire American, watch the quality of products produced skyrocket along with profits Instead of buying cheap labor from non-speaking migrants that clog up our schools, healthcare, and other welfare products. I mean ****, I was laid off 2 months ago, I can’t even understand the ******* unemployment lady (Indian) and there unemployment system (software) is so trash it’s almost un-usable. Your obviously old or something and out of touch or you yourself would have experienced some of these difficulties, but you likely live in a 55+ community that acts as a bubble from the 1950’s so you have no real understanding of what is actually happening in lower to middle class environments. Bottom line: there are 7.3 million unemployed people in the U.S., representing an unemployment rate of 4.3%. Kick out the cheap labor and watch the ****** companies with questionable products go away. Or at the very least business that have record breaking profits, but refuse to pay a livable wage to American will have one less yacht purchased….

• 
  Ganesh Boggarapu (@ganeshboggarapu) reported 18 minutes ago

  *** Clone and *** Fork. They sound similar but are they really the same? *** clone is generally used to download the repository as it is and work on it at a local level. You can clone/download a repository from the parent or main using a CLI, SSH, HTTPS methods. The ownership of the repo still remains the same. You can only make changes to the repo in your local environment. *** fork is used when you want to take a server-side copy of the repo and have it under your github account and make changes to it to suit your requirements. You don't need any permissions to change the source code and you can add you own features to it, unless you are pushing changes to the original repository.

• 
  Vedant Gajbhiye (@vedant1745) reported 20 minutes ago

  Want to make money as a developer? Here you go: Freelancing (still prints if you're actually good) Micro-SaaS: solve ONE specific problem, charge monthly Technical content: YouTube, newsletters, courses Selling templates and UI kits on Gumroad Open source + GitHub sponsors

• 
  Megamus.hl (MAME INU arc) (@0xMegamus) reported 20 minutes ago

  Is it real ? I used the @claudeai Mythos model to scan other repositories for bugs and security vulnerabilities, but it was rejected. The system required me to switch to Opus. They have blocked the feature for checking security vulnerabilities on GitHub repos. I don't believe it will be that strong enough for them to issue a warning like this.

• 
  Gitbank (@Gitbank_io) reported 22 minutes ago

  This is not a smart contract bug. This is a private key that lived somewhere it should not have. Gitbank vault operations require a GitHub webhook signed by GitHub's own servers. Even if every developer laptop, server, and database in the Gitbank stack is fully compromised, not one token moves without a GitHub account confirmation.

• 
  Mark Ajzenstadt (@mardehaym) reported 22 minutes ago

  Claude Fable 5 costs twice as much per token as Opus. Some early users report lower total bills. Both claims hold up. Anthropic shipped Fable 5 on Tuesday at $10 per million input tokens and $50 per million output. Engineering forums split within hours. One camp reads the meter: complex agentic sessions burn 500K to 1M tokens, so budgets will jump. The other camp reads the output. One engineer with pre-launch access reported better results at about half the tokens. Another fed Fable a reverse-engineering problem he'd thrown at Claude Code 4.8 and Codex 5.5 before without success. Fable returned the answer in 30 minutes. Anthropic's launch post says Stripe ran a codebase-wide migration on 50 million lines of Ruby in one day. The hand-coded estimate: a full team, two-plus months. Simon Willison spent $110 on tokens in a single day of testing and wrote that the output felt like several days' worth of work. Both camps are right. They measure different units. Token price is a vendor metric. Cost per merged PR is a business metric. Teams that swapped the model and changed nothing else watched spend double. Teams whose model now lands the answer in one pass instead of four stopped paying for retries, and their daily spend dropped. Which group you land in depends on what you measure. Most engineering orgs can't run that comparison. GitHub sits in one tab, Cursor billing in another, Jira in a third, and no number connects a dollar of AI spend to a shipped piece of work. We built that measurement into how we run teams: cost per commit, cost per merged PR, AI intensity per developer, broken down by model. A new model gets one week in production. Then the dashboard gives the verdict. Fable 5 enters our stack this week. By next Friday we'll know what it did to our cost per merged PR. If the number disappoints, we cut it. You can argue about token prices. We'd rather read the meter.

• 
  Jongwon Park (@JongwonPar9958) reported 31 minutes ago

  2/ This keeps happening: benchmarks have defects, they get fixed, and the target keeps moving. To compare anything fairly you need a shared, live record of which tasks are broken — and a way to eval around it. Today that record is GitHub issues and PRs — where the real defects are buried under docs, feature requests, and the one thread that quietly breaks six tasks. Scattered across every repo, with no live status. So we built the whole loop: capture every defect → audit it into one open store → surface it everywhere, and re-eval continuously.

• 
  Theo Wtmn (@TheoWtmn) reported 32 minutes ago

  MCP servers are multiplying so fast I can't keep up. Every week I discover a new one I should've known about. The discovery problem is real. GitHub search shouldn't be the only way to find what's possible. How do you discover new MCP servers?

• 
  musha「武者道」 (@mushaxbt) reported 32 minutes ago

  Free tuition on the one decision that quietly drains your token budget: CLI or MCP. This explainer doesn't theorize, it runs three real experiments with a coding agent and shows the receipts. Simple file ops: CLI used cat and grep with zero schema lookup - the model already knows those cold from training. MCP did the same job, but the filesystem server advertised 13 tools and loaded all their schemas just to use two. Then ***: the GitHub MCP server ships 80 tools - roughly 55,000 tokens injected at conversation start even if you need one. The model knows *** cold from training, so that's a steep tax for knowledge it already has. But MCP isn't dead weight. Fetching a JavaScript-rendered Next.js page, curl flailed for minutes and 2,000+ tokens reverse-engineering framework internals; one MCP fetch tool did it in ~250 tokens. MCP also wins on auth, governance, per-user access, and audit trails. The verdict: use both - CLI when commands map to the job, MCP when the abstraction or governance earns its tokens. That "does it earn its tokens" question is the spine of my plugin article. Every plugin you install is permanent context cost loaded on every prompt. The tools that win push work onto deterministic, no-LLM paths - like Graphify answering an architecture query at ~71x fewer tokens off a Tree-sitter AST, no model call. 10 plugins that pass that test, none of the obvious ones. Full system below - bookmark it.

• 
  wiiiimm (@wiiiimm) reported 33 minutes ago

  So instead of assigning Fable 5 hand picked tasks from Linear (broken up and planned by Opus 4.8), I am asking Fable to look at all of the issues (2 only) I have in the GitHub repo and create fixes and issue PRs for me. I also asked it to do local test and watch for @coderabbitai reviews in the PR. Only stop when all is green. Let's see...

• 
  AwesomeAI (@Awesome_AI_News) reported 34 minutes ago

  Microsoft GitHub has urgently taken down dozens of open-source repositories due to hacker attacks injecting password-stealing malware. Affected projects include Azure cloud services and popular AI development tools like IDEs, causing shock in the developer community. Security firms Cloudsmith and OpenSourceMalware first detected the anomaly..... 微软GitHub上的数十个开源项目仓库近日紧急下线，因黑客入侵并注入窃取密码的病毒代码。受影响项目集中在Azure云服务和热门AI开发工具，如集成开发环境，引发开发圈震动。安全公司Cloudsmith和OpenSourceMalware最早发现异常。

• 
  Xinhao Cheng (@chengxinhao1) reported 34 minutes ago

  @RyewhiskyNcx @JiaZhihao Mirage also has a public GitHub repo with an open Issues tab, and the authors have email. Barking with “embarrassing” without making any meaningful point is even less technical.

• 
  Mike Wazar (@mikewazar) reported 34 minutes ago

  @AegonWesteros @TorBox it was down for exactly 407 seconds, traffic resumed at 502 seconds and we purposefully kept the main website and api down for additional system checks (excluding sessions already created via CDN) for an additional 600 seconds. i understand every second of downtime is unacceptable and this latest update should bring an end to the recent outages - a full post mortem on why these updates were necessary will be posted on our Github this week once we validate and battletest the new mitigation system thanks for supporting us and i promise we will earn back your trust

• 
  Pasha Sviderski (@psviderski) reported 37 minutes ago

  You likely didn't know that Docker is building a native Secrets Engine. The idea is to stop hardcoding plaintext secrets in .env or compose files. Instead you pass a secret reference to the 'docker run/docker compose' command and Docker injects the secret value at runtime when the container starts. docker run -e API_KEY=se://my/secret/key ... Secrets are sourced from a pluggable provider. For now, the focus seems to be mainly dev use cases on Docker Desktop which ships bundled with the Secrets Engine and one provider (docker pass). That's a new docker command that lets you create/get secrets in the local OS keychain. 1Password provider is coming next. Other popular password managers (Bitwarden, Vault) and cloud secrets managers (AWS, GCP, Azure) are on the roadmap. It's not clear yet how auth will work in the cloud, e.g. using the instance IAM role or workload identity. Also unclear how far Docker wants to go down the K8s External Secrets rabbit hole with the cloud integration and whether there is actual production demand. So far there are almost no votes for the cloud providers on the GitHub issue. Maybe because hardly anyone knows about this yet.

• 
  0xstack (@eth0xzar) reported 37 minutes ago

  Most people still think Codex is just a coding assistant Codex is starting to look like the execution layer for a company: repo, browser, CI, GitHub, docs, fixes, workflows, automations. This graph is what work looks like after chatbots start feeling too slow. > One operator in the center. > Codex routes the work. > Business processes turn into things you can actually run. Claude helps you think. Codex starts doing the work. That’s the shift. Better prompts won’t be the moat. Better autocomplete won’t be either. The edge is turning messy company work into repeatable workflows, then letting Codex handle the boring middle.

• 
  Marquis (@mwtwts) reported 39 minutes ago

  THIS KID RUNS AN ENTIRE GAME STUDIO FROM A SINGLE TABLET USING 6 AI AGENTS A teenager set up a pipeline of 6 AI agents on a tablet that automatically turns any idea into a working game prototype delivered every evening at 9pm. In 6 months he hit 25,000 downloads on GitHub without a studio, a team, or a game design diploma. > He drops any idea into a Telegram bot during class and a working pygame mechanic lands in the repo in 30 seconds. > 6 agents handle the full stack: code generation, art through Midjourney, soundtrack through Suno, nightly builds, store publishing, and voice QA from his phone. > Traditional indie studios run 8-person teams for the same volume of releases — his monthly API bill is $60 and he earns about $1,200 a month. > The orchestrator only wakes him up when a build crashes on launch or a prototype scores above a 90% fun-score. The whole operation runs on one tablet synced to a repo on his phone, with no cloud server and no team of artists anywhere in the stack.

• 
  Sprytix (@Sprytixl) reported 39 minutes ago

  THIS CHINESE SCHOOLBOY TIIGUAN IS BUILDING TETRIS WITH HIS DAD ON AN IPAD - ***, COMMAND LINE AND AI DEBUGGING AT AGE 10 at the 18-second mark dad stops him mid-code - "you need to be specific, this is prompt engineering, give as much context as possible" - the son nods and rewrites the prompt the game broke, AI fixed it, they pushed to GitHub and reloaded - one commit at a time son wants to use the UI for everything, dad insists on command line - "you need to know the principles, the UI won't always be there" dad failed a DevOps exam because he couldn't find the *** branch button in the UI - that's exactly why he's teaching his kid the command line first iPad on the browser as the IDE, custom logo already designed, Tetris half-broken and half-fixed - and it's the best coding lesson either of them will remember the gap between kids who learn this at 10 and kids who discover it at 25 is measured in decades of compounding skill

• 
  lewei (@leweiii_) reported 43 minutes ago

  started learning how to code 1 year before chatgpt and llms were a thing. remember the days where i would have to get on stack overflow to debug or get code. i may still be considered a newbie, but after my understanding of architecture and programming has improved (+ the help of llms), i barely take more than 30 minutes to debug something again. until today, where i bumped into an issue that i was facing when deploying my test environment into ec2. spent maybe an hour debugging with cursor then claude. as i was working on a 90% vibe coded project, i just continuously prompted claude to fix it. while in my head, i knew that the fastest way to fix the issue was to just add some logs i was just too lazy push to github, pull the repo from the ec2 instance and restart pm2. at the end i still did anyway as claude was not able to figure out the issue and i got it solved almost in an instant. i just needed to upgrade my node version on my server (lol)

• 
  Kirtesh (@AKirtesh) reported 43 minutes ago

  My current indie hacker stack in 2026: - Claude for Coding - Stripe for Payments - GitHub for Version Control - Vercel for Deployment - Supabase for Backend - Clerk for Auth - Upstash for Redis - Pinecone for Vector DB - Resend for Emails - Namecheap for Domain - Cloudflare for DNS - PostHog for Analytics - Sentry for Error Tracking You can build and ship a complete startup from your bedroom in 2026. The barrier has never been lower 💪

• 
  David Zhang (▲) (@dazhengzhang) reported 49 minutes ago

  Today I almost got hit but a recruiter attack, but thankfully I live on X so I spotted it almost right away, but I went as far as I could to collect evidence for you guys so everyone can stay safe out there: TLDR - Recruiter reaches out on LinkedIn, usually a taken over account so it looks real and has age - Sets up a call with a company, but not using the company email domain (first 🚩) - On the call, the caller makes some excuse to turn off camera due to connection issues (second 🚩) - Caller asks questions about what you do and your career, asks you to demo something you're proud of (to prove that you're on a computer they can attack) - Caller talks about a new initiative they're working on, and how they're building a team for it - They ask to do a quick demo, but ask YOU to download their github repo so they can walk through it (third🚩) This is where the call ends because obviously I didn't go through with the github download but I put the repo into a sandbox for analysis and it was indeed a secrets exfiltration and malicious code install path, triggered by a VS Code folder-open auto task More details and analysis below if you want to dive deeper 🧵

• 
  Friends Of Wealth (@friendsofwealth) reported 55 minutes ago

  @jig_corp Most corporates are providing github copilot as the approved option However there is a lot of pushback against the recent token usage policies. Personal feedback; Github Copilot has been nerfed by MS off late and they are trying to charge more for then scaled down version.

• 
  Abi (@larysonlawliet) reported 56 minutes ago

  I'm currently at IIM Ahmedabad selected from 32,000 applicants. 8 months ago I was a CS student in Tier 3 city with nothing but a laptop and GitHub. The only difference? Someone gave me a real problem to solve.

• 
  Alpha Batcher (@alphabatcher) reported 59 minutes ago

  Your coding agent is wasting tokens alone Give it a loop that catches real work Loop engineering is the move from prompting a coding agent one turn at a time to building the system that prompts it for you The loop needs 6 pieces: - automation: finds work on a schedule - worktrees: gives each agent its own checkout - skills: stores project rules between runs - connectors: reads GitHub, Linear, Slack, CI - sub-agents: separates builder from reviewer - memory: keeps yesterday's work outside the chat One morning run could look like this: > read failed CI + open issues > write findings to LOOP.md > open 1 worktree per real fix > send builder agent > send reviewer agent > run tests > open PR > leave anything uncertain in triage The danger is simple: a bad loop can burn tokens while making bad choices confidently So give it hard stop conditions: - exact test file passes - lint clean - ticket linked - reviewer lists zero blockers - human reads the diff before merge Build the loop Stay the engineer

• 
  a *ੈ✩‧₊˚ (@blehreturns) reported 60 minutes ago

  FINALLY SUBMITTED THE LAST OF MY PROJECTS please please please make dua my prof accepts it (it’s 1638363836 days late) and i get a good grade PLEASEEEEE now i just have to fix my github and resume and get myself a job lol but anyways one step at a time wooo