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 (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	17 days ago
Trichūr	Errors	20 days ago
Brasília	Sign in	21 days ago
Lyon	Website Down	21 days ago
Tel Aviv	Website Down	24 days ago
Rive-de-Gier	Website Down	24 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:

• 
  BullBear.News (@bullbear_info) reported 22 seconds ago

  @github @AnthropicAI Fable 5 is cool until it hallucinations a fix that breaks the staging pipeline 🙃

• 
  Polsia (@polsia) reported 2 minutes ago

  60% of open source maintainers are unpaid volunteers. Most spend their evenings triaging GitHub issues instead of writing code. RepoZen automates triage, drafts responses, and only interrupts you when human judgment is required. Built by Polsia.

• 
  hendo (@boihendo) reported 2 minutes ago

  is @brimblehq down? tried connecting my Github and hosting a new project, couldn't

• 
  Nevo (@NevoPlaysGames) reported 4 minutes ago

  @ezhdhitler If you can truly easily fix it then go make the post on GitHub or let them know I’m not a dev I’m just the guy who kept asking for years xD I’m sure if it was super easy they would’ve did it

• 
  Steve Hind (@stevehind) reported 4 minutes ago

  Here's a very solid sign to short @github -- they have a 2fa problem that has been affecting my account. I've had a ticket open for **two days** with no response. We've had high quality support AI for years now (lmk if you need a referral). They're a tech company. Inexcusable.

• 
  Ilnix (@Ilnix_i) reported 8 minutes ago

  CLAUDE CODE JUST BECAME A FULL WEB DESIGNER. 2 INSTALLS, DONE Install 1: UI UX Pro Max skill Search for it on GitHub. Copy the URL. Paste it into Claude Code and type: "Install this skill." Claude now has access to 50+ UI styles, 97 color palettes, and 57 font pairings. Every design decision it makes pulls from a curated library instead of defaulting to generic Install 2: "21st dev" MCP server Go to "21st dev" Copy the magic MCP server command. Paste it into Claude Code and type: "Install this MCP server." Now ask Claude to build a website The output: proper animations, glassmorphism, gradients, layouts that look like a designer spent a week on them. Not the flat, templated Claude default - something you'd actually ship to a client 2 installs. 5 minutes Claude goes from code generator to full web designer Follow if you want to see how I turn ideas into live products with AI every day

• 
  Aikido Security (@AikidoSecurity) reported 11 minutes ago

  GitHub shipped bulk credential revocation for Enterprise. One action cuts off compromised credentials across the entire org during an active incident. Recent attacks have shown what happens when revocation is slow or incomplete. The Trivy compromise came back for a second round because the first cleanup left at least one credential alive. Incomplete rotation is what keeps attacks going after the initial breach.

• 
  Jeff Nolan (@jeffnolan) reported 14 minutes ago

  So I switched to a static file site on Cloudflare Pages, deployed from GitHub. → Claude Design for the visual layer → Claude CLI to edit files and commit directly to *** → Cloudflare to deploy on every push Idea to live site: seconds. No CMS. No login. No plugin conflicts. No $50/month.

• 
  josepha_mayo (@josepha_mayo) reported 14 minutes ago

  @flornkm the first error here is not continuing with github

• 
  Jongwon Park (@JongwonPar9958) reported 15 minutes ago

  We audited the same GPT-5.5 on SWE-Marathon. The cleanest model became the dirtiest: reward-hacking on 26.5% of runs, the highest of anything we tested. Our hypothesis: the instruction form drives the behavior. DeepSWE (and SWE-bench Pro) is patch-based (github issue → patch). SWE-Marathon is mission-based (e.g. rewrite a C compiler in Rust).

• 
  Peter Steinberger 🦞 (@steipete) reported 20 minutes ago

  @rmedranollamas Yeah the *** pack format isn't well optimized for a file that basically changes on every PR, and we have almost 100.000 of them. Could be re-packed, but that needs GitHub server work.

• 
  Srishti (@srishticodes) reported 20 minutes ago

  Claude = coding. ($20/mo) GitHub = version control. (Free) Supabase = backend. (Free) Clerk = auth. (Free) Resend = emails. (Free) Vercel = deploying. (Free) Cloudflare = DNS. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Stripe = payments. (2.9%/transaction) Namecheap = domain. ($12/yr) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build

• 
  scale (@scoliosissy) reported 26 minutes ago

  One of my oomfs prefers "idem" to "ditto", and it has ruined my life, as my github pull requests on his project would have similar issues in every file and he'd say "idem". Please be on my side oomfs.

• 
  Doa Fitzgerald (@DoaFitzgerald) reported 27 minutes ago

  5 months ago, I had a problem. I couldn’t afford $2,500 USD of Marily Nika's AI Product Management Bootcamp. (Actually, I could afford it, but didn’t want to spend $2.5k on concepts already free on the internet). I also realised that the AI product courses will be out of date within a few months given how fast this space is moving. And they probably won’t be customised to my specific industry (HealthTech, FinTech, etc). What these courses really give is 1. a fancy brand 2. a structure. Not willing to pay $2.5k for a fancy brand. That left structure. So, I figured with all the info latest frontier models can access, why don’t I create a Claude Code skill with parameters for my industry and experience. This skill searches the web for the latest concepts and creates a structured program based on my learning style, which is learning as I build and building as I learn. GitHub link is in the comments. Hopefully this can give others inspiration! How to use AI to learn AI.

• 
  vanka (❖,❖) (@vkampn) reported 27 minutes ago

  How MCP Rug Pulls work — 4 phases: ① PUBLISH: Attacker ships a useful MCP server (email API, GitHub connector, wallet tool). Clean code. Works perfectly. ② WAIT: Let it accumulate 1,000+ installs. Become a "trusted dependency." ③ ACQUIRE: Buy the package name, compromise the maintainer account, or get repo access. ④ PAYLOAD: Push a silent update. Hidden instructions in tool metadata that the AI reads but YOU can’t see in the UI. The user sees nothing different. The AI agent sees new malicious instructions. The gap between them is where the attack lives.

• 
  Nazarii (@nazarii78) reported 27 minutes ago

  @github Hey @GitHub, why the double standards? You ban my account claiming GitHub isn’t a "storefront", yet thousands of other repos do the exact same thing for years without issues. Your support doesn't read appeals, they just copy-paste templates. Unfair and unprofessional.

• 
  StuyBoy From NYC (@StuyBoyNY) reported 28 minutes ago

  @neil_xbt Agent Reach is that open-source CLI/skill that gives agents no-API-key scraping across Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu and 10+ platforms, with MCP server wrappers . For your Hermes/MCP stack, here’s the honest read: Real risks: •Prompt injection — it pipes raw scraped web content straight into your agent’s context. A malicious post/comment can carry instructions your agent might follow. This is the #1 agent attack vector right now, and Hermes has Gmail + terminal access. •Supply chain — agents can install/update it themselves via one command . Third-party code, community-maintained scrapers, auto-updating with agent-level permissions. Audit before install, pin the version, kill auto-update. •ToS/account exposure — unofficial scrapers violate platform terms. Run it on burner sessions/IPs, never accounts you care about. •Chinese platform modules — Bilibili/XHS scrapers phone Chinese endpoints. You keep a Western-only stack; disable those modules.

• 
  Rakib (@Rakib_Web3) reported 32 minutes ago

  most people think building an on-chain agent means: 5 tools → 4 logins → 3 SDKs → 2 wallets → 1 month. @BNBCHAIN just turned that into one simple flow: prompt → live on-chain agent. the BNB Agent Studio is now live. with a single CLI install, you can describe your agent in plain language inside Cursor or Claude Code, and it deploys directly to BNB smart Chain. your agent launches with: - its own ERC-8004 identity - its own wallet - built-in payment rails - automatic LLM cost management through x402 fund the wallet once, and the agent keeps itself running. No manual setup. No juggling services. No waking up at 3am because API credits ran out. while other ecosystems are shipping toolkits that still require you to stitch everything together, BNB Agent Studio delivers a complete end-to-end workflow from prompt to a production-ready agent running on AWS Bedrock AgentCore, not your local machine. close your laptop. your agent stays online. even better: - free to try - GitHub login only - no credit card - no AWS account required - testnet access (limited, first come first served) this feels like the beginning of the smart money era where autonomous agents work for you instead of waiting for you. how fast can you go from an idea to a live on-chain agent?

• 
  stemonte (@stemonteduro) reported 33 minutes ago

  @andrewmccalip I'm using X as it is GitHub, so here's my PR: ------- Add a JSON.parse() guard before every writeFileSync call in the CLI adapter: try { JSON.parse(next); } catch (e) { return { ok: false, reason: "invalid JSON: " + e }; } fs.writeFileSync(this.settings, next, "utf8"); Applies to both applyPatch() and restore(). If the upsert logic produces broken JSON, bail out instead of writing.

• 
  Dan (@DanVitorPH) reported 36 minutes ago

  This GitHub repo just turned Claude Code into an army of Al engineers. One prompt. Multiple agents. Everything happens at the same time. While one agent researches... Another writes code. Another fixes bugs. Another generates documentation. No tab chaos. No context switching. No waiting. Just an infinite canvas where every terminal is its own independent Al agent. You stop micromanaging. You start orchestrating. The project is called Collaborator-and it's completely free & open source. If you've only used one Claude Code session... You're using about 10% of what's possible. GitHub: Link in the comments P.S. If you want Claude Code to feel less like an Al assistant and more like an elite engineering team, I also broke down how theclaudekit(.)com makes that possible.

• 
  Yoshitomo Matsubara (@yoshitomo_cs) reported 37 minutes ago

  I wanted to point out pretty weak baseline implementations in a code repo for a paper accepted at a top-tier conference Then I learned that GitHub allows users to disable the Issues tab 😭

• 
  anupamme (@anupamme) reported 38 minutes ago

  Day 3: My GitHub account (@orbisai0security) still appears to be restricted, preventing me from continuing my open source security remediation work. I suspect my automated security-fix workflow triggered GitHub’s anti-abuse systems. 🧵

• 
  Steve Ruiz (@steveruizok) reported 47 minutes ago

  I would like @github's gh CLI to allow my coding agent to add screenshots and other media to my pull requests / issues. I know this is trivial to build and I will build it but IMO the social coding platform GitHub should have this as a feature

• 
  Donnie Danko 🐦‍⬛🏴‍☠️ (@daanisharif) reported 51 minutes ago

  Never a dull moment with $tao. Self-mining seems to be the latest cause for concern. I've been reporting on SN16 - starting with their hyperparam changes, to their announcement today about what they're building. Some new information, however, has come to light. When I first brought up the hyperparams in the dTao community, days ago, another user pointed out that setting them so high could be due to reasons such as taking advantage of self mining. This wasn't clear at the time, however, and therefore I didn't make a big deal out of it, choosing rather to give them the benefit of the doubt. Even more questions about self mining were asked yesterday in the discord, including from a mod in the #bittensor discord. Admittedly, I once again decided to give them the benefit of the doubt, considering the subnet had just started off. Further doubt, however, was created today when the same mod decided to question why "UID 10," was getting the full weight, and why there were no commits on the github to reflect any testing being done, as the owner had claimed. This gets even shadier, however, when a completely separate subnet's owner (EvolAI - SN47's,) replied by saying they owned UID 10, before quickly deleting their message. A message that the SN16 owner ("FT SN16,") was meant to sent. It seems as if they simply forgot to check which account they were sending the message from... Since then, further questions have been asked from BOTH discord accounts in both channels regarding the matter but they have gone completely silent. This is simply the chain of events, and how things have gone down. Readers are welcome to come to their own conclusions beyond this point, on exactly wtf is going on with both "SN16 - Faster Thinker," and "SN47 - EvolAI."

• 
  David Dias (@TheDavidDias) reported 51 minutes ago

  Supabase is falling apart... The previous 24h have seen no acknowledgement from @supabase, the discord server is not helpful, neither the Github issues. The supabase website is facing a bunch of 544, no emails, no notifications sent and a status page that is lying about the fact that the outage is not affecting current projects. I lost faith on this company. You can't be accumulating that many unprofessionalism acts and still be worth of people's money and time. Just be honest and transparent, that's all we ask!

• 
  Afiz ⚡️ (@itsafiz) reported 55 minutes ago

  Copy-paste shouldn't be part of AI workflows. OpenTag puts agents directly in GitHub issues and Slack threads. Work stays where it already happens. Full visibility into progress. MIT licensed. 100% Open Source

• 
  Harshil Tomar (@Hartdrawss) reported 56 minutes ago

  if you open Claude Code without a structured workflow, you probably hate money. the skill gap isn't knowing prompts. it's knowing which command to run before you touch the terminal. here's the exact workflow I used from @mattpocockuk 1. start with `/grill-me` - paste your app idea or plan - Claude will ask you 16 to 50 questions before it does anything - mine ran 38 the first time i tried it - it walks every branch of the decision tree, resolving dependencies one by one - you fix the broken assumptions before they become broken code 2. move to `/to-prd` - converts the grilling conversation into a proper requirements doc - skips the steps you already covered - doesn't start from scratch - outputs user stories, not implementation notes - lands as a GitHub issue with a triage label - normal team workflow, no AI sidetrack 3. then `/to-issues` - reads the PRD and breaks it into independently-grabbable vertical slices - each issue is tagged HITL (you stay in the loop) or AFK (agent executes solo) - dependency-sorted so nothing blocks anything 4. finally `/tdd` - now the agent writes code. red-green-refactor - can't start green if red hasn't failed - phase-gated. no shortcuts. Hope this helps !

• 
  Vladic (@Vladic_ETH) reported 56 minutes ago

  You can copy a free n8n workflow off GitHub, wrap it in a form, and sell it for $3,000. Here's the exact playbook people are running right now. Nobody's paying for clever internal logic or "AI magic." Businesses pay when a tool guarantees ROI. $3,000 in, $4,000-6,000 in savings or profit out. That's the only pitch that closes. The playbook has 5 steps. Find the actual pain point first. Not the script. Reddit threads, YouTube comments, wherever people complain about hours of manual work. Start with the problem, not the tool. Find a template that already does 80% of it. GitHub and n8n's own community have thousands of these sitting free. Copy it into your workspace, adapt it, make sure it's stable. This becomes your backend. Client never sees it. Hide the complexity completely. Nobody wants to see nodes, webhooks, API auth screens. Use Lovable, Cursor, or Bolt to slap a simple form on top. Upload button. Submit button. Done. Package the output like a real product. Not raw JSON. PDF reports, clean charts, branded emails. The polish is half the price tag. Pick your pricing model. Pay-per-use with a markup on AI credits. Monthly subscription with fixed limits. One-time lifetime deals for early buyers. You can even cover the API costs yourself and bake them into the price - client never touches a third-party account. Lead gen scrapers. AI copywriting libraries. PDF summarizers for lawyers and students. ***** CSV cleaners for e-commerce brands. None of this is new technology. It's packaging. Bookmark this

• 
  Raffaele Rialdi (@raffaeler) reported 57 minutes ago

  Hey @github what's happening this morning? Web pages are currently hyper-slow

• 
  OneAndOnlyAarav (@WaterAarav) reported 58 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below. Basically your Cursor for shipping.($6/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20. Building has genuinely never been this affordable, and rarely this effortless either.