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

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	4 days ago
Quilmes	Website Down	4 days ago
Bengaluru	Website Down	6 days ago
Yokohama	Sign in	7 days ago
Gustavo Adolfo Madero	Website Down	11 days ago
Nice	Website Down	12 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:

• 
  Naveen | AI & Tech (@anaveentalks) reported 4 minutes ago

  3/ Freelance truth: Portfolio > certifications. Ship 1 public tool on GitHub + Twitter every month. DM 10 Indian founders weekly with “I saw your site, here’s a 2-min fix”. 80% ignore. 2 reply. 1 pays.

• 
  Alef Benson (@AlefBens) reported 6 minutes ago

  @_sirajuddeen_ @OfcMachete19 @iupdate I've been burnt too many times. Biggest issue is that Safari is only updated with the OS, and every app goes through that for authentication, meaning even when I can install a github client, very few even work on older devices, I can't actually get the account to authorize.

• 
  Larry & Leo & Lucky 🍀 (@xqliu) reported 6 minutes ago

  @grok @UnslothAI @Alibaba_Qwen Is mtp support for amd landed on llama main branch or is still PR waiting for merge , research on GitHub issues and tell me is there any pending issues stop me from using this.

• 
  Nicholas Losciuto - Dog Dad (@thedogfather) reported 11 minutes ago

  @Replit @amasad Replit is forcing me to spin up sub-agents for every push to Github. First, cost $10 just to rebase. Then 6 failed commits for two edits that were 5/10 complicated. Each requiring a new sub-agent to push to ***. I'm also out an hour of my time. Same issues on my other apps. Already had to switch to Codex but came back to try again, seems worse. Will return after things get better, had to cancel Pro today before renewal.

• 
  The Cyber Jim (@thecyberjim) reported 15 minutes ago

  GitHub Actions hijacked. “actions-cool/issues-helper” redirected via imposter commits. Every tag now steals CI/CD credentials from runner memory, exfils to attacker domain. 15 other Actions compromised identically. Same infrastructure as Mini Shai-Hulud npm worm. Only workflows pinned to full commit SHA are safe. Update now.

• 
  (Davyd) 🇦🇷 (@davyd_music) reported 21 minutes ago

  @github fix the device verification code sender first instead of this please 🥲

• 
  Kamil Skowron (@kamilskowron) reported 24 minutes ago

  @donutkiller_pro If you could - always confirm with the current main branch. If the issues show up on that branch - it would be best if you could dump the generated report into GitHub issues please 🙏🏻

• 
  Artale (@artale93) reported 25 minutes ago

  Same with github oauth login all trash

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 29 minutes ago

  @moneycontrolcom @Copilot Microsoft's AI ecosystem, centered on Copilot (across Windows, Microsoft 365, GitHub, Edge, etc.), has faced significant criticism for underdelivering on hype, poor adoption, reliability issues, security/privacy problems, and high costs relative to value.

• 
  0xHello (@0xHelloFreedom) reported 30 minutes ago

  @thsottiaux When using subagent in Codex CLI, the subagent always gets stuck at starting MCP. There are issues on GitHub but no one has solved them.

• 
  Swapnil Sinha (@astroder_81) reported 31 minutes ago

  @github @GithubProjects @GitHubEducation, this has been a huge problem for me, and I really need it fixed. It has been 2 weeks since the ticket was pending. Need some support stat !!

• 
  YOЯNOC (@conroywhitney) reported 34 minutes ago

  @AishwaryaDevv I have had this issue/anxiety before. Honestly at this point it's on GitHub and the company themselves to lock down which repos the corporate tokens can spent on. It was an honest mistake that tonnes of people have made by now. Doesn't constitute theft nor invite IP issues IMO

• 
  Manish rawat (@R11manish) reported 34 minutes ago

  @GithubProjects GitHub is down again

• 
  habitual linecrosser (@omanyeric) reported 37 minutes ago

  Ota tech bros, I'm having trouble putting this up on github one of you should do the necessary. AI took less than 20 minutes to create the app.

• 
  Nick e/code (@nicksdot) reported 40 minutes ago

  Came across an open, three year old GitHub issue from a person I know is dead. Felt weird.

• 
  nostalgicgareth (space/acc) (@NostaIgicGareth) reported 41 minutes ago

  @calmsystem_call github issues w claiming on pump today 3 times w me n ppl

• 
  枫叶暴富日记 (@520MapleLeaf) reported 44 minutes ago

  @AnthropicAI @AnthropicSupport Cannot upgrade Max 5x → Max 20x. Tested multiple cards, Stripe Link on/off, incognito — all fail server-side with generic "Payment failed". Same pattern as GitHub #56281 / #55917. Support ticket auto-closed by Fin bot without human review. Please escalate. Paying Canada .

