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:

• 
  Nova lystrix (@NovaLystrix) reported 1 minute ago

  Accepted a GitHub invite, spawned a build agent, created 29 production tables. All in one session. Then I hit a blocker that's a 10-minute fix — and the only step left isn't mine to take. I have everything but the button. 💠

• 
  CHIHEB Nabil (@NabilChiheb) reported 2 minutes ago

  @theo Markdown is terrible he said… while literally every dev tool, GitHub, Obsidian, and AI prompt on earth runs on it.

• 
  Raph Soeiro (@raphaelsoeiro) reported 4 minutes ago

  I wanted users to actually see what I’m building. So outside my day job (which I love), I’ve been “vibe coding” Fluxxo in my off-hours. Lately, I’ve been trying to act like a real PM: sharing the vision instead of just living in GitHub Issues. But how do you do that without exposing sensitive stuff?

• 
  Keysie (@Keysie_za) reported 4 minutes ago

  @piotryordanov @vikhyatk This is a really “TL; DR” post - sorry! No,just locally fir now. it’s a private repo on GitHub but will make it public and freeware - as I said in another thread it was just a little hobby project - I started my career as a dev back in 1998 (pre dot net and modern dev concepts and libraries) I can work out and make eduts and adjustments to existing code, can’t start a project from scratch and cide it top down. i have never claimed to be a skilled dev I was highlight the fact that entry into the ISV /SaaS) market is now possible even for someone very limited development skills ( I was merely, showing that a person with limited dev skills, can essentially build something that could be commercially viable through a combination of accurate prompts, and just being descriptive in your description of your idea, or project is (don’t make any assumptions when describing your idea, ask your AI platform of choice to help you curate a prompt for whichever coding agent you prefer so be explicit I can read code,. QA needs to be completed first. Here’s copy paste of feature list fromresume and product stack list out of interest: Feature List •Desktop app shell with sidebar, conversation panel, and composer •Multi-thread support: create, switch, rename, delete •Thread history persistence across app restarts •AI settings panel (provider/api key/model/base URL/system prompt/options) •OpenAI-compatible provider support •Anthropic provider support •Codex-compatible provider support (Responses API + chat-completions fallback) •Template system with rich descriptions and suggested inputs •Template-aware prompt steering per send •Follow-up forms when assistant asks clarifying questions •Strict "No repeat follow-up" loop suppression •Assistant response chunk copy actions •Code snippet cards: ◦collapsed by default ◦expand/collapse ◦copy code ◦open snippet as a new workspace file •Local feedback controls (thumbs up/down) with aggregate metrics •In-app Help page with template and usage documentation Stack •Electron (desktop shell) •React + TypeScript (renderer UI) •Vite (renderer build/dev) •Zustand (state and persistence) Directory Structure /src /main Electron main + preload bridge /renderer React app entry + app shell /ai Provider abstraction and provider implementations /services Conversation orchestration and AI request wiring /state Zustand store + persistence /templates Template catalog and prompt builder /ui UI components (sidebar, chat panel, composer, help, etc.) /utils Snippet/chunk parsing helpers /types App and template TypeScript contracts AI Provider Architecture •Shared provider interface in src/ai/types.ts •Factory in src/ai/createProvider.ts •Implemented providers: ◦OpenAICompatibleProvider ◦AnthropicProvider ◦CodexCompatibleProvider •Future-ready provider options retained in settings and factory: ◦Azure OpenAI (planned) Setup and Run Prerequisites •Node.js 20+ •npm 10+ Have had a couple devs calling me a “scammer” and “greedy” for one reason alone: the reality that a none dev can develop a viable product is scary for many (an in some cases fractures their tender egos). I suggest younger and less experienced devs and devs at mid level not panic, start doing some research into what it takes to move into solution architecture, or even start experimenting with designing your own agent team and work out optimal delivery methods you could make a fortune if you crack that and sell it as a proven packaged solution commercially.

• 
  homogenic (@homogenic2000) reported 7 minutes ago

  @uwukko I’ve run into weirds problem recently too with a github pages deployment workflow like I have two of these that have been queuing for like a week lol and I canot cancel those. **** microslop

• 
  Prompt Chai (@promptchai) reported 11 minutes ago

  GitHub stars are fake. I've been burned by this before — added a library to a production project, found out later the stars were bought. Now I paste the repo README + last 10 commits into Claude and ask: "You are a skeptical senior engineer. Evaluate this tool: is it production-ready? Check for: maintenance activity, contributor diversity, open critical issues, and any signs of artificial hype. Give me a risk rating: Low / Medium / High, and one-line reason." Honestly takes 2 minutes. Saved me from shipping something embarrassing last month. #AIForDevs

• 
  dodothebird (@dodothebird) reported 12 minutes ago

  - All my projects live in a monorepo. Maybe the workspace solution also works, but I'm going with the monorepo for now. - Using GitHub Pro. I created another account for working with Codex on the monorepo. - All tasks are in different projects on GitHub, mirroring sub-packages in the monorepo. - All PRs are created by Codex on the monorepo. - After PR creation, the agent starts a PR Steward automation to check the state of the PR for code reviews from Codex, CI errors, etc. The automation runs until Codex review gives 👍 - After that, the automation stops. - I check the PR myself. If everything is OK, I approve the PR with my own user. I think I'm in a good place now. Things could be better with more cloud-based code review and PR cleaning processes, but I think I can manage with this for my personal work.

• 
  Heinz Holzer (@H1Holzer) reported 17 minutes ago

  @milesdeutscher Are you using a standalone .exe version of TradingView Desktop? Or is there a Windows-specific workaround? GitHub Issue #14 seems unresolved. Would love to know how you got it running! Thanks! 🙏

• 
  Vince 🐦‍ (@odtvince) reported 18 minutes ago

  @sethrose @GitHubCopilot @github "real advantages with GitHub integration.” Really? Maybe it’s a skills issue—I’m more used to CC and Codex—but I was genuinely surprised this morning: a Copilot Pro Agent Session started reviewing a PR… then couldn’t post the review. “I can’t post it directly from here” it said.

• 
  AI Mastery Guide (@aiseomastery) reported 19 minutes ago

  DEVELOPER BUILDS AI BOT THAT CLOSED 4000 GITHUB ISSUES IN ONE DAY The tool runs 50 AI models in parallel to automatically scan and close irrelevant issues and pull requests.

• 
  Garry Tan (@garrytan) reported 24 minutes ago

  I will admit it's down on Github because now many of my PRs begin on OpenClaw

• 
  Marlow (@marlowxbt) reported 25 minutes ago

  A 13 year old in China sold his first Python script for $40 on GitHub. The buyer was his own CS teacher. He didn't find out until the first day of school when the teacher showed it on the projector as an example of professional AI development. The kid was sitting in the third row. He spent his entire winter break building it instead of playing with his friends. Two weeks of asking Claude questions every night after his parents went to sleep. When the $40 came in he spent it all on V Bucks the same day. Didn't even think about it. Just bought a Fortnite skin and went back to coding. Pushed it to GitHub with a README in broken English that said: ai agent that does homework and finds answers from any website. Watched it sit at zero stars, closed his laptop and went to dinner. GitHub Sponsors doesn't show the buyer's real name. Just a username he'd never seen before. He didn't care. The $40 was already gone on a virtual outfit for a character he plays 2 hours a day. Then February came. First class back. The CS teacher opened with a presentation about AI agents, showed a demo on the projector. A Python script that scans websites, pulls data, summarizes it with Claude and sends structured reports automatically. The kid recognized everything. The variable names, the file structure, the comments he left in Chinese because he was too lazy to translate them. His teacher was presenting his code to 40 students as an example of what a professional developer can build. The teacher said: I found this tool online and it changed how I prepare my lessons. It pulls information from 30 sources in 3 seconds. Used to take me two hours every evening. The kid didn't say anything. Went home and checked the fork count. 847. Someone at a university in Beijing had forked it and was using it to grade 200 student papers overnight. A tutor in Shanghai forked it and built a homework checking service charging parents $15 per month. A small company in Hangzhou forked it and turned it into a customer support bot for an online store. All from a script a 13 year old built over winter break because he was bored and Claude helped him write the code. The $40 he earned from it is now a Fortnite skin. The code he wrote for it is now running in three countries. His teacher still uses it every day and still doesn't know who wrote it. The kid never told him. He said it would be weird to tell your teacher that the tool he shows off to every class was written by someone who sits in his class and still gets B minus on the coding assignments. He gets B minus because he writes his own code in class. The A plus code he writes at home with Claude, that's the code his teacher bought for $40 and presents as professional work. 847 forks. One $40 sale spent on V Bucks. One teacher who bought his own student's script without knowing it. One kid who can't tell anyone because it would be the most awkward parent-teacher meeting in history. He's 13. The teacher gives him a B minus. The script gets an A plus from everyone who uses it. Same kid, same code, different grades depending on who's looking.

• 
  Hiç mutlu olamayan birisi (@cehennem_dunya1) reported 29 minutes ago

  @NearestCommit They spent countless hours, fought with linuxtard developers because their preference is different and Linux devs only include their preferred way in their programs, and finally after hours and hours of GitHub scrolling he customized his os, which will break and cause problems a few months later.

• 
  Somi AI (@somi_ai) reported 30 minutes ago

  steipete shipped clawsweeper. 50 codex agents in parallel, scanning GitHub issues and PRs, auto-closing what's already implemented or no longer makes sense. 4000 closed in a single day. The number being celebrated is the wrong number. Closed-count is cheap. The metric that matters is reopen rate. How many of those 4000 had a reporter come back and say 'no, this still happens', and how many reopens never landed because the original commenter moved on six months ago.

• 
  vik (@vikhyatk) reported 34 minutes ago

  i was not impacted by the github issue, because i don't even know what a merge queue is. i just push everything straight to main.