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:

• 
  Corey J. Gallon (@CoreyGallon) reported 5 minutes ago

  Over 30% of changes are already getting merged without a review at all, and the median review time keeps climbing. . @ankitxg, founder and CEO of Aviator, argues in "*********** the Code Review" that the fix isn't a better diff reader, it's moving the review surface off the diff entirely. @aiDotEngineer has the talk on YouTube. It's a concrete proposal for teams whose coding bottleneck has quietly turned into a reviewing bottleneck. - The numbers say we already stopped reviewing. 861% code churn, a rising incident-to-PR ratio, and 4x the time spent waiting on reviews. - AI reviewing AI in a GitHub UI is a misconfiguration. Agents write it, agents comment on it, a human skims and merges. Ankit asks where the human actually is in that loop. - Code review was never only about code. Alignment, knowledge sharing, mentorship, architectural feedback, onboarding. He says that's the piece his earlier five-layer trust model missed. - Spec-driven development is waterfall with better tooling. Requirements, spec, implement, verify, no feedback loop. And the spec never gets updated once implementation surfaces new decisions. - Intent lives in your prompts, and you throw them away. The Jira ticket has the goal, the PRD has the plan, but the real decisions happen in the back-and-forth with the agent. Then the PR gets opened and that session is discarded. - The AI slop registry. Codify the review comments you write over and over so they become guardrails you never have to write again. It compounds with every merged PR. - Session becomes acceptance criteria, criteria plus invariants becomes a test plan. The test plan is written in English, so product managers and designers can participate in it. - Deterministic where it can be, LLM where it must be. For a new payment form, an agent browses the app, fills it out, captures screenshots and database snapshots as evidence. - You review the intent and the evidence, not the diff. What was set out, what was tried and rejected, whether the behavior met the criteria. Architecture arguments still happen; line-by-line reading doesn't. - There's a J-curve. Building the registry costs real time before it pays off. The homework he leaves the room with: go mine your last 1,000 review comments and build a slop registry from the ones that repeat. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Khalid (@KhalidDevLog) reported 7 minutes ago

  @razpxcked @expo I will work on resolving it. Can you open an issue on GitHub?

• 
  OldSchoolGamerP (@OldSchoolGamerP) reported 8 minutes ago

  @dabitch This is so much better than the terrible github diff viewer.

• 
  Tony Darrick Baker (@tonydbaker) reported 11 minutes ago

  @mairtinofaolain @RobCairns What if we eliminate the server? Local Code to github to cloudflare pages? Cloud backup of code. That's my current stack. For most local businesses without the need for a CMS, (they rarely updated anyway) it seems to be much more efficient. Updates via chat agent. Thoughts?

• 
  GTA CENTRAL | News & Updates (@THEGTAPOST) reported 12 minutes ago

  Clip 7 dropped today. ********** interior. Neon. Dancers. Pole physics. Jason walking through like he owns the place. Watermark on the footage: "$3 million market cap = **********." They're not hiding it anymore. The memecoin hit $3.76M market cap. They released the clip. The grift is the content now. Seven videos in six days. Basketball. Warehouse. Taser. **********. Gas station rampage promised next. Each leak a marketing beat for a Solana token that minted August 15 — three days before Clip 1. $CYBERLEEK hit $3.76M cap. Crashed 90%. Pumped again on the ********** drop. A GTA fan traced the wallet. The dev wallet holds 40% supply. They're not leaking the game. They're leaking *for* the coin. Rockstar's lawyers filed subpoenas against Microsoft, Discord, GitHub. Take-Two wants IPs by September 4. The website went down. Came back. Leaks kept coming. The "vigilante" narrative collapsed when digital forensics exposed the wallet timeline. Five days until the Extended Look. The ********** was supposed to be a moment in Rockstar's reveal. Now it's a pump signal. The game is still coming November 19. The devs are still grinding. But the reveal - the one moment that was supposed to be pure - has been auctioned off in $3M increments. We're not posting the clip. We're not buying the coin. We're just watching a masterpiece get strip-mined in real time. #GTA6 #GTAVI #RockstarGames

• 
  Warunk Digital 🪙 💻 ⚡⚡️ ₿ (@warunk_digital) reported 12 minutes ago

  @vikrantnyc i checked sign in method still use email account or github, no sign in method with connect wallet

• 
  ven (@anyframeisgood) reported 16 minutes ago

  @abue_ammar did you try opening an issue on github at the very least

• 
  Marketcalls (@marketcallsHQ) reported 18 minutes ago

  @anki1007 you can consider raising a github issue.

• 
  Jeremy W (@basicBrogrammer) reported 20 minutes ago

  What a time to be alive. My vam coated a Android launcher while walking my dog camping just talking to cursor on my phone. The agent "handed" me an apk and we iterated from there. After a few weeks of it being my daily driver and loving finally having the launcher I wish was on the Play store. The app was crashing randomly. I had my agent pick back up. Walk me through. Setting up sentry and had it right. A GitHub action that would publish to the Play store. Then I waited. The crash happened again. I sent the issue to my agents and now the app is running smoothly. It's the age of the geek baby. Go build

• 
  Alex Veremeyenko (@alex_verem) reported 20 minutes ago

  Your AI agents don't lack web access. They lack a clean path through it. This open-source tool fixes it. Anyone who has built an AI agent knows the model is rarely the bottleneck. Getting real, current information into it is the actual work. The open web is a mess of broken HTML, JavaScript walls, and bot blocks, and models choke on all of it. Firecrawl handles that ugly middle layer for you. You point it at a URL and it hands back clean markdown or structured JSON, ready to drop straight into a model. Here's what it actually does. Scrape a single page and get back markdown, JSON, or a screenshot. Crawl a whole site with one request and pull content from every page. Map a domain to see all its URLs before you touch it. Or run the agent mode, where you describe what you want in plain language with no URL at all, and it goes and finds it. It quietly handles what usually breaks a scraper, from rotating proxies and JavaScript-heavy pages to bot-blocked sites and PDFs or DOCX files buried inside a page. You configure none of it. It connects to any AI agent or MCP client with a single command, so an assistant you already run can pull live pages on demand. It has around 166,000 stars on GitHub, runs under the AGPL-3.0 license, and self-hosts if you want to run it all locally. The boring plumbing under an agent is usually the hardest part to get right. It's good to see someone building this one in the open.

• 
  TheLastSoul (@Holy_Terra40k) reported 22 minutes ago

  @thatguybg The app interfaces are terrible. An update is coming via a GitHub commit. They’re coded in Python and TypeScript. It’s not hard to offer a Rust backend and platform-specific frontends in native languages. I recommend they use the AI models they sell.

• 
  Fahad Heylaal (@fahad19) reported 22 minutes ago

  I would much rather receive a well written GitHub issue than a PR for my open source projects. before I would appreciate PRs more, but now with AI agents and the context I can offer, it's more convenient for me to just do it myself end to end.

• 
  Alex (@Saasterix) reported 23 minutes ago

  @iannuttall How can you build things online since 21 years but paying for GitHub is an issue?

• 
  Ian Nuttall (@iannuttall) reported 28 minutes ago

  @Saasterix I never said it was an issue I was asking how others do it since I have seen many alternatives to GH actions. I already pay for GitHub.

• 
  giosaia (@giosaia) reported 31 minutes ago

  @sickdotdev I doubt GitHub vibecoded their web auth process, yet they have the same issue.