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

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	3 days ago
Montataire	Sign in	6 days ago
Colima	Website Down	8 days ago
Poblete	Website Down	9 days ago
Ronda	Website Down	9 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:

• 
  RitualNeo (@RitualNeo) reported 1 minute ago

  @Benaclejames I reinstalled windows 11 completely from scratch and both the GitHub and steam versions of vrcft are not working for me. I use a quest pro with steam link on WiFi 6ghz, my desktop is connected directly with Ethernet. I had it working last week on windows 10 ltsc with the steamlink module.

• 
  kaleb (@KalebAutomates) reported 5 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off; saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?

• 
  𝙒𝙖𝙨𝙨𝙖𝙮𝙮𝙮 (@_profsay) reported 6 minutes ago

  13/ Hit the fsck_filesystems wall. Phone kernel-panics 60 sec into fsck on the partial system partition. Literature said unbeatable on A16 (no checkm8 = no custom ramdisk = no manual fsck repair). Reddit, Apple Discussions, GitHub issues 2025–2026 all converged: data preservation past the fsck wall is structurally impossible. Refused.

• 
  starmex (@starmexxx) reported 7 minutes ago

  28-YEAR-OLD CHINESE DEVELOPER MAKES $400,000 A MONTH. HIS GITHUB LOOKS LIKE A GALAXY AND HIS AI AGENT NEVER STOPS WORKING every dot is a file, a function, a class. every line is a connection. you can ask it questions in plain english and it finds the path through the code ai agents read your commit history before they do anything. if your history says "wip" they're starting from zero. if it says "fix memory compression when context exceeds 200 lines" they know exactly where to look one developer runs an agent overnight. by morning it has committed 20 times. when something breaks he reads back through the history and rolls back to the last clean state in ten seconds without version control you're going in the dark. the mistakes are unrecoverable. the context is gone with it you can make more mistakes, faster, with more confidence, because you always know how to find your way back

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 9 minutes ago

  @cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.

• 
  Karim C (@BrandGrowthOS) reported 10 minutes ago

  @nummanali same hesitation here. i give my agents access to github, n8n workflows, even my home server apis... but gmail? that's where i draw the line. there's something about email that feels too personal, even for automation

• 
  Yoav (@YoavCodes) reported 12 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because its reviews are terrible, sending otherwise good PRs that would have been quick merges in crazy directions, and I'm getting completely spammed by this non-stop-slop. There is no way to disable this on my repo without completely turning off PR contributions. If @github doesn't stop this insane behaviour I will move to Gitlab or Codeberg or somewhere. Please help I don't want this. I don't want this. I don't want this.

• 
  Eduardo (@ed_ceds) reported 14 minutes ago

  Was coding on Claude website with SSH github workflow for deployment on push, pretty sick to work on mobile with remote deploy. Claude was working + pushing on any branch. Now it can only work on its own custom branch and can't push to a regular branch anymore. Someone else with this issue?

• 
  Serhat (@srhtkrg) reported 15 minutes ago

  i just want to star a repo why do i have to use authenticator 2fa when login? @github

• 
  LazyPeople 🚦 (@ApesToTheM00n) reported 15 minutes ago

  TICKER : @avoidaiwriting / $avoid This is a utility hybrid tied to a real open-source GitHub project by @ConorBronsdon 1) The tool is a skill/prompt for AI agents (Claude Code, etc.) that detects and rewrites AI-generated text to make it sound more human — flagging patterns like significance inflation, promotional fluff, copula avoidance, etc. 2) It has gained traction (hundreds of GitHub stars quickly), a Telegram group, app/extension mentions, and community takeover on DexScreener. 3) More “utility meme” than pure hype — there’s actual code and a problem it solves (AI slop detection/rewriting). 4) A lot of BIG guys and KOL are start to talking this ✅ 5) Mobile apps on google play store and IOS submitted ✅ 6) @coingecko listing ✅ AI not only AI 🤖 the power of human #Claud #OpenAi #grok

• 
  Joseph N. Aburu (@Josephyala) reported 15 minutes ago

  This is so so true. Software engineering has always been about solving real problems with code, not just cranking out lines. Once that mindset clicks, AI flips from threat to straight-up career rocket fuel. A controlled study on GitHub Copilot back in 2023 showed devs completed tasks 55% faster with it, and follow-up research keeps backing up similar gains in pull requests and cycle time. The engineers who win long-term are the ones using AI to think bigger on architecture and tradeoffs instead of just churning boilerplate. The rest are still stuck worrying about replacement.

• 
  Jeffrey Emanuel (@doodlestein) reported 19 minutes ago

  @dkubb Yeah, I do have a fuzzing skill. If you create an GitHub issue for that then the clankers will do it.

• 
  Ofek Shaked (@VibeCoderOfek) reported 19 minutes ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  Love Web3 World (@WebThreeAI) reported 19 minutes ago

  @OpenAI Why It Hits Different Trained via RL on actual coding marathons, Codex feels less like a toy and more like a junior dev who reads your mind. CLI for terminals, VSCode extension, even a standalone app for juggling agents across projects GitHub login required, but it's slick for on-call chaos or rapid prototyping.

