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:

• 
  Angelica Parente (@draparente) reported 3 minutes ago

  Can we please do something about this @bcherny @trq212 @AnthropicAI ? This screenshot is a small subset of the total number of permissions requests I have to control. The github issues for this have been closed/reported as duplicates. This seems like a pretty large security risk, a bad actor could take advantage of people getting used to accepting *extremely opaque* full disk access requests.

• 
  Sai (@saidotdev) reported 4 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  Harshit Mathur (@spiderboyis) reported 6 minutes ago

  engineers talk endlessly about "technical debt," but nobody talks about the massive pile of "information debt" we accumulate every single week. ​we read deep research papers, bookmark obscure github repos, save architecture threads, and screenshot error fixes. we hoard data under the illusion that saving it equals learning it. ​three months later, when you actually need that exact solution, you spend 45 minutes trying to remember which app, chat, or folder you stashed it in. ​storage has become virtually free, but human context retrieval is more expensive than ever. the future of software isn't about capturing more data it's about zero-friction recall. ​how do you currently keep track of technical insights you know you’ll need months from now?

• 
  Suhail Roushan (@0xsuhailroushan) reported 10 minutes ago

  cursor looked at github's outage and said “interesting” then built github

• 
  Isaac Way (@isaac_ts_way) reported 11 minutes ago

  @jamonholmgren this can be avoided consistently without reading all the code consistently. It is not hard to put codex CLI in a github action and have it open change requests to prevent this type of code from ever getting merged, with 0 human involvement you do have to read code sometimes to know what is being missed by AI review but parallel AI review can continually be updated to prevent each newly noticed class of slop, and over time it’s possible to prevent all forms of common slop. Maybe not all of the slop, but 99% of it. And if that 1% isn’t going to explode the app, the trade off is not even close. Because the difference between “read all code” and “only read certain things that are important” is like a 50x difference in “developer time spent to feature added” ratio Personally I feel better about our codebase now than before AI, because now we have 9 parallel review agents that each look for different specific things that I care about a lot that cause long term maintainability issues over time, and we just keep adding new review agents as we think of new rules that make the code base better. Before AI it was actually *harder* to prevent bad code from making it into the codebase, because training people on 80 different things that can’t be caught by linters is not viable. But with AI running codex latest model, I rest easier knowing there is a check that will consistently make sure that no one writes code with any of the specific antipatterns I’ve seen over the years the generated code actually improves over time as new review agents are added, as long as people take the time to notice what is being generated, and are capable of codifying each rule into a prompt

• 
  nealjan (@NealjanNealjan) reported 11 minutes ago

  @GCNDiscs_ @108r5meme quest one? either way, i had the same issue (quest one, its a nightmare) you can actually get like a fix on github that uninstalls most of the weird meta thingy and launches you right into the steam vr app, which made my performance like 30-50% better

• 
  Jeetendra (@jeetendrayd) reported 14 minutes ago

  @RhysSullivan This was the reason the GitHub server was down, as more code is being pushed due to coding agents

• 
  Nathan Clark (@nathanclark_) reported 15 minutes ago

  As promised, here are some early thoughts on @bot Positives: Three-column setup It is nicely done, and the persistent computer screen preview is oddly satisfying and somehow signals/invites me to do work I know will require a workspace. Just visualising it is a smart UI/UX decision. Multiple accounts per connector!! And executed very well except in a small set of issues (see negatives below) Inline chat cards for auth, account setup, user question tool all very slick. It’s clear the system prompt encourages proactivity. This is definitely a net positive - just not something I personally want OOTB (I want to know its output quality, behaviour, defaults etc before it goes off as majority of my work ends up being a client deliverable that needs my oversight/contribution/refinement etc) Default communication style is clear and without too much puffery. Also good at telling me what isn’t yet done eg. “I have not put them in Notion yet.” Decently fast - though this is more a Grok 4.6 thing than a unique Bot thing. Having the Cursor plugin ecosystem available from day one means extremely high utility very quickly. You can Pin bots and create sections in the sidebar. Like Codex with threads/chats, one Bot can send prompts into others - great for an assistant/orchestrator style Bot - and the UI makes it very clear on both sides when it happens eg. “Message from [Bot]” You can create Routines in chat Channels is a really nice concept. Haven’t fully pulled on this idea yet but on face value I like it and already have some ideas. Negatives: Plugins that use an access token leave a “needs authentication” flag in the settings because you never complete an auth flow. You can’t add two github accounts - only auth option is via PAT (annoying), and while the UI presents the option to add another account it also only presents a single entry for “Setup Values”. I'd like more ability to set permissions and guardrails in a deterministic and obvious way - what can read, write and where. As it stands I’m not fully confident I can dial in with trust what the Bots can and can’t do. Skills and connectors mixed into the one place as “Plugins” feels awkward and not the right model. When installing a plugin and then reinstalling it, I noticed it had kept the accounts. Don’t like this behaviour. Mobile app for iPhone is great, no iPad optimised app - and Grok Bot uniquely out of all major agentic tool companies is already the most primed for it. Please ship a great iPad app! Skills management is limited to its own directory. Makes sense but is annoying for me as someone who across harnesses. Non-issue for “normies” and not a problem for anyone if they are all-in (for now I have a one-way sync from my .agents/skill directory into Private “plugins”) Pinned Bots take up too much space by default, at a relatively thin sidebar width I should still be able to have three across. I can’t manually order Bots inside a section.

