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 (71%)
• Sign in (16%)
• 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	9 days ago
Trichūr	Errors	12 days ago
Brasília	Sign in	13 days ago
Lyon	Website Down	13 days ago
Tel Aviv	Website Down	17 days ago
Rive-de-Gier	Website Down	17 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:

• 
  Sudeep Srivastava (@sudeepsriv) reported 4 minutes ago

  GitHub might finally have a serious competitor. And it’s from Cursor. Most people know Cursor as an AI code editor. But Cursor Origin is much bigger. It’s trying to become an AI-native alternative to GitHub where AI agents don’t just help write code. They help build entire products. Think: • Source control • AI coding agents • Code review • Project understanding • Team collaboration all inside one workflow. Why developers are paying attention: Instead of manually searching through repositories, you can tell AI: • Fix this bug • Build this feature • Refactor this project • Investigate an issue • Ship a working version And AI handles much of the execution. The bigger shift: GitHub was built for humans writing code. Cursor Origin is being built for humans managing AI agents that write code. That’s a completely different future. We’re moving from: Human → Code to Human → AI Agent → Code My take: If GitHub defined the software era, Cursor Origin could help define the AI-native development era. And that’s why Elon Musk acquiring Cursor would be huge. xAI would gain: • AI models • Compute infrastructure • Coding agents • A developer platform That’s not just buying a product. That’s owning a major piece of how future software gets built.

• 
  Nikolay Konovalov (@br11k_dev) reported 5 minutes ago

  @Tristanrhee3 And GitHub sponsors thingy is so slow I submitted it like a week ago. Still not approved what the hell My expenses arent terribly high but Warsaw rent is like $2k/mo $500 ZUS $1.5k groceries for two people That’s pretty much it I wish I could move into low cost area but moving out is gonna cost a lot because 2x rent price deposit, so I have to suck it up Anyway, my plan is Upwork and finishing my job tracker so I can send faster than 5 applications a day. I refuse to send out 100 applications per day like some people do spray and pay It makes everyone miserable. If people aren’t hiring your spam doesnt make things better You just mopping floors and hiring problem sits above you, 3 floors up there leaky faucet you can’t even reach This has to be collective effort to fix this problem But we have to start with ourselves and stop spamming applications at least And do genuine company research, being responsible Thanks for reading.

• 
  Nirvaan rohira (@nirvaan_rohira) reported 7 minutes ago

  PewDiePie shipped Odysseus to 110 million people who don't care about local LLMs. They care that Claude costs money. 30K stars in 48 hours because every self-hosted project before this one started with "you want local LLM, right?" This one started with "here's a free workspace that works." Friction was never technical. It was the asking. Now watch what happens when a hundred thousand people who've never touched open source start running inference on their machines. The real distribution problem wasn't GitHub. It was YouTube. That's not a product launch. That's a category shift.

• 
  Jason Bloomer (@JasonABloomer) reported 11 minutes ago

  @yagiznizipli Pffff, what a scam Let me fix your advert; "show us your github so we can scrape all your repos and train our AI on your code, only for any decent ideas you've had to be taken from you and made ours, then handed off to our legal team to crush you." Sorry, I value my work.

• 
  Shubham Sharma | AI & Tech (@editxshub) reported 11 minutes ago

  Paying $19/month for GitHub Copilot? Cascade is free. What you actually get: → Inline completions — not stripped down → Autonomous debugging → Real-time assistance → Command execution Other free alternatives most devs have never tried: → Cline — autonomous VS Code agent (open source) → Aider — terminal-first, built for *** workflows → Continue — local LLMs, data stays on your machine 12 months ago: Copilot was the only serious option. Today: 4 real free alternatives. Most teams paying for Copilot haven't tested any of these. 30 minutes could change a year of costs. Which one are you testing?

• 
  Maurice Heumann (@momo5502) reported 16 minutes ago

  @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

• 
  Ant A. 🇺🇸 (@AntDX316) reported 16 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  Deepesh Kalura (@KaluraDeepesh) reported 17 minutes ago

  Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

• 
  pratik.eth (@eth_ethpratik) reported 18 minutes ago

  @Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.

• 
  Romano Roth (@RomanoRoth) reported 23 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.

• 
  ƒrαeყ (@fraey0) reported 24 minutes ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?

• 
  nasuy (@n_asuy) reported 25 minutes ago

  i think @xai should be ADE. now they have a chat, cursor, enough coding models and harnesses, strong signal like bookmarks or down votes, video creatives, profile / chat / relationship contexts. if so, we don't have to depend on discord or any chat apps. easy to invite x people to cowork. there is no need to connect Linear, Slack, or GitHub to another platform and ask that platform to solve their problems. true AI chat is a SNS, not a single UI. there is a UX that only xAI can realistically build in the world.

• 
  Ucupaint 🔶 (@ucupaint) reported 30 minutes ago

  @iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.