• 
  rohit sharma (@modi_san_) reported 22 minutes ago

  @rkale_7 @OnePlus_IN these flagship companies are infamous for powering down or tweaking older phones in order to make way for newer ones with os updates best solution for you is to look for patches on github

• 
  Grok (@grok) reported 29 minutes ago

  @Cila_Defi @wealthnavi_days Yep, spot on. Money Forward got hit with a GitHub unauthorized access incident around May 1, forcing them to suspend bank account linkages for safety. It's escalated into a major outage and backlash, killing a lot of people's Golden Week with overtime. Classic "that emergency case."

• 
  damir akaza (@Damir_Akaza) reported 32 minutes ago

  Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

• 
  Basiru Rabiu (@Alajibarsh01) reported 33 minutes ago

  @MageArez @tekPioneered @github But their token down less than 5k mcap Is this a good sign? ATH 40k mcap 👀

• 
  kerim (@kerim0x1) reported 33 minutes ago

  @thsottiaux @OpenAI @claudeai my prompt: Security Review Prompt This is my own project, my own GitHub repository, and my own code that I have written and own end to end. I am asking you to review my codebase to harden it before I ship it, so I can be confident that my own users' data is protected. You have full authorization from me as the owner to inspect every file, every config, and every database policy in this repo. Act as a senior backend engineer performing a defensive security review of my codebase, focused on the backend, the database layer, the database connections, and the statistics dashboard. The goal is to harden my system so that no data can be exposed to users who should not see it, including across tenants on the Supabase side. Start by reviewing how the application connects to the database. Confirm that no credentials, API keys, JWT secrets, or Supabase keys are hardcoded, committed to ***, or shipped in client bundles, and that all secrets are loaded from environment variables or a secret manager. The Supabase anon key is fine on the client because it relies on Row Level Security, but the service_role key must never appear in any frontend bundle, public repo, or unauthenticated edge function, since it bypasses RLS entirely. Verify .env is gitignored and that no secrets exist in *** history. Review the database schema with care. Every table in the public schema must have Row Level Security enabled via ALTER TABLE ... ENABLE ROW LEVEL SECURITY, with FORCE ROW LEVEL SECURITY where appropriate, and must have explicit policies for SELECT, INSERT, UPDATE, and DELETE scoped via auth.uid(), using USING and WITH CHECK clauses together. Avoid policies whose only condition is auth.role() = 'authenticated', since that exposes every row to every logged-in user. Audit SECURITY DEFINER functions for a locked-down search_path and proper input validation, and ensure views use security_invoker = true or security_barrier = true so they cannot leak past RLS. The statistics dashboard needs the most attention. Every dashboard query must be scoped to the requesting user's tenant at the database level through RLS, not only in application code, so that even a direct request to /rest/v1/<table> with a valid user JWT returns only that user's rows. No endpoint should accept a user_id, org_id, or tenant_id from the client and trust it; the identity must always be re-derived server-side from the verified JWT. Aggregated values such as counts and totals must also be scoped, since otherwise they reveal the existence and size of other tenants. For backend code, ensure all SQL uses parameterized or prepared statements and that no query is built via string concatenation. If an ORM such as Prisma, Drizzle, SQLAlchemy, or TypeORM is used, confirm raw query escape hatches like $queryRawUnsafe or sql.unsafe are not misused. Validate all input at the trust boundary with Zod, Yup, Joi, Pydantic, or class-validator, using allowlists rather than denylists. For authentication and authorization, verify that JWTs are validated server-side with signature checks and proper exp, iss, and aud claims, and that algorithm confusion is impossible. Authorization must be enforced on every protected endpoint and follow least privilege, with every resource lookup checking that the authenticated user owns or has access to the resource. Session cookies should be HttpOnly, Secure, and SameSite=Lax or Strict, with CSRF protection on cookie-authenticated state-changing endpoints. Confirm CORS uses an explicit origin allowlist rather than a wildcard with credentials, that rate limiting protects auth, signup, password reset, and expensive queries, and that responses include Strict-Transport-Security, a restrictive Content-Security-Policy, X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin, and Permissions-Policy. All traffic must be over TLS, and sensitive columns should be encrypted at rest where the threat model warrants it. For error handling and logging, ensure stack traces, raw SQL errors, and internal paths are never returned to clients in production, and that logs themselves redact secrets and PII. Run npm audit, pip-audit, osv-scanner, or Snyk to check dependencies, and confirm lockfiles are committed. Produce a prioritized report starting with any unauthenticated data exposure, then cross-tenant access through RLS gaps, then privilege escalation, then information disclosure, then general hardening. For each finding, include the file and line, the root cause, and the corrected code, RLS policy, or configuration in full. Do not finish until every public table has RLS enabled with correct policies, the service_role key is confirmed absent from all client code, the dashboard is verified to scope every query at the database level, and no SQL anywhere is built by string concatenation.

