GitHub 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:

• 
  JoseSK (@JoseSK999) reported 37 seconds ago

  @evoskuil @kcalvinalvinn Sure, it’s bad if people think their nodes validate everything while they actually use AV. But it’s not like we are responsible for people not reading the GitHub docs for an experimental software. What is the problem with hash commitments you mention?

• 
  Jose Luis Matus (@jmatux) reported 1 minute ago

  From CodeRabbit's analysis of ~500 open-source GitHub PRs: AI-co-authored code has 1.7× more issues than human-only code. Logic errors: 75% more common. Security vulnerabilities: nearly 3× as frequent. The testing surface is expanding. The people covering it are losing ground.

• 
  Priyanshu (@imdevPU23) reported 2 minutes ago

  - Claude for coding. - Supabase for backend. - Lovable for frontend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - Resend for emails. - GitHub for version control. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally ship a startup from your bedroom now. It’s not even cost much many of them give free initial credits

• 
  Mario Figueiredo (@fromdevoid) reported 6 minutes ago

  @sporadica Briefly, they got they 42 of their packages compromised and pushed into npm, by a chain-attack involving a known PR workflow issue they didn't protect against and a documented Github Actions design flaw they couldn't protect against.

• 
  Iván (@seikv) reported 10 minutes ago

  GitLab only has to do the oposite of what GitHub is doing and make its UI prettier and boom all problems solved.

• 
  Robert Ta (@therobertta_) reported 14 minutes ago

  GitHub has 2,500+ repos with agent configuration files. The pattern is clear: teams are building skills in isolation, duplicating effort, and creating incompatible standards. At Workday, we had the exact same problem with internal tools. 50 teams building 50 slightly different deploy scripts. Skills across teams is a coordination problem, not a technical one. Here is how to solve it.

• 
  Lorden (@lorden_eth) reported 14 minutes ago

  24-YEAR-OLD BACKEND DEVELOPER FROM SHENZHEN CHARGES $11,000/MONTH FOR TEAMS HE NEVER JOINS Obsidian vault + Claude + a GitHub webhook Client connects their repo, and Claude returns a 6-page audit in 18 minutes Forwards audit report via email, teams respond within 24 hours Charges them $2,570/month before fix Does the same thing 4 times and makes $11k He never shows up for meetings

• 
  suresh kumar (@sureshkanbu) reported 16 minutes ago

  opened a github issue from october. 'why does X happen when you Y?' read the code. it's intentional. by me. 6 months ago. with a comment that says 'don't change this, it's on purpose.' i'm both halves of every bug report on this app.

• 
  Meet (@meetvchopra) reported 18 minutes ago

  @SimonHoiberg Just one issue I have faced is the CI/CD pipeline. Like just pushing to github usually makes the change live. Doing on VPS, I need to login and then push the code etc. Mapping it to custom domain and other things sometimes takes time, so I just skip all the headache and use Vercel for quick projects

• 
  T.J. Żelawski (@tjzeldev) reported 22 minutes ago

  @jdxcode I wouldn't say actions were misconfigured. I don't recall GitHub docs mentioning anywhere that `pull_request_target` is unsafe and can literally poison your entire workflow cache etc. The problem is the lack of granularity. GitHub actions in general only have permissions either for read or read & write, which concerns everything. I wish I could set a permission for a workflow to be able only to edit PR description or label a PR on GitHub without allowing it to do everything else possible within the repo and its secrets. And don't even start me on how annoying it is to actually enable proper caching for workflows. Doing it is so hard that you don't even think about security when you wonder for the xxth time why there was a cache miss.

• 
  Adib Hanna (@adibhanna) reported 25 minutes ago

  @emergencedaily can you create a github issue for this?

• 
  Kekko D’Amato (@kekkodamato_) reported 26 minutes ago

  @MnFounder The .well-known convention is the right call — follows RFC 8615 like OIDC discovery. Makes automated capability checking trivial. Would love to see this standardized fast so clients don't have to resort to GitHub scraping to find what a server supports.

• 
  wlp3s0 (@wlp3s0) reported 26 minutes ago

  @MarcusFranz @GamersNexus @BambulabGlobal how else is he supposed to report about corporate assholery and support the dude who's software got removed? "hello guys today we are here to talk about bambu lab and how orcaslicer bambu was removed from GitHub due to legal issues. this will be a very enjoyable video."

• 
  Oluwamayowa (@oluwamayowa) reported 27 minutes ago

  It starts with Sources. Vyrric can ingest support conversations, tickets, survey responses, reviews, product analytics, Slack messages, GitHub issues, uploaded transcripts, PDFs, docs, and text evidence. Each source gets synced, indexed, and monitored.

• 
  Beau Johnson (@BeauJohnson89) reported 29 minutes ago

  browser debugging is becoming agent infra ChromeDevTools/chrome-devtools-mcp > 39,363 stars on github > official chrome devtools mcp server for coding agents > lets claude, codex, cursor, gemini, copilot, and more control a live chrome browser > performance traces, network requests, console logs, screenshots, and puppeteer automation the point is simple: coding agents cant fix what they cant see terminal logs are not enough once the bug lives in the browser this is the missing bridge between write code and verify the actual app