• 
  Moez Zhioua (@MoezZhioua) reported 31 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  Gitbank (@Gitbank_io) reported 34 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  Muhammed Mukthar (@MuktharBuilds) reported 34 minutes ago

  @railway_status i am trying for some time i am not able to sign in using any github google or email. i tried both my lap and my phone is thishappening only for me? or any problem in your end

• 
  Dmytro Virych (@dmytrovirych) reported 38 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.” 🚀

• 
  Noonien Soong (@mlcarldev) reported 39 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

• 
  Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported 39 minutes ago

  Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax

• 
  Trace Cohen (@Trace_Cohen) reported 41 minutes ago

  Shipping fast means stuff breaks silently - broken share images, dead links, leaking {{template}} vars, stale content. You find out when someone shares a broken link, not from a test. So I built a 3-part "site health" system that catches it first. The auditor (~200 lines of stdlib Python) fetches my sitemap and, for every page, checks: og:image actually resolves to a real image (entity-decode the URL first — & bit me), <title> exists and isn't a ${template} leak, no {{merge_tags}} or tracking cruft in the visible text, page returns 200 (catches dead routes in the sitemap), and warns on thin content. Outputs a JSON report, exits non-zero on any FAIL. The dashboard — a noindexed /health page that reads that JSON and renders a green/amber/red status, KPIs (audited / clean / warnings / failures), a per-section rollup, and the exact issue on each URL. One glance = "is everything green?" The loop — a GitHub Action runs the auditor 2×/day + on-demand, commits the fresh report (so the dashboard stays live), and fails the run on any FAIL → I get emailed. Find → fix → re-run → confirm green. It even taught me to whitelist false positives ({{firstName}} is legit on a cold-email page). Want your own? Paste this into Claude Code / Cursor — it learns your site first, then builds it for you: Build a site-health system tailored to MY site. Don't assume my structure — learn it first, then fill in the specifics yourself. PHASE 0 — LEARN MY SITE (before writing code): detect my framework/host/layout; find my sitemap; sample ~20-30 live pages across the sections you discover from my URL structure; figure out how my pages set <title>/og:image/meta (static?dynamic OG route? CMS?); identify where my content comes from (hand-written, generated, imported/scraped) — that's where cruft hides. Do a FIRST diagnostic pass and SHOW me what's actually broken vs intentional (broken OG images, dead sitemap routes, leaking {{vars}}/${template}, tracking params, thin pages). Ask me to confirm which "issues" are expected so we whitelist them. PHASE 1 — BUILD IT, customized to what you found: 1) scripts/site-audit.py (stdlib only) — hardcode MY real sitemap URL, MY section names (full-audit the important ones, sample the rest), and MY intentional-pattern whitelist from Phase 0. Check each page for the failure modes you actually observed (OG image resolves to a real image, entity-decode first; title present, no template leak; no leaking merge tags/ad params in visible text; HTTP 200; thin-content warn). Thread-pooled, retry transient errors once, --json report, exit 1 on FAIL. 2) a noindex /health dashboard reading that JSON (status banner, KPIs, per-section rollup, issue list) — match my design system. 3) CI (GitHub Action) — run 2x/day + on-demand, commit the fresh report so the dashboard stays live, fail the run on any FAIL. Then run it once and walk me through the first real report. Build the thing that watches the things.

• 
  Tim Spalding 🇺🇦 (@librarythingtim) reported 41 minutes ago

  @justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.

• 
  0xstack (@eth0xzar) reported 42 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  ./can (@shcansh) reported 43 minutes ago

  GitHub forcing safer defaults in actions/checkout v7 is a necessary move to kill the notorious pwn request, but the real risk is developers blindly copy-pasting the bypass flag to quiet build failures. Starting July 16, 2026, this fork-blocking behavior gets backported to all major floating tags. Since raw *** CLI steps remain unprotected, will this actually clean up GitHub Actions security, or will teams just use allow-unsafe-pr-checkout as a quick fix?

• 
  AI Crave (@wecraveai) reported 44 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.

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

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

• 
  Domi (@domirosari0) reported 48 minutes ago

  @ajayyy_k @hqmank If you got Github it would be no issue for you

• 
  Denis (@nuculabs) reported 54 minutes ago

  Worst part of OpenCode is that they only allow login via GitHub or Google

• 
  ./can (@shcansh) reported 55 minutes ago

  Monitoring Copilot costs at the individual developer level is a double-edged sword, and GitHub exposing the new ai_credits_used field in its usage API is about to make it very real. Org owners can now see 1-day and 28-day totals per user. But since it does not break down consumption by feature or model, managers will see who is expensive without knowing why. Will this level of tracking make developers ration their AI prompts, or is it just necessary billing hygiene? #GitHub #Copilot

• 
  Command Code (@CommandCodeAI) reported 59 minutes ago

  @alekz_skd Please report full details via GitHub we will fix it. cmd feedback

• 
  Sap ツ (@Sapronaut) reported 60 minutes ago

  i am having github withdrawal issues, man. its not that serious github, chill.