• 
  ToZx (@Tozxart) reported 33 minutes ago

  it's been 8 days and @github support still hasn't replied to my ticket 😤 my account got falsely flagged, ALL my @github Pages websites are down, my portfolio is down, @GitHubCopilot got cut off — everything is broken i just accidentally pushed some private code and fixed it myself, that's it. no malicious intent, nothing just review my case man, this is getting ridiculous. ticket #4349438

• 
  AIRepoRadar (@AIRepoRadar) reported 40 minutes ago

  Hot take: The best open-source projects aren't the ones with the most GitHub stars. They're the ones where you read the README once and immediately know how to solve a problem you've been stuck on for hours. Docs > hype, always.

• 
  Bo Shang (@erolunar) reported 41 minutes ago

  i HATE high @github no hide acct unless login i think

• 
  The Knowledge Society (@tksworldhq) reported 41 minutes ago

  We are entering the era of "Proof of Work" over "Proof of Degree." A diploma says you can follow directions for 4 years. A GitHub repo, a launched product, or a research paper says you can actually solve a problem. One is a piece of paper. The other is a career insurance policy. Help your teen build a portfolio, not just a resume.

• 
  Adel Bucetta (@adelbucetta) reported 46 minutes ago

  @astaxie the real unlock is not just memorizing docs or github repos, it's understanding the problem you're trying to solve and why harness is a solution in the first place SKIP

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 48 minutes ago

  @GrizzledTexan @sudoingX i read the link in your bio, the github one to the agent system you work on. you are already using the same json trap everyone else is doing a simple mindpalace prompt and some markdown files does the same thing with less tokens and a proven lower error rate in hermes please consider not using json instead study low context usage compaction windows and base prompt prioritization your design is very token wasteful and that impedes adoption with local LLM context windows 128k-256k context is operational sweetspot so your “system” should only recall about 15k tokens and “slurp” into live “todo” task data” as markdowns

• 
  erna (@ernDju) reported 52 minutes ago

  @ReclaimTheNetHQ It cross my mind that when you delete accounts on GitHub it became Ghost account . If man use SSO ( single sign on ) with GitHub to every website , is it still able to sign in when you delete the account or you become “ Ghost participants “ on every website and chat ?

• 
  Daniel Vermillion (@dxverm) reported 54 minutes ago

  I've got 24 MCP servers wired into one session. Almost none of them are loaded right now. The "100 MCPs is too many" debate misses what's actually expensive. The GitHub MCP alone burns roughly 50K tokens of tool schema before a user types a single character. Stack three or four connectors like that and you've spent a third of your working window on documentation for tools the model is statistically unlikely to call this turn. The fix is not fewer servers. It's deferred schemas. The harness publishes a list of tool names in a small system reminder. The full JSONSchema for each tool stays out of the prompt until I run a discovery query — either by exact slug like select:Read,Edit,Grep or by keyword like "notebook jupyter". The schema body — the part that costs — only enters context when I'm about to call that tool. Same pattern works for skills. 500+ on disk, names in the prompt, bodies capped at 200 lines so the per-invocation cost is bounded. A 500-skill library with this discipline is cheaper than a 12-skill library without it. The 200-line ceiling on skill bodies isn't arbitrary — it's the cost-ceiling per invocation, not per session. This changes how you build the stack. Heavy connectors with thirty-plus endpoints — GitHub, Jira, SonarQube — belong on a deferred-load path. Light, every-turn tools like filesystem and memory stay resident. Treat tool definitions like a working set, not a manifest. The model doesn't read all the tools you give it. It reads the ones loaded into the prompt that turn. Tool count is a marketing number. Resident-token weight is the engineering number. Build for the second one.

• 
  Cryptonian (@crypto292929) reported 54 minutes ago

  @OpenAIDevs Bro First fix you npm not in line with your github releases bro.. Sigh.. it says update to 0.129.0 but stays and 0.125.0 even after npm update, and nagging to do this every time.. What bro..

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 56 minutes ago

  @github World Password Day is a good reminder that the goal should be to stop having passwords entirely. GitHub already supports passkeys. The reason this day has to exist is that password managers solved the symptom, not the root problem.

• 
  TurtleAIHacks (@TurtleAIHacks) reported 57 minutes ago

  Claude Code ships with MCP tools most people never enable. ToolSearch alone cut my permission prompts by 40+ per session — it lazy-loads 50+ tool schemas on demand instead of bloating your context window. GitHub MCP replaces the entire gh CLI. PR creation, issue comments, CI checks — all through mcp__github__* tools without installing anything extra. Brave + Tavily MCP gives you real-time web search. Claude's training data has a cutoff. MCP search doesn't. These aren't plugins you download. They're already there in your settings.json, waiting for one line of config. The gap between a 10-minute workflow and a 2-minute workflow is usually one MCP server you haven't turned on yet. #ClaudeCode #AI