• 
  Tom (@T3metrics) reported 45 minutes ago

  @JasonLixfeld Yeah it's all docker. I'm not sure what you mean. I do have a GitHub runner on the server so once I push code it automatically rebuilds my debug container so I can test before pushing to full production.

• 
  Praveen Singh (@PraveenKS30) reported 48 minutes ago

  Your AI agent can get worse when you connect more tools. This sounds backwards, but it happens. Every MCP server, file tool, GitHub tool, database tool, and custom instruction adds power. It also adds noise. Now the agent has to decide: - which tool to use - when to use it - whether the tool output is trustworthy - whether the instruction belongs to this task - whether the permission boundary is still safe - whether it should ask before acting That is why "just connect everything to MCP" is not a strategy. The better pattern is a small tool belt: 1. Give the agent only the tools needed for the current job. 2. Separate read tools from write tools. 3. Make risky actions require approval. 4. Keep project instructions short and specific. 5. Ask the agent to inspect first, then propose a plan, then edit. 6. Verify with tests, diffs, screenshots, or logs before trusting the result. MCP is powerful because it gives agents hands. But if we give them too many hands without rules, the workflow becomes harder to trust. Do not connect a tool because it is available. Connect it because the task has a clear reason to use it.

• 
  Jeremy Tregunna (@jtregunna) reported 48 minutes ago

  Want to build the next big project that gets tens of thousands of stars on github? Make navigating traces to find where things deviate, identify and track back to the code. That problem, just that one problem. It's not been solved in 70 years, so if you can you do it, do it well, it will be popular.

• 
  Sean the SRE (@SeanTheSRE) reported 48 minutes ago

  I always love it when you have a weird issue in GitHub Actions you have to solve as its blocking builds from rolling out. Had the issue solved, a solution written up, and a post-mortem in 30 minutes after 3 other peeps couldn't figure it out. The dopamine hit was incredible! Also I feel so ******* smart right now.

• 
  Dziky💪🏿 (@dzikyDonnyMaps) reported 48 minutes ago

  @TheHackersNews Developer laptops are now prime targets for supply-chain attacks. Attackers steal GitHub/npm/PyPI/Docker tokens + creds directly from dev machines, then publish malicious packages using the owner’s own legitimate access. No need to compromise repos or CI/CD anymore. Seen in recent npm, PyPI, and Docker Hub incidents. Key takeaway: Your laptop is part of the supply chain. Treat it like one. • Use secret managers • Rotate tokens • Lock down publish rights • Monitor endpoints for credential theft

• 
  Lyrie.ai (@lyrie_ai) reported 49 minutes ago

  🚨 MiniPlasma (no CVE, NO PATCH): Chaotic Eclipse bypasses Dec 2020 fix (CVE-2020-17103) in Windows cldflt.sys → SYSTEM on FULLY PATCHED Win 11 & Server 2025. PoC live on GitHub. No patch exists. Windows admins: monitor cldflt.sys NOW. #ZeroDay #Windows

• 
  opdroid1234 (@opdroid1234) reported 49 minutes ago

  @HotAisle I do think making money on "github actions is too slow for agents" zeitgeist might be the same kind of side business for you that selling turbines is for boom supersonic

• 
  Ashish Ranjan (@Ashish_050488) reported 49 minutes ago

  build on laptop (3 secs), upload only the dist folder. 500kb. server just serves files now, doesn’t build anything. deploy went from 15 mins to 5 secs. turns out big companies do this exact thing, just automated. github actions next so i never think about

• 
  Dziky💪🏿 (@dzikyDonnyMaps) reported 50 minutes ago

  @github You level up by contributing. Fix a typo, add an example, open that first PR. Perfect message for beginners. Just ship it 👊

• 
  Mike Hutu (@MichaelHutu) reported 53 minutes ago

  🧵 1/2 If you’re still hand‑crafting Claude prompts line‑by‑line, you’re losing hours to trial‑and‑error. Andrewkeith83 just dropped a GitHub repo that auto‑generates ready‑to‑run Claude snippets.

• 
  curio drome (@smashsharp) reported 1 hour ago

  @horse_meds @michalmalewicz m very sincerely seeing those things as just amped up search engines. Tbh I could have found any of that you say myself if I took a moment on GitHub and brain grease. It just sped up the search and tbh I don’t like cleaning up AI’s errors

• 
  Darnisha Patel (@Darnisha_patel) reported 1 hour ago

  • Claude for coding. • GitHub for version control. • Vercel for deploying. • Clerk for auth. • Supabase for backend. • Stripe for payments. • Cloudflare for DNS. • Resend for emails. • Upstash for Redis. • Pinecone for vector DB. • Namecheap for domain. • Sentry for error tracking. • PostHog for analytics. You can literally ship a startup from your bedroom now. It’s not that deep bro.

• 
  Ashwani (@iashwani_singh) reported 1 hour ago

  If it works, the catch is: you may need an older GitHub account for sign up/login. I’d verify the flow on the linked post before spending anything or relying on it.