• 
  Unique (@uniquewithsauce) reported 18 minutes ago

  @kobixyzHQ @RialoHQ Do I need to sign in with my Github in the Agent Grand Prix homepage?

• 
  Polsia (@polsia) reported 18 minutes ago

  Hygiene is a system problem, not a willpower problem. Built Dustloop to prove it — an AI agent living in your GitHub, triaging issues, sweeping stale PRs, enforcing CI before anything hits main, and posting a daily digest so nothing rots in the backlog. Live soon.

• 
  ven (@anyframeisgood) reported 22 minutes ago

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

• 
  Granite (@Granite0x) reported 22 minutes ago

  🚨 THIS IS ABSOLUTELY INSANE a developer just released a free tool that builds a vertical video with a talking presenter. out of one script and one photo. it's called lanshu-create-ai-presenter-video. it landed on GitHub two days ago. 267 stars. MIT. here's how it works: 1. You give it a script and a presenter photo you have the rights to. 2. The AI writes and voices the narration, generates the presenter, and locks the lips to the audio. 3. The skill edits, burns in subtitles and a cover, checks the sync, and hands back a master with a QA report. 9:16, 1080x1920, 30fps, 45-75 seconds. all of it happens in one run, on your own machine. save this before you sit down to cut your next video. i left the link in the next comment 👇

• 
  Rishabh (@crashedrishabh) reported 23 minutes ago

  Day 21 Shipped the full download backend. Users never see a GitHub link. Everything on free tiers. Serving a 108 MB installer without egress costs or serverless timeouts. That's the problem. Stack: • Next.js 14 + Bun + TypeScript • Neon Postgres + Prisma 7 • Cloudflare R2 (free egress) + Workers (edge delivery) • GitHub Releases API as source of truth Flow: sync script polls releases → upserts metadata into Postgres → installer streams from R2 via Worker → download starts directly. No 302 to GitHub. Why not proxy through Next.js? 108 MB through a serverless function = timeout risk + bandwidth bill. R2 egress is $0. Workers free up to 100k req/day. Also: AtCoder ABC 472. Solved A–E. E was a banger. @atcoder #buildinpublic @Cloudflare @nextjs

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 23 minutes ago

  A GitHub outage just delayed the launch of a GitHub competitor. You can't script this. Cursor was set to ship Origin, its own code hosting platform. GitHub went dark for 6.5 hours that same day. Millions of devs sat frozen. Then Origin went live. → Your code, your changes, and your AI agent in ONE window → Two-way sync with GitHub. Change either side, both update. → Agents live in every repo. Ask questions. It pushes fixes. → Connect Vercel and every change gets a live preview link You don't have to pick sides. GitHub stays the boss. Origin is the seat belt. When your code host goes dark, a second home stops being nice-to-have. Save this. You'll want it later.

• 
  RagerYT (@RagerrrYT) reported 24 minutes ago

  🚨JACK DORSEY JUST KILLED THE TRADITIONAL BUSINESS MODEL Free framework to run an entire company with AI agents, already at 29,000 GitHub stars Setup in 5 minutes 👇 >Clone the repository >Deploy your own server with channels, search, *** and automations >Add your agent to a channel like a team member, define its permissions and let it collaborate in real time >An AI coworker that operates 24/7 without salary, without breaks and without forgetting context Save this one